Uploaded image for project: 'V2 Specification Feedback'
  1. V2 Specification Feedback
  2. V2-25443

Need to separate Sex and Gender

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • V2.x Message Specification (V2)
    • V2.9
    • Infrastructure & Messaging
    • Control (Chapter 2)
    • V2.8 Chapter 2A - Control and Data Types
    • Hide

      We believe that the persuasive resolution of this partly duplicative issue, addresses much of this issue, but not all: V2-25518 Update Reference Range Administrative Sex component for Gender Harmony - Jira (hl7.org)

      The RFR data type is used to define the reference ranges in tests. It won't change over time. Similarly, the data type is an attribute of the lab test being performed.

       

       

      Show
      We believe that the persuasive resolution of this partly duplicative issue, addresses much of this issue, but not all: V2-25518 Update Reference Range Administrative Sex component for Gender Harmony - Jira (hl7.org) The RFR data type is used to define the reference ranges in tests. It won't change over time. Similarly, the data type is an attribute of the lab test being performed.    
    • Riki Merrick / Joe Kelly : 4 - 0 - 0
    • Enhancement
    • Non-substantive

      "2A.2.63.2 Administrative Sex (CWE)
      Definition: This component specifies which gender for which the reference range is valid. Refer to User-defined Table 0001 – Administrative Sex in Chapter 2C, section 3.4.2.8, "Administrative Sex" for suggested values." The area does not align with the Gender Sex Harminization work, the title says sex, yet the defintion says gender. Further the title of Administrative Sex or Gender could be offensive and outting. Need to drive the goal and seperation of gender and sex and their attributes and types and timeframes here as well. Further, implementation guide may require update dates on these attributes as the content of the attrubute can change over time for an individual. How is this update shared? It is also noted I may have two expresessed at one moment in time so categories or types or references as to when to use what where may be required and missing from the the current implementation guide. Standard may also want to consider confidentiality flags or support hiding this information from certain stakeholders and messaging flows. Implementation guide may also be missing techniques and considerations when implementing the split into their current standard. i.e. how does this implementatin guide guide to implementation of such a change?

      (Comment 24 - imported by: Ron G. Parker)

            Unassigned Unassigned
            Rongparker Ron G. Parker
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: