IHE Patient Care Device Technical Framework

IHE Patient Care Device Technical Framework, Vol. 2: Transactions________________________________________________________________________acknowledged. The value of MSH-9-3-Message structure for the generalacknowledgment message is always ACK.Applications that receive HL7 messages shall send acknowledgments using the HL7Original Mode (versus Enhanced Acknowledgment Mode).G.3 Message granularity1020The sending application shall send as many messages as there are events recorded. Forinstance, if at the same time there is a change both to the patient’s location (fromemergency room to GI surgery ward) and to the patient’s attending doctor (from Dr. EricEmergency to Dr. John Appendectomy), the sending application will transmit twomovements using HL7 messages ADT^A02 (transfer) and ADT^A54 (change attendingdoctor). Both events will have the same effective date/time (EVN-6 – Event Occurred). Ifthe Historic Movement option is in use, each of these movements will have a uniqueidentifier.The exceptions to this fine granularity are:• The Admit Inpatient (A01) and Register Outpatient (A04) events can also assign alocation and an attending doctor to the patient, known when the event is recorded.• A change of patient class (A06 or A07) also assigns at the same time a newlocation to the patient.• The Cancel Discharge/End Visit event also includes at the same time the patientlocation after the cancellation has been processed.G.4 HL7 empty field conventionAccording to the HL7 standard, if the value of a field is not present, the receiver shall notchange corresponding data in its database. However, if the sender defines the field valueto be the explicit NULL value (i.e., two double quotes ""), it shall cause removal of anyvalues for that field in the receiver's database. This convention is fully applied by IHEprofiles based on HL7 v2.x messages.Appendix HIHE Integration StatementsH.1 IHE Integration Statements30IHE Integration Statements are documents prepared and published by vendors to describethe intended conformance of their products with the IHE Technical Framework. Theyidentify the specific IHE capabilities a given product is designed to support in terms ofthe key concepts of IHE: Actors and Integration Profiles (described in Volume I, section2 of the IHE Technical Framework).Rev. 1.1 TI: 2006-08-1599Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA