FHIR Interoperability: A Practical Guide to Healthcare Data Exchange
FHIR interoperability uses HL7’s Fast Healthcare Interoperability Resources standard to represent and exchange healthcare information through reusable resources and defined interactions.
It helps connect EHRs, applications, and payer systems. Reliable exchange also depends on shared implementation rules, consistent terminology, accurate patient identification, appropriate permissions, and integration into clinical workflows.
For a practice administrator, the goal may be fewer outside records to chase before a visit. For an IT director, it may be connecting an application without rebuilding every data mapping from scratch.
FHIR provides a common foundation for that work. To turn it into useful exchange, organizations must define which information should move, how it should be interpreted, and who acts when something is missing.
What Is FHIR, and How Does It Work?
FHIR is a healthcare data exchange standard developed by HL7 International. It organizes information into building blocks called resources.
| FHIR resource | Information it represents |
| Patient | Demographic and administrative information |
| Observation | Measurements and observations, including many laboratory results |
| DiagnosticReport | Diagnostic findings and interpretations, with references to supporting results |
| MedicationRequest | Medication orders and prescription requests |
| ServiceRequest | Requests for tests, treatments, and other services |
Resources reference one another. An Observation can identify the patient it belongs to, while a DiagnosticReport can reference the observations supporting its findings.
FHIR commonly uses RESTful APIs and JSON or XML representations. It also supports messaging and document-based exchange. Its value comes from common data structures and interactions not from eliminating interfaces.
How FHIR Improves Healthcare Data Exchange
FHIR gives participating systems a shared starting point for representing and accessing information. Four capabilities make that useful.
| Capability | Practical benefit | What to verify |
| Targeted data access | An application can request supported data needed for a task. | Required resources, searches, and historical coverage |
| Reusable integration patterns | Common structures and guides can reduce repeated design work. | Profile versions and partner-specific differences |
| Application integration | Authorized apps can use supported EHR data and launch context. | Registration, permissions, launch behavior, and write access |
| Explicit data requirements | Profiles and terminology bindings define shared expectations. | Local mappings, missing fields, and clinical meaning |
These capabilities can support patient access, referral preparation, clinical applications, and payer-provider exchange. Their operational value depends on the implemented workflow, so savings should be measured against a documented baseline.
Why FHIR Interoperability Matters in 2026
FHIR is already used in production. ONC reported that 70% of non-federal acute care hospitals enabled patient access through FHIR-based apps in 2024. That measures reported capability, not patient usage or improved clinical outcomes.
Broader workflow integration remains uneven. Separate ONC research found that hospitals predominantly used nonstandard approaches to exchange data with third-party technology for clinical and administrative purposes.
Payer API Requirements Are Approaching
Under CMS-0057-F, API compliance dates primarily begin January 1, 2027. Requirements include new Provider Access, Payer-to-Payer, and Prior Authorization APIs, plus Patient Access API enhancements.
Impacted payers include Medicare Advantage organizations, state Medicaid and CHIP agencies, Medicaid managed care plans, CHIP managed care entities, and QHP issuers on federally facilitated exchanges. The rule’s prior authorization provisions exclude drugs.
These payer requirements do not impose the same API implementation obligation on every provider. Provider organizations should confirm how their EHR and payer partners will support the intended exchange.
Standards Versions Need Explicit Agreement
ONC adopted updated versions of several payer-related implementation guides through the FY2027 IPPS final rule, with specified replacements effective October 1, 2026.
This standards adoption date is distinct from an organization’s implementation deadline. Document the versions required by applicable rules and supported by participating vendors before development begins.
What FHIR Data Exchange Looks Like in Practice
Illustrative Workflow: Preparing a Cardiology Referral
A cardiology practice needs outside laboratory results before a consultation.
An authorized application connects to the source API, identifies the correct patient, and retrieves available results. The integration checks codes, units, dates, status, and source information before presenting the results for review.
The project should define what happens when that process is incomplete:
| Situation | Proposed acceptance criterion |
| Required result is available | Present agreed clinical details, dates, units, status, and source. |
| Patient identity is uncertain | Route the case for review before associating outside data. |
| Required result is absent | Flag that it was not retrieved; do not imply no test occurred. |
| Authorization fails | Distinguish an access failure from missing clinical information. |
| A result is corrected | Verify how the correction reaches the review workflow. |
Measure the share of referrals with required results available before review, manual follow-up per referral, and unresolved exceptions. These are proposed pilot measures, not claimed outcomes.
Production Example: CMS Blue Button
CMS Blue Button uses FHIR and the CARIN implementation guide to share Medicare claims data with authorized applications. It supplies JSON data and uses OAuth 2.0 for authorization.
This demonstrates how a data standard, implementation guide, and access controls work together. Its scope is claims data; it should not be described as providing a complete clinical record.
How FHIR, USCDI, US Core, and SMART Fit Together
Each component answers a different implementation question.
| Component | Role |
| FHIR | Defines resources and exchange interactions |
| USCDI | Defines standardized U.S. health data classes and elements |
| US Core | Defines U.S. FHIR profiles and interaction expectations |
| SMART on FHIR | Defines authorization and application integration patterns |
SMART App Launch can provide context such as the selected patient. It does not supply the app’s interface or resolve terminology differences.
An application can therefore launch successfully while the data required for its workflow remains unavailable. Test launch behavior and data completeness separately.
Does FHIR replace HL7 v2 or C-CDA?
FHIR can coexist with both. HL7 v2 commonly supports event messages such as admissions and laboratory results. C-CDA supports structured clinical documents. FHIR supports resource-based exchange, including APIs, messages, and documents.
Choose based on the workflow and supported systems. A working laboratory feed may remain appropriate while a new application uses FHIR. FHIR can also carry references to CDA documents; exchanging a document does not require converting all its content into discrete resources.
6 Steps to Implement Reliable FHIR Interoperability
1. Define the Workflow and Success Criteria
Specify required information, source systems, destination, acceptable delay, and clinical owner. Distinguish reading data from creating or updating records.
For the referral pilot, agree which results are required and how missing information reaches the responsible team.
2. Verify Vendor Capabilities and Access
Review API development and the CapabilityStatement, then corroborate capabilities through vendor confirmation and representative testing.
Confirm resources, profiles, searches, supported interactions, authorization, historical coverage, rate limits, production onboarding, and fees. Patient-access functionality does not establish support for every operational use case.
3. Preserve Clinical Meaning and Patient Identity
Map data to the agreed profiles and validate terminology, units, status, dates, and references.
A medication order, a dispensing event, and a reported medication history describe different information. Similar labels should not cause those meanings to be collapsed. Preserve distinctions such as “unknown,” “not recorded,” and “none.”
Also define identity matching and review rules for uncertain cases before attaching outside information to a patient’s record.
4. Secure Access and Document Permissions
Implement encrypted transport, appropriate authentication, scoped authorization, and audit controls. Document applicable permissions, consent requirements, and the legal basis for exchange.
FHIR adoption alone does not establish HIPAA compliance. Regulated organizations retain their applicable administrative, physical, and technical safeguard obligations.
5. Validate the Data and Complete Workflow
Test profile conformance and business rules, including missing fields, duplicate data, corrected results, expired authorization, pagination, and failed requests.
ONC’s Inferno provides conformance test kits. Pair appropriate technical tests with clinical review to verify that information reaches the intended workflow accurately and with sufficient context.
6. Assign Ownership After Launch
Name owners for failures, mapping changes, credentials, and clinical exceptions. Agree retry rules, escalation paths, monitoring, and regression testing.
Track required-data completeness, information freshness, manual follow-up, and exception resolution against the pilot baseline.
What Should a FHIR Integration Proposal Include?
Discovery findings should define cost and timeline. Before approving a proposal, request:
- A documented workflow and data scope.
- Confirmed vendor capabilities and external dependencies.
- Mapping and identity responsibilities.
- Agreed technical and clinical acceptance tests.
- Security and access responsibilities.
- Support ownership, exclusions, and ongoing costs.
Ask which findings could change the estimate. This makes proposals easier to compare and exposes dependencies before they become delivery problems.
Will Your EHR Support the Data Exchange You Need?
CapMinds provides HL7 and FHIR integration services across EHR connectivity, mapping, testing, and support.
Share the systems involved, the workflow you want to improve, and the information currently missing to discuss your integration requirements.
Frequently Asked Questions
Is FHIR Data Exchange Always Real Time?
No. Freshness depends on source updates, supported interactions, synchronization design, and application behavior. Define an acceptable delay for the intended workflow.
Can FHIR Applications Update an EHR?
Only when the server supports the required create or update interactions and the application has appropriate authorization. Read access does not establish write access.
Can FHIR Support Legacy System Integration?
Yes, through suitable interfaces and transformations where the required source data is accessible. Mapping and testing must account for the original system’s limitations.
Does FHIR Give Patients Field-by-Field Sharing Controls?
FHIR does not automatically provide those controls. Available choices depend on the source system, application, authorization model, and applicable policies.
Where Should a Healthcare Organization Begin?
Choose a frequent, measurable problem with a clear owner. Confirm data availability and access, then pilot one workflow before expanding.



