Platform · Architecture
How the layers fit
For technical evaluators. Layer by layer, with the reason for each choice rather than only the choice.
Layers
Identity, exchange, meaning, storage
Application architecture
Six decisions
| Layer | Approach | Why |
|---|---|---|
| Web | Responsive application against a FHIR API | One codebase, evaluator-friendly |
| Mobile | Offline-capable client with local store and background sync | Field connectivity is intermittent by default |
| Backend | FHIR R4 resource server with programme-specific services | Standards conformance at the boundary, flexibility inside |
| Data | India-resident, encrypted at rest, multi-tenant with export | Residency, and the ability for a provider to leave |
| AI layer | Assistive suggestion with attribution and dismissal | The human decides; the suggestion is auditable |
| Integration | ABDM, laboratory analysers, DICOM, messaging | The record is only useful if it connects |
Security
Five layers
Book a technical walkthrough.
With the people who wrote the specification.