2.16.840.1.113883.10.22.4.5

Comments on this page

Template IPSAllergyAndIntoleranceConcern

Description

Keine Beschreibung in Deutsch (de-DE) verfügbar
en-US: 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).

As long as the underlying condition is of concern to the author (i.e., as long as the allergy, whether active or resolved, is of ongoing concern and interest to the author), the statusCode is “active”.

In case the clinician deems that there is no longer any need to track the underlying conditions then the concern is inactive and the statusCode is set to "completed".
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"

Actual version

Id	2.16.840.1.113883.10.22.4.5	Effective Date	2024‑08‑04 10:09:24 Other versions this id: IPSAllergyAndIntoleranceConcern as of 2016‑11‑11
Status	Draft	Version Label	STU2
Name	IPSAllergyAndIntoleranceConcern	Display Name	IPS Allergy and Intolerance Concern
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). As long as the underlying condition is of concern to the author (i.e., as long as the allergy, whether active or resolved, is of ongoing concern and interest to the author), the statusCode is “active”. In case the clinician deems that there is no longer any need to track the underlying conditions then the concern is inactive and the statusCode is set to "completed". 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"
Context	Parent nodes of template element with id 2.16.840.1.113883.10.22.4.5
Classification	CDA Entry Level Template
Open/Closed	Open (other than defined elements are allowed)
Uses	Uses 1 template Uses as Name Version 2.16.840.1.113883.10.22.4.1 Containment IPS Allergy or Intolerance (STU2) DYNAMIC
Relationship	Specialization: template 2.16.840.1.113883.10.22.4.5 IPS Allergy and Intolerance Concern (2016‑11‑11) Adaptation: template 2.16.840.1.113883.10.12.301 CDA Act (2005‑09‑07) ref ad1bbr- Adaptation: template 1.3.6.1.4.1.19376.1.5.3.1.4.5.3 IHE Allergy and Intolerance Concern Entry (2013‑12‑20) ref IHE-PCC-
Example	Example <act classCode="ACT" moodCode="EVN">   <templateId root="2.16.840.1.113883.10.22.4.5"/>  <id root="1.2.3.999" extension="__example only__"/>  <code code="CONC" codeSystem="2.16.840.1.113883.5.6">     <statusCode code="active"/>    <effectiveTime>       <low value="..."/>      <high value="..."/>    </effectiveTime>    <entryRelationship typeCode="SUBJ" inversionInd="false">       <!-- template 2.16.840.1.113883.10.22.4.1 'IPS Allergy or Intolerance' (dynamic) -->     </entryRelationship>  </code></act>
Item DT Card Conf Description Label hl7:act 0 … * R (IPS...ern) @classCode cs 1 … 1 F ACT @moodCode cs 1 … 1 F EVN hl7:templateId II 1 … 1 M (IPS...ern) @root uid 1 … 1 F 2.16.840.1.113883.10.22.4.5 hl7:id II 0 … * R (IPS...ern) hl7:code CD 1 … 1 M (IPS...ern) @code CONF 1 … 1 F CONC @codeSystem 1 … 1 F 2.16.840.1.113883.5.6 (HL7ActClass) hl7:statusCode CS 1 … 1 R As long as the underlying conditions are of concern to the author (i.e., as long as allergies, whether active or resolved, is of ongoing concern and interest to the author), the statusCode is “ active ”. The concern is tracked by the author. Only when the underlying allergies are no longer of concern then the statusCode is set to “ completed ”. The author is no more tracking this concern and no further actions are expected. (IPS...ern)   CONF The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.19890 x_ActStatusActiveComplete (DYNAMIC) hl7:effectiveTime IVL_TS 1 … 1 R (IPS...ern) hl7:low IVXB_TS 1 … 1 R This element 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. (IPS...ern) hl7:high IVXB_TS 0 … 1 C This element asserts when the clinician deemed there is no longer any need to track the underlying conditions. (IPS...ern)   Constraint If statusCode/@code="completed" Completed, then effectiveTime *SHALL* contain [1..1] high   Schematron assert role  error     test not(../hl7:statusCode[@code='completed']) or hl7:high     Message If statusCode/@code="completed" Completed, then effectiveTime *SHALL* contain [1..1] high   hl7:entryRelationship 1 … * R Contains 2.16.840.1.113883.10.22.4.1 IPS Allergy or Intolerance (DYNAMIC) (IPS...ern) @typeCode cs 1 … 1 F SUBJ @inversionInd bl 0 … 1 F false

List of all versions of this template

• 2016-11-11 (Under develeopment)