Id2.16.840.1.113883.10.22.4.17Effective Date2020‑07‑14 16:35:58
Statusdraft DraftVersion Label2021
NameIPSProcedureEntryDisplay NameIPS Procedure Entry
DescriptionThe procedure entry is used to record procedures that have occurred, or which are planned for in the future.
ContextParent nodes of template element with id 2.16.840.1.113883.10.22.4.17
ClassificationCDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
Associated with
Associated with 5 concepts
IdNameData Set
hl7ips-dataelement-44draft Procedures Content Status draft CEN/TC 251 prEN 17269
hl7ips-dataelement-49draft Procedure code draft CEN/TC 251 prEN 17269
hl7ips-dataelement-48draft Procedure date draft CEN/TC 251 prEN 17269
hl7ips-dataelement-47draft Procedure draft CEN/TC 251 prEN 17269
hl7ips-dataelement-216draft Body site draft CEN/TC 251 prEN 17269
Used by / Uses
Used by 0 transactions and 2 templates, Uses 1 template
Used by as NameVersion
2.16.840.1.113883.10.22.3.4Containmentpending IPS History of Procedures Section (STU1)2017‑03‑27
2.16.840.1.113883.10.22.3.6Containmentdraft IPS Medical Devices Section (2021)2021‑10‑20 17:11:42
Uses as NameVersion
2.16.840.1.113883.10.22.4.31Containmentpending IPS Internal Reference (STU1)DYNAMIC
RelationshipVersion: 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/>  <hl7:entryRelationship typeCode="COMP" inversionInd="true">
    <!-- template 2.16.840.1.113883.10.22.4.31 'IPS Internal Reference' (2017-05-02T00:00:00) -->
  </hl7:entryRelationship></hl7:procedure>
ItemDTCardConfDescriptionLabel
hl7:procedure
IPSPdotsntry
 
target
hl7ips-dataelement-47draft Procedure draft CEN/TC 251 prEN 17269
@classCode
cs1 … 1FPROC
@moodCode
cs1 … 1R
 CONF
The value of @moodCode shall be drawn from value set 2.16.840.1.113883.11.20.9.18 MoodCodeEvnInt (DYNAMIC)
hl7:templateId
II1 … 1MIPSPdotsntry
@root
uid1 … 1F2.16.840.1.113883.10.22.4.17
hl7:id
II0 … *RIPSPdotsntry
hl7:code
CD.IPS (preferred)1 … 1RIPSPdotsntry
 
target
hl7ips-dataelement-44draft Procedures Content Status draft CEN/TC 251 prEN 17269
hl7ips-dataelement-49draft Procedure code draft 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
ED0 … 1RThe element if present points to the text describing the data being recorded; including any dates, comments, et cetera. The 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. IPSPdotsntry
hl7:reference
TEL1 … 1MIPSPdotsntry
@value
st1 … 1R When used it shall refer to the narrative, typically #{label}-{generated-id}, e.g. #xxx-1
hl7:statusCode
CS1 … 1MIPSPdotsntry
 CONF
The value of @code shall be drawn from value set 2.16.840.1.113883.11.22.22 ActStatusActiveCompletedAbortedCancelled (DYNAMIC)
hl7:effectiveTime
IVL_TS1 … 1RIPSPdotsntry
 
target
hl7ips-dataelement-48draft Procedure date draft CEN/TC 251 prEN 17269
hl7:targetSiteCode
CD.IPS (preferred)0 … *IPSPdotsntry
 
target
hl7ips-dataelement-216draft Body site draft CEN/TC 251 prEN 17269
 CONF
The value of @code comes preferably from value set 2.16.840.1.113883.11.22.55 IPS Target Site (DYNAMIC)
hl7:participant
1 … *RThe device is represented as a participant in the procedure structure. The following descriptions apply to the device structure.IPSPdotsntry
@typeCode
cs1 … 1FDEV
 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 … 1RIPSPdotsntry
@classCode
cs1 … 1FMANU
hl7:id
II0 … *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.
IPSPdotsntry
 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 … 1RThe playingDevice element describes the device instance. IPSPdotsntry
@classCode
cs1 … 1FDEV
@determinerCode
cs1 … 1FINSTANCE
hl7:code
CE.IPS (preferred)1 … 1RThe device code describes the type of device (e.g. arm prosthesis, arterial stent).IPSPdotsntry
 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)IPSPdotsntry
@typeCode
cs1 … 1FCOMP
@inversionInd
bl1 … 1Ftrue