Our (company Better) EHR Server has an administration function to merge EHRs. It physically moves all compositions from one EHR to another, but keeps a note of that in case the operation needs to be undone due to an error (“unmerge”). I find this to be quite an elegant and definitely a totally transparent solution, but I don’t think it needs to be standardised.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Merging and unmerging EHR Ids and their compositons | 12 | 381 | 13 June 2024 | |
| How to use a FHIR Patient instance as an external reference | 7 | 178 | 3 October 2024 | |
| Exploring the Use of openEHR for Integrating Patient Health Records Across Multiple Systems | 9 | 469 | 18 July 2024 | |
| Hard/physical delete | 3 | 482 | 9 November 2023 | |
| Query About openEHR Structure for Managing Multiple Patients | 2 | 54 | 5 September 2024 | |
| Duplicate check during composition upload | 9 | 690 | 28 April 2023 | |
| REST API - Inconsistent handling of EHR_STATUS between EhrBase and Better CDR | 11 | 551 | 20 April 2023 | |
| How to retrieve ehrid in ehrbase | 9 | 1827 | 7 October 2020 | |
| How to use Persistent Compositions? | 4 | 1501 | 23 March 2020 | |
| About Versioning and Redundant storage | 20 | 89 | 24 January 2026 |