Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-39615

genderIdentify extension is not backward compatible

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Core (FHIR)
    • 6.0.0-ballot [deprecated]
    • Cross-Group Projects
    • STU
    • US Core Gender Identity Extension
    • Hide

      Decision:

      Revert to the US Core V5 simple extension, and provide guidance in the extension to use the FHIR R5 gender identity extension instead to allow both multiple Gender Identities and associated dates.  And that this and will eventually be replaced by it in future versions of the FHIR R5-based US Core.

      Background:

       

      See FHIR-FHIR-37509  and See Changes Here

       

      version 5.0.1 US Core Gender Identity Extension

       

      version 6.0.0-ballot US Core Gender Extension

      Rationale:

      This extension is not compatible between v5.0.1 and v6.0.0.  Making a breaking change to a FHIR US Core extension could result in compatibility issues with existing systems, decreased adoption of the specification, reduced confidence in its stability, implementation challenges for developers, and decreased interoperability between systems due to different interpretations of the changes.

      It is imperative to note that the current extension is a duplication of the FHIR R5 gender identity extension and will eventually be replaced by it in future versions of the FHIR R5-based US Core. In light of this, creating a new extension in US Core would not align with the intended goal of being superseded by the FHIR Core extension.

       

       

       

      Please note that we have used OpenAI's chatCPG to assist in answering this question. We review these responses and the information provided is based on our experience and implementer feedback and our design choices for US Core.

      Show
      Decision: Revert to the US Core V5 simple extension, and provide guidance in the extension to use the FHIR R5 gender identity extension instead to allow both multiple Gender Identities and associated dates.  And that this and will eventually be replaced by it in future versions of the FHIR R5-based US Core. Background:   See FHIR- FHIR-37509   and See Changes Here   version 5.0.1 US Core Gender Identity Extension   version 6.0.0-ballot US Core Gender Extension Rationale: This extension is not compatible between v5.0.1 and v6.0.0.  Making a breaking change to a FHIR US Core extension could result in compatibility issues with existing systems, decreased adoption of the specification, reduced confidence in its stability, implementation challenges for developers, and decreased interoperability between systems due to different interpretations of the changes. It is imperative to note that the current extension is a duplication of the FHIR R5 gender identity extension and will eventually be replaced by it in future versions of the FHIR R5-based US Core. In light of this, creating a new extension in US Core would not align with the intended goal of being superseded by the FHIR Core extension.       Please note that we have used OpenAI's chatCPG to assist in answering this question. We review these responses and the information provided is based on our experience and implementer feedback and our design choices for US Core.
    • Brett Marquard / Jason Vogt : 16-0-1
    • Correction
    • Compatible, substantive

    Description

      Background

      In US Core v5, the genderIdentity requires value[x] with cardinality 1..1
      In US Core v6, the genderIdentity does not allow value[x] with cardinality 0..0

      Any Patient resources with genderIdentify extension, which are valid in v5, are invalid in v6.

      Suggestion

      Change the cardinality 0..0 of value[x] to optional 0..1 so that the extension is backward compatible.

      Attachments

        Activity

          People

            Unassigned Unassigned
            yunwwang Yunwei Wang
            Yunwei Wang
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: