ORBIS RIS
Document Information
Service-related contactinformation worldwide
All service-related contact information is available on this URL
https://www.dedalusgroup.de/radiologie-it/orbis-ris/
Table of Contents
1
Introduction... 5
Revision Record...5
Purpose and Intended Audience of this Document...5
Note...5
Acronyms and Abbreviations ...6
Related Documents ...6
2
ORBIS RIS INBOUND MESSAGES ... 7
ADT ...7
Supported ADT Events ...7
Processed ADT Segments...8
ORM...9
Supported ORM Events...9
Processed ORM Segments ...9
ORU...10
Supported ORU Events...10
Processed ORU Segments ...10
MFN ...11
Supported MFN Events ...11
Processed MFN Segments...11
3
ORBIS RIS Outbound Messages ... 12
ADT ...12
Supported ADT Events ...12
Generated ADT Segments...13
ORM...14
Supported ORM Events...14
Generated ORM Segments ...14
ORR...15
Supported ORR Events...15
Generated ORR Segments...15
ORU...16
Supported ORU Events...16
Generated ORU Segments ...16
DFT...17
Generated DFT Segments ...17
BAR ...18
Supported BAR Events ...18
Generated BAR Segments...18
MDM...19
Supported MDM Events...19
1
I
NTRODUCTION
R
EVISIONR
ECORDHL7 Conformance Statement ORBIS RIS Revision
Number Date Reason for Change draft 04/10/2013 Initial version
1.0 02/06/2014 Update document numbering 1.1 12/01/2021 Change for Dedalus Group
P
URPOSE ANDI
NTENDEDA
UDIENCE OF THISD
OCUMENTThis document is a HL7 Conformance Statement for the HL7 Services of the ORBIS RIS product 08.04.x. The user of this document is involved with system integration and/or software design. We assume that the reader is familiar with the terminology and concepts that are used in HL7 standard and the IHE Technical Framework.
Readers not familiar with HL7 terminology should first read the appropriate parts of the HL7 standard itself, prior to reading this conformance statement.
Although the use of this conformance statement in conjunction with the HL7 standard is intended to facilitate communication with ORBIS RIS 8.4.x, it is not sufficient to guarantee, by itself, the inter-operation of the connection between ORBIS RIS 8.4.x and the 3rd party HL7-based system.
The integration of any device into a system of interconnected devices goes beyond the scope of the HL7 standard and this conformance statement when interoperability is desired. The responsibility for analyzing the applications requirements and developing a solution that integrates the Agfa equipment with other vendors’ systems is the user’s responsibility and should not be underestimated.
N
OTEORBIS RIS is part of ORBIS HIS and uses the same technology and base for creating and communicating HL7 messages.
In some cases ORBIS RIS is used ‘stand-alone’ and exchanges HL7 messages with other HIS. Version numbers of ORBIS RIS and HIS are always consistently.
A
CRONYMS ANDA
BBREVIATIONSDefinitions, terms and abbreviations used in this document, many of which are defined within the HL7 standard. Abbreviations and terms are as follows:
ADT Admission, Discharge, and Transfer message AL1 Patient Allergy Information segment
BAR Add/change billing account DFT Detail financial transactions EVN Event Type segment HL7 Health Level 7
IHE Integrating the Healthcare Enterprise MRG Merge Patient Information segment MSH Message Header segment
NTE Notes and comments segment OBR Observation Request segment OBX Observation/Result segment ORC Common Order segment ORM Order Request message ORR Order response
ORU Observation Results - Unsolicited message PID Patient ID segment
PV1 Patient Visit segment
RIS Radiology Information System
R
ELATEDD
OCUMENTS HL7 Standard , see www.hl7.org IHE Radiology Technical Framework Revision 9.0 – Final Text, June 2008 – see www.ihe.net
AGFA Documents:
Functional Description_BI_HL7v2.5_external.pdf see Livelink ID: 28780177 Functional description_RIS_BI_HL7v2.5_external.pdf see Livelink ID: 36560744 Functional description_BI_HL7_MFN02 – Staff Practitioner_external.pdf see Livelink ID:
2
ORBIS RIS INBOUND MESSAGES
ADT
Supported ADT Events
For more information about the processed segments and segment mappings, refer to the document specified in the Conformance profile document column.
Table 1 Supported ADT Events Func
Area Event Code ADT Trigger Event Conformance profile document ADT A01 Admit/Visit notification Functional Description_BI_HL7v2.5_external.pdf ADT A02 Transfer a patient Functional Description_BI_HL7v2.5_external.pdf ADT A03 Discharge/End visit Functional Description_BI_HL7v2.5_external.pdf ADT A04 Register a patient Functional Description_BI_HL7v2.5_external.pdf ADT A05 Pre-admit a patient Functional Description_BI_HL7v2.5_external.pdf ADT A06 Change an outpatient to an inpatient Functional Description_BI_HL7v2.5_external.pdf ADT A07 Change an inpatient to an outpatient Functional Description_BI_HL7v2.5_external.pdf
ADT A08 Update patient information Functional Description_BI_HL7v2.5_external.pdf ADT A11 Cancel admit/visit notification Functional Description_BI_HL7v2.5_external.pdf ADT A12 Cancel transfer Functional Description_BI_HL7v2.5_external.pdf ADT A13 Cancel discharge/end visit Functional Description_BI_HL7v2.5_external.pdf ADT A14 Pending admit Functional Description_BI_HL7v2.5_external.pdf ADT A21 Leave of absence Functional Description_BI_HL7v2.5_external.pdf ADT A22 Patient returns from a leave of absence Functional Description_BI_HL7v2.5_external.pdf ADT A27 Cancel pending admit Functional Description_BI_HL7v2.5_external.pdf ADT A28 Add person or patient information Functional Description_BI_HL7v2.5_external.pdf ADT A29 Delete person information Functional Description_BI_HL7v2.5_external.pdf ADT A31 Update person information Functional Description_BI_HL7v2.5_external.pdf
ADT A34
Merge patient information - patient ID
only (for backward compatibility -- deprecated Functional Description_BI_HL7v2.5_external.pdf
ADT A38 Cancel pre-admit Functional Description_BI_HL7v2.5_external.pdf ADT A40 Merge patient - patient identifier list Functional Description_BI_HL7v2.5_external.pdf ADT A45 Move visit information - visit number Functional Description_BI_HL7v2.5_external.pdf
Func Area
Event Code
ADT Trigger Event Conformance profile document
ADT A47 Change patient identifier list Functional Description_BI_HL7v2.5_external.pdf ADT A50 Change visit number Functional Description_BI_HL7v2.5_external.pdf ADT A52 Cancel leave of absence for a patient Functional Description_BI_HL7v2.5_external.pdf ADT A53 Cancel patient returns from a leave of absence Functional Description_BI_HL7v2.5_external.pdf
Processed ADT Segments
The processd ADT segments are event-dependent.
ORM
Supported ORM Events
For more information about the processed segments and other details, refer to the document specified in the Conformance profile document column.
Table 2 Supported ORM Events Func
Area
Event Code
ORM Trigger Event Conformance profile document
ORM O01 General order message - Order Placer Functional description_RIS_BI_HL7v2.5_external.pdf
Processed ORM Segments
MSH Message Header / Nachrichtenkopfinformationen EVN Event Type / Ereignisinformationen
PID Patient Identification / Patienteninformationen PV1 Patient Visit /Fall-/Besuchsinformationen
{ ORC Common Order / Auftrag
[ OBR Observation Request / Auftragsdetail/Untersuchung [{ OBX Observation/Result / Ergebnis/Befund
}] ]
[ ZDS ] Study Instance UID
[{ ZBK }] Additional catalog / Zusatzkataloge Fall-Bendef }
ORU
Supported ORU Events
For more information about the processed segments and segment mappings, refer to the document specified in the Conformance profile document column.
Table 3 Supported ORU Events Func
Area
Event Code
ORU Trigger Event Conformance profile document ORU R01 Unsolicited Observation Message Functional
description_RIS_BI_HL7v2.5_external.pd f
Processed ORU Segments
MFN
Supported MFN Events
For more information about the processed segments and segment mappings, refer to the document specified in the Conformance profile document column.
Table 4 Supported MFN Events Func
Area
Event Code
MFN Trigger Event Conformance profile document MFN M02 Staff/Practitioner master file Fuctional description_BI_HL7_MFN02 –
Staff Practitioner_external.pdf
Processed MFN Segments
For detailed information please see documentation in “Fuctional description_BI_HL7_MFN02 – Staff Practitioner_external.pdf”
3
ORBIS RIS O
UTBOUND
M
ESSAGES
ADT
Supported ADT Events
For more information about the processed segments and segment mappings, refer to the document specified in the Conformance profile document column.
Table 5 Supported ADT Events Func
Area
Event Code
ADT Trigger Event Conformance profile document
ADT A01 Admit/Visit notification Functional Description_BI_HL7v2.5_external.pdf ADT A02 Transfer a patient Functional Description_BI_HL7v2.5_external.pdf ADT A03 Discharge/End visit Functional Description_BI_HL7v2.5_external.pdf ADT A04 Register a patient Functional Description_BI_HL7v2.5_external.pdf ADT A05 Pre-admit a patient Functional Description_BI_HL7v2.5_external.pdf ADT A06 Change an outpatient to an inpatient Functional Description_BI_HL7v2.5_external.pdf ADT A07 Change an inpatient to an outpatient Functional Description_BI_HL7v2.5_external.pdf ADT A08 Update patient information Functional Description_BI_HL7v2.5_external.pdf ADT A11 Cancel admit/visit notification Functional Description_BI_HL7v2.5_external.pdf ADT A12 Cancel transfer Functional Description_BI_HL7v2.5_external.pdf ADT A13 Cancel discharge/end visit Functional Description_BI_HL7v2.5_external.pdf ADT A14 Pending admit Functional Description_BI_HL7v2.5_external.pdf ADT A21 Leave of absence Functional Description_BI_HL7v2.5_external.pdf ADT A22 Patient returns from a leave of absence Functional Description_BI_HL7v2.5_external.pdf ADT A27 Cancel pending admit Functional Description_BI_HL7v2.5_external.pdf ADT A28 Add person or patient information Functional Description_BI_HL7v2.5_external.pdf ADT A29 Delete person information Functional Description_BI_HL7v2.5_external.pdf ADT A31 Update person information Functional Description_BI_HL7v2.5_external.pdf
ADT A34
Merge patient information - patient ID
only (for backward compatibility -- deprecated Functional Description_BI_HL7v2.5_external.pdf
ADT A38 Cancel pre-admit Functional Description_BI_HL7v2.5_external.pdf
ADT A40 Merge patient - patient identifier list Functional Description_BI_HL7v2.5_external.pdf ADT A45 Move visit information - visit number Functional Description_BI_HL7v2.5_external.pdf ADT A47 Change patient identifier list Functional Description_BI_HL7v2.5_external.pdf
Func Area
Event Code
ADT Trigger Event Conformance profile document
ADT A53 Cancel patient returns from a leave of absence Functional Description_BI_HL7v2.5_external.pdf
Generated ADT Segments
ORM
Supported ORM Events
For more information about the processed segments and segment mappings, refer to the document specified in the Conformance profile document column.
Table 6 Supported ORM Events Func
Area
Event Code
ORM Trigger Event Conformance profile document
ORM O01 General order message – Order Filler
Functional
description_RIS_BI_HL7v2.5_external.pdf
Generated ORM Segments
MSH Message Header / Nachrichtenkopfinformationen EVN Event Type / Ereignisinformationen
PID Patient Identification / Patienteninformationen PV1 Patient Visit /Fall-/Besuchsinformationen
{ ORC Common Order / Auftrag
[ OBR Observation Request / Auftragsdetail/Untersuchung [{ OBX Observation/Result / Ergebnis/Befund
}] ]
[ ZDS ] Study Instance UID
[{ ZBK }] Additional catalog / Zusatzkataloge Fall-Bendef }
ORR
ORR outbound messages are only used in a “Non-ORBIS HIS environment” for the communication of order changes to other HIS than ORBIS.
These messages are not necessary in an ORBIS environment.
Supported ORR Events
For more information about the processed segments and segment mappings, refer to the document specified in the Conformance profile document column.
Table 7 Supported ORR Events Func
Area Event Code ORM Trigger Event Conformance profile document ORR O02 Order response Functional description_RIS_BI_HL7v2.5_external.pdf
Generated ORR Segments
MSH Message Header / Nachrichtenkopfinformationen EVN Event Type / Ereignisinformationen
PID Patient Identification / Patienteninformationen PV1 Patient Visit /Fall-/Besuchsinformationen
ORC Common Order / Auftrag
{ OBR Observation Request / Auftragsdetail/Untersuchung
ORU
Supported ORU Events
For more information about the processed segments and segment mappings, refer to the document specified in the Conformance profile document column.
Table 8 Supported ORU Events Func
Area
Event Code
ORU Trigger Event Conformance profile document
ORU R01 Unsolicited Observation Message
Functional
description_RIS_BI_HL7v2.5_external.pdf
Generated ORU Segments
MSH Message Header / Nachrichtenkopfinformationen PID Patient Identification / Patienteninformationen PV1 Patient Visit /Fall-/Besuchsinformationen
{ OBR Observation Request / Auftragsdetail/Untersuchung
}
DFT
DFT outbound messages are only used in a “Non-ORBIS HIS environment” for the communication to other HIS than ORBIS.
These messages are not necessary in an ORBIS environment.
Supported DFT Events
For more information about the processed segments and segment mappings, refer to the document specified in the Conformance profile document column.
Table 9 Supported DFT Events Func
Area Event Code DFT Trigger Event Conformance profile document DFT P03 Post Detail Financial Transactions Functional
Description_BI_HL7v2.5_external.pdf
Generated DFT Segments
BAR
BAR outbound messages are only used in a “Non-ORBIS HIS environment” for the communication to other HIS than ORBIS.
These messages are not necessary in an ORBIS environment.
Supported BAR Events
For more information about the processed segments and segment mappings, refer to the document specified in the Conformance profile document column.
Table 10 Supported DFT Events Func
Area Event Code DFT Trigger Event Conformance profile document
BAR P01 Add patient accounts Functional
Description_BI_HL7v2.5_external.pdf
BAR P02 Purge patient accounts Functional
Description_BI_HL7v2.5_external.pdf
BAR P05 Update account Functional
Description_BI_HL7v2.5_external.pdf BAR P12 Update Diagnosis/Procedure Functional
Description_BI_HL7v2.5_external.pdf
Generated BAR Segments
MDM
Supported MDM Events
For more information about the processed segments and segment mappings, refer to the document specified in the Conformance profile document column.
Table 11 Supported MDM Events Func
Area
Event Code
DFT Trigger Event Conformance profile document MDM T01 Original document notification Functional
Description_BI_HL7v2.5_external.pdf MDM T02 Original document notification and content Functional
Description_BI_HL7v2.5_external.pdf MDM T09 Document replacement notification Functional
Description_BI_HL7v2.5_external.pdf MDM T10 Document replacement notification and content Functional
Description_BI_HL7v2.5_external.pdf MDM T11 Document cancel notification Functional
Description_BI_HL7v2.5_external.pdf
