Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Highest
-
FHIR Core (FHIR)
-
R5
-
FHIR Infrastructure
-
STU
-
Change Management & Versioning (versions/compatibility)
-
2.1.7.0.5
-
-
Grahame Grieve/Christiaan Knaap: 13-0-0
-
Clarification
-
Non-substantive
-
R5
Description
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.
Attachments
Issue Links
- is voted on by
-
BALLOT-43364 Negative - Vadim Peretokin : 2022-Sep-FHIR R5 STU
- Withdrawn
-
BALLOT-41614 Negative - Bas van den Heuvel : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-42742 Negative - Javier Espina : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-42844 Negative - Chris Melo : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-42930 Negative - Bert Roos : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-43247 Negative - Lisson Zhang : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-43804 Negative - David Simons : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-43946 Negative - Martin Rosner : 2022-Sep-FHIR R5 STU
- Closed
- relates to
-
FHIR-40494 Rules for Inter-version change are broken and need to be fixed in R6
- Published