Difference between revisions of "2.16.840.1.113883.10.22.4.26/static-2017-04-11T000000"

From HL7 IPS
Jump to: navigation, search
(Automated ADBot page content)
(Automated ADBot page content)
Line 1: Line 1:
<
+
<

Revision as of 09:34, 25 July 2018

Id2.16.840.1.113883.10.22.4.26Effective Date2017‑04‑11
Other versions this id:
    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)
    Associated with
    Associated with 6 concepts
    IdNameData Set
    hl7ips-data​element-57Kyellow.png Device Kyellow.png CEN/TC 251 prEN 17269
    hl7ips-data​element-60Kyellow.png Device Identifier Kyellow.png CEN/TC 251 prEN 17269
    hl7ips-data​element-218Kyellow.png Device content Status Kyellow.png CEN/TC 251 prEN 17269
    hl7ips-data​element-58Kyellow.png Device Type Kyellow.png CEN/TC 251 prEN 17269
    hl7ips-data​element-59Kyellow.png Use start date Kyellow.png CEN/TC 251 prEN 17269
    hl7ips-data​element-150Kyellow.png Use end date Kyellow.png CEN/TC 251 prEN 17269
    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 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 <supply> element shall be present. The moodCode attribute shall be EVN to reflect that a medical device has been provided.</supply>(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: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 … 1R
    This element provides the interval of time corresponding to the device usage by/presence in the patient.
    (IPS...ice)
    Treeblank.pngTreetree.png@xsi:type
    1 … 1FIVL_TS
    Treeblank.pngTreetree.pnghl7:low
    TS1 … 1RThe lower bound of the interval represents the start date/time.(IPS...ice)
     
    Target.png
    hl7ips-data​element-59Kyellow.png Use start date Kyellow.png CEN/TC 251 prEN 17269
    Treeblank.pngTreetree.pnghl7: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.(IPS...ice)
     
    Target.png
    hl7ips-data​element-150Kyellow.png Use end date Kyellow.png CEN/TC 251 prEN 17269
    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)
     
    Target.png
    hl7ips-data​element-57Kyellow.png Device Kyellow.png CEN/TC 251 prEN 17269
    Treeblank.pngTreetree.png@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>
    Treeblank.pngTreetree.pnghl7:participantRole
    1 … 1R(IPS...ice)
    Treeblank.pngTreeblank.pngTreetree.png@classCode
    cs1 … 1FMANU
    Treeblank.pngTreeblank.pngTreetree.pnghl7: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.
    (IPS...ice)
     
    Target.png
    hl7ips-data​element-60Kyellow.png Device Identifier Kyellow.png 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"/>
    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.IPS (preferred)1 … 1RThe device code describes the type of device (e.g. arm prosthesis, arterial stent).(IPS...ice)
     
    Target.png
    hl7ips-data​element-218Kyellow.png Device content Status Kyellow.png CEN/TC 251 prEN 17269
    hl7ips-data​element-58Kyellow.png Device Type Kyellow.png 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)