Difference between revisions of "2.16.840.1.113883.10.22.4.7"

From HL7 IPS
Jump to: navigation, search
(Automated ADBot page content)
(Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd))
Line 4: Line 4:
 
[[Category:Template]]
 
[[Category:Template]]
 
=Template ''IPSProblemConcernEntry''=
 
=Template ''IPSProblemConcernEntry''=
 +
 +
<p>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.There are different kinds of status that could be related 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 PainLater, 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): EsophagitisMany systems display the nested Problem Observation with the most recent author time stamp, and provide a mechanism for viewing prior observations.</p>
 
==Actual version==
 
==Actual version==
 
{{:{{BASEPAGENAME}}/dynamic}}
 
{{:{{BASEPAGENAME}}/dynamic}}
  
 
==List of all versions of this template==
 
==List of all versions of this template==
−
* [[2.16.840.1.113883.10.22.4.7/static-2017-02-15T000000|2017-02-15 (Under pre-publication review)]]
+
*[[2.16.840.1.113883.10.22.4.7/static-2017-02-15T000000|2017-02-15 (Under pre-publication review)]]
 +
<!--c11d3f82b61e104f958c4e40caf66c0c60fb9e54-->

Revision as of 22:00, 7 July 2020

Comments on this page

Template IPSProblemConcernEntry

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.There are different kinds of status that could be related 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 PainLater, 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): EsophagitisMany systems display the nested Problem Observation with the most recent author time stamp, and provide a mechanism for viewing prior observations.

Actual version

Id2.16.840.1.113883.10.22.4.7Effective Date2021‑08‑04 08:49:27
Other versions this id:
  • Kblank.png IPSProblemConcernEntry as of 2017‑02‑15
StatusKyellow.png DraftVersion Label2021
NameIPSProblemConcernEntryDisplay NameIPS Problem Concern Entry
Description

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.

There are different kinds of status that could be related 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.10.22.4.7
ClassificationCDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
Uses
Uses 1 template
Uses as NameVersion
2.16.840.1.113883.10.22.4.8ContainmentKyellow.png IPS Problem Entry (2021)DYNAMIC
RelationshipVersion: template 2.16.840.1.113883.10.22.4.7 IPS Problem Concern Entry (2017‑02‑15)
Adaptation: 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 eHDSI Problem Concern (DYNAMIC)
ref
epsos-
Example
Active Concern with several conditions
<act classCode="ACT" moodCode="EVN">
  <templateId root="2.16.840.1.113883.10.22.4.7"/>  <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="20170309"/>  </effectiveTime>  <entryRelationship typeCode="SUBJ" inversionInd="false">
    <!-- template 2.16.840.1.113883.10.22.4.8 'IPS Problem Entry' (dynamic) -->
    <!-- A condition could be active, inactive,.... -->
  </entryRelationship>  <entryRelationship typeCode="SUBJ" inversionInd="false">
    <!-- template 2.16.840.1.113883.10.22.4.8 'IPS Problem Entry' (dynamic) -->
  </entryRelationship></act>
Example
Concern no longer tracked
<act classCode="ACT" moodCode="EVN">
  <templateId root="2.16.840.1.113883.10.22.4.7"/>  <id root="1.2.3.999" extension="__example only__"/>  <code code="CONC" codeSystem="2.16.840.1.113883.5.6"/>  <statusCode code="completed"/>  <effectiveTime>
    <low value="20161210"/>    <low value="20170309"/>  </effectiveTime>  <entryRelationship typeCode="SUBJ" inversionInd="false">
    <!-- template 2.16.840.1.113883.10.22.4.8 'IPS Problem Entry' (dynamic) -->
  </entryRelationship></act>
ItemDTCardConfDescriptionLabel
hl7:act
R(IPS...try)
Treetree.png@classCode
cs1 … 1FACT
Treetree.png@moodCode
cs1 … 1FEVN
Treetree.pnghl7:templateId
II1 … 1M(IPS...try)
Treeblank.pngTreetree.png@root
uid1 … 1F2.16.840.1.113883.10.22.4.7
Treetree.pnghl7:id
II0 … *R(IPS...try)
Treetree.pnghl7:code
CD1 … 1M(IPS...try)
Treeblank.pngTreetree.png@code
1 … 1FCONC
Treeblank.pngTreetree.png@codeSystem
1 … 1F2.16.840.1.113883.5.6
Treetree.pnghl7: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”.		(IPS...try)
 CONF
The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.19890 x_ActStatusActiveComplete (DYNAMIC)
Treetree.pnghl7:effectiveTime
IVL_TS1 … 1M(IPS...try)
Treeblank.pngTreetree.pnghl7: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.(IPS...try)
Treeblank.pngTreetree.pnghl7:high
IVXB_TS0 … 1CThis element asserts when the clinician deemed there is no longer any need to track the underlying conditions.(IPS...try)
 ConstraintIf the statusCode is completed this element is required
Treetree.pnghl7:entryRelationship
1 … *RContains 2.16.840.1.113883.10.22.4.8 IPS Problem Entry (DYNAMIC)(IPS...try)
Treeblank.pngTreetree.png@typeCode
cs1 … 1FSUBJ
Treeblank.pngTreetree.png@inversionInd
bl0 … 1Ffalse


List of all versions of this template

Retrieved from "http://wiki.international-patient-summary.net/index.php?title=2.16.840.1.113883.10.22.4.7&oldid=6342"