IHE Patient Care Device Technical Framework

More documents

Recommendations

Info

IHE Patient Care Device Technical Framework, Vol. 2: Transactions________________________________________________________________________SubjectContainment Tree Hierarchical LevelMedical:OBX-4Examples1Virtual (Medical)Ordinal11112Virtual (Medical)Ordinal11223Virtual (Medical)Ordinal1213Recommend that Ordinal value is unique among entire setFigure 8 Example of Mapping Containment to OBX-4For example the OBX-4 for the would be expressedas 1.2.1.3.10OBX-2 the valid HL7 types for the mapping are NM, ST, SN, CE, CF (String may havesome implied structure)The specification of the containment tree provides a mechanism to address dynamicconfiguration of a PCD. For example, a patient monitor may have one or more “plug-ins”which may be added to and removed from the patient monitor as the patient’s clinicalcondition changes. When a plug-in is removed the ordinal numbers previously assignedto that plug-in shall be reserved. Replacement of the plug-in shall result in the reassignmentof the reserved ordinal numbers to the plug-in which has been replaced.Addition of a new plug-in shall result in the assignment of ordinal numbers which havenot been reserved.A.2 ISO/IEEE Nomenclature mapping to HL7 OBX-320The ISO/IEEE Nomenclature provides an unambiguous coding which is mapped to HL7OBX-3 as follows:HL7 OBX-3 is of type CE consisting of:Rev. 1.1 TI: 2006-08-1527Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA
IHE Patient Care Device Technical Framework, Vol. 2: Transactions________________________________________________________________________Table 7 HL7 Component Table - CE - Coded ElementSEQ LEN DT Usage Card. TBL# Component Comments SecNameRef1 20 ST R [1..1] Identifier Nomenclature 2.A.74Code2 199 ST R [1..1] Text Reference ID 2.A.743 20 ID R [1..1] 0396 Name of “MDC”2.A.35Coding System4 20 ST O [0..1] Alternate2.A.74Identifier5 199 ST O [0..1] Alternate Text 2.A.746 20 ID O [0..1] 0396 Name of2.A.35AlternateCoding System10Definition: This data type transmits codes and the text associated with the code.Maximum Length: 483Where:Nomenclature Code is the string representation of the decimal value corresponding to thecontext free 32 bit representation of the Nomenclature Code[context-free] Nomenclature Code == (Code Block number * 2 ** 16 ) + [contextsensitive],where [context-sensitive] is an offset, reflecting a particular variant of anassociated “discriminator”. The Reference ID is also modified to reflect the variant.For example, for the “Device Type” Nomenclature, the Device Type discriminator is asfollows:Ref ID variant Description Term CodeOffsetDEV Not-otherwise specified 0MDS Medical Device System 1VMD Virtual Medical Device 2CHAN Channel 3The context-free nomenclature code for a term in code block number 1 whose termcode=4104 is equal to (( 1 * 2 ** 16 ) + 4104) = 1*65536 + 4104 = 69640 (which uniquelyidentifies the SpO2 monitor term) with a Reference ID ofMDC_DEV_ANALY_SAT_O2. The context-sensitive form for the variant “MDS” isRev. 1.1 TI: 2006-08-1528Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA
Page 3 and 4: 10203040IHE Patient Care Device Tec
Page 7 and 8: IHE Patient Care Device Technical F
Page 9 and 10: 1020IHE Patient Care Device Technic
Page 27: IHE Patient Care Device Technical F
Page 33 and 34: 102030IHE Patient Care Device Techn
Page 35 and 36: 10IHE Patient Care Device Technical
Page 79 and 80:
Attribute Description Term Code Dat
Page 81 and 82:
elowChannel AttributesAttribute Des
Page 83 and 84:
IHE Patient Care Device Technical F
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
102030IHE Patient Care Device Techn
Page 95 and 96:
102030405060IHE Patient Care Device
Page 97 and 98:
10203040IHE Patient Care Device Tec
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
show all

IHE Patient Care Device Technical Framework

Create successful ePaper yourself

Delete template?

Save as template?