I suspect that the idea of 'final' requires something more like a
'locked for modification' flag. But nothing is guaranteed to be
immutable - what if the consent was given, and the committed information
was considered clinically 'final' but then a simple typo error (e.g.
patient name, or the date of procedure) was found?
- thomas
On 10/06/2015 15:32, Sebastian Iancu wrote:
Hello all,
Does anybody (with an openEHR persistence system/solution) encountered
the need to record other states than 'incomplete', complete',
'deleted' for a VERSION.lifecycle_state?
The use case is that in some circumstances a version need to become
immutable and any change should be forbidden. Imagine a care plan that
was already 'inform-consented' - it should not be allowed to be
changed in any way, neither logically deleted (unless perhaps some
administrative reasons). In contrast, by current version of
specifications, a 'complete' version can be still changed or
logically-deleted (which is valid behavior also).
Regards,
Sebastian
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
