FHIR, which stands for Fast Healthcare Interoperability Resources, is a healthcare data exchange standard that lets lab systems connect to hospitals, research institutions, and other healthcare systems through a single setup. Your LIMS implements FHIR once and from that point it can share data with any system that supports it, without building custom interfaces for each connection.

That is a big change from how lab integrations have worked. Until FHIR, your LIMS vendor built a custom interface for Epic and then built a completely different one for Cerner. Each connection was its own project with its own budget, and the tenth one cost about as much as the first. Firely's 2025 State of FHIR survey found that 71% of countries now report active FHIR use and 73% of healthcare data regulations explicitly mandate or recommend it.

What is FHIR?

FHIR works by defining resources, standardised data structures for things like lab results, patient records, and diagnostic reports. Each resource follows a published specification so that a CBC result from your LIMS looks the same to an Epic EHR as it does to a research database.

The technical foundation is REST APIs and JSON, the same web technologies behind most modern software. That means developers who build FHIR integrations do not need specialised healthcare middleware training. They work with familiar tools.

FHIR R4 was the first release with normative content, published in 2019. By 2025, 71% of countries report active use, up from 66% the year before.

Part 1: Why FHIR matters for lab operations

What FHIR regulations apply to labs?

Regulations now mandate FHIR support in specific contexts:

• United States: The 21st Century Cures Act requires certified health IT systems to provide FHIR access to patient data. The ONC HTI-1 Final Rule mandates FHIR support by January 2025 and the CMS Prior authorisation Rule requires FHIR-based APIs by January 2026.
• Global adoption: Firely's 2025 survey found that 78% of countries surveyed have regulations governing electronic health data exchange. Of those, 73% mandate or recommend FHIR, up from 65% in 2024 and 56% in 2023.

If your lab serves hospitals or participates in clinical trials, FHIR compliance affects your software requirements alongside other mandates like 21 CFR Part 11. Verify FHIR capabilities when evaluating LIMS vendors or planning upgrades.

How does FHIR reduce integration costs?

Traditional lab integrations took months of custom development. Your vendor built an HL7 v2 interface for one hospital, then started from scratch for the next. Each connection was expensive.

FHIR cuts that cycle. The standardised format eliminates the custom mapping work that used to make every integration a one-off project. Once your system speaks FHIR, connecting to a new partner is configuration, not a development project.

ONC data shows that 70% of US hospitals had enabled FHIR-based app access by 2024. As more systems come online, each new FHIR connection your lab makes gets easier because the ecosystem around it is maturing.

How does FHIR improve lab data quality?

Fragmented data causes real problems. A patient gets duplicate lab tests because the specialist never saw results from the primary care visit. Research studies lack complete records because lab data sits in systems that do not talk to each other.

FHIR lets data follow patients across settings. Your lab results reach the hospital EHR and the patient portal without anyone re-entering data. Clinicians see complete histories and patients can access their own results directly.

Firely's 2025 survey found that 54% of healthcare leaders expect strong increases in FHIR adoption over the next few years, up from 39% the year before.

Part 2: What lab directors need to understand

What FHIR implementation guides do labs need?

FHIR is flexible, which creates a problem. Two systems can both claim FHIR support and exchange data differently. Implementation guides solve this by specifying exactly how FHIR should be used in particular contexts.

US Core is the mandatory implementation guide for US-based systems. It defines how clinical data should be represented and which coding systems and data elements are required. When evaluating lab software, verify it supports US Core profiles specifically. Generic FHIR support is not enough.

Da Vinci profiles address payer-provider interactions including coverage requirements and prior authorisation. If your lab works with insurance companies, Da Vinci compliance may be on the table.

CARIN profiles enable patient access to their own data. If you run a patient-facing results portal, CARIN guides apply.

Ask vendors which implementation guides they support. A system claiming "FHIR support" without naming specific guides is probably not ready for production integrations.

How does LOINC coding work with FHIR?

Lab results need standardised codes to be useful across systems. Your lab might call a test "HbA1c" while another calls it "Glycated Hemoglobin." Without standard codes, systems cannot match identical tests.

LOINC (Logical Observation Identifiers Names and Codes) is the required standard for lab observations. FHIR implementation guides mandate LOINC codes for test results and the LOINC database contains tens of thousands of codes covering lab tests and clinical observations.

When you implement FHIR, your lab software maps internal test codes to LOINC. This mapping happens once during implementation and after that every result includes a standard code that receiving systems recognize.

Verify your LIMS vendor has completed LOINC mapping for your test menu. Incomplete mapping creates integration failures when results hit hospital systems.

How does FHIR handle patient privacy?

The standard includes an authorisation framework called SMART on FHIR that controls who can access what data.

When a patient uses a health app to access lab results, SMART authorisation controls the scope so the app only receives data the patient approved. When a research institution queries your lab database, SMART controls which records they can see.

The granularity is useful. One app might get read-only access to lab results while another gets permission to create orders and submit data. Different access patterns run through the same framework.

Your lab software should support SMART authorisation even if FHIR data exchange is the immediate priority. Regulatory requirements for patient-directed data access are growing and that requires proper authorisation.

Part 3: Questions to ask software vendors

When evaluating LIMS or lab software that claims FHIR support, ask these:

