EHRServer

First open-source implementation of a full Cilnical Data Repository following the openEHR specifications. Multi-tenant, cluster ready, secure, integrated with SNOMED-CT.

EHRServer was envisioned as a sample implementation of the openEHR specifications for education purposes, so our students of openEHR-related training courses could actually test in practice what we talked about in theory.

While helping tens of students, EHRServer became an open source product, adopted by many companies that needed a clinical data repository for testing, developing proof of concepts and clinical apps.

EHRServer is the sibling of Atomik. Basically Atomik is EHRServer on steroids.

What's EHRServer?

EHRServer is the first open source Clinical Data Storage system based on the openEHR open standard. It is designed to help healthcare software companies build integrated applications by providing a standardized data platform that separates data from the software.

Key points about EHRServer:

It is a generic repository component that can be used as part of a software architecture to implement the persistence layer. It is focused on managing clinical information.

It leverages the openEHR specification to create a separation between data and software, allowing changes to data structures without impacting the software codebase or database schemas. This reduces development cycles and increases flexibility.

EHRServer has a user-friendly web console to manage data and definitions, as well as versioning and auditing capabilities.

It provides REST APIs for integrating with other systems, including openEHR-compliant APIs, admin APIs, sync/cluster APIs, and monitoring APIs.

The persistence layer is built on Hibernate, allowing the use of any relational database with a Java connector, providing database flexibility.

Overall, EHRServer is designed to enable healthcare software companies to build integrated, standards-based applications that can easily share and access clinical data, without the burden of complex data management.

How does it work?

EHRServer works by providing a standardized, vendor-neutral data platform based on the openEHR open standard. Here's a breakdown of how it works.

Data Model:

EHRServer uses the openEHR information model, which defines a standardized way to represent clinical data.
This allows EHRServer to store data in a semantically correct and interoperable manner.

Data Storage:

EHRServer's persistence layer is built on Hibernate, a popular Java ORM framework.
This allows EHRServer to use any relational database that has a Java connector, providing flexibility in the choice of database.

APIs:

EHRServer exposes a set of REST APIs for integrating with other systems and applications.
Sync/cluster ing API.

Web Console:

EHRServer provides a web-based user interface called the Web Console.
The Web Console allows administrators to manage data, data definitions, stored queries, and other aspects of the platform.

Data Management:

EHRServer automatically handles data versioning and auditing, ensuring a comprehensive history of all changes to the data.
It also includes a query builder component that allows creating and executing complex queries on the stored data.

Integration Components:

EHRServer can be integrated directly with applications or through a proxy/integration engine for additional data transformation tasks.
It also integrates with external services, such as a SNOMED CT terminology service and the openEHR Toolkit for template management and other services.

The key principles behind EHRServer's design are flexibility, maintainability, and standards-compliance. By separating data from software and providing a vendor-neutral, openEHR-based platform, EHRServer aims to enable healthcare software companies to build integrated, scalable, and adaptable applications without the burden of complex data management.

Check the EHRServer playlist

Use cases

Patient monitoring and wearables

EHRServer is an ideal tool for storing biometric data coming from any kind wearable device or patient monitoring app, and by creating smart queries you can get aggregated and more meaningful information out the EHRServer and into your applications.

Clinical Decision Support

EHRServer can play an important role in the CDS context, by serving as a standardized data source for evaluating CDS rules that can help clinicians remember to order a lab test or check medication interactions to prevent adverse reactions.

Shared health records

EHRServer is an ideal tool for aggregating and centralizing clinical information that needs to be shared between different clinicians, specialties, teams, departments, and hospitals.

Open Source

EHRServer on GitHub