2.16.840.1.113883.10.22.4.17/static-2020-07-14T163558

Id	2.16.840.1.113883.10.22.4.17	Effective Date	2020‑07‑14 16:35:58 Other versions this id: IPSProcedureEntry as of 2024‑08‑04 11:08:35 IPSProcedureEntry as of 2017‑03‑27
Status	Draft	Version Label	2021
Name	IPSProcedureEntry	Display Name	IPS Procedure Entry
Description	The procedure entry is used to record procedures that have occurred, or which are planned for in the future.
Context	Parent nodes of template element with id 2.16.840.1.113883.10.22.4.17
Classification	CDA Entry Level Template
Open/Closed	Open (other than defined elements are allowed)
Associated with	Associated with 5 concepts Id Name Data Set hl7ips-data​element-216  Body site  CEN/TC 251 prEN 17269 hl7ips-data​element-44  Procedures Content Status  CEN/TC 251 prEN 17269 hl7ips-data​element-47  Procedure  CEN/TC 251 prEN 17269 hl7ips-data​element-48  Procedure date  CEN/TC 251 prEN 17269 hl7ips-data​element-49  Procedure code  CEN/TC 251 prEN 17269
Uses	Uses 1 template Uses as Name Version 2.16.840.1.113883.10.22.4.31 Containment IPS Internal Reference (STU1) DYNAMIC
Relationship	Version: template 2.16.840.1.113883.10.22.4.17 IPS Procedure Entry (2017‑03‑27) Adaptation: template 1.3.6.1.4.1.19376.1.5.3.1.4.19 IHE Procedure Entry (2016‑09‑28 10:37:28) ref IHE-PCC- Adaptation: template 2.16.840.1.113883.10.12.306 CDA Procedure (2005‑09‑07) ref ad1bbr-
Example	Example <hl7:procedure classCode="PROC" moodCode="EVN">   <hl7:templateId root="2.16.840.1.113883.10.22.4.17"/>  <hl7:id root="1.2.3.999" extension="--example only--"/>  <hl7:code/>  <hl7:text>     <hl7:reference value="value"/>  </hl7:text>  <hl7:statusCode code="completed"/>  <hl7:effectiveTime>     <hl7:low value="20200714163551"/>  </hl7:effectiveTime>  <hl7:targetSiteCode/>  <cda:entryRelationship typeCode="COMP" inversionInd="true">     <!-- template 2.16.840.1.113883.10.22.4.31 'IPS Internal Reference' (2017-05-02T00:00:00) -->   </cda:entryRelationship></hl7:procedure>
Item DT Card Conf Description Label hl7:procedure (IPS...try)   hl7ips-data​element-47  Procedure  CEN/TC 251 prEN 17269 @classCode cs 1 … 1 F PROC @moodCode cs 1 … 1 R   CONF The value of @moodCode shall be drawn from value set 2.16.840.1.113883.11.20.9.18 MoodCodeEvnInt (DYNAMIC) hl7:templateId II 1 … 1 M (IPS...try) @root uid 1 … 1 F 2.16.840.1.113883.10.22.4.17 hl7:id II 0 … * R (IPS...try) hl7:code CD.IPS (preferred) 1 … 1 R (IPS...try)   hl7ips-data​element-44  Procedures Content Status  CEN/TC 251 prEN 17269 hl7ips-data​element-49  Procedure code  CEN/TC 251 prEN 17269   CONF The value of @code comes preferably from value set 2.16.840.1.113883.11.22.35 IPS Procedures (DYNAMIC) or The value of @code comes preferably from value set 2.16.840.1.113883.11.22.36 Absent or Unknown Procedures (DYNAMIC) hl7:text ED 0 … 1 R The <text> element if present points to the text describing the data being recorded; including any dates, comments, et cetera. The <reference> contains a URI in value attribute. This URI points to the free text description of the element (problem, procedure,...) in the document that is being described.</reference> </text> (IPS...try) hl7:reference TEL 1 … 1 M (IPS...try) @value url 1 … 1 R When used it shall refer to the narrative, typically #{label}-{generated-id}, e.g. #xxx-1 hl7:statusCode CS 1 … 1 M (IPS...try)   CONF The value of @code shall be drawn from value set 2.16.840.1.113883.11.22.22 ActStatusActiveCompletedAbortedCancelled (DYNAMIC) hl7:effectiveTime IVL_TS 1 … 1 R (IPS...try)   hl7ips-data​element-48  Procedure date  CEN/TC 251 prEN 17269 hl7:target​Site​Code CD.IPS (preferred) 0 … * (IPS...try)   hl7ips-data​element-216  Body site  CEN/TC 251 prEN 17269   CONF The value of @code comes preferably from value set 2.16.840.1.113883.11.22.55 IPS Body Site (DYNAMIC) hl7:participant 1 … * R The device is represented as a participant in the procedure structure. The following descriptions apply to the device structure. (IPS...try) @typeCode cs 1 … 1 F DEV   Example <participant typeCode="DEV">   <participantRole classCode="MANU">     <id root="1.2.3.999" extension="__example_only__"/>    <playingDevice classCode="DEV" determinerCode="INSTANCE">       <code code="" codeSystem=""/>      <!-- ... -->     </playingDevice>  </participantRole></participant> hl7:participantRole 1 … 1 R (IPS...try) @classCode cs 1 … 1 F MANU hl7:id II 0 … * R The device ID, e.g. using UDI, is represented by the id element of the participant role. This element is optional, as not all production identifiers (e.g., serial number, lot/batch number, distinct identification number) may be known to the provider or patient. (IPS...try)   Example UDI GS1: DeviceIdentifier 00844588003288, Serial# 10987654d321, Lot# 7654321D <id root="2.16.840.1.113883.3.3719" extension="{01}00844588003288{17}141120{10}7654321D{21}10987654d321"/>   Example UDI ICCBBA: DeviceIdentifier 00844588003288 <id root="2.16.840.1.113883.3.3719" extension="A9999XYZ100T0474"/>   Example UDI HIBCC: Serial# XYZ456789012345678, Lot# LOT123456789012345 <id root="2.16.840.1.113883.3.3719" extension="+H123PARTNO1234567890120/$$420020216LOT123456789012345/SXYZ456789012345678/16D20130202C"/> hl7:playingDevice 1 … 1 R The playingDevice element describes the device instance.  (IPS...try) @classCode cs 1 … 1 F DEV @determiner​Code cs 1 … 1 F INSTANCE hl7:code CE.IPS (preferred) 1 … 1 R The device code describes the type of device (e.g. arm prosthesis, arterial stent). (IPS...try)   CONF The value of @code comes preferably from value set 2.16.840.1.113883.11.22.23 IPS Medical Devices (DYNAMIC) or The value of @code comes preferably from value set 2.16.840.1.113883.11.22.61 Absent or Unknown Devices (DYNAMIC) hl7:entryRelationship 0 … * Contains 2.16.840.1.113883.10.22.4.31 IPS Internal Reference (DYNAMIC) (IPS...try) @typeCode cs 1 … 1 F COMP @inversionInd bl 1 … 1 F true