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

Person.gender Paitent.gender (administrative gender coding)

    XMLWordPrintableJSON

Details

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

      This value covers the Administrative Gender only, and as provided in the examples, we are able to handle the 80% and support extensions for finer detail where desired.

      This keeps things simple for one of the key attributes for identification. And the text of this code is not what would be displayed on a user interface anyway.

      This name is also quite clear about which value "U" is, unknown, not unidentified.

      Show
      This value covers the Administrative Gender only, and as provided in the examples, we are able to handle the 80% and support extensions for finer detail where desired. This keeps things simple for one of the key attributes for identification. And the text of this code is not what would be displayed on a user interface anyway. This name is also quite clear about which value "U" is, unknown, not unidentified.
    • Brian Postlethwaite/Peter Bernhardt: 4-0-0
    • Correction

    Description

      The fact that FHIR requires "male" and "female" means that every system that already implements with coded gender as coded term (e.g. M, F) will have to map to a text value. This both a problem national localization issue (because FHIR favors English) but also backwards compatibilty issue. Recommendation: allow coded gender to be use either in place of or alongside the label.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ioana13 Ioana Singureanu
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: