Uploaded image for project: 'CDA Specification Feedback'
  1. CDA Specification Feedback
  2. CDA-20692

Sex Observation Purpose Statement Needs to be clearer

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • C-CDA R2.1 Companion Guide (CDA)
    • 4.1.0
    • Structured Documents
    • Templates
    • Hide

      1- Add to description - use for any generic collection of sex. USCDI v3 includes a data element for sex, intended to support the exchange of sex that is not characterized as sex assigned at birth or birth sex which has been identified as a problematic in terms of quality and reliability. See Gender Harmony Project documentation. This version of the C-CDA companion guide supports USCDI v3.

      2- Do not use this for birth sex

      3- Binding at Observation/value is SHOULD to aa grouped value set contain snomed and the Administrative Gender (HL7 V3) OID: 2.16.840.1.113883.1.11.1

      4- This value MAY contain zero or one [0..1] @nullFlavor, which SHOULD be selected from ValueSet Asked but Unknown and Other urn:oid:2.16.840.1.113762.1.4.1114.17 DYNAMIC

      5 - If value.code is not snomed, then value.translation.code must be from the snomed Sex value set 2.16.840.1.113762.1.4.1099.53

      Show
      1- Add to description - use for any generic collection of sex. USCDI v3 includes a data element for sex, intended to support the exchange of sex that is not characterized as sex assigned at birth or birth sex which has been identified as a problematic in terms of quality and reliability. See Gender Harmony Project documentation. This version of the C-CDA companion guide supports USCDI v3. 2- Do not use this for birth sex 3- Binding at Observation/value is SHOULD to aa grouped value set contain snomed and the Administrative Gender (HL7 V3) OID: 2.16.840.1.113883.1.11.1 4- This value MAY contain zero or one [0..1] @nullFlavor, which SHOULD be selected from ValueSet Asked but Unknown and Other urn:oid:2.16.840.1.113762.1.4.1114.17 DYNAMIC 5 - If value.code is not snomed, then value.translation.code must be from the snomed Sex value set 2.16.840.1.113762.1.4.1099.53
    • Gay Dolin / Lisa Nelson : 11-0-1
    • Enhancement
    • Compatible, substantive

    Description

      The purpose statement for the Sex Observation needs to be clearer. It needs to explain the relationship between recordTarget.administrativeGender and itself.  Do these data element concepts represent the same information?  Does Sex Observation hold "the recorded administrative gender" of the patient as it is entered by the clinician or patient on a data entry screen or form at a point in time? And, is the recordTarget.administrativeGender information in the header information that systematically populated into the document header through the use of prior recorded Sex Observation information or other information for easy indexing and use in patient matching algorithms?

      In C-CDA and US Core we now have 3 places for basic "Sex/Gender" information.  Can you just be clear in the Sex Observation purpose statement how they are different or the same?

      I think a lot of implementers are going to get confused by the three very similar spots in the model, so over communicating and very specific instructions explaining how all three are intended/expected to function together over time would be useful.

      Consult with recent comments provided by Gender Harmony group on the HTI-1 Rule regarding the Patient.extension.sex data element and align with the nuanced clarity they have provided on the difference between data elements that are entered by end-users and data elements that are system generated (not entered by a user).

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            LisaRNelson Lisa R. Nelson
            Lisa R. Nelson
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: