Difference between revisions of "2.16.840.1.113883.10.22.4.10"

From HL7 IPS
Jump to: navigation, search
(Automatic ADBot page (ac18df9bec40931c426878b4fa64f14b713befe0))
(Automatic ADBot page (ac18df9bec40931c426878b4fa64f14b713befe0))
 
Line 5: Line 5:
 
=Template ''IPSResultObservation''=
 
=Template ''IPSResultObservation''=
  
−
<p>This generic template is the basic set of constraints, which apply to any kind of observation grouped in a Result Organizer. The IPS Result Observation template is generic. It is further specialized by child templates, which  constrain  clinical laboratory observations or radiology observations or anatomic pathology observations. The generic IPS Result Observation template is usable in a patient summary for observations, which do not fall within one of the specialized categories.  The result observation includes a
+
<p>This generic template is the basic set of constraints, which apply to any kind of observation grouped in a Result Organizer. The IPS Result Observation template is generic. It is further specialized by child templates, which  constrain  clinical laboratory observations or radiology observations or anatomic pathology observations. The generic IPS Result
−
      statusCode to allow recording the status of an observation. “Pending” results (e.g., a test has been run but results have not been reported yet) should be represented as “active” ActStatus. However, in most cases, observations selected for an international patient summary are  results that are final and approved, and thus, have a "completed" statusCode.The result of the observation may be commented through an entryRelationship introducing an "IPS Comment activity" template. </p>
+
                Observation template is usable in a patient summary for observations, which do not fall within one of the specialized categories.  The result observation includes a statusCode to allow recording the status of an observation. “Pending” results (e.g., a test has been run but results have not been reported yet) should be represented as “active” ActStatus. However, in
 +
                most cases, observations selected for an international patient summary are  results that are final and approved, and thus, have a "completed" statusCode.The result of the observation may be commented through an entryRelationship introducing an "IPS Comment activity" template. </p>
 
==Actual version==
 
==Actual version==
 
{{:{{BASEPAGENAME}}/dynamic}}
 
{{:{{BASEPAGENAME}}/dynamic}}
Line 12: Line 13:
 
==List of all versions of this template==
 
==List of all versions of this template==
 
*[[2.16.840.1.113883.10.22.4.10/static-2017-03-02T000000|2017-03-02 (Under pre-publication review)]]
 
*[[2.16.840.1.113883.10.22.4.10/static-2017-03-02T000000|2017-03-02 (Under pre-publication review)]]
−
<!--1709ffb7430334f54b4b6c856b09daf03ec4b5af-->
+
<!--0f0f2f84309b73d7483a78d5479cf06495cd9f92-->

Latest revision as of 05:12, 3 April 2024

Comments on this page

Template IPSResultObservation

This generic template is the basic set of constraints, which apply to any kind of observation grouped in a Result Organizer. The IPS Result Observation template is generic. It is further specialized by child templates, which  constrain  clinical laboratory observations or radiology observations or anatomic pathology observations. The generic IPS Result Observation template is usable in a patient summary for observations, which do not fall within one of the specialized categories.  The result observation includes a statusCode to allow recording the status of an observation. “Pending” results (e.g., a test has been run but results have not been reported yet) should be represented as “active” ActStatus. However, in most cases, observations selected for an international patient summary are  results that are final and approved, and thus, have a "completed" statusCode.The result of the observation may be commented through an entryRelationship introducing an "IPS Comment activity" template.

Actual version

Id2.16.840.1.113883.10.22.4.10Effective Date2017‑03‑02
StatusKorange.png Under pre-publication reviewVersion LabelSTU1
NameIPSResultObservationDisplay NameIPS Result Observation
Description
This generic template is the basic set of constraints, which apply to any kind of observation grouped in a Result Organizer. The IPS Result Observation template is generic. It is further specialized by child templates, which  constrain  clinical laboratory observations or radiology observations or anatomic pathology observations. The generic IPS Result Observation template is usable in a patient summary for observations, which do not fall within one of the specialized categories.  
The result observation includes a statusCode to allow recording the status of an observation. “Pending” results (e.g., a test has been run but results have not been reported yet) should be represented as “active” ActStatus. However, in most cases, observations selected for an international patient summary are  results that are final and approved, and thus, have a "completed" statusCode.
The result of the observation may be commented through an entryRelationship introducing an "IPS Comment activity" template.
ContextParent nodes of template element with id 2.16.840.1.113883.10.22.4.10
ClassificationCDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
Associated with
Associated with 4 concepts
IdNameData Set
hl7ips-data​element-106Kyellow.png Observation Result Kyellow.png CEN/TC 251 prEN 17269
hl7ips-data​element-143Kyellow.png Date of observation Kyellow.png CEN/TC 251 prEN 17269
hl7ips-data​element-144Kyellow.png Observation Type Kyellow.png CEN/TC 251 prEN 17269
hl7ips-data​element-145Kyellow.png Value Kyellow.png CEN/TC 251 prEN 17269
Uses
Uses 2 templates
Uses as NameVersion
2.16.840.1.113883.10.22.4.14IncludeKorange.png IPS Body Author (STU1)DYNAMIC
2.16.840.1.113883.10.22.4.22ContainmentKorange.png IPS Comment Activity (STU1)DYNAMIC
RelationshipAdaptation: template 2.16.840.1.113883.10.12.303 CDA Observation (2005‑09‑07)
ref
ad1bbr-

Adaptation: template 2.16.840.1.113883.10.20.22.4.2 Result Observation (V3) (2015‑08‑01)
ref
ccda-
Example
Example
<observation classCode="OBS" moodCode="EVN">
  <templateId root="2.16.840.1.113883.10.22.4.10"/>  <id root="1.2.3.999" extension="__example only__"/>  <code code="..." codeSystem="1.2.3.999"/>  <statusCode/>  <effectiveTime>
    <low value="20170721091742"/>  </effectiveTime>  <value xsi:type="PQ" value="136" unit="mmol/L"/>  <interpretationCode code="..." codeSystem="2.16.840.1.113883.5.83"/>  <methodCode code="..." codeSystem="1.2.3.999"/>  <targetSiteCode code="..." codeSystem="1.2.3.999"/>  <author>
    <!-- template 2.16.840.1.113883.10.22.4.14 'IPS Body Author' (dynamic) -->
  </author>  <referenceRange>
    <observationRange>
      <value xsi:type="PQ" value=".." unit="..."/>      <interpretationCode code="N" codeSystem="2.16.840.1.113883.5.83" displayName="Normal"/>    </observationRange>  </referenceRange>  <entryRelationship typeCode="COMP">
    <!-- template 2.16.840.1.113883.10.22.4.22 'IPS Comment Activity' (dynamic) -->
  </entryRelationship></observation>
ItemDTCardConfDescriptionLabel
hl7:observation
(IPS...ion)
 
Target.png
hl7ips-data​element-106Kyellow.png Observation Result Kyellow.png CEN/TC 251 prEN 17269
Treetree.png@classCode
cs1 … 1FOBS
Treetree.png@moodCode
cs1 … 1FEVN
Treetree.pnghl7:templateId
II1 … 1M(IPS...ion)
Treeblank.pngTreetree.png@root
uid1 … 1F2.16.840.1.113883.10.22.4.10
Treetree.pnghl7:id
II0 … *R(IPS...ion)
Treetree.pnghl7:code
CD.IPS1 … 1M(IPS...ion)
 
Target.png
hl7ips-data​element-144Kyellow.png Observation Type Kyellow.png CEN/TC 251 prEN 17269
 CONF
The value of @code shall be drawn from value set 2.16.840.1.113883.11.22.38 IPS Results Observation (DYNAMIC)
Treetree.pnghl7:statusCode
CS1 … 1M(IPS...ion)
Treetree.pnghl7:effectiveTime
IVL_TS1 … 1R(IPS...ion)
 
Target.png
hl7ips-data​element-143Kyellow.png Date of observation Kyellow.png CEN/TC 251 prEN 17269
Choice1 … 1Elements to choose from:
  • hl7:value[@xsi:type='CE.IPS']
  • hl7:value[@xsi:type='PQ']
  • hl7:value[@xsi:type='IVL_PQ']
  • hl7:value[@xsi:type='ST']
  • hl7:value[@xsi:type='TS']
  • hl7:value[@xsi:type='RTO_QTY_QTY']
Treeblank.pngTreetree.pnghl7:value
CE.IPS0 … 1R(IPS...ion)
where [@xsi:type='CE.IPS']
 
Target.png
hl7ips-data​element-145Kyellow.png Value Kyellow.png CEN/TC 251 prEN 17269
 Example
Result code: code '201' from code system 2.16.840.1.113883.2.4.4.30.1045
<value xsi:type="CE" code="201" codeSystem="2.16.840.1.113883.2.4.4.30.1045" displayName="regular"/>
 Example
Result code: code 'POS' from code system 2.16.840.1.113883.5.83
<value xsi:type="CE" code="POS" codeSystem="2.16.840.1.113883.5.83"/>
Treeblank.pngTreetree.pnghl7:value
PQ0 … 1R(IPS...ion)
where [@xsi:type='PQ']
 ConstraintIf Observation/value is a physical quantity (xsi:type="PQ"), the unit of measure SHALL be selected from ValueSet UnitsOfMeasureCaseSensitive 2.16.840.1.113883.1.11.12839 DYNAMIC
 Example
Result physical quantity (data type PQ): 136 mmol per liter
<value xsi:type="PQ" value="136" unit="mmol/L"/>
Treeblank.pngTreetree.pnghl7:value
IVL_PQ0 … 1R(IPS...ion)
where [@xsi:type='IVL_PQ']
 Example
