2.16.840.1.113883.10.22.4.26/static-2017-04-11T000000

From HL7 IPS
Revision as of 16:15, 24 July 2017 by ADbot (talk | contribs) (Automated ADBot page content)
Jump to: navigation, search
Id2.16.840.1.113883.10.22.4.26Effective Date valid from 2017‑04‑11
StatusKyellow.png DraftVersion Label
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)
Used by / Uses
Used by 0 transactions and 2 templates, Uses 0 templates
Used by as NameVersion
2.16.840.1.113883.10.22.3.6ContainmentKyellow.png IPS Medical Devices Section2017‑04‑11
2.16.840.1.113883.10.22.1.1Link.pngKyellow.png International Patient Summary2017‑04‑11
RelationshipAdaptation: template 1.3.6.1.4.1.12559.11.10.1.3.1.3.5 (2013‑12‑20)
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 value="20070728"/>  <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 <supply> element shall be present. The moodCode attribute shall be EVN to reflect that a medical device has been provided.(IPS…ice)
Treetree.png@classCode
cs1 … 1FSPLY
Treetree.png@moodCode
cs1 … 1FEVN
Treetree.pnghl7:templateId
II1 … 1M(IPS…ice)
Treeblank.pngTreetree.png@root
uid1 … 1F2.16.840.1.113883.10.22.4.26
Treetree.pnghl7:id
II0 … *RThis optional element identifies the provision of the device (e.g. implant procedure)(IPS…ice)
Treetree.pnghl7:code
CD.IPS0 … 1RThis code can be used to classify the provision of the device, e.g. the kind of implant procedure.
If no implant is in situ this element is omitted.
(IPS…ice)
 Example<code code="71861002" codeSystem="2.16.840.1.113883.6.96" displayName="Implantation (procedure)"/>
Treetree.pnghl7:text
ED0 … 1R(IPS…ice)
Treeblank.pngTreetree.pnghl7:reference
TEL1 … 1M(IPS…ice)
Treeblank.pngTreeblank.pngTreetree.png@value
1 … 1RReference pointing to the narrative, typically #{label}-{generated-id}, e.g. #xxx-1
Treetree.pnghl7:effectiveTime
IVL_TS1 … 1RThe effectiveTime element denotes the date and time the device was provided to the patient. For an implanted device, that is the date and time of implantation. If this entry indicate a past use if a device, the time interval form of shall be used, with the low and high values describing when the device was used.(IPS…ice)
Treetree.pnghl7:participant
1 … *RThe device is represented as a participant in the supply structure. The following descriptions apply to the device structure.(IPS…ice)
Treeblank.pngTreetree.png@typeCode
cs1 … 1FDEV
 Example<participant typeCode="DEV">
  <participantRole classCode="MANU">
    <id root="..." extension="..."/>    <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>
Treeblank.pngTreetree.pnghl7:participantRole
1 … 1R(IPS…ice)
Treeblank.pngTreeblank.pngTreetree.png@classCode
cs1 … 1FMANU
Treeblank.pngTreeblank.pngTreetree.pnghl7:id
0 … *RThe device ID, e.g. using UDI, is represented by the id element of the participant role. This element is optional, as not all device identifiers (serial numbers) may be known to the provider or patient.(IPS…ice)
 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"/>
Treeblank.pngTreeblank.pngTreetree.pnghl7:playingDevice
1 … 1RThe playingDevice element describes the device instance. (IPS…ice)
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.png@classCode
cs1 … 1FDEV
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.png@determiner​Code
cs1 … 1FINSTANCE
Treeblank.pngTreeblank.pngTreeblank.pngTreetree.pnghl7:code
CE.IPS1 … 1RThe device code describes the type of device (e.g. arm prosthesis, arterial stent).(IPS…ice)
 CONF
The value of @code shall be drawn from value set 2.16.840.1.113883.11.22.23 IPS Medical Devices (DYNAMIC)