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

Improve sub-organization modularity for Recorded Sex or Gender

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Cross Paradigm Gender Harmony - Sex and Gender Representation (OTHER)
    • Terminology Infrastructure
    • 2.3 Recorded Sex or Gender Template [deprecated]
    • Hide

      The current implementation uses inlined constraints on an observation for Jurisdiction of sub observation organization - This can cause issues during implementation and we will create a corresponding template with unique template id

       

      Show
      The current implementation uses inlined constraints on an observation for Jurisdiction of sub observation organization - This can cause issues during implementation and we will create a corresponding template with unique template id  
    • Rob McClure / John D'Amore : 12-0-0
    • Enhancement
    • Compatible, substantive

      The Recorded Sex or Gender template has several observations contained with entryRelationships like:

      Jurisdiction is the organization that issued the document and therefore defines the concept.
      Typically a state or nation, but possibly a firm or professional society.
      10. MAY contain zero or one [0..1] entryRelationship (CONF:4536-107) such that it
      a. SHALL contain exactly one [1..1] observation (CONF:4536-108).
      i. This observation SHALL contain exactly one [1..1] @classCode="OBS"
      Observation (CodeSystem: HL7ActClass
      urn:oid:2.16.840.1.113883.5.6) (CONF:4536-110).
      ii. This observation SHALL contain exactly one [1..1] @moodCode="EVN" Event
      (CodeSystem: HL7ActMood urn:oid:2.16.840.1.113883.5.1001)
      (CONF:4536-111).
      iii. This observation SHALL contain exactly one [1..1] code="77969-4"
      Jurisdiction code (CodeSystem: LOINC urn:oid:2.16.840.1.113883.6.1)
      (CONF:4536-109).
      iv. This observation SHALL contain exactly one [1..1] statusCode="complete"
      Completed (CodeSystem: HL7ActStatus
      urn:oid:2.16.840.1.113883.5.14) (CONF:4536-112).
      v. This observation SHALL contain exactly one [1..1] value with @xsi:type="CD"
      (CONF:4536-113).
      1. This value MAY contain zero or one [0..1] originalText (CONF:4536-
      114).

      It would be much more readable and maintainable to create separate templates for these, the way the C-CDA IG does. That is, we'd have something like:

      10. MAY contain zero or one [0..1] entryRelationship (CONF:4536-107) such that it
      a. SHALL contain exactly one [1..1] Jurisdiction Observation (CONF:4536-108).

      And then move the observation details (and description) to a new entry-level observation template. The same would go for document type, date of entry, and patient record type.

            seanmuir Sean Muir
            mszczepa Matt Szczepankiewicz
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: