Atomik

Store, query and share clinical and demographic information data, in a single, simple to use, and standard-based platform.

Do you start from scratch on every new clinical application?

Simplify projects and save time
Focus on you app features not on how data will be stored
Develop applications faster with less debugging
Support any data structure without changing database schemas or code

Atomik provides a standardized data platform, allowing you to build high-quality applications quickly and efficiently. With our user-friendly interface and powerful tools, you'll be able to focus on creating innovative healthcare solutions, without worrying about the complexities of data management.

What's Atomik?

Atomik is a Clinical and Demographic Data Storage solution 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 Atomik:

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 and demographic 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.

Atomik 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, Atomik is designed to enable healthcare software companies to build integrated, standards-based applications that can easily share and access clinical and demographic data, without the burden of complex data management.

How does it work?

Atomik 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:

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

Data Storage:

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

APIs:

Atomik exposes a set of REST APIs for integrating with other systems and applications.
The main API is the openEHR-compliant API, which allows querying, storing, and managing clinical and demographic data.
Other APIs include admin, sync/cluster, and monitoring APIs.

Web Console:

Atomik 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:

Atomik 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:

Atomik 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 Atomik's design are flexibility, maintainability, and standards-compliance. By separating data from software and providing a vendor-neutral, openEHR-based platform, Atomik aims to enable healthcare software companies to build integrated, scalable, and adaptable applications without the burden of complex data management.

Use cases

Patient monitoring and wearables

Atomik 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 Atomik and into your applications.

Clinical Decision Support

Atomik 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

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

Documentation

Check the full documentation here.

For a quick read of all the elements you need to know as an Atomik user, we recommend these sections of the documentation:

openEHR basics will give you the foundation concepts you need to know to manage standardized data and their models.
Web Console gives you an overview of all the things you can see and do from Atomik's user interface.
Managing data models helps you with the definition and configuration of the openEHR models needed to store, validate and retrieve data to/from Atomik.
Storing data shows you how data is stored in Atomik and how the data is processed to grant quality, conformance and accessibility.
Querying and retrieving data describes how data can be accessed in different ways once stored in Atomik.

The last three items on that list are also related to how to integrate your system/app with Atomik, and using it as a CDR and/or DDR.