Eleven modules · one clinical record · See all
The capture layer

The health ID is built.
The consulting room is the gap.

India has issued crores of digital health identities. Most clinics a patient walks into still cannot accept one — because no software has ever been faster than the paper pad it was asking them to give up.

Every clinical entry is coded at the point of writing, by the clinician who wrote it.

Sunita Devi · last visit 12 Mar
1Fever · 4 daysSNOMED 386661006
33Dengue feverICD-10 A90 · differential
4Paracetamol 650 · TDS · 3dATC N02BE01
2CBC panelLOINC 58410-2

1 complaint · 2 test · 3 diagnosis · 4 medicine

Standards & complianceSNOMED CT·LOINC·ICD-10/11·ATC·HL7 FHIR·ABHA·DPDP
The bottleneck

The rails are built.
The desk is the constraint.

A national identity layer exists and works. What is missing sits three feet from the patient: software that survives contact with a ninety-second consultation.

~95Crdigital health identities issued nationally
~12lakhclinics across India
~2.7lakhwith software able to use one

Storage is commoditising. The ninety seconds in the consulting room is the durable, defensible layer.

Figures are public national totals, rounded. Clinic counts in India are estimates rather than a census; the registry-based figure is the conservative one.

The engine

Four numbers.
No coding dialog.

Every clinical system that codes to SNOMED asks the clinician to walk a hierarchy. The Attribute Box inverts it: the clinician types what they were going to write anyway, and the binding happens underneath.

what the clinician seeswhat is stored ↓
InterfaceThe Attribute Box

One control. First character selects the domain. No dialog, no hierarchy, no second screen.

ParserKey grammar

Domain key, query, and a shorthand for dose and frequency written the way prescriptions already are.

IndexOn-device terminology

Ranked by this clinician's own history. Served locally — the capture path makes no network call.

BindingConcept resolution

SNOMED, LOINC, ICD and ATC bound at entry, with the original words kept verbatim alongside.

ExchangeFHIR R4 bundle

Assembled after the encounter closes, never in the path between the doctor and the printer.

Coding is a by-product,
never a task.

  • 1 complaint · 2 test · 3 diagnosis · 33 differential · 4 medicine
  • Nothing blocks. An encounter with one medicine and no diagnosis closes without complaint.
  • Original words are kept. What the clinician actually wrote survives alongside the code, permanently.
  • No network in the capture path. Verified by packet capture, not by assertion.

How the Attribute Box works →

Principles

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.

Trust

Clinical data outlives
the software that made it.

A prescription written today may be read in twenty years by a clinician who has never heard of us. That constrains the architecture more than any feature request.

Residency

India

Stored in India on empanelled infrastructure, with staff access limited to role.

Consent

Granular

Care, linkage and messaging are separate consents. Refusing any of them does not degrade care.

Ownership

The clinic's

We hold it on their behalf under a written agreement, with an exit provision.

Record

Append-only

Amendment creates a version. Nothing is overwritten, nothing is silently deleted.

Get started

Prove it in your own clinic.

Pilot clinics are partners, not customers. We set you up in person, then leave you alone for three weeks and come back to ask what broke.