HealthRecordCommunity
FHIR🌏 InternationalEnriched

FHIR Normative Content and Version Compatibility Guidance

FHIR normative content and version compatibility

August 14, 2026

Summary

This guidance provides principles for implementing FHIR to ensure stable (normative) behavior and avoid breaking changes. It advises clients, in particular, to use forward-compatible parsing that ignores unknown elements and avoid hardcoding assumptions not based on the FHIR standard.

Details

This document offers detailed guidance on handling 'normative content' and 'version compatibility' when integrating systems using FHIR (Fast Healthcare Interoperability Resources). Since FHIR contains a mix of stable 'normative' parts and evolving 'non-normative' parts, it warns that breaking changes may occur in the latter. System developers are strongly advised to implement 'defensively' to minimize disruption from server evolution. Specifically, they should adopt 'forward-compatible parsing' that ignores unknown elements rather than failing upon them when parsing JSON, and avoid hardcoding assumptions about optional elements not required by the standard. Version compatibility also requires attention; when using different endpoints like R4 and R6, clients must be designed to handle version-specific differences in resource models or search parameters. Before integration, it is recommended that developers follow a workflow of first verifying supported resource types and operations (read/search/create, etc.) using the 'capability statement' (server metadata).

πŸ“°
Read Original Article
docs.oracle.com
β†’

Original content copyright by respective publishers