Some persistent compos are event in the CKM

Heather Leslie heather.leslie at
Fri Jul 7 22:02:10 EDT 2017

Hi Pablo,

This is a longstanding issue and workaround.

See the last paragraph in 'Use' for each of the COMPOSITIONS that theoretically should be persistent but have been modelled as an event:
"This archetype is usually managed as a persistent list, however there are situations where the list may be used within episodic care and require additional attributes such as context etc to enable accurate recording. The openEHR reference model currently only allows context to be recorded within Event-based COMPOSITION archetypes. As a result, this archetype has been modelled as an Event, rather than Persistent, COMPOSITION, to allow for flexibility so that some clinical systems can safely manage Problem lists for episodes of care, while others will choose to implement this COMPOSITION to act in a persistent manner."

Until there is a change in the RM to cater for this use case we are a bit stuck!



From: openEHR-clinical [mailto:openehr-clinical-bounces at] On Behalf Of Pablo Pazos
Sent: Friday, 7 July 2017 11:27 AM
To: For openEHR clinical discussions <openehr-clinical at>
Subject: Some persistent compos are event in the CKM

Doing testing for the EHRServer with persistent compositions found problem list and medication list have category 433 (event) instead of 431 (persistent).
Maybe other compositions have the same issue.
This might affect many people.

Ing. Pablo Pazos Gutiérrez
Cel:(00598) 99 043 145
Skype: cabolabs

pablo.pazos at<mailto:pablo.pazos at>
Subscribe to our newsletter<>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openEHR-clinical mailing list