Tegris Technical Information

Tegris
HL7 Specification

This document is intended to provide information to an international audience outside of the US.
TTI170520XYEN01
Legal statement

Copyright

Copyright© 2012-2022 Getinge AB. All rights reserved. Getinge AB and all of its subsidiaries and/or
affiliates, hereinafter referred as Getinge, expressly reserve and retain all right, title and interest in and
to all existing intellectual property in the products of Getinge, its subsidiaries and/or affiliates. No right,
title or interest is granted by Getinge.

Trademark

Getinge and Tegris are trademarks or registered trademarks of Getinge AB, Maquet GmbH, and/or
their subsidiaries and/or affiliates. All other company or product names are trademarks or registered
trademarks of their respective holders.

No Warranty

The software, documents, information, and materials in this publication are provided “as is” without
warranty of any kind, either express or implied, including, but not limited to the implied warranties of
merchantabilities, fitness for a particular purpose, or non-infringement. The contents of this publication
may include technical inaccuracies or typographical errors. Changes are periodically added to the
information herein; these changes will be incorporated in new editions of the publication. Getinge Ma-
quet GmbH may make improvements and/or changes to the product(s) and/or program(s) described in
this publication at any time without notice.

Limitation of Liability

To the fullest extent permitted by applicable laws, in no event, shall Getinge be liable for any loss of
profits or revenues, or any direct, indirect, consequential, incidental, unforeseen, special or punitive
damages including, but not limited to, loss of use of any Products, loss of stored, transmitted or re-
corded data, damage to Products, cost of capital, cost of substitute products, facilities, service or re-
placement service, or downtime costs, arising out of any products, information, software, documents
or materials described herein, even if advised of the possibility of such damages.

Disclaimer

This document is intended to provide information to an international audience outside the U.S.
Revision History

Revision Date Author Change

1.0 2022.02 DM, MS, MF First Creation

TTI170520XYEN01
Abbreviations

ACK Acknowledgement

ADT Admission – Discharge - Transfer

DICOM Digital Imaging and Communications in Medicine

HL7 Health Level Seven

HIS Hospital Information System

IHE Integrating the Healthcare Enterprise

MLLP Minimum Lower Layer Protocol

MWL DICOM Modality Worklist

ORM Order Request Message

ORU Unsolicited Transmission of an Observation

RIS Radiological Information System

SIU Scheduling Information Unsolicited

TCP/IP Transmission Control Protocol / Internet Protocol

TTI170520XYEN01
 Tegris IEC 80001 Hospital Network Integration Information

Inhalt
1 Introduction__________________________________________________________ 6
1.1 Intended Audience_______________________________________________ 6
1.2 Supported HL7 Versions___________________________________________ 6
1.3 Supported Character Sets__________________________________________ 6
2 Networking___________________________________________________________ 6
2.1 Minimum Lower Layer Protocol (MLLP)______________________________ 6
2.2 Acknowledgement and Error Messages______________________________ 7
2.3 Data Flow Diagram_______________________________________________ 7
3 HL7 Messages_________________________________________________________ 8
3.1 Inbound Messages_______________________________________________ 8
3.2 SIU Message Structure____________________________________________ 8
3.3 HL7 mapping to Tegris Patient Service_______________________________ 9
4 Limitations__________________________________________________________ 12
5 Support of alternative HL7 message types_________________________________ 12
6 SIU sample message__________________________________________________ 12

TTI170520XYEN01
Tegris IEC 80001 Hospital Network Integration Information

1 Introduction
This document specifies the conformance of the Tegris system with the HL7 standard. It describes the
interface to receive HL7 messages and thus is essential to evaluate whether another HL7 compliant
system can transmit data to the Tegris system.

1.1 Intended Audience

This document is intended for hospital staff, health system integrators, software designers or imple-
menters. It is assumed that the reader has a working understanding of HL7 and communication stan-
dards in Healthcare.

1.2 Supported HL7 Versions

The Tegris system supports HL7 messages in version 2.7. Further changes to the specification are
possible within the scope of customer-specific requirements.

1.3 Supported Character Sets

Tegris HL7 Integration supports Unicode UTF8 character set by default. Other character sets are pos-
sible within the scope of customer-specific requirements.

2 Networking
Tegris HL7 communication works with socket communication based on TCP/IP protocol. Behind the
port a TCP listener observes incoming messages. The communication link between the sockets is kept
until the client or server terminates the connection.

2.1 Minimum Lower Layer Protocol (MLLP)

The low-level protocol uses the standard HL7 start and stop bytes to mark the message. Each mes-
sage is transported via the socket following this scheme:

<VT><...HL7 message...><FS><CR>
• VT - vertical tab (0x0B)
• FS - file separator (0x1C)
• CR - carriage return (0x0D)

6 / 13 TTI170520XYEN01
 Tegris IEC 80001 Hospital Network Integration Information

2.2 Acknowledgement and Error Messages

The Tegris system is configured to send an acknowledgement after successful processing the HL7
message. If the message could not be processed successfully by the Tegris system, an error message
is sent back to the sender. Acknowledgement and error messages are sent on the same connection
the incoming HL7 message has been received.

2.3 Data Flow Diagram

Figure 1:  Data Flow Diagram

Getinge Communication Broker is the interface between customer hospital IT systems and the Get-
inge applications. The Communication Broker is connected to Tegris Patient Service, that manages
worklist communication to all individual Tegris units. Assignment of a surgery case to an individual OR
is based on the field “PlannedOR”.

TTI170520XYEN01 7 / 13
Tegris IEC 80001 Hospital Network Integration Information

3 HL7 Messages

3.1 Inbound Messages

The following HL7 events are supported by the Tegris Inbound Worklist interface.

Role Rights
SIU^S12 Notification of new appointment booking
SIU^S13 Notification of appointment rescheduling
SIU^S14 Notification of appointment modification
SIU^S15 Notification of appointment cancellation
SIU^S16 Notification of appointment discontinuation
SIU^S17 Notification of appointment deletion

Table 1:  Inbound Messages

3.2 SIU Message Structure

New/ modified appointment bookings will be processed as SIU message in the following format:

MSH Message Header

SCH Scheduling Activity Information
[ { NTE } ] Notes and Comments for the SCH
PID Patient Identification
[ { OBX } ] Observation/Result for Patient
[ PV1 ] Patient Visit
RGS Resource Group
{ AIS } Appointment Information - Services
AIL Appointment Information - Location Resource
[{ AIP }] Appointment Information - Personnel Resource

8 / 13 TTI170520XYEN01
 Tegris IEC 80001 Hospital Network Integration Information

3.3 HL7 mapping to Tegris Patient Service

Seq Element name Tegris Patient Mandatory / Description

Service Optional
Sending Applica- System, which sends the
MSH.3 SourceSystem M
tion message
Date/Time Of Mes-
MSH.7 MessageCreation M
sage
Message Control
MSH.10 MessageID M
ID
PID.3.1 Patient ID PatientID M PatientID in hospital
Patient Name.
PID.5.1 PatientLastName M Last name
Family Name
Patient Name.Giv-
PID.5.2
en Name
First name + (optional) middle
Second And Fur- PatientFirstName O
name / Initial
PID.5.3. ther Given Names
Or Initials Thereof
Patient Name.Pro-
PID.5.14 PatientTitle O Title
fessional Suffix
PatientDateOf- Birthday
PID.7 Date/Time of Birth O
Birth if empty: 1980-01-01
Sex

Default mapping Tegris Pa-

tient Service:
PID.8 Sex PatientSex O
‘empty’ - unknown
M - male
F - femal
O - other
Optional other IDs, e.g. case
PV1.19.1 Visit Number PatientOtherID O number, Social Security num-
ber
CurrentPatient
PV1.3.1 Point of Care O Current location of the patient
Location
Planned OR of the study.
AIL.3.2 Room PlannedOR M Must match configuration en-
try in Tegris
Planned study date and
AIL.6 Start Date/Time StudyDateTime M planned study time.
if invalid: DateTime.Now
Planned procedure duration
AIL.9 Duration StudyDuration O Not displayed in Tegris work-
list

