FHIR format adoption in US healthcare has enabled specific capabilities. Understanding what FHIR unlocks (vs. what it doesn't) shapes strategic decisions.
What FHIR enables
1. **Third-party app ecosystem via SMART on FHIR. Third-party integration surface is standard. 2. Bulk data movement via Bulk Data IG. Analytics pipelines feed from FHIR store. 3. Point-of-care decision support via CDS Hooks. In-workflow clinical support. 4. Regulatory compliance via US Core profiles. CMS-0057 baseline. 5. Cross-vendor data exchange.** FHIR REST is the common language.
What FHIR doesn't change
1. Legacy HL7v2 workflows still dominate upstream data. 2. Data quality is still an operational challenge. 3. Terminology management is still complex. 4. Clinician workflow constraints haven't changed. 5. Regulatory pressure still increases.
Ecosystem impact (mid-2026)
1. App marketplaces. Epic App Orchard, Cerner code, SMART launched app catalogs. 2. CMS-0057 attestation. Payers required to expose FHIR APIs. 3. Standard integration. Vendors ship FHIR APIs as baseline. 4. Analytics products. Growing category of FHIR-native analytics.
Adoption phases (2020-2026)
| Phase | Focus |
|---|---|
| 2020-2022 | US Core reads, first SMART launches |
| 2022-2024 | Bulk data, CDS Hooks, initial CMS-0057 |
| 2024-2026 | Full CMS-0057, Da Vinci widespread |
| 2026+ | AI on FHIR, ambient documentation, ML analytics |
FHIR value delivery
1. Faster third-party integration — universal SMART surface. 2. Regulatory compliance easier — standardized profiles. 3. Ecosystem effects — app innovation. 4. Data movement standardized — Bulk data. 5. Point-of-care support — CDS Hooks.
Common misunderstandings
1. "FHIR replaces HL7v2." No, complements. 2. "FHIR solves interoperability." No, enables it. 3. "FHIR is universal." No, US Core in US; different profiles elsewhere.
FHIR format enables real capabilities in US healthcare. Understanding what it does and doesn't do shapes realistic strategy.