Change 'Person.gender' data type and binding strength

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • Normative
    • Patient
    • 812
    • Hide

      This is a duplicate of issues 14768, 11037, 11930, 3070 (which have previously been marked as non-persasive, notes extracted from one of the resolutions)

      Please come to PA to discuss further if desired.

      ------

      This has been addressed and discussed extensively in the past, and relaxing the binding will not assist in improving interoperability.

      11930, 3070, 11037

      If jurisdictions decide that they would like to provide alternative concepts for gender, they can add an extension onto the existing values.

      ConceptMaps have already been provided to v2 and v3.

      Other jurisdications (and vendors) may create ConceptMaps to their own internal/proprietary/local ValueSets as required.

      No change will be made.

      Show
      This is a duplicate of issues 14768, 11037, 11930, 3070 (which have previously been marked as non-persasive, notes extracted from one of the resolutions) Please come to PA to discuss further if desired. ------ This has been addressed and discussed extensively in the past, and relaxing the binding will not assist in improving interoperability. 11930, 3070, 11037 If jurisdictions decide that they would like to provide alternative concepts for gender, they can add an extension onto the existing values. ConceptMaps have already been provided to v2 and v3. Other jurisdications (and vendors) may create ConceptMaps to their own internal/proprietary/local ValueSets as required. No change will be made.
    • Brian Postlethwaite/Christian Hay:7-0-1
    • Correction

      The Patient.gender is of type "- code -" which limits the ability of implementers to harmonize this terminlogy with other systems and emerging needs. If we change the type from "code" to either "Coding" or "CodeableConcept", we allow National affiiliates to implement

      In addition, the *Terminology Binding for Patient.gender *should be either *Preferred *or *Example *to allow for National profiles and implementation guides to substitute an appropriate value set binding/coding system..

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            greg_staudenmaier, Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: