Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIR Core (FHIR)
-
R5
-
FHIR Infrastructure
-
Change Management & Versioning (versions/compatibility)
-
2.1.7.0.5
-
-
Bas van den Heuvel/Josh Mandel: 11-0-0
-
Clarification
-
Non-substantive
-
R5
Description
This relates to FHIR-38876, whose comment states:
This was discussed during the "Breaking Change" Birds of a Feather during the Sept 2022 WGM in Baltimore.
The section "rules for inter-version change" is broken and needs to be revised.
The section should also clearly indicate what kind of interoperability the HL7 community strives for; whether FHIR intends implementation or data representation based interoperability.I think FHIR should strive for data representation based interoperability; (normative) data from one version should be understood (parsed, interpreted) by implementations of a newer version.
This was only partially resolved in the resolution to FHIR-38876. The aspect of data vs implementation interoperability has not been addressed yet. This must still be done (as was discussed in FHIR-i on 20-Feb-2023).
Attachments
Issue Links
- relates to
-
FHIR-38876 Rules for Inter-version change are broken
- Published