Template ID(s) |
1.3.6.1.4.1.19376.1.5.3.1.4.5.1 (IHE PCC TF-2: 6.3.4.11)
1.3.6.1.4.1.19376.1.5.3.1.4.5.3 (IHE PCC TF-2: 6.4.3.13)
2.16.840.1.113883.10.20.1.27 (CCD 3.5.2.1) |
|
Description |
The allergies and intolerances concern entry is a concern entry template related to the expression of an allergy or intolerance the patient is or did suffer. |
|
RMIM Class |
Act |
|
Expected Entry Relationships |
|
|
Entry |
Template ID |
Reference |
Allergy and Intolerances Observation |
2.16.840.1.113883.10.20.1.28
2.16.840.1.113883.10.20.1.18
1.3.6.1.4.1.19376.1.5.3.1.4.6
1.3.6.1.4.1.19376.1.5.3.1.4.5 |
3.4.2.4 |
Profiled Elements |
|
|
Element |
Notes |
|
code [1..1]
CD |
The code element shall be present and shall carry a nullFlavor of NA (Not Applicable) |
|
statusCode [1..1]
CS |
The status code must be present and must be valued as follows:
|
Code |
Description |
active |
The concern is still being tracked and monitored. |
completed |
The problem, concern or medical state has been resolved and no longer needs to be monitored, except for historical purposes. |
|
effectiveTime [1..1]
IVL_TS |
The effectiveTime element must be present and must carry a high and low element whereby low indicates the time the concern began (or nullFlavor if unknown) and high indicates the time when the concern was no longer active (or nullFlavor if unknown). |
|
OpenSHR Implementation Notes |
|
|
Data Model |
Allergy |
|
Code File |
AllergiesAndIntolerancesConcernEntryProcessor.java |
|
Permitted Moods |
EVN |
|
Additional Constraints |
- Only active or suspended status codes are permitted in OpenSHR even though additional status codes are permitted in the IHE PCC documentation.
- OpenSHR will calculate the status of a concern entry based on the value of effectiveTime
- OpenSHR will map elements from the allergy/intolerance observation into the active list item where needed (severity, type of allergy, etc.). It is important that content creators accurately express allergies with an observation entry relationship.
- If more than one entry relationship exists for the concern, then OpenSHR will map those to multiple Allergy items in the OpenMRS database.
|
|
Example |
|
|
The following example illustrates a drug allergy to Aspirin. The allergy concern is active (still being monitored) and has no known start date.
|
|
|
<entry typeCode="DRIV" contextConductionInd="true">
<act classCode="ACT" moodCode="EVN">
<templateId root="1.3.6.1.4.1.19376.1.5.3.1.4.5.3"/>
<templateId root="1.3.6.1.4.1.19376.1.5.3.1.4.5.1"/>
<templateId root="2.16.840.1.113883.10.20.1.27"/>
<code nullFlavor="NA"/>
<statusCode code="active"/>
<effectiveTime>
<low nullFlavor="UNK"/>
</effectiveTime>
<entryRelationship typeCode="SUBJ" inversionInd="false" contextConductionInd="true">
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.1.28"/>
<templateId root="2.16.840.1.113883.10.20.1.18"/>
<templateId root="1.3.6.1.4.1.19376.1.5.3.1.4.6"/>
<templateId root="1.3.6.1.4.1.19376.1.5.3.1.4.5"/>
<code code="DALG" codeSystem="2.16.840.1.113883.5.4" codeSystemName="ObservationIntoleranceType" displayName="Drug Allergy"/>
<text representation="TXT" language="en-US">
<reference value="#obs9fc4cfd8"/>
</text>
<statusCode code="completed"/>
<effectiveTime nullFlavor="UNK"/>
<value xsi:type="CD" code="1191" codeSystem="2.16.840.1.113883.6.88" codeSystemName="RxNORM" displayName="Aspirin">
<originalText representation="TXT" language="en-US">
<reference value="#txt2df7355f"/>
</originalText>
</value>
<participant typeCode="CSM" contextControlCode="OP">
<participantRole classCode="MANU">
<playingEntity classCode="MMAT" determinerCode="INSTANCE">
<code code="1191" codeSystem="2.16.840.1.113883.6.88" codeSystemName="RxNORM" displayName="Aspirin">
<originalText representation="TXT" language="en-US">
<reference value="#txt2f4d0c7d"/>
</originalText>
</code>
<name>Aspirin (1191)</name>
</playingEntity>
</participantRole>
</participant>
</observation>
</entryRelationship>
</act>
</entry>
|
|
|