FamilyMemberHistory.gender should be mapped to AdminitrativeGender valueset, not BirthSex valueset - STU #195

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Care
    • FamilyMemberHistory
    • 9.4.5
    • Hide

      Change the value set to PA's http://build.fhir.org/valueset-administrative-gender.html, which means the birthSex element will be bound to an AdministrativeGender value set.

      See GF#17780 for additional discussion notes.

      Patient Care is keeping a *single *birthSex element, which should ideally reflect whether the individual is genetically male or female. However, as reported information based on the knowledge of the patient or reporting friend/relative, there may be situations where the reported sex might not be totally accurate

      Show
      Change the value set to PA's http://build.fhir.org/valueset-administrative-gender.html , which means the birthSex element will be bound to an AdministrativeGender value set. See GF#17780 for additional discussion notes. Patient Care is keeping a *single *birthSex element, which should ideally reflect whether the individual is genetically male or female. However, as reported information based on the knowledge of the patient or reporting friend/relative, there may be situations where the reported sex might not be totally accurate
    • Stefan/George: 8-0-0
    • Correction
    • Compatible, substantive
    • STU3

      Existing Wording: Terminology Binding Birth Sex (Extensible)

      Proposed Wording: Terminology Binding AdministrativeGender (Extensible)

      Comment:

      FamilyMemberHistory.gender should be mapped to AdminitrativeGender valueset, not BirthSex valueset

      If there is intention to identify the documented sex (at birth) of a FamilyMember, it should be a separate BirthSex element, separate from the gender element so as not to further conflate concepts of administrative gender and clinical sex at birth

      Summary:

      FamilyMemberHistory.gender should be mapped to AdminitrativeGender valueset, not BirthSex valueset

            Assignee:
            Unassigned
            Reporter:
            Ken Sinn
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: