2.16.840.1.113883.10.22.4.26/static-2017-04-11T000000

Id	2.16.840.1.113883.10.22.4.26	Effective Date	2017‑04‑11
Status	Under pre-publication review	Version Label	STU1
Name	IPSMedicalDevice	Display Name	IPS Medical Device
Description	The medical devices entry content module describes the kind of device that is, or has been used by the patient
Context	Parent nodes of template element with id 2.16.840.1.113883.10.22.4.26
Classification	CDA Entry Level Template
Open/Closed	Open (other than defined elements are allowed)
Associated with	Associated with 6 concepts Id Name Data Set hl7ips-data​element-150  Use end date  CEN/TC 251 prEN 17269 hl7ips-data​element-218  Device content Status  CEN/TC 251 prEN 17269 hl7ips-data​element-57  Device  CEN/TC 251 prEN 17269 hl7ips-data​element-58  Device Type  CEN/TC 251 prEN 17269 hl7ips-data​element-59  Use start date  CEN/TC 251 prEN 17269 hl7ips-data​element-60  Device Identifier  CEN/TC 251 prEN 17269
Relationship	Adaptation: template 1.3.6.1.4.1.12559.11.10.1.3.1.3.5 Medical Devices (2013‑12‑20) ref epsos-
Example	Example <supply moodCode="EVN" classCode="SPLY">   <templateId root="2.16.840.1.113883.10.22.4.26"/>  <id root="2.16.840.1.113883.19.811.3"/>  <text>     <reference value="#dev_1"/>  </text>  <effectiveTime xsi:type="IVL_TS">     <low value="20070728"/>  </effectiveTime>  <participant typeCode="DEV">     <participantRole classCode="MANU">       <id/>      <playingDevice classCode="DEV" determinerCode="INSTANCE">         <code code="304184000" displayName="Ankle joint implant" codeSystem="2.16.840.1.113883.6.96"/>      </playingDevice>    </participantRole>  </participant></supply>
Item DT Card Conf Description Label hl7:supply R The <supply> element shall be present. The moodCode attribute shall be EVN to reflect that a medical device has been provided.</supply> (IPS...ice) @classCode cs 1 … 1 F SPLY @moodCode cs 1 … 1 F EVN hl7:templateId II 1 … 1 M (IPS...ice) @root uid 1 … 1 F 2.16.840.1.113883.10.22.4.26 hl7:id II 0 … * R This optional element identifies the provision of the device (e.g. implant procedure) (IPS...ice) hl7:text ED 0 … 1 R (IPS...ice) hl7:reference TEL 1 … 1 M (IPS...ice) @value 1 … 1 R Reference pointing to the narrative, typically #{label}-{generated-id}, e.g. #xxx-1 hl7:effectiveTime IVL_TS 1 … 1 R This element provides the interval of time corresponding to the device usage by/presence in the patient. (IPS...ice) @xsi:type st 1 … 1 F IVL_TS hl7:low TS 1 … 1 R The lower bound of the interval represents the start date/time. (IPS...ice)   hl7ips-data​element-59  Use start date  CEN/TC 251 prEN 17269 hl7:high TS 0 … 1 C The upper bound represents the end date/time. If it is not present, the device is still used by or present in the patient. (IPS...ice)   hl7ips-data​element-150  Use end date  CEN/TC 251 prEN 17269 hl7:participant 1 … * R The device is represented as a participant in the supply structure. The following descriptions apply to the device structure. (IPS...ice)   hl7ips-data​element-57  Device  CEN/TC 251 prEN 17269 @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>   Example Presence of implanted device not known (situation) <participant typeCode="DEV">   <participantRole classCode="MANU">     <playingDevice>       <code code="000000" codeSystem="2.16.840.1.113883.6.96" displayName="Presence of implanted device not known (situation)"/>    </playingDevice>    <scopingEntity>       <id root="2.16.840.1.113883.3.3719"/>    </scopingEntity>  </participantRole></participant>   Example No implant in situ (situation) <participant typeCode="DEV">   <participantRole classCode="MANU">     <playingDevice>       <code code="000000" codeSystem="2.16.840.1.113883.6.96" displayName="No implant in situ (situation)"/>    </playingDevice>    <scopingEntity>       <id root="2.16.840.1.113883.3.3719"/>    </scopingEntity>  </participantRole></participant> hl7:participantRole 1 … 1 R (IPS...ice) @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...ice)   hl7ips-data​element-60  Device Identifier  CEN/TC 251 prEN 17269   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...ice) @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...ice)   hl7ips-data​element-218  Device content Status  CEN/TC 251 prEN 17269 hl7ips-data​element-58  Device Type  CEN/TC 251 prEN 17269   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)