Page tree
Skip to end of metadata
Go to start of metadata

To accurately process the Header and Allergies sections of a C-CDA CCD, in the Clinical:AllergyCcda Data Space, certain elements are required and must contain valid information. There are also certain elements that are optional but, if present, must also contain valid information.

In the Header section, there are eight elements that are required and three elements that are optional. For more information see CCDA Header: Data Preparation Checklist.

In the Allergies section, there are three elements that are required and twelve elements that are optional

This checklist provides a description of the Allergies elements and how they should be validated prior to processing in CDS.  

The allergies section of a CCD will typically have several sub-sections to represent different observations made by a practitioner:

  • Allergy Concern
  • Allergy-Intolerance Observation
  • Reaction Observation
  • Severity Observation
  • Criticality Observation 

Each sub-section is uniquely identified by its templateId. When elements occur in multiple sub-sections (for example, valuecodeeffectiveTime), the templateId helps differentiate validation requirements.

 Section or Sub-SectionElementXPath
Required ElementsAllergy Section templateIdsection/templateId
codesection/code
Allergy Concern ActtemplateIdsection/entry/act/templateId
Optional (but validated
if present) Elements
Allergy Concern ActstatusCodesection/entry/act/statusCode
Allergy-Intolerance Observation
templateIdsection/entry/act/entryRelationship/observation/templateId
effectiveTimesection/entry/act/entryRelationship/observation/effectiveTime
valuesection/entry/act/entryRelationship/observation/value
authorsection/entry/act/entryRelationship/observation/author
playingEntitysection/entry/act/entryRelationship/observation/participant/participantRole/playingEntity
Reaction Observation
templateIdsection/entry/act/entryRelationship/observation/entryRelationship/observation/templateId
valuesection/entry/act/entryRelationship/observation/entryRelationship/observation/value
Severity Observation
templateIdsection/entry/act/entryRelationship/observation/entryRelationship/observation/templateId
valuesection/entry/act/entryRelationship/observation/entryRelationship/observation/value
Criticality Observation
templateIdsection/entry/act/entryRelationship/observation/entryRelationship/observation/templateId
valuesection/entry/act/entryRelationship/observation/entryRelationship/observation/value

A full copy of the sample Continuity of Care Document (CCD) used in this section is attached.

 


Required Elements

This section details the elements that are required for processing in Clinical Data Spaces, that is, they must be present, contain certain information, and be correct.

Allergy Section templateId

XPath:section/templateID
Purpose:

Specifies which CCDA R2.1 template is being used to structure the allergy section. R2.1 templates define the requirements, format, and structure of a CCD section. This section lists and describes any allergies, adverse relations, and intolerances to medication, food and other substances. At a minimum it lists active and any relevant historical allergies and intolerances.

The templateId element must:

  • be present

  • contain a root attribute

    AttributeValuePurpose
    rootMust have a value of 2.16.840.1.113883.10.20.22.2.6.1Uniquely identifies the allergies section template.
Code Example of Allergy Section templateId
<section>
    <templateID root="2.16.840.1.113883.10.20.22.2.6.1"/>
</section>

The entire allergy section is ignored if the templateId element is not provided with a root attribute of 2.16.840.1.113883.10.20.22.2.6.1. None of the allergies in this CCD section will be processed and you will not receive any notification that the section was ignored.

 

 

Allergy Section code

XPath:section/code
Purpose:

Identifies that this section is detailing allergy, intolerance, and adverse reaction information.

The code element must:

  • be present

  • contain code and codeSystem attributes

    AttributeValuePurpose

    code

    Must have a value of 48765-2

    Identifies that this section is detailing allergy, intolerance, and adverse reaction information.

    codeSystem

    Must have a value of 2.16.840.1.1113883.6.1

    Identifies the LOINC coding system used to translate the identifier provided in the code attribute.

    displayName and codeSystemName are not required for processing.

Code Example of Allergy Section code
<section>
    <templateID root="2.16.840.1.113883.10.20.22.6.1"/>
    <code code="48765-2" codeSystem=”2.16.840.1.113883.6.1"/> 
</section>

Processing of the code element will fail if it does not contain correctly populated code AND codeSystem attributes.

 

 

Allergy Concern Act templateId

XPath:section/entry/act/templateId
Purpose:Specifies which CCDA R2.1 template is being used to structure the allergy concern act sub-section. R2.1 templates define the requirements, format, and structure of a CCD section. This sub-section reflects the ongoing concern of a practitioner that placed this allergy on the patient's list of allergies.

The templateId element must:

  • be present

  • contain a root attribute

    AttributeValuePurpose
    rootMust have a value of 2.16.840.1.113883.10.20.22.2.4.30Uniquely identifies the allergy concern act template
Code Example of Allergy Concern Act templateId
<entry typeCode="DRIV"> 
	<act classCode="ACT" moodCode="EVN"> 
    	<templateID root="2.16.840.1.113883.10.20.22.4.30"/>
	</act>
</entry>

The entire allergy concern act sub-section is ignored if the templateId element is not provided with a root attribute of 2.16.840.1.113883.10.20.22.4.30. The information provided in this sub-section will not be processed and you will not receive any notification that this sub-section was ignored.

 

 


Optional Elements

This section details elements that are not required but if present, must contact certain information and be correct for accurate processing in Clinical Data Spaces (CDS). 

Allergy Concern Act statusCode

XPath:section/entry/act/statusCode
Purpose:

Indicates the current status of the allergy or intolerance

If present, the statusCode element must:

contain a code attribute:

AttributeValuePurpose

code

Must have one of the following:

  • completed
  • aborted
  • active
  • suspended

Indicates the current status of the allergy or intolerance. Specifically, active indicates that the allergy is an ongoing concern and completed indicates that the allergy is no longer a going concern. 

Code Example of Allergy Concern Act templateId
<entry typeCode="DRIV">
	<act classCode="ACT" moodCode="EVN"> 
    	<templateID root="2.16.840.1.113883.10.20.22.4.30"/>
    	<statusCode code="active"/>
	</act> 
</entry>

Processing of the statusCode element will fail if it does not contain a correctly populated code attribute.

 

 

Allergy-Intolerance Observation templateId

XPath:section/entry/act/entryRelationship/observation/templateId
Purpose:

Specifies which CCDA R2.1 template is being used to structure the allergy-intolerance sub-section. R2.1 templates define the requirements, format, and structure of a CCD section. This sub-section details a discrete observation about a patient's allergy or intolerance.

If present, the templateId element must:
  • be contained within an entryRelationship element with a typeCode attribute of "SUBJ"
  • have a parent element of observation
  • contain a root attribute:
AttributeValuePurpose

root

2.16.840.1.113883.10.20.22.4.7

Uniquely identifies the allergy-intolerance observation template

Code Example of Allergy-Intolerance Observation templateId
<entry typeCode="DRIV">
	<act classCode="ACT" moodCode="EVN">
		<entryRelationship typeCode="SUBJ">
    		<observation classCode="OBS" moodCode="EVN">
        		<templateId root="2.16.840.1.1113883.10.20.22.4.7"/>
    		</observation>
		</entryRelationship>
	</act>
</entry>

The entire allergy-intolerance observation sub-section is ignored if the templateId element is not provided with a root attribute of 2.16.840.1.113883.10.20.22.4.7. The information provided in this sub-section will not be processed and you will not receive any notification that this sub-section was ignored.

 

 

Allergy-Intolerance Observation effectiveTime

XPath:section/entry/act/entryRelationship/observation/effectiveTime
Purpose:

Specifies the onset date, duration, and resolution date (if known) of an allergy or intolerance. Also referred to as the "biologically relevant time". It is the definitive indication within a CCD of whether or not the allergy or intolerance has been resolved.

If present, the effectiveTime element must:
  • be contained within an entryRelationship element with a typeCode attribute of "SUBJ", which has a templateId of: 2.16.840.1.113883.10.20.22.4.7
  • have a parent element of observation
  • contain an attribute of xsi:type, value or nullFlavor

    AttributeValuePurpose
    xsi:type

    Must be populated with IVL_TS and effectiveTime must:

    1. have a low child element, which can be:
      • empty
      • have a nullFlavor attribute
      • have a value attribute indicating a specific date and time
    2. optionally have a high child element which can be:
      • empty
      • have a nullFlavor attribute
      • have a value attribute indicating a specific date and time
    Indicates the period over which the allergy has occurred. Low indicates the onset date (when the allergy first became active) and high specifies when the allergy or intolerance was known to be resolved. If high is not present, the allergy or intolerance is still active.
    valueMust be populated with a date in the format YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ] where +/-ZZZZspecifies the offset from Coordinated Universal Time. Onset date. Specifies when the allergy first became active.
    nullFlavor

    Must be one of the following:

    • ASKU - asked but unknown
    • MSK - masked (for sensitivity or confidentiality reasons)
    • NA - not available, system down
    • NASK - not asked
    • NAV - not available
    • NI - no information
    • OTH - other
    • UNK - unknown 
    Indicates that an attribute was needed, but was not provided, and gives a reason for why the information is not present. In this case, it suggests that the allergy or intolerance was resolved, but it was not recorded when.
Code Example of Allergy-Intolerance Observation effectiveTime
<entry typeCode="DRIV">
	<act>
		<entryRelationship typeCode="SUBJ">
   			 <observation classCode="OBS" moodCode="EVN">
       			<templateId root="2.16.840.1.1113883.10.20.22.4.7"/>
					<effectiveTime>
							<low value="20110215"/>
					</effectiveTime>
   			 </observation>
		</entryRelationship>
	</act>
</entry>

Processing of the effectiveTime element will fail if it does not contain a correctly populated xsi:typevalue or nullFlavor attribute.

 

 

Allergy-Intolerance Observation value

XPath:section/entry/act/entryRelationship/observation/value
Purpose:

Specifies the category of allergen or substance of intolerance.

If present, the value element must:
  • be contained within an entryRelationship element with a typeCode attribute of "SUBJ" which has a templateId of: 2.16.840.1.113883.10.20.22.4.7
  • have a parent element of observation
  • contain xsi:type, code and codeSystem attributes:

    AttributeValuePurpose
    xsi:typeCDIndicates that the value element is providing code and codeSystem information
    code

    Must include an alphanumeric string of any length. For example:

    • 419199007 - Allergy to substance
    • 416908002 - Drug allergy
    • 59037007 - Drug intolerance
    • 414285001 - Food allergy 
    • 235719002 - Food intolerance
    • 420134006 - Propensity to adverse reactions 
    • 41951103 - Propensity to adverse reactions to drug
    • 418471000 - Propensity to adverse reactions to food
    • 418038007 - Propensity to adverse reactions to substance
    Identifies the specific category of allergy or intolerance in the coding system.
    codeSystemMust have a value of 2.16.840.1.113883.6.96Identifies the SNOMED CT coding system used to translate the identifier provided in the code attribute

    displayName and codeSystemName are not required for processing in Clinical Data Spaces.

    For accurate processing, we except to see code with code and codeSystem attributes, as documented above. However <value nullFlavor="UNK"/> or <value nullFlavor="OTH"/> is acceptable.

    If value is populated with nullFlavor="OTH", a child element of translation must be present and contain code and codeSystem attributes. Clinical Data Spaces will process the information provided here instead.

Code Example of Allergy-Intolerance Observation value
<entry typeCode="DRIV">
	<act>
		<entryRelationship typeCode="SUBJ">
    		<observation classCode="OBS" moodCode="EVN">
       			<templateId root="2.16.840.1.1113883.10.20.22.4.7"/>
        		<value xsi:type="CD" code="416098002" displayName="drug allergy" codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT"/>
   		 	</observation>
		</entryRelationship>
	</act>
</entry>

Processing of the value element will fail if it does not contain correctly populated xsi:typecode and codeSystem attributes.

 

 

Allergy-Intolerance Observation author

XPath:section/entry/act/entryRelationship/observation/author
Purpose:Indicates the unique identifier of the person observing the allergy or intolerance, or the person adding notes to the document about the allergy.
If an author element is present, it must
  • be contained within an entryRelationship element with a typeCode attribute of "SUBJ", which has a templateId with of: 2.16.840.1.113883.10.20.22.4.7
  • have a parent element of observation
  • have a child element of assignedAuthor, which must
  • have a child element of id, which must
  • contain a root attribute and optionally contain an extension attribute

    AttributeValuePurpose
    root

    Must include an alphanumeric string in an OID (object identifier) or UUID (universally unique identifier) format. 

    For example, OID: 2.16.840.1.1113883.x.xx.x  or  UUID: 53459040-b1b4-49ed-ae1f-a52c8c502df4

    Uniquely identifies the author of the current allergy-intolerance observation entry

    extension

    Is optional and can include an alphanumeric string of any length

    Uniquely identifies the author of the current allergy-intolerance observation entry

Code Example of Allergy-Intolerance Observation author
<entry typeCode="DRIV">
	<act> 
		<entryRelationship typeCode="SUBJ">
			<observation classCode="OBS" moodCode="EVN">
				<templateId root="2.16.840.1.1113883.10.20.22.4.7"/>\
				<author>
					<assignedAuthor>
						<id extension="222223333" root="2.16.840.1.113883.4.6"/>
					</assignedAuthor>
				</author>
			</observation>
		</entryRelationship>
	</act>
</entry>

The author element and its contents will be ignored if the id element does not contain a correctly populated root attribute. Information provided within the author element in the document header will be processed instead.

 

 

Allergy-Intolerance Observation playingEntity

XPath:section/entry/act/entryRelationship/observation/participant/participantRole/playingEntity
Purpose:

Specifies the agent or substance which caused the allergic or adverse reaction.

If present, the playingEntity element must:
  • be contained within an entryRelationship element with a typeCode attribute of "SUBJ", which has a templateId of: 2.16.840.1.113883.10.20.22.4.7
  • have a parent element of participantRole
  • have a child element of code, which must
  • contain a code and codeSystem attribute

    AttributeValuePurpose
    code

    Must include an alphanumeric string of any length.

    Identifies the agent or substance which caused the allergic or adverse reaction.
    codeSystem

    Must include a numeric string of any length in the following format: 2.16.840.1.1113883.X.XX.X.X.

    Typically, agents or substances are determined by one of the following code systems:

    • 2.16.840.1.11388.3.6.88 (RxNorm)
    • 2.16.840.1.113883.3.26.1.5 (NDFRT)
    • 2.16.840.1.113883.4.9 (UNII) 
    Identifies the coding system used to translate the identifier provided in the code attribute

    displayName and codeSystemName are not required for processing in Clinical Data Spaces.

Code Example of Allergy-Intolerance Observation playingEntity
<entry typeCode="DRIV">
	<act>
		<entryRelationship typeCode="SUBJ">
			<observation classCode="OBS" moodCode="EVN">
				<templateId root="2.16.840.1.1113883.10.20.22.4.7"/>
				<participant typeCode="CSM">
					<participantRole classCode="MANU">
						<playingEntity classCode="MMAT">
							<code code="314422" displayName="ALLERGENIC EXTRACT, PENICILLIN" codeSystem="2.16.840.1.113883.6.88" codeSystemName="RxNorm"/>
						</playingEntity>
					</participantRole>
				</participant>
			</observation>
		</entryRelationship> 
	</act>
</entry>

Processing of the playingEntity element will fail if it does not contain a code element with correctly populated code and codeSystem attributes.

 

 

Reaction Observation templateId

XPath:section/entry/act/entryRelationship/observation/entryRelationship/observation/templateId
Purpose:

Specifies which CCDA R2.1 template is being used to structure the reaction observation sub-section. R2.1 templates define the requirements, format, and structure of a CCD section. This sub-section describes the specific allergy symptoms or adverse reaction observed.

If present, the templateId element must:
  • be contained within an entryRelationship element with a typeCode attribute of "MFST"
  • have a parent element of observation
  • contain a root attribute

    AttributeValuePurpose

    root

    2.16.840.1.113883.10.20.22.4.9

    Uniquely identifies the template which describes the reaction of the allergy or intolerance.

Code Example of Reaction-Observation templateId
<entry typeCode="DRIV"> 
	<act classCode="ACT" moodCode="EVN"> 
		<entryRelationship typeCode="SUBJ">
			<observation>
				<templateId root="2.16.840.1.113883.10.20.22.4.7"/>					
				<entryRelationship typeCode="MFST">
					<observation>
						<templateId root="2.16.840.1.113883.10.20.22.4.9"/>
					</observation>
				</entryRelationship>
			</observation>
		</entryRelationship> 
	</act> 
</entry> 

The entire Reaction Observation sub-section will be ignored if the templateId does not have a root attribute of 2.16.840.1.113883.10.20.22.4.9. You will not receive a notification that the sub-section was ignored.

 

 

Reaction Observation value

XPath:section/entry/act/entryRelationship/observation/entryRelationship/observation/value
Purpose:

Specifies the type of allergic or adverse reaction.

If present, the value element must:
  • be contained within an entryRelationship element with a typeCode attribute of "MFST", which has a templateId of: 2.16.840.1.113883.10.20.22.4.9
  • have a parent element of observation
  • contain xsi:type, code and codeSystem attributes:

    AttributeValuePurpose
    xsi:typeCDIndicates that the value element is providing code and codeSystem information

    code

    Must be an alphanumerical string of any length. For example:

    • 247472004 - Hives
    • 39579001 - Anaphylaxis
    • 129851009 - Alteration in comfort: pain 

    Identifies the specific reactive symptom (or problem) presented in this particular instance of the allergic reaction.

    codeSystemMust have a value of 2.16.840.1.113883.6.96Identifies the SNOMED CT coding system used to translate the identifier provided in the code attribute

    displayName and codeSystemName are not required for processing in Clinical Data Spaces.

    For accurate processing, we except to see code with code and codeSystem attributes, as documented above. However <value nullFlavor="UNK"/> or <value nullFlavor="OTH"/> is acceptable.

    If value is populated with nullFlavor="OTH", a child element of translation must be present and contain code and codeSystem attributes. Clinical Data Spaces will process the information provided here instead.

Code Example of Reaction Observation value
<entry typeCode="DRIV"> 
	<act classCode="ACT" moodCode="EVN"> 
		<entryRelationship typeCode="SUBJ">
			<observation>
				<templateId root="2.16.840.1.113883.10.20.22.4.7"/>
				<entryRelationship typeCode="MFST">
					<observation>
						<templateId root="2.16.840.1.113883.10.20.22.4.9"/>
						<value xsi:type="CD" code="247472004" codeSystem="2.16.840.1.113883.6.96" displayName="Hives"/>
					</observation>
				</entryRelationship>
			</observation>
		</entryRelationship>	
	</act> 
</entry> 

Processing of the value element will fail if it does not contain correctly populated xsi:type, code and codeSystem attributes.

 

 

Severity Observation templateId

XPath:section/entry/act/entryRelationship/observation/entryRelationship/observation/templateId
Purpose:

Specifies which CCDA R2.1 template is being used to structure the severity observation sub-section. R2.1 templates define the requirements, format, and structure of a CCD section. This sub-section describes the severity of the allergy or intolerance.

If present, the templateId element must:
  • be contained within an entryRelationship element with a typeCode attribute of "SUBJ"
  • have a parent element of observation
  • contain a root attribute

    AttributeValuePurpose

    root

    2.16.840.1.113883.10.20.22.4.8

    Uniquely identifies the template which describes the severity of the allergy or intolerance.

Code Example of Severity Observation templateId
<entry typeCode="DRIV"> 
	<act classCode="ACT" moodCode="EVN"> 
		<entryRelationship typeCode="SUBJ">
			<observation>
				<templateId root="2.16.840.1.113883.10.20.22.4.7"/>
				<entryRelationship typeCode="SUBJ">
					<observation>
						<templateId root="2.16.840.1.113883.10.20.22.4.8"/>
					</observation>
				</entryRelationship>
			</observation>
		</entryRelationship>	
	</act> 
</entry> 

The entire Severity Observation sub-section will be ignored if the templateId does not have a root attribute of 2.16.840.1.113883.10.20.22.4.8. You will not receive a notification that the sub-section was ignored.

 

 

Severity Observation value

XPath:section/entry/act/entryRelationship/observation/entryRelationship/observation/value
Purpose:

Specifies the level of severity of the allergic or adverse reaction.

If present, the value element must:
  • be contained within an entryRelationship element with a typeCode attribute of "SUBJ" which has a templateId of: 2.16.840.1.113883.10.20.22.4.8
  • have a parent element of observation
  • contain xsi:type, code and codeSystem attributes:

    AttributeValuePurpose
    xsi:typeCDIndicates that the value element is providing code and codeSystem information

    code

    Must be an alphanumerical string of any length. For example:

    • 255604002 - Mild
    • 371923003 - Mild to moderate
    • 6736007 - Moderate
    • 371924009 - Moderate to severe
    • 24484000 - Severe
    • 399166001 - Fatal

    Identifies the severity of the allergic or adverse reaction.

    codeSystemMust have a value of 2.16.840.1.113883.6.96Identifies the SNOMED CT coding system used to translate the identifier provided in the code attribute

    displayName and codeSystemName are not required for processing in Clinical Data Spaces.

    For accurate processing, we except to see code with code and codeSystem attributes, as documented above. However <value nullFlavor="UNK"/> or <value nullFlavor="OTH"/> is acceptable.

    If value is populated with nullFlavor="OTH", a child element of translation must be present and contain code and codeSystem attributes. Clinical Data Spaces will process the information provided here instead.

Code Example of Severity Observation value
<entry typeCode="DRIV"> 
	<act classCode="ACT" moodCode="EVN"> 
		<entryRelationship typeCode="SUBJ">
			<observation>
				<templateId root="2.16.840.1.113883.10.20.22.4.7"/>
				<entryRelationship typeCode="SUBJ">
					<observation>
						<templateId root="2.16.840.1.113883.10.20.22.4.8"/>
						<value xsi:type="CD" code="371924009" displayName="Moderate to severe" codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT"/>
					</observation>
				</entryRelationship>
			</observation>
		</entryRelationship>	
	</act> 
</entry> 



Processing of the value element will fail if it does not contain correctly populated xsi:type, code and codeSystem attributes.

 

 

Criticality Observation templateId

XPath:section/entry/act/entryRelationship/observation/entryRelationship/observation/templateId
Purpose:

Specifies which CCDA R2.1 template is being used to structure the section detailing the criticality of a potential allergic or adverse reaction. This template controls which elements and attributes are required and specifies their expected formats. This sub-section determines the potential risk for life-threatening reactions when a patient is exposed to the allergen or reactive substance.

If present, the templateId element must:
  • be contained within an entryRelationship element with a typeCode attribute of "SUBJ"
  • have a parent element of observation
  • contain a root attribute

    AttributeValuePurpose

    root

    2.16.840.1.113883.10.20.22.4.145

    Uniquely identifies the template which describes the criticality of a potential allergic or adverse reaction.

Code Example of Criticality Observation templateId
<entry typeCode="DRIV"> 
	<act classCode="ACT" moodCode="EVN"> 
		<entryRelationship typeCode="SUBJ">
			<observation>
				<templateId root="2.16.840.1.113883.10.20.22.4.7"/>
				<entryRelationship typeCode="SUBJ">
					<observation>
						<templateId root="2.16.840.1.113883.10.20.22.4.145"/>
					</observation>
				</entryRelationship>
			</observation>
		</entryRelationship>	
	</act> 
</entry> 

The entire Criticality Observation sub-section will be ignored if the templateId does not have a root attribute of 2.16.840.1.113883.10.20.22.4.145. You will not receive a notification that the sub-section was ignored.

 

 

Criticality Observation value

XPath:section/entry/act/entryRelationship/observation/entryRelationship/observation/value
Purpose:

Specifies the level of criticality of the allergy or intolerance.

If present, the value element must:
  • be contained within an entryRelationship element with a typeCode attribute of "SUBJ" which has a templateId of: 2.16.840.1.113883.10.20.22.4.145
  • have a parent element of observation
  • contain xsi:type, code and codeSystem attributes

    AttributeValuePurpose
    xsi:typeCDIndicates that the value element is providing code and codeSystem information

    code

    Must be an alphanumerical string of any length. For example:

    • CRITL - Low criticality
    • CRITH - High criticality
    • CRITU - Unable to assess criticality

    Identifies the criticality of the allergic or adverse reaction.

    codeSystemMust have a value of 2.16.840.1.113883.5.1063
    Identifies the Observation Value coding system used to translate the identifier provided in the code attribute

    displayName and codeSystemName are not required for processing in Clinical Data Spaces.

    For accurate processing, we except to see code with code and codeSystem attributes, as documented above. However <value nullFlavor="UNK"/> or <value nullFlavor="OTH"/> is acceptable.

    If value is populated with nullFlavor="OTH", a child element of translation must be present and contain code and codeSystem attributes. Clinical Data Spaces will process the information provided here instead.

Code Example of Criticality Observation value
<entry typeCode="DRIV"> 
	<act classCode="ACT" moodCode="EVN"> 
		<entryRelationship typeCode="SUBJ">
			<observation>
				<templateId root="2.16.840.1.113883.10.20.22.4.7"/>
				<entryRelationship typeCode="SUBJ">
					<observation>
						<templateId root="2.16.840.1.113883.10.20.22.4.145"/>
						<value xsi:type="CD" code="CRITH" displayName="High Criticality" codeSystem="2.16.840.1.11388 3.5.1063" codeSystemName="LOINC"/>
					</observation>
				</entryRelationship>
			</observation>
		</entryRelationship>	
	</act> 
</entry>   

Processing of the value element will fail if it does not contain correctly populated xsi:type, code and codeSystem attributes.

 

  • No labels