FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions

Downloads

Page standards status: Informative

Package File

The following package file includes an NPM package file used by many of the FHIR tools. It contains all the value sets, profiles, extensions, list of pages and urls in the IG, etc defined as part of this version of the Implementation Guides. This file should be the first choice whenever generating any implementation artifacts since it contains all of the rules about what makes the profiles valid. Implementers will still need to be familiar with the content of the specification and profiles that apply in order to make a conformant implementation. See the overview on validating FHIR profiles and resources:

Downloadable Copy of this Specification

A downloadable version of this IG is available so it can be hosted locally:

Package Dependencies

IGPackageFHIRComment
.. FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2R4
... HL7 Terminology (THO)hl7.terminology.r4#6.5.0R4Automatically added as a dependency - all IGs depend on HL7 Terminology
.... FHIR Extensions Packhl7.fhir.uv.extensions.r4#5.2.0R4
... FHIR Tooling Extensions IGhl7.fhir.uv.tools.r4#0.7.1R4for example references

Package hl7.fhir.uv.extensions.r4#5.2.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00)

Package hl7.fhir.uv.tools.r4#0.7.1

This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Sat, Jul 26, 2025 06:59+1000+10:00)

Global Profile Definitions

There are no Global profiles defined

Cross-Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B} systems. Packages for both R4 (hl7.fhir.uv.xver-r5.r4.r4) and R4B (hl7.fhir.uv.xver-r5.r4.r4b) are available.