Hi everyone, has anyone any experience in merging and unmerging ehrIds, along with associated compositions, specifically into an EHRBase CDR? I hope someone might be able to help with a problem we have encountered. I have a source ehrId and a target ehrId, with the source being merged into the tar…

I am not sure if this variant of merge-functionality is wide spread across all CDR implementation. It is not wrong, but I don’t know if this is a standard - if I am wrong please correct me with a reference. We have in any case a different view and implementation: we ‘move’ compositions and contribu…

Hi @steve.pillar there is no standard way of doing this in openEHR yet, though it’s a very common use case. Having thinking a little bit about this in the past, there are many approaches, and I don’t think anyone is wrong. In my view there are three architectures: merging two EHRs into one of th…

Hi Pablo, I think the requirements and possible process is actually pretty well documented largely @thomas.beale , of course! Common Information Model openEHR Common Information Model specification and AFAIK, Better have largely faithfully implemented that…

[image] Linking and Merging EHR IDs Platform 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 (“unme…

Thanks for the reminder @ian.mcnicoll I totally forgot about that part in the specs. My memory is getting worst with the years!

Thanks Pablo, The way we have approached it so far is: Deactivate tne source ehr id, ie is_modifiable and is_queryable are both set to false. The compositions of the source ehr id, if any, are copied over to the target ehr id, and then deleted, ie a logical delete with the composition’s lifecycle…

@pablo @ian.mcnicoll , I was also not sure anymore if we have that formally described - in any case I was speaking about the other type of merge=move that we implemented

@sebastian.iancu in your implementation, after the move, is it possible to unmerge? If yes, what kind of metadata do you store in order to know how the unmerge should be done?

We don’t support ‘unmerge’, wasn’t required so far. An somehow alternative solution is to merge it again, but thins won’t be always what the end user may want.

[image] ian.mcnicoll: They did encounter an issue with persistent compositions which required a spec change,so they have followed the spec at least in part @matijap ?? From CDR perspective, persistent compositions are no different. We make no effort to prevent you having 2 of them in the same…

Merging and unmerging EHR Ids and their compositons

Implementation Platform

ian.mcnicoll (Ian McNicoll) 22 May 2024 11:22 5

Topic		Replies	Views
Linking and Merging EHR IDs Platform	14	1533	13 January 2021
Exploring the Use of openEHR for Integrating Patient Health Records Across Multiple Systems New to openEHR?	9	519	18 July 2024
Duplicate check during composition upload Platform	9	716	28 April 2023
Can a single CONTRIBUTION ever affect two separate EHRs? Technical (archive)	2	13	28 January 2010
Metadata in REST resources Platform atomik	1	47	22 July 2026
Linking multiple compositions with a "compound composition" Implementation	14	424	10 April 2025
Referring to the enclosing composition from ACTION.instruction_details? Specifications	14	350	26 March 2025
About Versioning and Redundant storage New to openEHR?	20	312	24 January 2026
Template versioning requirements in CDRs Clinically Relevant RM Discussions rest-apis , template	5	198	30 January 2026
Composition commit format to EHR Technical (archive)	6	43	10 April 2014

Merging and unmerging EHR Ids and their compositons

Related topics