Template

Show index

Template VPS Problem Concern Act 2017‑05‑22 17:18:05

Id2.16.840.1.113883.2.9.10.1.6.60Effective Date2017‑05‑22 17:18:05
Statusdraft DraftVersion Label
NameHL7ITVPSProblemConcernDisplay NameVPS Problem Concern Act
Description
(it-IT)

This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. 
The purpose of the concern act is that of supporting the tracking of a problem or a condition.

Different statuses could be considered in relation 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). 

So long as the underlying conditions are 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”.
Only when the underlying conditions are no longer of concern is the statusCode set to “completed”. 

The effectiveTime reflects the time that the underlying condition was felt to be a concern; it may or may not correspond to the effectiveTime of the condition (e.g., even five years later, the clinician may remain concerned about a prior heart attack).
The effectiveTime/low of the Problem 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 become inactive, and it is present if the statusCode of the concern act is "completed".

A Problem Concern Act can contain many Problem Observations.

The many Problem Observations nested under a Problem Concern Act reflect the change in the clinical understanding of a condition over time. For instance, a Concern may initially contain a Problem Observation of “chest pain”:

- Problem Concern 1

--- Problem Observation: Chest Pain

Later, a new Problem Observation of “esophagitis” will be added, reflecting a better understanding of the nature of the chest pain. The later problem observation will have a more recent author time stamp.

- Problem Concern 1

--- Problem Observation (author/time Jan 3, 2012): Chest Pain

--- Problem Observation (author/time Jan 6, 2012): Esophagitis

Many systems display the nested Problem Observation with the most recent author time stamp, and provide a mechanism for viewing prior observations.

ContextParent nodes of template element with id 2.16.840.1.113883.2.9.10.1.6.60
ClassificationCDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
Associated with
Associated with 2 concepts
IdNameData Set
vpsee-dataelement-1178draft  draft Emergency Encounter report
vpsee-dataelement-1180draft Healthcare Provider infos draft Emergency Encounter report
Used by / Uses
Used by 0 transactions and 1 template, Uses 3 templates
Used by as NameVersion
2.16.840.1.113883.2.9.10.1.6.55Containmentdraft VPS Sezione Anamnesi2017‑05‑22 14:58:22
Uses as NameVersion
2.16.840.1.113883.2.9.10.1.6.61Containmentdraft VPS Problem ObservationDYNAMIC
2.16.840.1.113883.10.12.318Containmentactive CDA Author (Body)DYNAMIC
2.16.840.1.113883.10.12.319Containmentactive CDA Informant (Body)DYNAMIC
RelationshipAdaptation: template 1.3.6.1.4.1.19376.1.5.3.1.4.5.1 IHE Concern Entry (DYNAMIC)
ref
IHE-PCC-

Adaptation: template 2.16.840.1.113883.10.20.1.27 Problem act (DYNAMIC)
ref
ccd1-

Adaptation: template 1.3.6.1.4.1.19376.1.5.3.1.4.5.2 IHE Problem Concern Entry (DYNAMIC)
ref
IHE-PCC-
ItemDTCardConfDescriptionLabel
hl7:act
RHL7Idotscern
 
target
vpsee-dataelement-1178draft  draft Emergency Encounter report
@classCode
cs1 … 1FACT
@moodCode
cs1 … 1FEVN
hl7:templateId
II1 … 1MHL7Idotscern
@root
uid1 … 1F2.16.840.1.113883.2.9.10.1.6.60
hl7:id
II0 … *RHL7Idotscern
hl7:code
CD1 … 1RHL7Idotscern
@code
CONF0 … 1FCONC
@codeSystem
0 … 1F2.16.840.1.113883.5.6
hl7:statusCode
CS1 … 1RSo long as the underlying conditions are 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”. 

Only when the underlying conditions are no longer of concern is the statusCode set to “completed”.
HL7Idotscern
 CONF
The value of @code shall be drawn from value set 2.16.840.1.113883.3.1937.777.13.11.4 (DYNAMIC)
hl7:effectiveTime
IVL_TS1 … 1RHL7Idotscern
hl7:low
IVXB_TS1 … 1RThis 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.
HL7Idotscern
hl7:high
IVXB_TS0 … 1CThis element asserts when the clinician deemed there is no longer any need to track the underlying conditions.
HL7Idotscern
 ConstraintIf the statusCode is completed this element is required
hl7:author
0 … *Contains 2.16.840.1.113883.10.12.318 CDA Author (Body) (DYNAMIC)HL7Idotscern
 
target
vpsee-dataelement-1180draft Healthcare Provider infos draft Emergency Encounter report
hl7:informant
0 … *Contains 2.16.840.1.113883.10.12.319 CDA Informant (Body) (DYNAMIC)HL7Idotscern
hl7:entryRelationship
1 … *RContains 2.16.840.1.113883.2.9.10.1.6.61 VPS Problem Observation (DYNAMIC)HL7Idotscern
@typeCode
cs1 … 1FSUBJ
@inversionInd
bl0 … 1Ffalse