Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R4 in FHIR R5 - Downloaded Version null See the Directory of published versions

Home

Official URL: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5 Version: 0.1.0
IG Standards status: Trial-use Maturity Level: 0 Computable Name: Hl7_fhir_uv_xver_r4_r5

The Cross-Version Extensions for FHIR (XVer) project provides a set of packages that define extensions, profiles, and value sets for cross-version compatibility in FHIR. These packages are designed to support the validation and interoperability of FHIR resources across different versions.

About This Guide

Cross-version extension content is generated via a combination of automatic differential detection and manual editing.

For details or questions, please reach out on Zulip or to the FHIR Infrastructure WorkGroup.

Frequently Asked Questions and related guidance can be found on the Confluence Cross-Version FAQs Page

Goals

  • Ability to use elements from another version of FHIR
  • Encode information added in a newer version of FHIR
    • Community identified additional data that is needed
    • Need to provide a consistent way of representing it in an earlier version of FHIR
  • Encode information removed in a newer version of FHIR
    • Community decided data was no longer necessary
    • Need to provide a consistent way of representing it in a later version of FHIR
    • Version migration requires interoperability between versions and cannot break old expectations
    • Scenarios where data needs to round-trip conversion between different versions

Known Limitations

  • Not 100% coverage of all elements in all versions
    • Resource type elements are excluded (e.g., R5:Bundle.issues)
  • Mappings are generally between adjacent versions, so "back-and-forth" conversions may be needlessly verbose
  • Large / infinite value sets (e.g., UCUM, LOINC, MIME) are excluded and assumed 'equivalent' across versions
  • Mapping elements that split into multiple elements has a lot of complications that are out-of-scope for this package, but should be noted when using it. E.g., when mapping from a single CodeableReference element to CodeableConcept and Reference elements, decisions must be made about any existing extensions, etc.

Intellectual Property Statements

This publication includes IP covered under the following statements.