---
title: "HL7 FHIR explained for health data exchange | Quantlix"
description: "HL7 FHIR is the standard for exchanging health data through web APIs. Learn which versions matter, what FHIR covers and how it shapes health software projects."
canonical: "https://quantlix.com/en/standards/hl7-fhir/"
last-updated: 2026-11-16
---

Source: https://quantlix.com/en/standards/hl7-fhir/
Language: en
Description: HL7 FHIR is the standard for exchanging health data through web APIs. Learn which versions matter, what FHIR covers and how it shapes health software projects.

**HL7 FHIR** [Health and clinical data](https://quantlix.com/en/standards/#health)

# HL7 FHIR: the web API standard for health data

HL7 FHIR is the HL7 International standard for exchanging health data as small, linked resources over web APIs, used by EHRs, patient apps, payers and research platforms.

[Discuss your project](https://quantlix.com/en/contact/) [Read the key points](https://quantlix.com/en/standards/hl7-fhir/#standard-overview)

## At a glance

**Full name**

Fast Healthcare Interoperability Resources (FHIR)

**Published by**

HL7 International

**Type**

Interoperability standard (data model and REST API specification)

**Current version**

Release 5 (5.0.0, March 2023) is the current published release; R4 (4.0.1) is the version US certification rules require; R6 was in normative ballot in 2026

**Applies to**

Healthcare providers, payers, health IT vendors, public health and research systems that exchange clinical and administrative data

**Last reviewed**

November 16, 2026 (2026-11-16)

## In plain terms

### Key points

- FHIR models health data as resources, such as Patient, Observation and Encounter, that systems read and write through a RESTful API.
- R4 brought the first normative content: the REST API, JSON and XML formats, base data types, terminology, conformance, Patient and Observation.
- R5 (5.0.0, March 2023) is the current published release. R6 was still in normative balloting when we checked in November 2026.
- Real projects run on implementation guides, such as US Core and SMART App Launch, that profile the base resources for a country or use case.

### What is HL7 FHIR?

HL7 FHIR (Fast Healthcare Interoperability Resources) is **a standard for exchanging health data through web APIs**, published by HL7 International. It breaks clinical and administrative information into small, well-defined resources, such as a patient, an observation, a medication request or an appointment, and lets systems read, search and update them over HTTP using JSON or XML.

It exists because older health data standards were hard to use outside hospital interface engines. FHIR borrows familiar web conventions, so a developer who has built a REST API can fetch a lab result with tools they already know, while the clinical meaning stays consistent from one system to the next.

### What FHIR covers

- **Resources.** Defined building blocks for clinical, administrative, financial and workflow data, each with elements, data types and references to other resources.
- **The RESTful API.** Standard interactions to create, read, update, delete, search and view history, plus named operations for work that goes beyond simple reads and writes.
- **Formats and bundles.** JSON and XML representations of every resource, with Bundles that group resources into documents, messages, transactions and search results.
- **Terminology.** CodeSystem and ValueSet resources that bind elements to code systems such as SNOMED CT, LOINC and RxNorm.
- **Conformance.** StructureDefinition and CapabilityStatement resources, so implementation guides can profile resources for a use case and servers can publish exactly what they support.

### Versions and implementation guides

FHIR releases are numbered, and the number matters. **R4 (4.0.1) was the first release with normative content**: the REST API, the JSON and XML formats, the base data types, the terminology and conformance layers and the Patient and Observation resources, which HL7 commits to keep backward compatible. R5 (5.0.0), published in March 2023 as a trial-use release, is the current version on hl7.org, but much of the installed base still runs R4. R6 is being balloted as a fully normative standard; HL7 ran its second full R6 ballot in 2026, and R6 had not been published when we checked in November 2026.

The base specification is deliberately broad, so production work runs on implementation guides. In the United States, US Core (now at STU 9, built on R4) sets the minimum profiles for patient data, and SMART App Launch defines how apps and backend services are authorized. Certified US health IT must expose a FHIR R4 API that follows these guides, and other countries publish national profiles of their own.

### How it shows up in software projects

- **Version and profile choices.** Each interface names the FHIR release and the guide versions it follows, because “a FHIR API” means little without them.
- **Mapping and terminology.** Records from EHRs, labs or HL7 v2 feeds are mapped to resources, and local codes are translated to the value sets each profile requires.
- **Authorization.** Apps are registered and scoped through SMART App Launch, with patient, user and system scopes, token lifetimes and revocation treated like any other access right.
- **Validation in the pipeline.** Resources are checked against profiles with the FHIR validator on every build, and servers are tested against the capability statement they publish.
- **Privacy and audit.** Access is logged, for example with AuditEvent and Provenance resources, and the design follows the privacy law that applies, such as HIPAA in the US.

### How we work with HL7 FHIR

We design and build FHIR integrations for [healthcare](https://quantlix.com/en/industries/healthcare/) and [life sciences](https://quantlix.com/en/industries/life-sciences/) teams: FHIR APIs over existing databases, mappings from HL7 v2 and proprietary formats, SMART-enabled apps and pipelines that turn resources into analytics. Imaging usually arrives through [DICOM](https://quantlix.com/en/standards/dicom/) alongside the record, and we plan privacy controls around [HIPAA](https://quantlix.com/en/standards/hipaa/) from the first sprint. Our [enterprise applications](https://quantlix.com/en/services/enterprise-applications/) team leads this integration work.

We keep our claims precise. We can build to a named profile and run its validators and test kits, while certification under a national program and compliance with health privacy law belong to you, your certifying body and your auditors. If you are scoping a FHIR project, [talk to us](https://quantlix.com/en/contact/).

## Where it applies

Industries where this standard often shapes the work.

- ### [Healthcare](https://quantlix.com/en/industries/healthcare/)

  Hospital and clinic workflows, digital health and medical technology

## Related standards

[All standards](https://quantlix.com/en/standards/)

- DICOM

  ### [Medical imaging data and communication](https://quantlix.com/en/standards/dicom/)

  DICOM is the international standard for medical imaging that defines how images and related data are encoded, stored, exchanged and displayed, so scanners, archives and viewers from different vendors work together.
- HIPAA

  ### [US health information privacy and security](https://quantlix.com/en/standards/hipaa/)

  HIPAA is the US federal law whose Privacy, Security and Breach Notification Rules govern how health plans, providers and their business associates use, disclose and protect patient health information.
- CDISC

  ### [Clinical trial data standards](https://quantlix.com/en/standards/cdisc/)

  CDISC is a global nonprofit whose clinical research data standards, such as SDTM, ADaM and Define-XML, are required by FDA and Japan's PMDA for study data in drug submissions.

## Services that support this work

The services we usually bring to projects that involve this standard.

[View all services](https://quantlix.com/en/services/)

### [Enterprise applications](https://quantlix.com/en/services/enterprise-applications/)

Quantlix designs and builds enterprise applications for internal workflows, business rules and system integration, with clear access controls and maintainable architecture.

### [Web application development](https://quantlix.com/en/services/web-application-development/)

Quantlix designs and builds web applications with responsive interfaces, business logic and system integrations, balancing accessibility, performance and maintainability.

### [Data analytics](https://quantlix.com/en/services/data-analytics/)

Quantlix builds analytics pipelines and business intelligence tools that turn operational data into defined metrics, useful reports and decision support.

## Questions, answered

What teams usually ask us about this standard.

**Which FHIR version should we build on?**

For most production work today, R4 (4.0.1). US certification rules for health IT and the US Core guide are based on it, and its core is normative. R5 is the current published release and R6 was in normative balloting in 2026, so keep the version behind a mapping layer rather than spreading it through your code.

**Is FHIR mandatory?**

FHIR itself is a voluntary standard, but some regulations require it. In the United States, certified health IT must offer a standardized API built on FHIR R4, US Core and SMART App Launch under certification criterion 170.315(g)(10). Other countries set their own national profiles and rules.

**How does FHIR differ from HL7 version 2?**

HL7 v2 is an older messaging standard made of pipe-delimited segments, still common for hospital feeds such as admissions and lab results. FHIR uses resources, JSON or XML and web APIs. Many organizations run both, with interfaces that map between them.

**What is SMART on FHIR?**

SMART App Launch is an HL7 implementation guide that uses OAuth 2.0 so apps can be authorized to reach FHIR data, either launched by a user or running as a backend service with no user present. Version 2.2.0 is the current published release.

**Can software be certified for FHIR?**

HL7 does not certify products against the base specification. Conformance is shown by testing against specific profiles, for example with the FHIR validator and implementation guide test kits, and national programs such as US health IT certification test products against named FHIR requirements.

## Official sources

Read the official text before relying on any detail. What applies to you depends on your role, your location and the version in force.

- [HL7 FHIR specification (current release)](https://hl7.org/fhir/)
- [FHIR publication history](https://hl7.org/fhir/history.html)
- [FHIR R4 (4.0.1)](https://hl7.org/fhir/R4/)
- [Standardized API certification criterion 170.315(g)(10)](https://www.healthit.gov/test-method/standardized-api-patient-and-population-services)

These guides explain each standard in plain terms. They are not legal advice, and they do not state that any product or organization conforms to a standard.

## Planning software around this standard?

Tell us which systems are involved and what you need to show. We will help you build the requirements in from the start.

[Discuss your project](https://quantlix.com/en/contact/)
