# Hospital Integration

dot.base does not strive to be an "all-in-one" solution. Wherever possible, dot.base aims to integrate existing tools and to sync its data with them. Without addressing this interoperability issue, new healthcare software just creates new "data silos".

By natively using FHIR for data storage, dot.base comes with great interoperability possibilities out of the box. However, the current IT infrastructure in hospitals is still widely based on HL7 v2.x (opens new window) or custom as well as vendor-specific interfaces. To tackle this issue, dot.base takes advantage of its microservice architecture and uses a variety of adapters to assure interoperability with other software solutions.

# dot.base uses adapters for the following purposes:

Most of the dot.base adapters listed below might not work out-of-the-box in your environment, since they highly depend on your environment's system architecture and interfaces. However, these examples should provide a general understanding of the dot.base extension system and how it can be adapted to your needs.

# Import data from a hospital information system

# Example: HDP Adapter

# Software stack

# Implementation

The import of legacy data in the dot.base@Charité setup is based on a SQL server, that mirrors the hospital information system. In this example the hospital information system is an i.s.h.Med system. This SQL-Server is a custom solution and part of the Charité Health Data Platform (HDP).

The SQL server can be addressed using the HDP-Adapter API. The API offers endpoints to search for legacy data and import this data to dot.base, provided you have the appropriate user role and authorization.

A well-known scenario is the import of patient administrative data. If a patient does not yet exist in the dot.base system, a dot.base user can search for patients on the SQL server through the hdp-adapter. Importing the patient, results in a new Patient entity being created on the Patient FHIR Server. Additionally, new patients can also be registered at a Trusted Third Party

Legacy Data Import

# Export data to a hospital information system

# Example: COMM Server Adapter

# Software stack

# Implementation

Using dot.base should never create another data silo. That is why exporting data plays a key role in the dot.base software architecture. To offer a basic solution that works with a broad variety of systems, dot.base allows PDF export of all dot.base data.

The dot.base@Charité setup uses a HL7 v2.x Message Broker (in German often referred to as a comm-server), that processes HL7 messages and works as a middleware to other systems. HL7 Message Brokers are implemented at mostly all larger hospitals and can be communicated with using the Comm-Server-Adapter API. The API accepts FHIR Documents, processes them into valid HL7 MDM messages, and forwards them to the comm-server.

# Integration of other medical software

# Example: Medication Tool

# Software stack

# Implementation

Documentation of prescriptions and medication plays a key role in a patient's treatment but is already handled by various tools. Thus, we integrate AiDKlinik (opens new window), which is already in use at Charité and also compatible with the German nationally standardized medication schedule.

# Example: Deep Brain Stimulation Settings

Software stack & dot.base services:

# Implementation

Since our project evolved from the Movement Disorders and Neuromodulation Unit at Charité Neurology Department our clinical focus includes deep brain stimulation (DBS).

Deep brain stimulation comes along with a big amount of data being generated for each patient. Currently, DBS data can often not be used sufficiently for patient treatment and research, due to export functionalities missing completely or only allowing manual data export.

Our medtronic-dbs-api can consume DBS data that is sent by the Medtronic ACTIVA™ DBS Platform. The API processes incoming HL7 Messages, parses them into FHIR resources and stores the data for the according patient on a FHIR server. Finally, a patient's DBS setup and settings can be viewed in dot.base without the immense and error-prone work of manual data transfer.