Atomik
A clinical data platform built on openEHR for healthcare software companies that need reliable, standards-based data storage.
Building healthcare software means deciding how to store clinical data. Most teams end up making those decisions under time pressure, creating custom schemas that work for one project but become a liability the next time requirements change.
Atomik separates that decision from the rest of your application. It provides a persistent, standards-based data layer that your applications connect to — so your team can focus on clinical workflows, not on data infrastructure.
The Problem
Most healthcare software companies end up building a custom data layer for every project. Schemas diverge, clinical concepts get encoded differently across applications, and integrations become brittle. The result is technical debt that compounds over time. Atomik exists because we kept solving this same problem across multiple client engagements.
Custom schemas on every project
Clinical data gets stored however the first developer decided to store it. A year later, the data model is a constraint on what the application can do.
Brittle integrations
When two applications encode the same clinical concept differently, every integration point becomes a translation problem — and those translations break when either side changes.
Schema migrations on every change
When clinical requirements change — and they always do — a custom database schema means code changes, migrations, and deployment risk.
What Atomik Is
Atomik is a standards-based Clinical Data Repository (CDR) and Demographic Data Repository (DDR) built on the openEHR specification. It provides a single, persistent data layer that multiple applications can share.
Data is stored following openEHR templates, which means structure and semantics are defined separately from the software. Changing what data you collect does not require database migrations or code changes — you update the template and Atomik handles the rest.
Atomik is not an EMR or a clinical application. It is a backend service that stores clinical data and exposes it through standard APIs. Your applications connect to Atomik instead of managing their own persistence layer.
Because Atomik is built on openEHR, it supports the full openEHR information model: EHRs, compositions, versioning, and demographics. It includes a query engine with AQL support for structured data retrieval, and a FHIR facade for environments that require FHIR interoperability.
Key Capabilities
What Atomik provides out of the box.
openEHR-compliant data storage
Store clinical data as openEHR compositions validated against operational templates. No custom schemas, no proprietary formats.
FHIR facade for interoperability
Expose stored data as FHIR R4/R5 resources without migrating or duplicating the underlying data.
Query engine with AQL support
Design, test and deploy stored queries to retrieve clinical data across EHRs and compositions. Supports a subset of Archetype Query Language (AQL) for common retrieval patterns.
Web console
Browser-based interface for managing templates, EHRs, compositions, stored queries, users, and audit logs.
Versioning and auditing built in
Every composition is versioned automatically. The full history of changes is preserved and queryable — a core requirement for clinical records.
Clustering for redundancy and backups
Atomik can be deployed as a cluster of nodes for automated redundancy and backups, keeping clinical data available even when individual nodes fail.
Use Cases
Where Atomik fits in a real healthcare software architecture.
Patient Monitoring
Atomik stores biometric and observation data from monitoring devices using standardized openEHR templates. The query engine makes it straightforward to retrieve time-series data, calculate trends, or trigger alerts based on stored values.
Clinical Decision Support
CDS systems need a reliable, structured source of patient data. Atomik provides that data through semantic queries — making it easier to evaluate rules, check medication interactions, or surface relevant history without parsing unstructured notes.
Shared Health Records
When multiple teams, departments, or facilities need access to the same clinical record, Atomik acts as the shared persistence layer. Applications read and write through the same API, keeping data consistent across the system.
Do you have any questions?
Let us know how we can help you.