IHE Patient Care Device Technical Framework

More documents

Recommendations

Info

IHE Patient Care Device Technical Framework, Vol. 2: Transactions________________________________________________________________________102030MSH-1 Field Separator, required:The IHE PCD Technical Framework requires that applications support HL7-recommended value that is | (ASCII 124).MSH-2 Encoding Characters, required:This field contains the four characters in the following order: the componentseparator, repetition separator, escape character, and subcomponent separator. TheIHE PCD Technical Framework requires that applications support HL7-recommended values ^~\& (ASCII 94, 126, 92, and 38, respectively).MSH-3 Sending Application (HD), required:Components: ^ ^ First component (optional): Namespace ID. Locally unique name for applicationimplementing PCD actor(s).Second component (required): Universal ID expressed as string of hexadecimaldigits. Implementations of PCD actors shall use an EUI 64 identifier. The IEEEdefined 64-bit extended unique identifier (EUI-64) is a concatenation of the 24-bitcompany_id value by the IEEE Registration Authority and a 40-bit extensionidentifier assigned by the organization with that company_id assignment.Third component (required): EUI-64.MSH-4 Sending Facility (HD), required but may be empty:Components: ^ ^ For the IHE PCD Technical Framework, when populated, this field shall beimplemented as:First component (required): Namespace ID. The name of the organizational entityresponsible for the sending application.Second component (optional): The URI (OID) of the organizational entity responsiblefor the sending application.Third component (optional): The type of identification URI provided in the secondcomponent of this field. The codification of these three components is entirely sitedefined.It may be detailed in the national extensions of this framework.MSH-5 Receiving Application (HD), required but may be empty:Components: ^ ^ Rev. 1.1 TI: 2006-08-1531Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA
102030IHE Patient Care Device Technical Framework, Vol. 2: Transactions________________________________________________________________________For the IHE PCD Technical Framework, when populated, this field shall beimplemented as:First component (required): Namespace ID. The name of the organizational entityresponsible for the receiving application.Second component (optional): The URI (OID) of the organizational entity responsiblefor the receiving application.Third component (optional): The type of identification URI provided in the secondcomponent of this field. The codification of these three components is entirely sitedefined.It may be detailed in the national extensions of this framework.MSH-6 Receiving Facility (HD), required but may be empty:Components: ^ ^ For the IHE PCD Technical Framework, when populated, this field shall beimplemented as:First component (required): Namespace ID. The name of the organizational entityresponsible for the receiving application.Second component (optional): The URI (e.g. OID) of the organizational entityresponsible for the receiving application.Third component (optional): The type of identification URI provided in the secondcomponent of this field. The codification of these three components is entirely sitedefined.It may be detailed in the national extensions of this framework.MSH-7 Date/Time of Message (TS), required:The IHE PCD TF requires this field be populated with:For the IHE PCD Technical Framework, when populated, this field shall beimplemented as:Format: YYYY[MM[DD[HH[MM[SS]]]]][+/-ZZZZ]Time zone qualification of the date/time is required.MSH-7 shall be used only to provide message created timeMSH-9 Message Type (MSG), required:Components: ^ ^ Definition: This field contains the message type, trigger event, and the messagestructure ID for the message. All three components are required.Its content is defined within each transaction-specific section of this document.Rev. 1.1 TI: 2006-08-1532Copyright © 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 31: IHE Patient Care Device Technical F
Page 35 and 36: 10IHE Patient Care Device Technical
Page 43 and 44: 102030IHE Patient Care Device Techn
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?