AllergyConcernAct

Allergy Concern Act

draftC-CDA Templates4.0.0logical13 key elements

This template reflects an ongoing concern on behalf of the provider that placed the allergy on a patient's allergy list. As long as the underlying condition is of concern to the provider (i.e., as long as the allergy, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode is "active". Only when the underlying allergy is no longer of concern is the statusCode set to "completed". The effectiveTime reflects the time that the underlying allergy was felt to be a concern.

The statusCode of the Allergy Concern Act is the definitive indication of the status of the concern, whereas the effectiveTime of the nested Allergy - Intolerance Observation is the definitive indication of whether or not the underlying allergy is resolved.

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 was completed (e.g., when the clinician deemed there is no longer any need to track the underlying condition).

#### Templates Used Although open templates may contain any valid CDA content, the following templates are specifically called out by this template:

Required EntryRelationships: AllergyIntoleranceObservation

Metadata

hl7.org/fhir
Canonical URL
http://hl7.org/cda/us/ccda/StructureDefinition/AllergyConcernAct
ID
AllergyConcernAct
Type
Base Definition
Act
Derivation
constraint
Mandatory and Must-Support Elements

Elements with cardinality > 0 or marked as Must Support (S)

PathCard.TypeFlagsDescription
templateId
1+
:allergy-concern-act1..1
1+
templateId.root
1+
templateId.extension
1+
id
1+
code.code
1+
code.codeSystem
1+
statusCode
1+
statusCode.code
1+
effectiveTime
1+
entryRelationship
1+
:allergyObs1..1
1+
entryRelationship.observation
http://hl7.org/cda/stds/core/StructureDefinition/Observation
1+