Result interval of physical quantities (data type IVL_PQ): 150 - 400 Milliard per 10 exp 9 liter
<value xsi:type="IVL_PQ">
  <low value="150" unit="10+9/l"/>  <high value="400" unit="10+9/l"/></value>
Treeblank.pngTreetree.pnghl7:value
ST0 … 1R(IPS...ion)
where [@xsi:type='ST']
 Example
Result free text (data type ST)
<value xsi:type="ST">This is a result as a free text</value>
Treeblank.pngTreetree.pnghl7:value
TS0 … 1R(IPS...ion)
where [@xsi:type='TS']
 Example
Result time stamp (data type TS): 6-Aug-2014
<value xsi:type="TS" value="20140806"/>
Treeblank.pngTreetree.pnghl7:value
RTO_QTY_QTY0 … 1R(IPS...ion)
where [@xsi:type='RTO_QTY_QTY']
 Example
Result ratio (data type RTO_QTY_QTY): 1/179
<value xsi:type="RTO_QTY_QTY">
  <numerator xsi:type="INT" value="1"/>  <denominator xsi:type="INT" value="179"/></value>
Treetree.pnghl7:interpretationCode
CE.IPS0 … 1R(IPS...ion)
 CONF
The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.78 ObservationInterpretation (DYNAMIC)
Treetree.pnghl7:target​Site​Code
CD.IPS (preferred)0 … 1(IPS...ion)
 CONF
The value of @code comes preferably from value set 2.16.840.1.113883.11.22.55 IPS Body Site (DYNAMIC)
Included0 … *R from 2.16.840.1.113883.10.22.4.14 IPS Body Author (DYNAMIC)
Treetree.pnghl7:author
0 … *R(IPS...ion)
Treeblank.pngTreetree.pnghl7:templateId
II1 … 1M(IPS...ion)
Treeblank.pngTreeblank.pngTreetree.png@root
uid1 … 1F2.16.840.1.113883.10.22.4.14
Treeblank.pngTreetree.pnghl7:time
TS.IPS.TZ1 … 1R(IPS...ion)
Treeblank.pngTreetree.pnghl7:assignedAuthor
1 … 1M(IPS...ion)
Treeblank.pngTreeblank.pngTreetree.pnghl7:id
II1 … *R(IPS...ion)
Treeblank.pngTreeblank.pngTreetree.pnghl7:code
0 … 1R(IPS...ion)
Choice0 … 1Elements to choose from:
  • hl7:assigned​Person
  • hl7:assigned​Authoring​Device
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:assigned​Person
0 … 1C(IPS...ion)
Treeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreetree.png@classCode
cs0 … 1FPSN
Treeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreetree.png@determiner​Code
cs0 … 1FINSTANCE
Treeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:name
PN1 … *RName of the person (e.g. the Healthcare Professional)  authoring this document(IPS...ion)
 Example<name>
  <given>John</given>  <family>Español Smith</family></name>
Treeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:family
1 … *R(IPS...ion)
Treeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:given
1 … *R(IPS...ion)
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:assigned​Authoring​Device
0 … 1C(IPS...ion)
 Example<assignedAuthoringDevice classCode="DEV" determinerCode="INSTANCE">
  <softwareName displayName="Turriano"/></assignedAuthoringDevice>
Included from 2.16.840.1.113883.10.22.9.2 IPS CDA Device (DYNAMIC)
Treeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreetree.png@classCode
cs0 … 1FDEV
Treeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreetree.png@determiner​Code
cs0 … 1FINSTANCE
Treeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:code
CE0 … 1(IPS...ion)
Treeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:manufacturer​Model​Name
SC0 … 1(IPS...ion)
Treeblank.pngTreeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:softwareName
SC0 … 1(IPS...ion)
Treeblank.pngTreeblank.pngTreetree.pnghl7:represented​Organization
0 … 1(IPS...ion)
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:id
II0 … *(IPS...ion)
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:name
0 … *(IPS...ion)
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:telecom
TEL0 … *(IPS...ion)
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:addr
AD0 … *(IPS...ion)
Treetree.pnghl7:referenceRange
0 … *R(IPS...ion)
Treeblank.pngTreetree.pnghl7:observationRange
1 … 1M(IPS...ion)
Treeblank.pngTreeblank.pngTreetree.pnghl7:code
CDNP(IPS...ion)
Treeblank.pngTreeblank.pngTreetree.pnghl7:value
ANY1 … 1M(IPS...ion)
Treeblank.pngTreeblank.pngTreetree.pnghl7:interpretationCode
CE0 … 1(IPS...ion)
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.png@code
CONF0 … 1FN
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.png@codeSystem
0 … 1F2.16.840.1.113883.5.83 (Observation Interpretation)
Treetree.pnghl7:entryRelationship
0 … *Contains 2.16.840.1.113883.10.22.4.22 IPS Comment Activity (DYNAMIC)(IPS...ion)
Treeblank.pngTreetree.png@typeCode
cs1 … 1FCOMP


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.10&oldid=10145"