One record,
understood in layers.
The Integrated Health Interoperable Platform runs as three connected layers — capture, institution and individual — over one patient identity and one terminology substrate.
Records are made in ninety seconds,
or they are not made.
Every architectural decision downstream exists to protect the capture path. If coding is slower than the pad, nothing else in this document matters.
The capture path issues no network request. The terminology index is resident on the device and ranked by the clinician's own history.
No validation, alert or sync condition may prevent a consultation being finished and a prescription printed. Advisories are inline and dismissible.
The clinician's verbatim entry is stored alongside the bound concept — the only recoverable ground truth when a mapping is later found wrong.
FHIR assembly and ABDM linkage happen after the encounter closes and the patient has left, never in the path between the doctor and the printer.
Offline is the normal case,
not the fallback.
Specified as an offline application that opportunistically synchronises. A clinic on a dead connection is not a degraded clinic; it is the design centre.
Thick, self-sufficient
Full capture, print and search with no network for a rolling 72 hours.
Append-only events
Idempotent by client-generated identifier. Replay is safe and expected.
Union, never merge
Two devices adding to one encounter union. Duplicate patients are never merged automatically.
Never user-facing
An ABDM outage is queued, retried and reported to operations — not to the clinic.
A record that outlives
the software that wrote it.
Every coded entry carries the code system, the version in force at the time, the author's registry identifier and the device it came from. Amendment creates a version.
Code, system URI, and the code-system version in force at entry — permanently distinguishable from a later revision.
Exactly what the clinician typed or said, retained on every entry including coded ones.
Author, HPR identifier, device, timestamp, input mode and index version.
Duration, severity, laterality, dose, frequency — structured, and always optional.
Append-only. Correction supersedes; nothing is overwritten and nothing is hard-deleted.
Built for software that lives
next to patient care.
Nothing blocks
No validation, no gate and no sync failure may stop a clinician finishing a consultation. Incompleteness is recorded, never enforced.
Coding is a by-product
If a clinician performs an action whose only beneficiary is the data model, the design has failed.
Offline is the normal case
Specified as an offline application that opportunistically syncs — not an online one with a fallback.
Compliance is invisible
Registry onboarding, consent and linkage are done on the clinic's behalf. Nobody is sent to a portal.
Put the platform to work on your cases.
Anchor clinics get early capability and a real say in what gets built next.