Healthcare Software Development

Healthcare software in India is different from healthcare software anywhere else. The difference is not the medicine. The identity system is national, consent is now required by law, and the money a clinic makes depends on a number most software does not even measure.

ABDM and ABHA: identity you do not own

The Ayushman Bharat Digital Mission gives a patient an ABHA number — a health identity that the patient can carry anywhere. It is theirs, not your hospital's. To link your records to it, your facility must register in the ABDM system and set up the Health Information Provider flows. It must also honour a consent request from a Health Information User you have never heard of, correctly, on demand. Teams often underestimate this last part.

The mental shift is real. Your patient record is no longer a row in your database that you control. It is a record the patient can let a different hospital see, for a set purpose and a set time, and then take back. Software written on the idea that the hospital owns the data cannot be fixed to fit this cleanly. We build consent as a core part of the system from the first sprint. Every time clinical data is read, it is checked against a live consent, not against a role.

The DPDP Act made consent a legal artefact, not a checkbox

Under the Digital Personal Data Protection Act, health data is sensitive. Consent must be specific, informed and easy to take back. You must be able to prove, not just claim, what a patient agreed to and when. A checkbox in a form, with no record of what the notice said when it was ticked, does not do that.

So we keep each version of the consent notice. We store the exact text the patient was shown with the consent, add the time, and record the purpose. When a patient takes consent back, we really cut access, not just set a flag. We log every access to sensitive data in an audit trail that only grows, which an engineer cannot quietly edit. The data layer allows data to be used only for the stated purpose. This is more work. It is also the difference between a compliance story and a compliance claim.

No-shows are the number that decides whether a clinic is profitable

A specialist consultation slot that goes unfilled is money that cannot be recovered, because the hour is gone. Indian outpatient no-show rates are commonly between 20 and 30 percent. Most hospital software does not measure it at all, let alone act on it.

What actually works, in the order it works: a WhatsApp reminder 24 hours before, with a one-tap confirm or reschedule, because SMS is ignored and calls take too much time. A second nudge on the morning of the visit. A waitlist that offers a freed slot to the next patient as soon as a cancellation comes in. Booking with a deposit for the appointment types where no-shows are most common. And a risk score for each patient, based on their own history, so the front desk knows which slots to overbook. We have taken no-shows from 27 percent to 11 percent doing exactly this. Nothing on that list is clever. It is just measured, and then acted on.

HL7 v2 and FHIR, in the real world

Your radiology system speaks HL7 v2 with pipes and carets, because it was installed in 2016 and nobody is replacing it. ABDM speaks FHIR R4. The lab machine speaks something the vendor invented. We build a connecting layer that takes in all three, maps them to one standard internal model, and does not let the ugliest of the three decide the shape of your whole system. Every incoming message is saved raw before it is read, because the day a mapping is wrong you will want the original.