Data elements highlighted in HL7 CDA documents

When you use a HL7 CDA Data Analysis profile to analyze HL7 CDA documents, specific data elements are highlighted in the HL7 CDA documents.

The following table details the data elements that are highlighted, the attributes that are analyzed, and the code sets that are used to replace the attribute values with meaningful names, when you use a HL7 CDA (Clinical Document Architecture) Data Analysis profile to analyze HL7 CDA documents.

Identifying element name Attribute analyzed Code set
participant typeCode HL7 Participant Type (2.16.840.1.113883.5.90)
performer typeCode HL7 Participant Type (2.16.840.1.113883.5.90)
Any element with a child element named templateId root IHE templates
  • Discharge Summary (1.3.6.1.4.1.19376.1.5.3.1.1.4)
  • Medical Document (1.3.6.1.4.1.19376.1.5.3.1.1.1)
  • Medical Summary (1.3.6.1.4.1.19376.1.5.3.1.1.2)
  • PHR Extract (1.3.6.1.4.1.19376.1.5.3.1.1.5)
  • PHR Update (1.3.6.1.4.1.19376.1.5.3.1.1.6)
CCD templates (2.16.840.1.113883.10)
Sections
  • Advance directives (2.16.840.1.113883.10.20.1.1)
  • Alerts (2.16.840.1.113883.10.20.1.2)
  • Encounters (2.16.840.1.113883.10.20.1.3)
  • Family history (2.16.840.1.113883.10.20.1.4)
  • Functional status (2.16.840.1.113883.10.20.1.5)
  • Immunizations (2.16.840.1.113883.10.20.1.6)
  • Medical equipment (2.16.840.1.113883.10.20.1.7)
  • Medications (2.16.840.1.113883.10.20.1.8)
  • Payers (2.16.840.1.113883.10.20.1.9)
  • Plan of care (2.16.840.1.113883.10.20.1.10)
  • Problem (2.16.840.1.113883.10.20.1.11)
  • Procedures (2.16.840.1.113883.10.20.1.12)
  • Purpose (2.16.840.1.113883.10.20.1.13)
  • Results (2.16.840.1.113883.10.20.1.14)
  • Social history (2.16.840.1.113883.10.20.1.15)
  • Vital signs (2.16.840.1.113883.10.20.1.16)
Clinical Statements
  • Advance directive observation (2.16.840.1.113883.10.20.1.17)
  • Alert observation (2.16.840.1.113883.10.20.1.18)
  • Authorization activity (2.16.840.1.113883.10.20.1.19)
  • Coverage activity (2.16.840.1.113883.10.20.1.20)
  • Encounter activity (2.16.840.1.113883.10.20.1.21)
  • Family history observation (2.16.840.1.113883.10.20.1.22)
  • Family history organizer (2.16.840.1.113883.10.20.1.23)
  • Medication activity (2.16.840.1.113883.10.20.1.24)
  • Plan of care activity (2.16.840.1.113883.10.20.1.25)
  • Policy activity (2.16.840.1.113883.10.20.1.26)
  • Problem act (2.16.840.1.113883.10.20.1.27)
  • Problem observation (2.16.840.1.113883.10.20.1.28)
CTD templates
  • Consultation Note (2.16.840.1.113883.10.20.4)
  • General Header Constraints (2.16.840.1.113883.10.20.3)
  • History And Physical (2.16.840.1.113883.10.20.2)
  • Level One Conformance (2.16.840.1.113883.10.20.10)
  • Level Two Conformance (2.16.840.1.113883.10.20.20)
  • Level Three Conformance (2.16.840.1.113883.10.20.30)
  • Progress Note (2.16.840.1.113883.10.20.21.1)
HITSP templates (C32, C83, and C80)
  • Discharge Summary (2.16.840.1.113883.3.88.11.48.2)
  • Patient Summary (2.16.840.1.113883.3.88.11.32.1)
  • Referral Summary (2.16.840.1.113883.3.88.11.48.1)
  • Unstructured Document (2.16.840.1.113883.3.88.11.62.1)
  • Unstructured or Scanned Document (2.16.840.1.113883.10.20.19.1)
Any element with a child element named code.

There are many examples in CDA documents where an element has child elements that are called templateId and code. In these instances, both forms of identification are displayed in the Data Analysis Model.

Common examples of dual highlighting include section, observation, act, organizer, encounter, participant, manufacturedProduct, substanceAdministration, supply, procedure and participantRole.

code The code system is contained in the document element itself in an attribute called codeSystem.

A code system that contains the value 2.16.840.1.113883.6.1 identifies the code as being a LOINC code. To resolve LOINC codes, the LOINC glossary must be configured. For information about configuring the LOINC glossary, see Analyzing healthcare data in message flows

observation classCode Pre-defined codes:
  • OBS observation
  • COND condition
organizer classCode Pre-defined codes:
  • CLUSTER cluster
  • BATTERY battery
specimenRole classCode Pre-defined codes:
  • SPEC specimen
  • ISLT isolate
addr use Pre-defined codes:
  • HP permanent home address
  • H home address
  • HV vacation home address
  • WP work place address
  • DIR direct work place address
  • PUB public work place address
  • BAD bad address
  • TMP temporary address
entryRelationship typeCode HL7 Act Relationship codes (2.16.840.1.113883.5.1002)
associatedEntity classCode HL7 Role Class codes (2.16.840.1.113883.5.110)
entry typeCode HL7 Act Relationship codes (2.16.840.1.113883.5.1002)
reference typeCode HL7 Act Relationship codes (2.16.840.1.113883.5.1002)
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 2011, 2013Copyright IBM Corporation 2011, 2013.

        
        Last updated
        
        Last updated : 2013-03-18 14:27:10


Reference topicReference topic | Version 8.0.0.0 | ha05330