In many clinics, the most important information is in the wrong system. The gait trainer protocol, the cardiopulmonary exercise test or the assessment form is created in a subsystem, but the doctor looks for it in the HIS. In between are printouts, scanned PDFs and retyped values. A good HIS interface closes this gap in both directions. This guide shows how orders and findings flow between the HIS and the subsystem, which messages are involved and how an interface project runs.
Which standards exist for connecting individual devices is explained in the guide Connecting medical devices. Here, the focus is on the route between the HIS and the subsystem.
The cycle: from order to finding
A complete HIS connection is a cycle of four steps.
- Master data: the HIS reports a patient’s admission with patient number, case number and master data. The subsystem creates the person or updates them.
- Order: a ward or outpatient department requests a service in the HIS, such as a gait analysis or a therapy session. The subsystem receives the order with patient, service and appointment.
- Execution: in the subsystem, the matching workflow starts with the right devices, forms and parameters. The readings are automatically assigned to the person and the order.
- Finding: the subsystem sends the results back to the order, as individual readings, as a report or both. In the HIS, they appear in the patient record.
If one of these steps is missing, manual work is the result. Without master data, people are created twice; without an order, someone has to assign the examination manually; without a return route, the finding is printed out and scanned in.
What is order entry in a hospital?
Order entry is the electronic request for a service from the HIS. It is best known from the laboratory: the ward requests a blood test, the laboratory system receives the order, and the finding comes back to exactly this order. The same principle works for functional diagnostics, therapy and rehabilitation.
The benefit lies in the assignment. Because every order carries a unique number, the result automatically ends up with the right patient and case, without searching and without mix-ups. At the same time, the requesting unit sees in the HIS whether a service has been requested, performed or reported.
In the Datico® Life Hub, Order Entry takes on this role for measurement, therapy and training workflows. Each incoming service number is assigned via a procedure to a workflow that defines devices, parameters, forms and sequence, and if required also to a series of appointments. The devices are addressed via the Device Connector, even if the HIS itself has no device connection.
Which messages flow: HL7 v2, FHIR, GDT
There are three common routes for the HIS interface. Which one is used depends on the HIS, the clinic’s communication server (interface engine) and the subsystem.
| Step in the cycle | HL7 v2 | FHIR | GDT |
|---|---|---|---|
| Master data | ADT messages, e.g. admission and update | Patient and Encounter resources | Record type 6301 (transfer master data) |
| Order | ORM or OML | ServiceRequest resource | Record type 6302 (request new examination) |
| Result as values | ORU | Observation and DiagnosticReport resources | Record type 6310 (transfer examination data) |
| Report as document | MDM or embedded in ORU | DiagnosticReport with attachment, DocumentReference | Reference to a file |
| Typical use | Standard in German clinics, usually via a communication server | New interfaces, apps, applications related to the ePA | Diagnostic devices connected to practice and hospital software |
HL7 v2 is available in almost every HIS. In larger hospitals, all messages run via a communication server that distributes and translates them. Because the standard leaves room for interpretation, each interface is agreed in a specification: which message types, which version, which fields, which service numbers.
FHIR describes data as individual resources and is easier to connect with modern applications. Many HIS now offer FHIR interfaces; in practice, the two standards often run side by side.
GDT is the usual way in German-speaking countries to connect a single diagnostic device to practice or hospital software. For documents such as reports, some hospitals additionally use IHE XDS.
The HIS Connector of the Datico® Life Hub supports HL7 v2 and v3, HL7 FHIR R4, GDT/EDT and IHE XDS. An overview of all standards can be found on the Standards page.
Individual values instead of a PDF
Many devices output their results as a PDF report. That is sufficient for documentation, but not for anything else: a PDF cannot be displayed in a history, compared with other values or analysed.
It is better to return both: the individual readings as structured data and the report for the record. The doctor then sees the familiar report in the HIS, and at the same time the values are available for progress charts, quality reports and your own analyses.
The Datico® Life Hub transfers device findings, therapy histories, questionnaire results, scores and test batteries to the HIS in structured form, event-based or scheduled, encrypted and logged in the Audit Trail.
Subsystem or HIS module?
Many HIS vendors offer their own modules for therapy or functional diagnostics. Whether a module or a subsystem is the better fit depends mainly on the devices and the analyses.
| HIS module | Subsystem alongside the HIS | |
|---|---|---|
| Device connection | Depends on the module, often limited to a few device types | Focus of the system, manufacturer-independent |
| Readings | Often as a report or individual value without history | Structured, with origin, longitudinal |
| Analysis and history | Standard views of the HIS | Own scores, reference values, progress charts |
| Patient app and questionnaires | Rarely included | Often part of the system |
| Changing the HIS | Data and workflows depend on the HIS | The subsystem stays, only the interface is reconnected |
| Effort for IT | One vendor | One additional interface and one more contract |
A HIS module is often the simpler choice if only a few devices are connected and the standard views are sufficient. A subsystem pays off when many devices from different manufacturers come together, when histories are to be analysed over weeks or when patients are involved via an app.
The Datico® Life Hub is such a subsystem. It is not an electronic patient record and does not replace the HIS, but supplements it with measurement, therapy and progress data. At the Neurological Rehabilitation Centre Rosenhügel in Vienna, for example, it receives orders, controls an arm therapy device in both directions and returns results and report via the HIS Connector.
An interface project in six steps
- Define workflows: which services should be requested from the HIS, which results should come back? Start with one area, such as gait analysis or arm therapy.
- Agree the specification: the HIS side, communication server and subsystem agree on standard, version, message types, fields and service numbers.
- Clarify patient identification: which number is leading, the patient number or the case number? How are admissions, transfers and merges handled?
- Assign services: each service number from the HIS is assigned to a workflow in the subsystem. In the Datico® Life Hub, this is done via procedures; you add new services later without any changes to the HIS.
- Test: first in the test system with test patients, then with real workflows in one area. Pay particular attention to special cases such as cancelled orders and corrections.
- Secure operation: who monitors the interface, who is notified in the event of errors, and how are new devices and services added?
Plan the coordination with the HIS vendor early. This is often where the schedule is decided, and depending on the vendor, there are costs for setting up the interface.
Data protection and rights at the interface
Health data under Art. 9 GDPR flows via the HIS interface. The usual rules therefore apply here too: the subsystem receives only the data it needs for the order, access is logged, and there is a data processing agreement if an external provider operates the subsystem.
In the Datico® Life Hub, Roles & Rights define who may see which people and data. Each customer receives a separate database on servers in Germany; on request, the system runs in your own infrastructure. If you want to use measurement and progress data for AI analyses later on, you will find the relevant questions in the guide AI and health data.
Checklist: setting up a HIS interface
- Workflows and services you are starting with are defined.
- Contacts at the HIS vendor, clinic IT and subsystem are named.
- Standard and version are agreed: HL7 v2, FHIR or GDT.
- Message types for master data, order, result and report are defined.
- Leading patient and case number is clarified.
- Service numbers are assigned to the workflows in the subsystem.
- It is defined which results go back as individual values and which as a report.
- Test system and test patients are available.
- Special cases are tested: cancellation, correction, transfer, merge.
- Data processing agreement and role concept are in place.
- Monitoring and error notification during operation are arranged.
The key points for your IT department and your data protection officer are summarised on three pages in the PDF “Datico® alongside your HIS”. If you would like to go through your workflows with us, arrange a personal initial consultation.
Frequently asked questions
What is a HIS interface?
A HIS interface is the technical connection between the hospital information system and another system, such as a laboratory, diagnostic or therapy system. Through it, both sides exchange patient master data, orders and results, usually via HL7 v2, increasingly via FHIR and, for diagnostic devices, often via GDT.
What does order entry mean in a hospital?
Order entry is the electronic request for a service from the HIS, for example a laboratory test, a functional diagnostic examination or a therapy session. The ward or outpatient department creates the order in the HIS, the performing system receives it with patient, service and appointment, and reports the result back to the order.
Which HL7 messages do I need for orders and findings?
Typical are ADT messages for admission and master data, ORM or OML for the order and ORU for the result. Documents such as discharge letters or reports are often transferred as an MDM message or via IHE XDS. Which message types and versions are used is defined by the HIS side and the subsystem in an interface specification.
Does the HIS have to be adapted for every new device?
Not if a platform sits between the devices and the HIS. There is then one agreed interface to the HIS, and new devices are added on the platform. In the Datico® Life Hub, you assign new service numbers to a workflow as a new procedure, without any changes to the HIS.
Does Datico® replace the HIS or the electronic patient record?
No. The Datico® Life Hub works alongside the HIS as a subsystem for measurement, therapy and progress data. It receives orders from the HIS and returns findings, histories and scores to it. Where an electronic patient record is connected, reports can be transferred as a supplement to the German electronic patient record (ePA).
What does a HIS interface cost?
That depends mainly on the HIS. On the HIS side, depending on the vendor, there are costs for setting up or licensing the interface, plus the effort for coordination and testing. Clarify this early with your IT department and the HIS vendor. If a platform sits between the devices and the HIS, this effort is incurred only once instead of for each device.
Related features
- Audit TrailYou can trace every measurement with its context, and every action in the system, completely – even years later.
- Device ConnectorYou connect diagnostic, therapy and training devices from different manufacturers and receive their measurements automatically and in structured form in the Datico® Life Hub.
- HIS ConnectorYou receive orders from hospital and practice management systems automatically and return findings to these systems in structured form.
- Order EntryExternal orders automatically start the right examination workflow, and you receive all results bundled with the original order.
- Roles & RightsYou define who may use which function and see which data – down to function and attribute level.