Consolidated CDA (C-CDA), published by Health Level Seven. This guide is not an authorized publication; it is the continuous build for version 4.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/CDA-ccda/ and changes regularly. See the Directory of published versions
This content is an example of the Entry Reference Logical Model and is not a FHIR Resource
<!-- Show how an encounter can include a discharge diagnosis which references an
item on the problem list using the Entry Reference template.
The primary example is the act reference itself -->
<act classCode="ACT" moodCode="EVN" xmlns="urn:hl7-org:v3">
<templateId root="2.16.840.1.113883.10.20.22.4.122" />
<id root="R1234567" />
<code nullFlavor="NP" />
<text><reference value="#dischargeDiagnosisReference"/></text>
<statusCode code="completed"/>
</act>
<!-- The following demonstrates how this ID may exist elsewhere
An entry in the problem's section:
<observation>
<id root="R1234567" />
<code code="123" codeSystem="1.2.3" displayName="asthma" />
</observation>
The encounter entry which contains an entry references
This is for illustrative purposes only. In this particular
case, the template requires a nested Problem
Observation. In the Health Concern template,
we'd need a constraint that says it's allowable to
include the Entry Reference template.
<encounter xmlns="urn:hl7-org:v3">
<entryRelationship typeCode="COMP">
<act>
<code code="145" codeSystem="4.5.6" displayName="discharge diagnosis" />
<templateId root="2.16.840.1.113883.10.20.22.4.33" extension="2014-06-09" />
...
<entryRelationship typeCode="SUBJ">
<act classCode="ACT" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.22.4.122" />
<id root="R1234567" />
<code nullFlavor="NP" />
</act>
</entryRelationship>
</act>
</entryRelationship>
</encounter>-->