# \#atomik

**URL:** https://discourse.openehr.org/tag/atomik/150.md

[Latest](https://discourse.openehr.org/latest.md) · [Categories](https://discourse.openehr.org/categories.md) · [Tags](https://discourse.openehr.org/tags.md)

---

## [Metadata in REST resources](https://discourse.openehr.org/t/metadata-in-rest-resources/17127)

<div class="topic-metadata">

**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\
**Replies:** 1\
**Last updated:** [22 July 2026 20:03 UTC](https://discourse.openehr.org/t/metadata-in-rest-resources/17127 "2026-07-22T20:03:24Z")

</div>

While working with EHR and patient (PERSON/ROLE) merge processes I have found the current resources based on the RM a little restrictive. While we can have versioning info embedded in the LOCATABLE.uid, there is no nati…

---

## [EHR merging process](https://discourse.openehr.org/t/ehr-merging-process/11717)

<div class="topic-metadata">

**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\
**Replies:** 0\
**Last updated:** [4 February 2026 00:10 UTC](https://discourse.openehr.org/t/ehr-merging-process/11717 "2026-02-04T00:10:36Z")

</div>

This might interest some people here. There were discussions about this before, but we never show something concrete. In this video, I show how the EHR merge process works in Atomik, how the patient identities of both E…

---

## [Test instance of Atomik](https://discourse.openehr.org/t/test-instance-of-atomik/5033)

<div class="topic-metadata">

**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\
**Replies:** 5\
**Last updated:** [26 March 2024 10:34 UTC](https://discourse.openehr.org/t/test-instance-of-atomik/5033 "2024-03-26T10:34:20Z")

</div>

Soon we will put an Atomik test server online so anyone can play with it. Atomik is an #openEHR platform that works as a clinical and demographic vendor neutral data storage, management and integration system. Please let…