Hi all, most here might not know we are working on Atomik, a new openEHR CDR.
Soon we will release a set of demos, tutorials and documentation that would help as educational materials for anyone interested. We would like to know if you have anything in particular you would like to see on those educational materials, for instance in the video demos.
About Atomik, it’s derived from EHRServer which was the first open source implementation of an openEHR CDR. In Atomik we improved and optimized many areas of EHRServer, and did some changes. For instance EHRServer is multi-tenant, and Atomik is single-tenant, which removes complexity and improves performance.
One interesting feature is Atomik will support storing and querying demographic data, so it can be used just as a CDR, or just as a DDR (demographic data repository) or as both. So the CDR and the MPI could be in the same system. This configuration might be useful for some small projects, PoC or quick prototypes.
Atomik will support integration with the openEHR Toolkit as the storage of Operational Templates, since the Toolkit has a better internal management of OPTs than EHRServer (with semver versioning inside that is useful when developing OPTs). We might also use some tools from the Toolkit, like the data generators to be able to load some test data automatically when trying the server out.
In EHRServer, clusters of servers where supported by a sync REST API, which allows HA and automatic backups for all data (EHRs, CONTRIBUTIONs, COMPOSITIONs, FOLDERs, templates and even queries). In Atomik we will have a faster TCP sync process, removing the HTTP delays and increasing throughput, so servers can be synchronized in a fraction of the time it takes when using HTTP. Note this is system to system not database to database!
Finally we will offer integrations with other formats, APIs and standards via Mirth Connect, that is a very popular integration engine with support for many communication protocols and message formats, it can even be used for ETL though it’s not the main use case for Mirth.
One last thing to clarify is Atomik will be licensed and is not open source, we are trying a new business model for this tool to be offered in parallel to EHRServer which is open source and the business model is based on support.
I personally want to hear what the community is looking for, even if you are not interested in this server itself, in general, what would you like to see in educational materials, because even though the materials will be focused on Atomik, we will talk about openEHR implementation in general, which I think will be valuable for the whole community.
Get in touch!