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

May Patient.gender be used to represent other kinds of gender?

    XMLWordPrintableJSON

Details

    • Icon: Technical Correction Technical Correction
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • Patient
    • 8.1.7
    • Hide

      The Patient Gender notes on patient will be updated to the following:

      Patient Gender and Sex

      Many systems and organizations only provide for a single attribute that aspires to represent all aspects of a patient's gender and sex with a single value. However there are many considerations around sex and gender documentation and interoperability. Listed below are the various social and biological attributes that are relevant in the healthcare setting, as well as information on how each can communicated.

        • Administrative Gender* - in order to interoperate with systems that use a single generic property, the basic Patient.gender property attempts to represent an administrative gender: the gender that the patient is considered to have for administration and record keeping purposes. This property is often used as an input to patient matching algorithms, for example.

      In addition to this administrative gender, other kinds of gender or sex properties may be represented:

        • Clinical Sex* - a testable observation about a biological property of the patient. There are several different types of clinical sex, including karyotypic/genetic/chromosomal, gonadal, ductal, phenotypic, etc. Clinical sex observations should be represented using Observation, qualified with the appropriate clinical codes from LOINC and/or SNOMED.
        • Clinical Gender* - an observation about the patient, often collected as part of social history documentation, and represented as an Observation using, for example, the LOINC code 76691-5). Clinical gender observations can provide both history and confidentiality, where the genderIdentity extension does not.
        • Gender Identity* - an indication from the patient about what gender they consider themselves to be. This can influence how the patient prefers to be addressed by care providers and other individuals. The standard genderIdentity extension may be used to communicate this property. This extension is appropriate when the gender identity is openly known.
        • Sex assigned at Birth* - the sex assigned at birth, as documented on the birth registration. Some countries allow variations such as not yet determined, unknown, or undifferentiated, while others do not. Some countries also allow birth registration information to be updated. The US realm defines a US Specific extension for this property.
        • Legal Sex* - regional and national entities often categorize citizens using a single legal sex value. The legal sex of a patient can vary from region to region and country to country. A single patient may have multiple legal sex values at the same time in different jurisdictions. In case where the Patient.gender administrative property is not sufficient to communicate legal sex, realm specific extensions should be used.

      For veterinary use, the animal extension also includes the genderStatus which indicates sterility information.

      Show
      The Patient Gender notes on patient will be updated to the following: Patient Gender and Sex Many systems and organizations only provide for a single attribute that aspires to represent all aspects of a patient's gender and sex with a single value. However there are many considerations around sex and gender documentation and interoperability. Listed below are the various social and biological attributes that are relevant in the healthcare setting, as well as information on how each can communicated. Administrative Gender* - in order to interoperate with systems that use a single generic property, the basic Patient.gender property attempts to represent an administrative gender: the gender that the patient is considered to have for administration and record keeping purposes. This property is often used as an input to patient matching algorithms, for example. In addition to this administrative gender, other kinds of gender or sex properties may be represented: Clinical Sex* - a testable observation about a biological property of the patient. There are several different types of clinical sex, including karyotypic/genetic/chromosomal, gonadal, ductal, phenotypic, etc. Clinical sex observations should be represented using Observation, qualified with the appropriate clinical codes from LOINC and/or SNOMED. Clinical Gender* - an observation about the patient, often collected as part of social history documentation, and represented as an Observation using, for example, the LOINC code 76691-5 ). Clinical gender observations can provide both history and confidentiality, where the genderIdentity extension does not. Gender Identity* - an indication from the patient about what gender they consider themselves to be. This can influence how the patient prefers to be addressed by care providers and other individuals. The standard genderIdentity extension may be used to communicate this property. This extension is appropriate when the gender identity is openly known. Sex assigned at Birth* - the sex assigned at birth, as documented on the birth registration. Some countries allow variations such as not yet determined, unknown, or undifferentiated, while others do not. Some countries also allow birth registration information to be updated. The US realm defines a US Specific extension for this property. Legal Sex* - regional and national entities often categorize citizens using a single legal sex value. The legal sex of a patient can vary from region to region and country to country. A single patient may have multiple legal sex values at the same time in different jurisdictions. In case where the Patient.gender administrative property is not sufficient to communicate legal sex, realm specific extensions should be used. For veterinary use, the animal extension also includes the genderStatus which indicates sterility information.
    • Brian Postlethwaite/Cooper Thompson:7-0-0
    • Non-substantive
    • STU3

    Description

      [quote] ... The basic gender included in Patient.gender has a limited use, that of the administrative gender: the gender that the patient is considered to have for administration and record keeping purposes. * In addition, to * this gender, other kinds of gender may be represented:... [/quote]

      Potential Typo:

      "In addition*, to" --> In addition *to ?

      Question:

      May Patient.gender be used to represent other kinds of gender in addition to this basic gender?

      Attachments

        Activity

          People

            Unassigned Unassigned
            linzhang Lin Zhang (Inactive)
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: