Submitted:
23 June 2026
Posted:
24 June 2026
You are already at the latest version
Abstract
Keywords:
1. Introduction
2. Methods
2.1. Study Design
2.2. Desk Research and Practitioner Insights
2.3. Stakeholder Survey
2.4. Key Informant Interviews
2.5. Field Validation
2.6. International Benchmarking
2.7. Synthesis Process
2.8. Ethics
3. Results
3.1. National Policy and Implementation Landscape
3.2. Technical Alignment with Global FHIR Cores
3.3. Participant Details
3.4. Key Bottlenecks to FHIR Adoption
3.4.1. Field Validation of Key Bottlenecks to FHIR Adoption
3.5. Triangulated Maturity Assessment from the Synthesis
3.6. International Benchmarking
3.7. Strategic Priorities and National Roadmap
4. Discussion
4.1. Principal Findings
4.2. Interpretation
4.3. A Comparison with Mature FHIR Ecosystems
4.4. Policy and Implementation Implications
4.5. Strengths and Limitations
5. Conclusions
Author Contributions
Funding
Institutional Review Board Statement
Data Availability Statement
Acknowledgments
Conflicts of Interest
Appendix A: Stakeholder Ecosystem Overview
| Domain / Actor | Example Implementations | FHIR Alignment / Resources | Observations |
| National Programs | ABDM (HIE-CM), NHCX, eSanjeevani | NRCeS IG (FHIR R4); ABDM Sandbox; HCX IGs | Centralised frameworks; adoption primarily compliance-led; limited community feedback loops. |
| State Health Missions | Kerala eHealth, Andhra Pradesh HADP, Punjab iHMS | FHIR R4; ABDM Sandbox APIs | Early experimentation; constrained by top-down governance and limited autonomy for localisation. |
| Private Hospitals & Chains | Apollo, Manipal, Max Healthcare | Internal FHIR APIs for ABDM linkage | Integration centred on ABHA and Consent; little internal interoperability or analytics reuse. |
| Diagnostics & Lab Networks | SRL, Metropolis, Thyrocare | Observation, DiagnosticReport | Early maturity; value clearer where structured results improve efficiency. |
| Insurance & TPAs | MediAssist, Raksha, Star Health, ICICI Lombard | Claim, Coverage, ClaimResponse | Alignment emerging under NHCX; readiness linked to validator availability and policy rollout. |
| Digital Start-ups & PHR Vendors | HealthPlix, Practo, ekacare, 1mg | MedicationRequest, Patient, DocumentReference | FHIR integral to product architecture; need clearer conformance guidance and validation tools. |
| ABDM Adaptors / Middleware | Driefcase, Healthelife | Plug-and-play ABDM connectors | Important bridge for small providers; could accelerate ecosystem participation once certification stabilises. |
Appendix B: Comparative Table: India Pilots vs. Global Deployments
| Domain / Use Case | India (Status) | Global Benchmarks | Alignment / Divergence | Implications for India |
| ePrescription Exchange | ABDM-linked apps (EkaCare, DRiefcase) in production, but uneven coverage | Australia: National ePrescription Service (AMT-coded, scaled); US: US Core MedicationRequest + RxNorm pilots | India missing RxNorm/AMT; coverage uneven | ⚠ Strong national pilots but weak drug terminology → needs terminology upgrade to scale |
| Lab Result Sharing | Pilots with Thyrocare, SRL; ABDM “Scan & Share” program in production | US: US Core DiagnosticReport nationwide; AU: Pathology FHIR IG live | NRCeS DiagnosticReportRecord close to global | ✅ Good alignment; ⚠ India needs wider rollout beyond metros |
| Claims Exchange | NHCX sandboxand early pilots | US: CARIN Blue Button IGs; AU: Private insurance FHIR pilots | India profiles divergent from CARIN/AMT | ⚠ Governance critical to avoid fragmentation; India could harmonize with CARIN where feasible |
| PHR / Consumer Access | ABDM-linked PHR apps (HealthPlix, Tata Health) live | US: TEFCA Roadmap; Israel: patient access guaranteed via FHIR | India’s approach strong but fragmented by vendor | ✅ Ahead of many LMICs; ⚠ Needs uniform UX and cross-vendor portability |
| Discharge Summaries | Some hospitals piloting ABDM FHIR records | AU: National eDischarge FHIR profiles; US: CCD on FHIR | India more prescriptive, aligned in intent | ⚠ Could harmonize with AU CCD-lite for simplicity |
| State-level Exchange | Kerala DHIS2–FHIR bridge pilot | Singapore: Healthier SG programnational exchange; Israel: National HIE | India still state-by-state | ⚠ Lagging in state-wide rollout; opportunity to replicate SG model |
Appendix C: Descriptions and Implications of Bottlenecks by Domain
| Domain 1: Ecosystem and Institutional Bottlenecks | ||
| Challenge | Description | Implications |
| 1. Low Digital Footprint | India’s healthcare ecosystem continues to rely heavily on paper-based workflows, particularly across primary and secondary care. While larger hospitals are adopting digital systems, clinical data remains fragmented, inconsistently structured, and rarely coded using standardized terminologies. The absence of robust, longitudinal EHR systems severely limits interoperability and reuse of clinical information across institutions [3]. | ⚠ Limited interoperability and poor data liquidity; FHIR adoption remains confined to digitally mature providers until broader digitization occurs. |
| 2. Lack of Incentives | Survey and interview feedback consistently identified the absence of clear business or operational incentives as the single biggest barrier to adoption. Implementers consistently ask: “Why should we adopt FHIR?” Compliance may be mandatory for ABDM, but without funding, policy push, or demonstrable business benefits, most vendors and providers perceive no ROI [20]. | ⚠ FHIR adoption remains shallow and compliance-driven; limited motivation for sustained ecosystem investment. |
| 3. Procurement Misalignment | Government and public-sector procurement guidelines rarely mandate interoperability standards such as FHIR. Contracts typically emphasize feature delivery rather than open-standards conformance, providing no incentive for vendors to embed FHIR capabilities proactively. | ⚠ Vendors under-invest in standards and interoperability; proprietary solutions persist and fragment the market. |
| 4. Resistance to Change | Many implementers perceive HL7 FHIR primarily as an “ABDM-only” compliance requirement. This narrow view obscures its global, vendor-neutral potential for product scalability, process efficiency, and research use. The result: FHIR ≈ ABDM rather than FHIR as a universal interoperability language. | ⚠ Narrow perception undermines ecosystem-wide investment and learning; slows organic innovation. |
| 5. Restricted Autonomy | FHIR’s open, consensus-driven model depends on continuous feedback loops, implementer participation, and iteration. In contrast, India’s current framework—designed for rapid nationwide rollout—operates as a prescriptive, closed specification. This prioritizes uniformity over iterative standardization. When Implementation Guides are seen as fixed compliance checklists rather than living documents, implementers lose ownership and motivation to improve them. | ⚠ Ecosystem prioritizes procedural compliance over meaningful interoperability; widens maturity gap and discourages innovation. |
| 6. Fragmented and Rigid Governance | Governance around digital-health standards in India remains both fragmented and over-centralized. Multiple agencies (NRCeS, NHA, MeitY, and state health departments) operate with overlapping mandates and limited coordination, while decision-making and profile stewardship follow a uniform, top-down model. Several interviewees described the current process as highly centralised, with limited visibility into how feedback from implementers is incorporated into evolving specifications. This combination results in fragmented accountability but rigid execution—a difficult balance for an ecosystem as diverse as India’s. Stakeholders observed that the current top-down rollout model also spreads limited institutional capacity across too many fronts, stretching governance and implementation bandwidth thin. A more focused approach—where national agencies concentrate on a small number of strategic, public-sector use cases to demonstrate value—could strengthen coherence, build confidence, and lead by example. Ideally, national authorities could focus on a few high-impact areas (for instance, public-sector entities or primary-care screening programs) to showcase success while allowing the broader ecosystem to innovate around other use cases through iterative, community-driven experimentation. |
⚠ Constraints on flexibility and prioritization; uneven adoption across sectors; missed opportunities for iterative, evidence-based scaling. |
| Domain 2: Technical Bottlenecks | ||
| 7. Legacy HIS and Structural Mismatch | Most hospital and laboratory systems store data in relational or unstructured formats. Mapping these to FHIR’s hierarchical, resource-linked model requires complex ETL pipelines and domain expertise. Legacy applications often lack coded terminologies, producing free-text results that resist automated transformation. | ⚠ High conversion cost and data-loss risk; limits scalability of FHIR integration, especially for small providers with minimal IT capacity. |
| 8. Profile Divergence and Document-Centric Exchange | NRCeS profiles (v 6.5.0) diverge from US Core and AU Core. India’s record-type compositions (e.g., DischargeSummaryRecord, OPConsultRecord) enforce uniformity but favor document bundles over granular transactions. This restricts real-time clinical updates for specialties like oncology or radiology and complicates modular reuse. | ⚠ Limited support for incremental updates or specialty workflows; constrains ecosystem to “upload once” document flows instead of dynamic interoperability. |
| 9. Proprietary or Non-FHIR Constructs | National components extend beyond native FHIR semantics — for example, the MeitY Consent Artefact instead of FHIR Consent, custom JSON for Patient demographics , and omission of FHIR AuditEvent / Provenance resources or OAuth2/OIDC scopes in patient-facing apps [3]. | ⚠ Dual-layer compliance burden (FHIR + national artefacts ); weak alignment with global tooling; complicates participation of international vendors. |
| 10. Testing and Certification Oversight | ABDM certification primarily verifies connectivity (API availability, token flow) rather than data semantics. No public “India FHIR Compliance Suite” defines content-level validation. Developers depend on manual checks or ad-hoc scripts; the ABDM Sandbox lacks pre-loaded NRCeS packages and terminology services. | ⚠ Inconsistent payload quality; limited ability for self-validation; certification does not guarantee true interoperability. |
| 11. Limited Ecosystem for Tooling and Developer Support | There is a general absence of a structured ecosystem for tooling development and implementer enablement. Lack of SDKs, sample payload generators, example datasets, and community-maintained libraries forces developers to rebuild basic components from scratch. Documentation gaps and unstable APIs further limit collaborative learning or community-driven improvements. | ⚠ Steep learning curve and duplication of effort; discourages innovation among smaller vendors; slows ecosystem-wide maturity. |
| 12. Terminology Gaps and Mapping Issues | India partially employs SNOMED CT and LOINC but lacks mappings for drug vocabularies such as RxNorm or AMT [4]. Absence of a national terminology service impedes consistent code validation. | ⚠ Weak semantic interoperability; constrains analytics, claims processing, and cross-border data use. |
| 13. Version Management and Lifecycle Governance | No transparent release cadence or regression-testing framework exists for NRCeS IG updates. Implementers face uncertainty about version changes and downstream impact. | ⚠ Operational instability; recurring re-work and compliance drift. |
| 14. Infrastructure and Performance Constraints | Many providers operate with limited connectivity, outdated hardware, and constrained compute resources. FHIR’s verbose JSON increases payload size, further stressing low-bandwidth environments. | ⚠ Poor performance in rural or low-resource settings; limits real-time data exchange and scalability for large provider networks. |
| 15. Security and Privacy Implementation overhead | Technical adoption of FHIR Security labels, Provenance, and AuditEvent remains inconsistent. Smaller facilities lack secure hosting or audit tooling. Privacy compliance imposes extra cost with limited perceived benefit, creating an unfavorable risk–reward trade-off. | ⚠ Uneven privacy enforcement; potential trust deficit and exposure to data-handling risks. |
| Domain 3: Operational Challenges | ||
| Challenge | Description | Implications |
| 16. Fragmented Workflows and Ownership | In most health-care organizations, interoperability remains a parallel IT activity rather than an embedded operational function. FHIR implementations are frequently vendor-led, detached from clinical and administrative workflows. Responsibilities are distributed across IT, quality, and medical teams with no single accountable owner. Consequently, hospitals often “upload” or “share” data post-hoc instead of integrating data exchange within registration, consultation, discharge, or billing processes. | ⚠ Interoperability becomes a reporting task rather than a process-improvement tool; lack of clear ownership weakens accountability for data quality and long-term sustainability. |
| 17. Limited Workforce Capacity | Skilled FHIR developers, health-informatics experts, and implementation architects are scarce. Training programmes remain ad-hoc and focused on vendors rather than health-system staff. | ⚠ Dependence on a few expert vendors; constrains scaling and public-sector adoption. |
| 18. Absence of Sustainable Business Rationale | Many providers view FHIR compliance as a regulatory cost rather than an operational investment. There is limited linkage between interoperability and measurable returns such as faster claims settlement, reduced duplication, or improved patient retention [20]. | ⚠ Weak motivation for continuous maintenance; systems degrade once mandatory checks conclude. |
| 19. Weak Change-Management and Communication | Onboarding and capacity-building efforts emphasize technical API testing rather than redesigning workflows or communicating clinical and managerial benefits. | ⚠ Low staff buy-in; clinicians and administrators perceive FHIR as bureaucratic, not enabling. |
| 20. Fragmented Vendor Ecosystem | The market comprises hundreds of small HIS vendors with proprietary data models and limited coordination. Few share open libraries or testing environments aligned with NRCeS profiles. | ⚠ Duplicate effort, inconsistent conformance, and higher integration costs when providers change vendors. |
| 21. Innovation and Experimentation Constraints | Uniform compliance timelines and rigid certification checklists discourage experimentation with advanced FHIR-based applications such as decision-support, analytics, or patient-facing tools. | ⚠ Innovation limited to large vendors; ecosystem learning and adaptation remain slow. |
Appendix D: Field Insights on Bottlenecks
| Theme | Observation / Quote | Interpretation and Implications |
| 1. Lack of Incentives and Value Proposition | “FHIR is hard to implement—why should we take the trouble?” was the most common sentiment. Implementers described FHIR adoption as a cost centre with no measurable returns or policy rewards. | ⚠ FHIR is still perceived as a compliance burden, not a source of value. Unless linked to tangible outcomes—e.g., faster reimbursements, visibility on ABDM dashboards, or simplified onboarding—participation will remain superficial. |
| 2. Steep Learning Curve and Complexity | Many developers find FHIR “too abstract” or “too heavy” for real-world projects. Some acknowledged that they were unaware of HL7’s global training materials, connectathons, or open tooling communities. | ⚠ Indicates information asymmetry and weak knowledge pathways. ABDM-linked communication does not sufficiently expose implementers to the global FHIR ecosystem and its learning resources. |
| 3. Confusion Between FHIR and ABDM | When asked about FHIR, several implementers immediately spoke about ABDM APIs or gateway registration steps. Few differentiated between FHIR as a data-exchange standard and ABDM as a network architecture. | ⚠ The FHIR ≈ ABDM conflation reinforces a compliance mindset. Clearer messaging and education are needed to help implementers see FHIR as a globally reusable foundation, not just an ABDM requirement. |
| 4. Limited Support for Testing and Troubleshooting | Respondents repeatedly highlighted the lack of a public, trusted validator and conformance suite as a key reason for implementation hesitation. Issues often require bilateral vendor–NHA communication, slowing iteration. | ⚠ Highlights the need for a support ecosystem—peer forums, open validator tools, and shared implementation playbooks—to reduce friction and encourage collaboration. |
| 5. Uneven Capacity Across Market Segments | Large EMR vendors and diagnostic networks have dedicated integration teams, whereas smaller hospitals and startups struggle with both staffing and technical literacy. | ⚠ Without tier-specific enablement strategies, ecosystem maturity will remain uneven; small providers risk permanent exclusion from digital health networks. |
References
- Ayaz, M.; Pasha, M.F.; Alzahrani, M.Y.; Budiarto, R.; Stiawan, D. The Fast Health Interoperability Resources (FHIR) standard: systematic literature review of implementations, applications, challenges and opportunities. JMIR Med. Inform. 2021, 9(7), e21929. [Google Scholar] [CrossRef] [PubMed]
- Vorisek, C.N.; Lehne, M.; Klopfenstein, S.A.I.; Mayer, P.J.; Bartschke, A.; Haese, T.; et al. Fast Healthcare Interoperability Resources (FHIR) for interoperability in health research: systematic review. JMIR Med. Inf. 2022, 10(7), e35724. [Google Scholar] [CrossRef]
- Mission, Ayushman Bharat Digital. ABDM portal: national digital health ecosystem [Internet]; National Health Authority, Government of India: New Delhi, 2024; Available online: https://abdm.gov.in/ (accessed on 2025 Oct).
- National Resource Centre for EHR Standards. NRCeS FHIR Implementation Guide [Internet]. Ministry of Health and Family Welfare, Government of India: New Delhi, 2024; Available online: https://nrces.in/ndhm (accessed on 2025 Oct).
- Balch, J.A.; Ruppert, M.M.; Loftus, T.J.; Guan, Z.; Ren, Y.; Upchurch, G.R.; et al. Machine learning-enabled clinical information systems using Fast Healthcare Interoperability Resources data standards: scoping review. JMIR Med. Inf. 2023, 11, e48297. [Google Scholar]
- Ministry of Health and Family Welfare. Health dynamics of India (infrastructure and human resources) 2022-23 [Internet]; Central Bureau of Health Intelligence, Government of India: New Delhi, 2024; Available online: https://mohfw.gov.in/ (accessed on 2025 Oct).
- Karan, A.; Negandhi, H.; Hussain, S.; Zapata, T.; Mairembam, D.; De Graeve, H.; et al. Size, composition and distribution of health workforce in India: why, and where to invest? Hum. Resour. Health 2021, 19, 39. [Google Scholar] [CrossRef] [PubMed]
- Selvaraj, S.; Karan, A.K.; Srivastava, S.; Bhan, N.; Mukhopadhyay, I. India health system review; World Health Organization, Regional Office for South-East Asia: New Delhi, 2022. [Google Scholar]
- HL7 India. About HL7 India [Internet]. Available online: https://www.hl7india.co.in/ (accessed on 2025 Oct).
- Australian Digital Health Agency. National ePrescribing Service [Internet]. Australian Government: Canberra; Available online: https://www.digitalhealth.gov.au/initiatives-and-programs/eprescribing (accessed on 2025 Oct).
- HL7 Australia; Australian Digital Health Agency. AU Core Implementation Guide [Internet]. Available online: https://build.fhir.org/ig/hl7au/au-fhir-core/ (accessed on 2025 Oct).
- Centers for Medicare; Medicaid Services; Office of the National Coordinator for Health Information Technology. Trusted Exchange Framework and Common Agreement (TEFCA) [Internet]. U.S. Department of Health and Human Services: Washington; Available online: https://www.healthit.gov/tefca/ (accessed on 2025 Oct).
- Synapxe. Healthier SG programme [Internet]. Government of Singapore: Singapore; Available online: https://www.synapxe.sg/our-programmes/healthier-sg (accessed on 2025 Oct).
- Israel Ministry of Health. National health information exchange [press release on the Internet]. 19 Aug 2014. Available online: https://www.health.gov.il/English/News_and_Events/Spokespersons_Messages/Pages/19082014_1.aspx (accessed on 2025 Oct).
- HL7 International; U.S. Core Project Team. US Core: DiagnosticReport profile (STU6) [Internet]. Available online: https://hl7.org/fhir/us/core/STU6/StructureDefinition-us-core-diagnosticreport.html (accessed on 2025 Oct).
- Australia, H.L.7. Pathology FHIR Implementation Guide [Internet]. Available online: https://build.fhir.org/ig/hl7au/au-fhir-pathology/branches/master/index.html (accessed on 2025 Oct).
- National Library of Medicine. RxNorm [Internet]. U.S. National Institutes of Health: Bethesda; Available online: https://www.nlm.nih.gov/research/umls/rxnorm/index.html (accessed on 2025 Oct).
- HL7 International. CARIN Blue Button Implementation Guide [Internet]. Available online: https://build.fhir.org/ig/HL7/carin-bb/ (accessed on 2025 Oct).
- DHIS2. DHIS2: District Health Information Software 2 [Internet]; University of Oslo: Oslo; Available online: https://www.dhis2.org/ (accessed on 2025 Oct).
- Economic Times Healthworld. Experts warn on barriers to private adoption of Ayushman Bharat Digital Mission [Internet]. 19 Nov 2024. Available online: https://health.economictimes.indiatimes.com/news/industry/experts-warn-on-barriers-to-private-adoption-of-ayushman-bharat-digital-mission/124028026 (accessed on 2025 Oct).
- HL7 International. US Core Implementation Guide [Internet]. Available online: https://build.fhir.org/ig/HL7/US-Core/ (accessed on 2025 Oct).
- Ayushman Bharat Digital Mission. ABDM Sandbox [Internet]; National Health Authority, Government of India: New Delhi; Available online: https://sandbox.abdm.gov.in/ (accessed on 2025 Oct).
- Mission, Ayushman Bharat Digital. National Health Claims Exchange (NHCX) sandbox [Internet]; National Health Authority, Government of India: New Delhi; Available online: https://sandbox-hcx.abdm.gov.in/ (accessed on 2025 Oct).
- Mission, Ayushman Bharat Digital. Scan and Share [Internet]; National Health Authority, Government of India: New Delhi; Available online: https://abdm.gov.in:8081/scanandshare/ (accessed on 2025 Oct).
- HL7 International; U.S. Core Project Team. US Core: MedicationRequest profile (STU6) [Internet]. Available online: https://hl7.org/fhir/us/core/STU6/StructureDefinition-us-core-medicationrequest.html (accessed on 2025 Oct).
- Australia, H.L.7. AU Base: national eDischarge Summary FHIR profile [Internet]. Available online: https://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-discharge-summary.html (accessed on 2025 Oct).
- HL7 International. C-CDA on FHIR Implementation Guide [Internet]. Available online: https://hl7.org/fhir/us/ccda/STU1/StructureDefinition-ccda-on-fhir.html (accessed on 2025 Oct).
| Data source | Scope | Analytical contribution |
| Desk research | ABDM, NHCX, NRCeS implementation guides, global HL7 resources, comparator-country implementation guides, public documentation of pilots and deployments | Characterised national architecture, technical alignment, pilots, and benchmarking domains |
| Stakeholder survey | 22 completed responses from ecosystem participants | Identified perceived maturity, barriers, incentives, tooling gaps, and capacity needs |
| Key informant interviews | 10 semi-structured interviews | Explained implementation experiences, governance concerns, and practical constraints |
| Field validation | Structured conversations with early implementers | Validated bottlenecks and refined practical recommendations |
| International benchmarking | United States, United Kingdom, Australia, Singapore, Israel | Identified transferable lessons on governance, tooling, incentives, and ecosystem development |
| Use Case | Stakeholders | Stage | Scope |
| ePrescription Exchange | eka.care, Driefcase, ABDM | Production | ABDM-linked e-prescriptions via mobile apps and EMR systems; adoption uneven across providers |
| Lab Result Sharing | Thyrocare, SRL, ABDM | Pilot | Laboratory reports shared to patient PHRs; limited geographic scope |
| Claims Exchange (NHCX Sandbox) | Insurers, TPAs, ABDM/NRCeS | Pilot | Structured claims submission and adjudication; first-of-its-kind payer–provider standardisation |
| Personal Health Record Apps | HealthPlix, Tata Health, eka.care | Production | Patient-controlled PHR linked to ABHA; fragmented vendor ecosystem |
| State Health System Bridge | Kerala Health Mission | Pilot | Linking state DHIS2 system with ABDM via FHIR; no scale yet achieved |
| EMR Vendor Integrations | Apollo, Fortis, Manipal, HIS vendors | Pilot/Production | Hospital EMRs made ABDM-compliant; smaller providers largely excluded |
| Telemedicine Platforms | 1mg, Practo, HealthPlix | Pilot | ABDM API integration for virtual consultations; not yet scaled |
| Scan & Share Initiative | ABDM, hospitals, laboratories | Production | QR-code-based patient registration; widely adopted by 2024–2025, though largely facility-led with low rural uptake and not yet using core FHIR Patient resources |
| Domain | India / NRCeS approach | Selected global comparison | Interpretation for India |
| FHIR version | NRCeS IG v6.5.0 based on FHIR R4 | US Core and AU Core also use FHIR R4 | Strong baseline compatibility with global tooling, but profile-specific validation requires packaged NRCeS artefacts. |
| Patient profile | ABHA-linked identifiers and India-specific demographic requirements | US and Australian profiles use jurisdiction-specific identifiers | Appropriate for national use, but mapping guidance is needed for portability and cross-system reuse. |
| Consent | MeiTY consent artefact and gateway-based exchange | SMART-on-FHIR/OAuth scopes and FHIR Consent patterns in some settings | Strong national governance model, but adds onboarding complexity and can limit reuse of global tooling. |
| Terminology | ICD-10, SNOMED CT, LOINC; medication terminology remains less mature | RxNorm in the US; AMT in Australia | Medication terminology is a major gap for prescriptions, claims, analytics, and semantic interoperability. |
| Claims and insurance | NHCX-specific Claim, Coverage, and ClaimResponse workflows | CARIN Blue Button and payer-provider implementation guides | Important payer-provider standardisation effort, but maturity validation and harmonisation are needed. |
| Extensions and national artefacts | ABHA linkage, national identifiers, programme-specific extensions | Jurisdiction-specific extensions in US and AU cores | Captures Indian policy needs but increases developer burden unless documented, packaged, and validated. |
| Domain | Number of barriers | Representative barriers | Main implementation consequence |
| Institutional and policy | 6 | Low digital footprint, lack of incentives, procurement misalignment, restricted autonomy, fragmented governance, perception of FHIR as ABDM-only compliance | Adoption remains shallow, compliance-led, and concentrated among digitally mature actors. |
| Technical and infrastructure | 9 | Legacy HIS mismatch, profile divergence, national artefacts beyond native FHIR semantics, weak conformance testing, limited tooling, terminology gaps, version-management uncertainty, infrastructure constraints, privacy implementation overhead | Developers face high implementation burden and limited ability to self-validate or reuse global tooling. |
| Operational and capacity | 6 | Fragmented workflows, limited workforce capacity, weak change management, fragmented vendor ecosystem, limited business rationale, constrained experimentation | FHIR remains a parallel IT activity rather than embedded operational capability. |
| Level | Description | Minimum criteria | Representative Actors / Examples |
| 0 – Awareness | Basic conceptual familiarity with FHIR; no implementation activity | Awareness of FHIR but no sandbox testing or implementation activity | Smaller state departments, public hospitals, early-stage start-ups |
| 1 – Exploration / Sandbox Testing | Experimentation within ABDM sandbox environments; limited API calls | Registration or sandbox testing; limited API calls; no live exchange | State health mission teams, local HIS vendors, ABDM-certified pilot vendors |
| 2 – Piloting / Limited Use | Partial FHIR implementation for discrete workflows (e.g., e-prescriptions, discharge summaries) | FHIR-aligned workflow implemented in limited setting or pilot | Diagnostic laboratories, TPAs, private hospitals |
| 3 – Operational Use | Live exchange of FHIR documents through ABDM APIs, linked to ABHA and Consent artefacts | Production exchange in selected workflows linked to ABHA, consent, or NHCX | ABDM production environment, NHCX pilots, large EMR vendors |
| 4 – Institutionalised Use | FHIR embedded organisation-wide with automated validation, monitoring, and quality control | Routine use with validation, monitoring, quality control, and workflow integration | Not yet fully realised; a small number of large vendors developing internal roadmaps |
| 5 – Scale & Optimisation | Continuous interoperability improvement, benchmarking, and nationwide replication | Continuous improvement, benchmarking, nationwide replication, and mature conformance monitoring | Not yet attained |
| Timeframe | Strategic priorities | Illustrative actions / milestones |
| Short term (0–1 year) | Establish common foundations and proof-points | Finalise and publish an India Core Implementation Guide as the recommended national reference; launch public FHIR sandboxes and validator suites linked to ABDM/NHCX test environments; initiate pilots in priority use cases (OP consults, e-prescriptions, claims); deliver capacity-building using a three-tier (technical, implementation, policy) framework. |
| Medium term (1–3 years) | Scale adoption through incentives and ecosystem alignment | Embed FHIR conformance clauses in public procurement and accreditation; expand sandboxes into a federation of regional competence centres; introduce recognition programmes for certified vendors and professionals; publish domain-specific IGs (immunisation, diagnostics, insurance) derived from the India Core IG; establish national terminology services including a national medication terminology. |
| Long term (3–5 years) | Institutionalise and sustain interoperability at national scale | Establish a multi-stakeholder governing platform for national FHIR stewardship under government facilitation; operationalise an India FHIR Academy/Consortium for ongoing training, certification, and global collaboration; integrate FHIR-based exchange into public-health surveillance, research, and analytics; align national conformance with emerging FHIR R5+ standards. |
| Strategic priority | Barrier addressed | Near-term action |
| Participatory governance | Fragmented and rigid governance | Create a national multi-stakeholder FHIR forum |
| Layered, openly governed IG model — with the India Core as a recommended baseline | Profile divergence and version uncertainty | Publish India Core, domain IGs, and programme-specific layers |
| Focused public-sector use cases | Diffuse implementation effort | Prioritise 2–4 high-value workflows |
| Incentives and policy alignment | Weak business rationale | Link FHIR conformance to procurement, accreditation, and reimbursement |
| Tooling and sandbox infrastructure | Limited validation and developer support | Launch public validators, test suites, SDKs, and synthetic data |
| Capacity building | Workforce constraints | Create tiered training and certification |
| Regional/global leadership | Limited global feedback loop | Contribute to HL7, WHO-SEARO, and regional FHIR communities |
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content. |
© 2026 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (http://creativecommons.org/licenses/by/4.0/).