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

Change data type of Patient Gender

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Patient Administration
    • Patient
    • Hide

      As lloyd notes below, the basic patient gender datatype is defined as the Code to simplify the base patient resource to a more static set of values. Many systems use their own values and require mapping to other values anyway (govt's don't define the same set) so loosening this binding wouldn't improve interoperability.

      This has been discussed at length in other tracker items and Zulip.

      If you need more values than in the base set, you can extend the other code value. And for non administrative gender usecases, the observation should be used (or other extensions on patient for things like gender at birth or jurisdictional variants that are additional to the adminsitrative gender).

      Show
      As lloyd notes below, the basic patient gender datatype is defined as the Code to simplify the base patient resource to a more static set of values. Many systems use their own values and require mapping to other values anyway (govt's don't define the same set) so loosening this binding wouldn't improve interoperability. This has been discussed at length in other tracker items and Zulip. If you need more values than in the base set, you can extend the other code value. And for non administrative gender usecases, the observation should be used (or other extensions on patient for things like gender at birth or jurisdictional variants that are additional to the adminsitrative gender).
    • Brian Postlethwaite/Line Saele: 7-0-0
    • Correction

    Description

      Recommend changing Gender from Code to a non-required Coding so that jurisdiction specific Gender codes can be efficiently used. The current set is too narrow and often countries have mandated valuesets. If HL7 wishes to create a wide Codeset which jurisdictions may subset via valuesets then that would be workable as would an example coding, but not a narrow required code.

      Attachments

        Activity

          People

            Unassigned Unassigned
            pknapp Paul Knapp
            Paul Knapp
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: