Id1.3.182.11.10.3.5Effective Date2018‑05‑07 11:54:07
Statusdraft DraftVersion Label
NameAllergiesandIntoleranceConcernEntryDisplay NameeHDSI Allergies and Intolerance Concern Entry
Description
This template reflects an ongoing concern on behalf of the person that placed the allergy on a patient’s allergy list.
A concern may refer to one or more allergies or intolerances.
There are different kinds of status that could be related to an allergy, or more in general to a condition:
  • The status of the concern (active, inactive,..)
  • The status of the condition (e.g. active, inactive, resolved,..)
  • The confirmation status [clinical workflow status, certainty] (e.g. confirmed, likely, unlikely,…)
Not all of them can be represented in a CDA using the statusCode elements of the concern (ACT) and observation (condition).
The statusCode within the Patient Summary is as long as it is of concern to the provider (i.e., as long as the condition, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode is “active”. 
When the underlying conditions are no longer of concern the information is the statusCode would be “completed” and those entries are not foreseen in the Patient Summary.

The effectiveTime/low of the Allergy Concern Act asserts when the concern became active. This equates to the time the concern was authored in the patient's chart.
The effectiveTime/high asserts when the concern became inactive, and it is present if the statusCode of the concern act is "completed", normally not foreseen in the Patient Summary.
ContextPathname /
ClassificationCDA Entry Level Template
Open/ClosedClosed (only defined elements are allowed)
Used by / Uses
Used by 0 transactions and 1 template, Uses 1 template
Used by as NameVersion
1.3.182.11.10.2.2Containmentdraft eHDSI Allergies and Other Adverse Reactions2018‑05‑07 11:02:32
Uses as NameVersion
1.3.182.11.10.3.4Containmentdraft eHDSI Allergies and Intolerances EntryDYNAMIC
ItemDTCardConfDescriptionLabel
hl7:act
0 … *RAlledotsntry
@moodCode
cs1 … 1FEVN
@classCode
cs1 … 1FACT
hl7:templateId
II1 … 1MAlledotsntry
@root
uid0 … 1F1.3.182.11.10.3.5
hl7:code
CD1 … 1RAlledotsntry
@code
CONF0 … 1FCONC
@codeSystem
0 … 1F2.16.840.1.113883.5.6
hl7:statusCode
CS1 … 1MThe statusCode within the Patient Summary is as long as it is of concern to the provider (i.e., as long as the condition, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode is “active”. 

When the underlying conditions are no longer of concern the information is the statusCode would be “completed” and those entries are not foreseen in the Patient Summary.
Alledotsntry
@code
cs1 … 1Factive
hl7:effectiveTime
IVL_TS0 … 1RRequired entry, but from history it may not be clear in all cases when the Allergy occured first.

The low value asserts when the concern became active. This equates to the time the concern was authored in the patient's chart and the author started tracking this concern.

The high value asserts when the concern became inactive and the clinician deems that there is no longer any need to track underlying conditions.		Alledotsntry
hl7:entryRelationship
0 … *RThis entry shall contain one or more allergy or intolerance entries that conform to the Allergy and Intolerance Entry Content Module. This shall be represented with the <entryRelationship> element. The typeCode shall be ‘SUBJ’ and inversionInd shall be ‘false’ .

Contains 1.3.182.11.10.3.4 eHDSI Allergies and Intolerances Entry (DYNAMIC)		Alledotsntry
@typeCode
cs1 … 1FSUBJ
@inversionInd
bl1 … 1Ffalse