US Core & India (NRCeS) profiles
Two national FHIR rulebooks side by side — what each mandates, and why the same patient record looks different in Boston and Bengaluru.
The answer in one paragraph
A national FHIR profile set answers one question: what must every system in this country agree on? US Core answers it for the United States — the profile baseline that federal regulation effectively mandates EHRs expose through patient-access APIs. NRCeS FHIR profiles answer it for India — built for ABDM's document-exchange architecture, where health information flows as signed FHIR documents through a consent manager. Same FHIR underneath; different national problems; instructively different rulebooks.
US Core in five lines
Maintained by HL7, anchored to the USCDI data-element list that US regulation references. It profiles the everyday resources (Patient, Condition, Observation, MedicationRequest…), mandates terminologies (LOINC, SNOMED CT, RxNorm), and pins "must-support" elements — if a system records it, the API must expose it. Its pairing with SMART on FHIR is what made "connect any app to any US EHR" real. If you integrate in the US, US Core conformance is the entry ticket.
NRCeS profiles in five lines
Published by NRCeS (C-DAC Pune) for ABDM. The center of gravity is the document Bundle: profiles define clinical artefacts — DiagnosticReport records, Discharge Summary, Prescription, OP Consult Note, Immunization records, Wellness records — each a composition carrying its sections, exchanged HIP→HIU under HIE-CM consent and digital signature. Terminology bindings lean on SNOMED CT (free in India via NRCeS) and LOINC; identifiers anchor to ABHA. If you build for ABDM, these profiles plus the consent flow are the entry ticket.
The instructive difference
| US Core | NRCeS / ABDM | |
|---|---|---|
| Unit of exchange | Individual resources via REST API queries | Signed document Bundles via gateway |
| Driving force | Regulation (info-blocking rules, patient access) | National mission architecture (ABDM) |
| Identity anchor | No single national ID; matching is hard | ABHA number/address by design |
| Consent | App-level OAuth scopes (SMART) | Dedicated consent manager (HIE-CM) |
| Terminology spine | LOINC + SNOMED + RxNorm | SNOMED + LOINC, India extension |
The deeper lesson for any country-pack thinker: profiles encode policy. Reading a nation's IG tells you how its health system wants data to move — which is why this platform treats country content as overlays over one global core, never forks.
Where to go next
SMART on FHIR & app launch — the authorization layer that turns these profiled APIs into an app ecosystem.