How we handle a hospital's data.
A hospital or clinic that hands us a project is trusting us with patient-adjacent data and internal operations, not just a feature request. These are the commitments that shape every project we take on, not just the ones we get asked about.
Data stays where you put it
Most systems we build run inside the client's own environment. We do not keep a working copy of production data after a project wraps up, and we never move a client's data anywhere they have not approved.
Role-based access by default
Every system ships with permissions scoped to what each role actually needs to see and do. That is designed in from the first commit, not something we bolt on when someone asks.
Confidentiality is the default
The case studies on this site only show what a client has agreed we can share: a description, a screenshot, sometimes a live link. Where that agreement does not cover something, it stays undiscussed, whoever asks.
Source code and access transfer at handover
When a project wraps up, you get the codebase, the deployment access, and the documentation needed to run it without us. Holding a system hostage to keep a client is not how we operate.
Designed around Indonesia's UU PDP
Data minimization, purpose limitation, and clear consent flows shape how a system is architected from the discovery stage, in line with Indonesia's personal data protection law, not retrofitted after a client raises it.
What hospitals usually ask first.
Can we see the code or architecture before signing anything?
Yes. During discovery we walk through the architecture of a comparable project and, where confidentiality allows, a sample of the codebase, so you know what you are approving before you approve it.
Do you sign NDAs?
Yes, as standard practice for any engagement that touches real patient or organizational data. If your legal team has a preferred template, we work from that.
What happens if something breaks after launch?
You reach Aden directly, not a ticket queue. He leads every project personally, so there is no handoff between the person who understands the code and the person who answers the phone.
Who actually owns the system once it is built?
You do. Source code, infrastructure access, and documentation transfer to your team at handover, and we are available afterward by agreement, not by default lock-in.
Are you a registered company, or an individual practice?
Right now Haicare operates as Aden Kesuma's individual practice, not under a separate registered legal entity, with trusted collaborators brought in for specific projects. Contracts, invoices, and NDAs are issued directly in his name. If your procurement process requires a registered company, tell us during the first conversation so we can work out whether that is a blocker before either side invests time in a proposal.
Have a question specific to your organization's compliance requirements? Bring it up on the first call. Ask us directly.
Let's build something
healthcare can rely on.
Tell us about your hospital, clinic, or health product. We reply personally, usually within a day, and the first conversation is about your workflow, not a sales pitch.
Based in Medan, Indonesia. We work with hospitals and medical organizations across the country, remotely and on site.