TTI170520XYEN01 9 / 13
Tegris IEC 80001 Hospital Network Integration Information

Seq Element name Tegris Patient Mandatory / Description

Service Optional
Physician, contains more in-
formation in a matrix, Refer
to „Table  3: Physician data
mapping“ auf Seite 11
n/a n/a Physician O
Only first surgeon (Title and
Name) is processed and dis-
played by Tegris
Universal Service Surgical procedure designa-
AIS.3.2 StudyType O
Identifier.Text tion
Filler Appointment
SCH.2.1 AccessionNumber M Procedure request number
ID
Only used for internal han-
dling Refer to „Table  4: Han-
dling of appointment state
SCH.25 Filler Status Code AppointmentState M
(SCH.25)“ auf Seite 11
Not displayed in Tegris work-
list
NTE#4.1 = 0010,4000
NTE.3.1 Comment PatientComments O NTE#4.2 = Patient Comments
NTE#4.3 = 99TG
NTE#4.1 = 0010,2000
NTE.3.1 Comment MedicalAlerts O NTE#4.2 = Medical Alerts
NTE#4.3 = 99TG
NTE#4.1 = 0010,2110
NTE.3.1 Comment ContrastAllergies O NTE#4.2 = Allergies
NTE#4.3 = 99TG
NTE#4.1 = 0038,0050
NTE.3.1 Comment SpecialNeeds O NTE#4.2 = Special Needs
NTE#4.3 = 99TG
Pregnancy state

Multiple Coding-Systems sup-

ported

LOINC - LN:

OBX#3.1 = 82810-3
OBX#3.2 = Pregnancy status
PatientPregnancy OBX#3.3 = LN
OBX.5.1 Observation Value O
Status
Tegris – 99TG:

OBX#3.1 = 0010,21C0
OBX#3.2 = PregnancyStatus
OBX#3.3 = 99TG

Refer to „Table  5: Pregnancy

Status (OBX.5)“ auf Seite
12

Table 2:  HL7 – Tegris Patient Service data mapping

10 / 13 TTI170520XYEN01
 Tegris IEC 80001 Hospital Network Integration Information

Seq Element name Tegris Patient Mandatory / Description

Service Optional
Personnel Re-
AIP.3.1 source ID.ID Num- PersonalID M Staff ID in hospital
ber
Personnel Re-
AIP.3.2 source ID.Family Staff Last Name
Name
Name M
Personnel Re-
AIP.3.3 source ID.Given Staff First Name
Name
Personnel Re-
AIP.3.21 source ID.Profes- Title O Title of staff, e.g. Dr
sional Suffix
Resource Group. Identifier for role of staff
AIP.5.1 Role O
Identifier Expected for surgeon: “Surg”
Derived from Order of staff
n/a n/a Rang O
entries

Table 3:  Physician data mapping

Value Description Handling in Tegris

Blocked The indicated time slot(s) is(are) blocked Shown on worklist
Booked The indicated appointment is booked Shown on worklist
The indicated appointment was stopped from oc-
Cancelled Removed from worklist
curring (canceled prior to starting)
The indicated appointment has completed normal-
Complete Removed from worklist
ly (was not discontinued, canceled, or deleted)
The indicated appointment was discontinued
DC (DC'ed while in progress, discontinued parent ap- Shown on worklist
pointment, or discontinued child appointment)
The indicated appointment was deleted from the
Deleted Removed from worklist
filler application
Noshow The patient did not show up for the appointment Removed from worklist
The appointment has been confirmed; however it
Overbook Shown on worklist
is confirmed in an overbooked state
Pending Appointment has not yet been confirmed Not shown on worklist
The indicated appointment has begun and is cur-
Started Shown on worklist
rently in progress
Appointment has been placed on a waiting list for
Waitlist Shown on worklist
a particular slot, or set of slots

