Hi everyone, In rest api specification, composition has a ‘PUT’ update but without ‘PATCH’ update, does it means it produces redundant storage even I only change little in a huge composition? In my case, a clinical document contains medication records equipment data, and much more other data duri…

So rough guide on our approach, pretty close ? identical to Silje.. One Vital Signs template - multiple composition instances for each recording event One Medications /fluids administration template using ACTION.medication, with a separate composition instance for each ‘event’ i,e bundle up meds/f…

openEHR is technology and implementation agnostic, or is supposed to be as much as possible. This is to avoid a standard that is strongly coupled to a particular technology. There has to be compromise though, and Implementation Technology Specifications such as REST is how we do this balancing act. …

@Michael_Lin Would you be using ‘PATCH’ for saving drafts during data entry or do you intend to update finalized compositions (saved some time ago)?

@Seref @borut.jures I feel my previous explanation wasn’t clear. To be more specific, for example, if my document has 5 parts, but it wasn’t written all at once, then based on my current experiment using components in ehrbase, when saving, it will generate 5 historical versions sequentially, like t…

Does your document absolutely need to be persisted as a single composition, or could it conceivable be for example five compositions?

Does your document absolutely need to be persisted as a single composition, or could it conceivable be for example five compositions? I’ve considered that too, but how should I represent the entire document?

The image below shows part of the document I mentioned; it dynamically records data generated during the surgery, so it saves multiple times. [image]

Your screenshot gives very valueable context information! I would definitely split this into multiple compositions, maybe even separate compositions per vital sign measurement, medication action or other event. One way of linking them together to give the overall context of a single surgery could be…

I would definitely split this into multiple compositions, maybe even separate compositions per vital sign measurement, medication action or other event. I agree. I also guessed that it could be done using a “folder” or, as you just mentioned, by “compound composition”. I initially thought this w…

I’m not sure how a stream would be handled in practice, but my gut feeling is that the full stream should probably be kept in a specialised and maybe short-time storage of some kind, while only exerpts deemed “documentation-worthy” (or something like that) would be kept for posterity in the openEHR …

About Versioning and Redundant storage

New to openEHR?

siljelb (Silje Ljosland Bakke) 23 January 2026 08:08 8

Others have discussed the possibility of creating a “compound composition” or “compound document” previously: Linking multiple compositions with a “compound composition” - Implementation - openEHR

Topic		Replies	Views
AQL on versioned compositions Technical (archive)	6	32	2 November 2018
Some confusion about COMPOSITION Specifications	11	952	15 December 2020
Commiting ACTIONs for the same INSTRUCTION ACTIVITY Technical (archive)	17	74	12 September 2012
Representing event timelines using the history package RM modelling-patterns	11	116	2 April 2026
PATCH for persistent compositions Specifications	11	164	19 February 2025
Composition commit and change types Technical (archive)	18	96	4 April 2016
How to use Persistent Compositions? RM	4	1537	23 March 2020
Composition commit format to EHR Technical (archive)	6	44	10 April 2014
How do we update the compositions if we modify/update a template? Ask IEB archetype , template	18	971	2 February 2023
Duplicate check during composition upload Platform	9	716	28 April 2023

About Versioning and Redundant storage

Related topics