IHE Patient Care Device Technical Framework

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