Table 4:  Handling of appointment state (SCH.25)

TTI170520XYEN01 11 / 13
Tegris IEC 80001 Hospital Network Integration Information

OBX.5.1 Identifier OBX.5.2 Handling in Tegris

LA15173-0 Pregnant LN
LA26683-5 Not pregnant LN
LA4489-6 Unknown LN

1 Not pregnant 99TG

2 Possibly pregnant 99TG
3 Definitely pregnant 99TG
4 Unknown 99TG

Table 5:  Pregnancy Status (OBX.5)

4 Limitations
Tegris only supports one surgery appointment per message. If more is required, the HL7 Message
needs to be splitted in several messages.

5 Support of alternative HL7 message types

The Tegris HL7 interface can be adapted to support alternative message types, e.g. ADT/ ORM within
the scope of customer-specific requirements.

6 SIU sample message

MSH|^~\&|HIS|HIS|Tegris|Tegris|20211216152843.726+0100||SIU^S12^SIU_
S12|114226|P|2.7|||AL|NE||UNICODE UTF-8 SCH||114226^HIS||||Create^Create OR-Appoint-
ment^99zzz|ROUTINE^Routine appointment - default if not valued^HL70276||||||||||||||||||Pending^Ap-
pointment has not yet been confirmed^HL70278 NTE|1||COVID-19, Pacemaker|0010,2000^Medical
Alerts^99TG NTE|2||Penicillin, Intravenous contrast dye|0010,2110^Allergies^99TG NTE|3||Wheel-
chair|0038,0050^Special Needs^99TG NTE|4||Needs specialcare after surgery|0010,4000^Patient
Comments^99TG PID|1||2098276^^^HIS^PT||Doe^Jane^^^^^L^^^^^^^Dr.||19510101|F PV1|1|I|Ward-
1A^^^ORTH||||||||||||||||6103015560^^^HIS^VN OBX|1|CWE|82810-3^Pregnancy status^LN||-
LA26683-5^Not pregnant^LN||||||F RGS|1||114226^TAE suprakoronar^99zzz AIS|1||TAE_supra-
koronar^TAE suprakoronar^99zzz|20211216100000+0100|||280|min^Minute^UCUM||||ORTH^Or
thopedics^99zzz AIL|1||^OPS1|OR^Operationroom^99zzz||20211216093000+0100|||325|min^Minute^
UCUM AIP|1||jlongbow^Longbow^John^^^^^LDAP^HIS^^^^EI^^^^^^^^Dr.||Surg^Surgeon^99zzz

12 / 13 TTI170520XYEN01
Getinge is a global provider of innovative solutions for operating rooms, intensive care units, sterilization departments and for life science companies and institutions. Based on

our firsthand experience and close partnerships with clinical experts, healthcare professionals and medtech specialists, we are improving the everyday life for people - today

and tomorrow.

Integrated Workflow Solutions (IWS), as part of the business area Surgical Workflows, offers best-in-class IT solutions within the areas of OR integration, OR scheduling, patient

flow management and sterile supply management. We help create a safer integrated and better utilized facility that supports greater consistency and efficiency, enabling

healthcare professionals to focus on delivering the best possible care for patients.

Getinge IT Solutions ApS · Amaliegade 4 · 1256 Copenhagen K · Denmark · +45 33 33 88 55

Getinge IT Solutions Limited · Unit 5, Bowling Hill Business Park · Chipping Sodbury, Bristol · BS37 6JL · United Kingdom · +44 (0)1454 318373

Getinge IT Solutions GmbH · Südportal 5 · 22848 Norderstedt · Germany · +49 40 514 35-0

Getinge Cetrea A/S · Brendstrupgårdsvej 21F · 8200 Aarhus · Denmark · +45 38 40 05 70

Maquet GmbH · Kehler Str. 31 · 76437 Rastatt · Germany · +49 7222 932-0

www.getinge.com