What is FHIR?
FHIR (Fast Healthcare Interoperability Resources) is an international standard developed by HL7 (Health Level Seven International) for exchanging healthcare information electronically. It defines how health data should be structured, represented, and transmitted — enabling different systems to understand each other's data.
Think of FHIR as the universal language of healthcare IT. Just as JSON is the standard format for web APIs, FHIR is the standard format for health data APIs. ABDM mandates FHIR R4 (Release 4) for all health record exchanges in India's digital health ecosystem.
Why Did India Choose FHIR for ABDM?
The National Health Authority chose FHIR R4 because it is:
- Globally adopted: Used by the US, UK, Australia, and 30+ countries for national health systems
- REST-based: Familiar to modern developers — standard HTTP methods, JSON/XML payloads
- Extensible: Can be profiled to meet India-specific requirements
- Mature: FHIR R4 (2019) is the normative standard with extensive tooling and libraries
- Interoperable: Enables data exchange across diverse health systems without custom mappings
Key FHIR Resources Used in ABDM
FHIR organises health data into Resources — individual, modular data objects. Key FHIR resources used in ABDM include:
| FHIR Resource | Used For |
|---|---|
| Patient | Patient demographics linked to ABHA |
| Practitioner | Doctor / healthcare provider details |
| Organization | Hospital / facility information |
| Condition | Diagnoses and clinical conditions |
| Observation | Vitals, lab values, clinical findings |
| MedicationRequest | Prescriptions and drug orders |
| DiagnosticReport | Lab reports and pathology results |
| ImagingStudy | Radiology / DICOM imaging reports |
| Encounter | Patient visits / care episodes |
| Composition | Discharge summaries, clinical documents |
| Bundle | Container for multiple FHIR resources |
ABDM FHIR Profiles
NHA has defined India-specific FHIR profiles (Implementation Guides) that extend base FHIR R4 with Indian healthcare requirements. These profiles specify:
- Mandatory fields for Indian patient records
- Use of SNOMED CT, ICD-10, and LOINC coding systems
- ABHA number as a patient identifier
- Required extensions for Indian healthcare context
All FHIR bundles shared via ABDM must conform to these NHA profiles — not just base FHIR R4.
FHIR Bundle Types in ABDM
ABDM supports several document types as FHIR bundles:
- Prescription: MedicationRequest + Condition + Practitioner
- Diagnostic Report (Lab): DiagnosticReport + Observation + Specimen
- Diagnostic Report (Radiology): ImagingStudy + DiagnosticReport
- Discharge Summary: Composition + Encounter + Condition + Procedure
- OP Consultation: Encounter + Condition + Observation + MedicationRequest
- Immunization Record: Immunization + Patient
- Wellness Record: Observation (vitals, BMI, etc.)
Tools and Libraries for FHIR Development
- HAPI FHIR (Java): Most popular open-source FHIR server and client library
- Microsoft FHIR SDK (.NET): Azure Health Data Services FHIR tools
- Python fhirclient: Lightweight Python library for FHIR R4
- FHIR.js: JavaScript FHIR client library
- Smile CDR: Enterprise FHIR server
Conclusion
FHIR is not optional for ABDM integration — it is mandatory. Every health record shared through the ABDM ecosystem must be structured as a FHIR R4 bundle conforming to NHA's India-specific profiles. Building FHIR expertise is a prerequisite for any healthcare platform aiming to be ABDM-compliant.
Medi4u has deep expertise in FHIR R4 implementation and NHA profile compliance. We build FHIR-compliant APIs, validate bundles against NHA specifications, and support sandbox testing and NHA certification. Contact us to learn how we can help your platform meet FHIR requirements for ABDM.
