Template

Show index

Template IPS Medical Device 2017‑04‑11

Id2.16.840.1.113883.10.22.4.26Effective Date2017‑04‑11
Statuspending Under pre-publication reviewVersion LabelSTU1
NameIPSMedicalDeviceDisplay NameIPS Medical Device
DescriptionThe medical devices entry content module describes the kind of device that is, or has been used by the patient
ContextParent nodes of template element with id 2.16.840.1.113883.10.22.4.26
ClassificationCDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
Associated with
Associated with 6 concepts
IdNameData Set
hl7ips-dataelement-57draft Device draft CEN/TC 251 prEN 17269
hl7ips-dataelement-60draft Device Identifier draft CEN/TC 251 prEN 17269
hl7ips-dataelement-218draft Device content Status draft CEN/TC 251 prEN 17269
hl7ips-dataelement-58draft Device Type draft CEN/TC 251 prEN 17269
hl7ips-dataelement-59draft Use start date draft CEN/TC 251 prEN 17269
hl7ips-dataelement-150draft Use end date draft CEN/TC 251 prEN 17269
Used by / Uses
Used by 1 transaction and 5 templates, Uses 0 templates
Used by as NameVersion
2.16.840.1.113883.3.1937.777.13.4.2Transactiondraft IPS Created2017‑04‑07 11:10:54
2.16.840.1.113883.10.22.1.1linkpending International Patient Summary (STU1)2017‑04‑11
2.16.840.1.113883.10.22.1.1linkpending International Patient Summary (TI-2020)2020‑05‑08 12:30:59
2.16.840.1.113883.10.22.1.1linkdraft International Patient Summary (2021)2020‑07‑14 16:08:21
2.16.840.1.113883.10.22.3.6Containmentpending IPS Medical Devices Section (STU1)2017‑04‑11
2.16.840.1.113883.10.22.3.6Containmentdraft IPS Medical Devices Section (2021)2021‑10‑20 17:11:42
RelationshipAdaptation: 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>
ItemDTCardConfDescriptionLabel
hl7:supply
RThe element shall be present. The moodCode attribute shall be EVN to reflect that a medical device has been provided.IPSMdotsvice
@classCode
cs1 … 1FSPLY
@moodCode
cs1 … 1FEVN
hl7:templateId
II1 … 1MIPSMdotsvice
@root
uid1 … 1F2.16.840.1.113883.10.22.4.26
hl7:id
II0 … *RThis optional element identifies the provision of the device (e.g. implant procedure)IPSMdotsvice
hl7:text
ED0 … 1RIPSMdotsvice
hl7:reference
TEL1 … 1MIPSMdotsvice
@value
1 … 1RReference pointing to the narrative, typically #{label}-{generated-id}, e.g. #xxx-1
hl7:effectiveTime
IVL_TS1 … 1R
This element provides the interval of time corresponding to the device usage by/presence in the patient.
IPSMdotsvice
@xsi:type
1 … 1FIVL_TS
hl7:low
TS1 … 1RThe lower bound of the interval represents the start date/time.IPSMdotsvice
 
target
hl7ips-dataelement-59draft Use start date draft CEN/TC 251 prEN 17269
hl7:high
TS0 … 1CThe upper bound represents the end date/time. If it is not present, the device is still used by or present in the patient.IPSMdotsvice
 
target
hl7ips-dataelement-150draft Use end date draft CEN/TC 251 prEN 17269
hl7:participant
1 … *RThe device is represented as a participant in the supply structure. The following descriptions apply to the device structure.IPSMdotsvice
 
target
hl7ips-dataelement-57draft Device draft CEN/TC 251 prEN 17269
@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>
 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 … 1RIPSMdotsvice
@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.
IPSMdotsvice
 
target
hl7ips-dataelement-60draft Device Identifier draft 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 … 1RThe playingDevice element describes the device instance. IPSMdotsvice
@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).IPSMdotsvice
 
target
hl7ips-dataelement-218draft Device content Status draft CEN/TC 251 prEN 17269
hl7ips-dataelement-58draft Device Type draft 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)