CRIS HL7 Conformance Statement (RIS PD166)

CRIS HL7 Conformance Statement (RIS_PD166) v1.3

CRIS HL7Conformance Statement (RIS_PD166)

This HL7 conformance statement describes the HL7 functionality of the CRIS Radiological Information System.

Author:Steven Verdon

Version:v1.3

Issue Date:29th December 2014

Copyright 2014Healthcare Software Systems. All Rights Reserved

These materials are or comprise restricted and proprietary confidential information of Healthcare Software Systems. Disclosure to or use by the recipient shall not convey any intellectual property rights in these materials. The right to use these materials by the recipient is subject to restrictions and limitations contained in the Provision of Integrated Care Record System and Associated Services Agreement and related agreements.

Confidentiality

All information in this document is provided in confidence for the sole purpose of adjudication of the document and shall not be used for any other purpose and shall not be published or disclosed wholly or in part to any other party without HSS’s prior permission in writing and shall be held in safe custody. These obligations shall not apply to information which is published or becomes known legitimately from some source other than HSS.

Many of the product, service and company names referred to in this document are trademarks or registered trademarks.

They are all hereby acknowledged.

Document Control

1Introduction

1.1Intended Audience

1.2Important considerations for the reader

1.3Related documents

2Acronyms and Abbreviations

3Inbound messages (to RIS)

3.1Messages supported

3.1.1ADT Messages supported

3.1.2OMG Messages supported

3.1.3ORU Messages supported

3.1.4SIU Messages supported

3.1.5QRY Messages supported

3.1.6QBP Messages supported

4Outbound messages (from RIS)

4.1Messages supported

4.1.1ADT Messages supported

4.1.2OMG Messages supported

4.1.3ORU Messages supported

4.1.4SIU Messages supported

4.1.5ORG Messages supported

4.1.6RSP Messages supported

4.1.7DSR Messages supported

4.1.8ACK Messages supported

1Introduction

This HL7 conformance statement describes the HL7 functionality of the CRIS Radiological Information System.

This version of the conformance statement applies to CRIS interface release 2.09.10k onwards.

1.1Intended Audience

This document is intended for system integrators, third party suppliers and potential customers, the reader is assumed to be familiar with the HL7 v2.4 standard.

1.2Important considerations for the reader

This conformance statement by itself is insufficient to guarantee successful connectivity between CRIS and software/equipment from other vendors. Readers should be aware of the following issues.

• CRIS has been tested to ensure that the implementation corresponds with this conformance statement. When attempting to determine the compatibility of equipment from another vendor the first step would be to compare the HL7 conformance statement of the equipment under consideration with this document. If comparison of the two conformance statements suggests that the two systems should be compatible then additional tests should be carried out to ensure that the required functionality and performance is achievable.
• As the HL7 standard evolves Healthcare Software Systems LTD reserves the right to make changes to the CRIS HL7 functionality. The user or user’s agent should ensure that any equipment connected via HL7 also evolves with the HL7 standard. Failure to do so may result in loss of connectivity.

1.3Related documents

• HL7 Standard (
• RIS_PD151, PAS Link, (
• RIS_PD154, OCS Link (
• RIS_PD160, HL7 Outbound Interface (
• RIS_PD163, HL7 Inbound Interface (

2Acronyms and Abbreviations

The following acronyms and abbreviations are used in this document and it’s associated documents detailed in 1.3 related documents

• ACKAcknowledgement
• ADTAdmission, Discharge and Transfer message
• AL1 Patient Allergy Information segment
• DSPDisplay data segment
• DSRDisplay query response
• EVNEvent Type segment
• HL7Health Level 7 (v2.4 adhered to)
• MRGMerge Patient Information segment
• MSAMessage acknowledgement segment
• MSHMessage Header segment
• NK1Next of Kin segment
• NTENotes and Comments segment
• OBRObservation Request segment
• OBXObservation/Result segment
• OMGOrder message (replaces ORM)
• ORCCommon order segment
• ORGApplication Level acknowledgement for OCS (Orders)
• ORUObservation results (provisional, final and changed)
• PD1Patient Additional demographics segment
• PID Patient Identifier segment
• PV1 Patient Visit segment
• QAKQuery acknowledgement
• QBPQuery by parameter
• QPDQuery parameter definition segment
• QRDQuery definition segment
• QRYDisplay query
• RSPResponse
• SCHSchedule information unsolicited segment
• SIU Schedule information unsolicited
• TXATranscription document header segment
• ZDSCustom segment required by certain PACS vendors

3Inbound messages (to RIS)

3.1Messages supported

3.1.1ADT Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

3.1.2OMG Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

3.1.3ORU Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

3.1.4SIU Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in-depth detail of the extent we use these messages.

3.1.5QRY Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

3.1.6QBP Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

4Outbound messages (from RIS)

4.1Messages supported

4.1.1ADT Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

4.1.2OMG Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

4.1.3ORU Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

4.1.4SIU Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

4.1.5ORG Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

4.1.6RSP Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

4.1.7DSR Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

4.1.8ACK Messages supported

Please refer to the technical specifications detailed in “1.3 related documents” for in depth detail of the extent we use these messages.

Healthcare Software Systems2014Commercial in ConfidencePage 1 of 9