Uploaded image for project: 'Other Specification Feedback'
  1. Other Specification Feedback
  2. OTHER-2496

Gender Identity Table - CDA row requests

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • Cross Paradigm Gender Harmony - Sex and Gender Representation (OTHER)
    • 1.0.0-ballot
    • Structured Documents
    • STU
    • Design Considerations
    • Hide

      This ticket list MANY different issues effecting the Design Considerations tables. All the issues require changes to the CDA column, but across multiple elements. This resolution will focus only on the following RSG table changes. The other concerns will be replicated in 3 other Jira issues, linked to this ticket.

      This resolution address the following:
      Recorded Sex or Gender - make `Make value set references links
      Will make the following changes:
       * International equivalent value set - this row will be removed as this element is now removed
       * Source Type value set - Link torecorded-sex-or-gender-type

       * Designated value set -will link to Administrative Gender value set in THO

      (updated based upon typo 8/18/23)

      code.originalText - could be dataType ST (String)

      • This entry is not correct and the template will need to be updated to properly identify where to record the string representation of the original field name. What is currently included in the template is on page 13 "Patient Record Type characterizes the field containing the recorded sex or gender. If the value comes from an EHR, it may be encoded (e.g., "76689-9 sex assigned at birth"). If it comes from a paper form, put the text label in the root Observation.code.originalText, not here." This will be clarified.
      Show
      This ticket list MANY different issues effecting the Design Considerations tables. All the issues require changes to the CDA column, but across multiple elements. This resolution will focus only on the following RSG table changes. The other concerns will be replicated in 3 other Jira issues, linked to this ticket. This resolution address the following: Recorded Sex or Gender - make `Make value set references links Will make the following changes:  * International equivalent value set - this row will be removed as this element is now removed  * Source Type value set - Link to recorded-sex-or-gender-type  * Designated value set -will link to Administrative Gender value set in THO (updated based upon typo 8/18/23) code.originalText - could be dataType ST (String) This entry is not correct and the template will need to be updated to properly identify where to record the string representation of the original field name. What is currently included in the template is on page 13 "Patient Record Type characterizes the field containing the recorded sex or gender. If the value comes from an EHR, it may be encoded (e.g., "76689-9 sex assigned at birth"). If it comes from a paper form, put the text label in the root Observation.code.originalText, not here." This will be clarified.
    • Rob M / Brett M : 13-0-0
    • Correction
    • Compatible, substantive
    • Yes
    • current

      • Gender Identity Table 
      • CDA Column:
      • General:
      • what does "Responsibility of Template Container" mean?
      • Validity period/duration- change effectiveTime to effectiveTime/low and effectiveTime/high
      • Name to Use: instead of RecordTargetName, specify EntityNamePartQualifier of CL:

      PersonNamePartMiscQualifier CL (callme)        

      "A callme name is (usually a given name) that is preferred when a person is directly addressed".

      • Recorded Sex or Gender - make `Make value set references links
      • code.originalText - could be dataType ST (String)

            seanmuir Sean Muir
            GDolin Gay Dolin
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: