HL7 FHIR Release 4
FHIR R4 defines resources, RESTful interactions, data types, terminology bindings, conformance artifacts, security considerations, and exchange patterns. It includes the first normative FHIR content and remains the base for major U.S. implementation guides.
What the authority record establishes
FHIR R4 defines resources, RESTful interactions, data types, terminology bindings, conformance artifacts, security considerations, and exchange patterns. It includes the first normative FHIR content and remains the base for major U.S. implementation guides.
Voluntary standard unless adopted by regulation, certification, contract, or program; FHIR R4 is the base release used by current U.S. certified API and CMS payer API requirements
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
Buyers must distinguish base R4 support from support for a named profile or implementation guide. FHIR R4 does not establish production connectivity, semantic quality, authorization design, or conformity for a particular product.
Affected operating stages
- Data Modeling
- Profile Selection
- API Implementation
- Authorization
- Validation
- Testing
- Production Operations
- Version Change Control
Capabilities to examine
FHIR Server And Repository
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FHIR server and repository.
FHIR API Gateway And Orchestration
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FHIR API gateway and orchestration.
FHIR Profile And Implementation-Guide Support
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FHIR profile and implementation-guide support.
SMART On FHIR Authorization
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for SMART on FHIR authorization.
Bulk Data Access And Export
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for bulk data access and export.
Terminology Normalization And Value-Set Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for terminology normalization and value-set management.
Conformance Testing And Validation
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for conformance testing and validation.
Operational Monitoring And Exception Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for operational monitoring and exception management.
Affected buyer audiences
- health IT developers
- health systems
- health plans
- interoperability platforms
- certification and compliance teams
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
FHIR is not a single product certification. Conformance must be evaluated against named versions, profiles, capabilities, and test methods.