1. Which FHIR version do you support? Release 4 (R4) is the current standard. Some vendors still run older versions. Verify the version matches what your integration partners expect.
2. Which implementation guides do you support? US Core is mandatory for most US contexts. Ask which version (v3, v4, v5) they implement. US Core v3 is the minimum for ONC certification. If a vendor cannot name the version, they have not implemented it properly.
3. How complete is your LOINC mapping? Ask what percentage of your test menu is mapped. Gaps cause integration failures when results reach hospital systems. Ask which tests remain unmapped and when completion is expected. A vendor saying "we map as needed" is shifting work onto you.
4. Do you support bulk data operations? If your lab participates in research or population health work, you need bulk data export. Individual record queries do not scale for research datasets.
5. What authorisation mechanisms are included? Verify SMART on FHIR support for patient-directed access and research data sharing.
6. How do you handle updates? FHIR standards evolve and implementation guides release new versions. Ask how the vendor manages updates and whether they maintain backward compatibility.
7. Can I test integrations before going live? Vendors should provide sandbox environments for testing FHIR connections with your partners before production.

Part 4: Preparing your lab for FHIR

Audit your current integrations

Document every system your lab exchanges data with:

• Hospital EHRs
• Research databases
• Patient portals
• Billing systems
• Reference labs

For each connection, note whether it uses FHIR or a legacy method like HL7 v2 or custom file transfers. The integrations that cause the most maintenance headaches are your best candidates for FHIR migration. If you are not sure which integrations are worth the investment, our guide on which lab integrations actually save time covers how to evaluate that.

Verify compliance requirements

Check whether your contracts or regulations require FHIR support. Clinical trial sponsors are starting to mandate FHIR-based data submission and hospital networks are following suit. Understanding these requirements before vendor selection saves you from picking a system that falls short six months later. If you are planning a broader laboratory digitalisation effort, FHIR readiness should be part of your tech stack evaluation.

Plan terminology standardisation

LOINC mapping takes time but you only do it once. Budget for terminology work during implementation. The investment pays off through faster integrations and fewer data quality issues when you onboard new partners.

Work with your LIMS vendor to identify tests that lack standard LOINC codes. For proprietary or specialised tests, you may need to request new codes from the Regenstrief Institute, which maintains the LOINC database.

Test with real partners

Before deploying FHIR integrations to production, test with actual partners. Most hospital networks offer sandbox environments where you can validate connections without touching real patient data.

Conclusion

FHIR adoption is accelerating and regulatory mandates are making it required across clinical and administrative healthcare settings. That adoption will keep growing as more hospital networks and research institutions require it.

For labs, this means faster integrations and lower costs when connecting to new partners. Labs that adopt FHIR now will have an easier time onboarding new connections than competitors still maintaining legacy interfaces.

Labs that skip FHIR due diligence during vendor selection often discover the gaps months later, when a hospital partner rejects results because of missing LOINC codes or an incompatible implementation guide. By that point, switching vendors is expensive and staying means custom workarounds that defeat the purpose of a standard. For a broader look at how to choose the right lab software approach, we cover that separately.

Evaluating lab software for your organization? FHIR capabilities affect integration timelines and compliance. We help diagnostic labs and biotech companies assess LIMS requirements and vendor capabilities. Discuss your needs with our team.

References

• FHIR Overview - HL7 International
• US Core Implementation Guide - HL7 FHIR
• 2025 State of FHIR Survey - Firely
• Hospital FHIR Adoption Data - ONC/ASTP
• LOINC Database - Regenstrief Institute

Frequently Asked Questions

Does FHIR replace HL7 v2?

Not immediately. Your lab will likely run both in parallel for a while. Here is how they compare:

	HL7 v2	FHIR
Primary use	Real-time messaging (orders, results)	API access (portals, research queries)
Integration model	Point-to-point, custom per partner	Standardised API, implement once
Data format	Pipe-delimited messages	JSON/XML over REST
Adoption trend	Legacy, still widely used	Growing, regulatory mandates accelerating

Expect a gradual transition. HL7 v2 still handles real-time messaging well and FHIR covers API access for patient portals and research queries.

How long does FHIR implementation take?

It depends on your starting point. Labs with a modern LIMS and complete LOINC mapping can get FHIR running in weeks. Labs with legacy systems or incomplete terminology may need months. Ask vendors for realistic timelines based on your current state.

What if my lab runs specialised tests not in LOINC?

Work with the Regenstrief Institute to request new codes. The process takes time so start early. FHIR allows local codes with proper documentation until standard codes become available.

Do I need FHIR for hospital connections?

Increasingly, yes. Major hospital networks are moving to FHIR-based integrations. HL7 v2 still works for existing connections but new partners will likely require FHIR. Plan for it even if nobody has asked yet.

How does FHIR affect patient privacy?

FHIR includes authorisation frameworks (SMART on FHIR) that control data access at a granular level. Properly implemented, it improves privacy by letting you control exactly which data each app can see. HIPAA compliance requirements still apply to all patient data regardless.

What about international labs?

FHIR is a global standard. US Core is US-specific but other countries maintain their own implementation guides. Check which guides apply in your jurisdiction.

Last updated: March 20, 2026