HL7 Conformance Statement syngo.plaza VB30A siemens.com/healthineers Table of Contents 1 Introduction .................................................................................... 4 1.1 Purpose ................................................................................................................ 4 1.2 Audience ............................................................................................................... 4 1.3 Definitions, Terms and Abbreviations .................................................................... 4 Abbreviations .................................................................................................................................... 4 Definition and Terms ........................................................................................................................ 4 1.4 References ............................................................................................................ 5 2 General Information ........................................................................ 7 3 Overview ......................................................................................... 8 3.1 Supported Messages ............................................................................................. 8 3.2 Acknowledgement Behavior .................................................................................. 9 4 Implementation Details ................................................................... 9 4.1 HL7 Version ........................................................................................................... 9 4.2 Configuration ........................................................................................................ 9 4.2.1 Minimal Layer Protocol ............................................................................................................ 9 4.2.2 Sending Messages to syngo.plaza .......................................................................................... 10 4.2.3 Sending Messages out of syngo.plaza ................................................................................... 10 4.2.4 General message syntax ........................................................................................................ 10 4.2.5 Uniqueness of Patient ID ....................................................................................................... 12 4.2.6 Patient Identification ............................................................................................................. 12 4.2.7 Patient Name ......................................................................................................................... 12 4.2.8 Supported Character-Sets ...................................................................................................... 14 4.3 Restrictions ......................................................................................................... 16 5 Inbound Messages ........................................................................ 17 5.1 Patient Administration Messages ........................................................................ 17 5.1.1 Transfer a patient (ADT^A02) ................................................................................................ 17 5.1.2 Transfer an Outpatient to Inpatient (ADT^A06) .................................................................... 20 5.1.3 Transfer an Inpatient to Outpatient (ADT^A07) .................................................................... 22 5.1.4 Patient Information Update (ADT^A08) ................................................................................ 24 5.1.5 Patient Merge (ADT^A40) ...................................................................................................... 26 5.1.6 Merge Patient Information (ADT^A18) ................................................................................. 29 5.2 Order Messages ...................................................................................................... 30 5.2.1 General order message (ORM^O01) ..................................................................................... 30 5.2.2 Unsolicited Observation Message (ORU^R01) ...................................................................... 33 5.2.3 Imaging Order Message (OMI^O23) ...................................................................................... 38 5.3 Order Administration Messages (proprietary) ......................................................... 42 5.3.1 Order Level Correction Message (ZPA^I05) ........................................................................... 42 5.3.2 Study Level Correction Message (ZPA^S05) .......................................................................... 45 © Siemens Healthcare GmbH / Siemens Medical Solutions USA, Inc., 2018. All rights reserved.. HL7 Conformance Statement syngo.plaza VB30A 2 of 57 5.4 Image Notification Resent Trigger (ZPA^G01) .......................................................... 47 6 Outbound Messages ...................................................................... 49 6.1 Image Notifications (via Report Export) ............................................................... 49 7 Security ......................................................................................... 53 7.1 Secure Transport Connection Profiles .................................................................. 53 8 Appendix: Some more examples for HL7 messages ........................ 54 8.1 ADT messages from RIS to syngo.plaza ................................................................ 54 7.1.1 Change of patient’s demographic data ................................................................................. 54 7.1.2 Change of patient name ........................................................................................................ 54 7.1.3 Change of a patient ID ........................................................................................................... 54 7.1.4 Merge of two patients ........................................................................................................... 54 8.2 ORU messages from syngo.plaza to RIS ............................................................... 55 © Siemens Healthcare GmbH / Siemens Medical Solutions USA, Inc., 2018. All rights reserved.. HL7 Conformance Statement syngo.plaza VB30A 3 of 57 1 Introduction 1.1 Purpose This document gives a compact view of the HL7 interface provided by syngo.plaza. The HL7 interface of syngo.plaza is based on the requirements and suggestions of the IHE Framework [1] in regards to supported message types. Hint: Messages, which do not 100% comply with the definition of IHE, but contain the minimum required information as per definition of syngo.plaza, will nevertheless be processed. 1.2 Audience This document is intended for hospital IT staff, health system integrators, software designers or implementers. It is as- sumed that the reader has a basic understanding of HL7 and IHE. 1.3 Definitions, Terms and Abbreviations Abbreviations ADT Admission, Discharge, Transfer DICOM Digital Imaging & Communication in Medicine HL7 Health Level Seven HIS Hospital Information System IHE Integrating the Healthcare Enterprise ISO International Standards Organization IS Information System NHS National Health Service OEM Original Equipment Manufacturer ORM Order Request Message OSI Open Systems Interconnection PACS Picture Archiving and Communication System PID Patient Identifier- segment within ADT and ORM PPS Performed Procedure Step RIS Radiology Information System RP Requested Procedure SPS Scheduled Procedure Step TCO Total Cost of Ownership XML Extensible Mark-up Language Definition and Terms ADT Admission, Discharge, Transfer. A record type used by the HL7 standard for communication of admission of patients into the hospital, discharges from hospital or internal patient transfers inside the hospital. EVN The EVeNt segment is a part of a HL7 message. Its purpose is to communicate the pragmatic intention (called “event”) of the message. Example: a transfer of a patient to a different location will have an event code “A02” which means in HL7 a “transfer”. HL7 HL7 is a standard for information exchange between medical applications. It is an abbreviation of "Health Level Seven" which stands for the 7th OSI layer protocol for the health environment. The HL7 protocol © Siemens Healthcare GmbH / Siemens Medical Solutions USA, Inc., 2018. All rights reserved.. HL7 Conformance Statement syngo.plaza VB30A 4 of 57 defines the format and the content of the messages that applications have to pass to one another under various conditions. Example: a central information system sends a message to a subsystem that a patient has been admitted in a hospital. IHE Integrating the Healthcare Enterprise is an organisation designed to stimulate the integration of the information systems that support modern healthcare institutions. IP Internet Protocol (IP) is a wide spread network protocol and base of the internet. It defines the routing of the data communication from one computer through the network to another computer. It is working in the “network layer” which is level 3 of the ISO / OSI model. MRG The MeRGe segment is a part of an HL7 merge message. In this segment a second patient will be referenced which is to be merged with the first patient referenced in the PID segment. The patient from PID segment will inherit all information from the other patient while