Sebastian,
I think this is about right. I think 'immutable' in law and 'immutable'
in information systems have to be understood as different things. The
law is always local, so I think the best that could be done is a
standard kind of attestation whose reason for change was something like
'final version approved by governing health authority' or similar.
- thomas
On 10/07/2015 10:23, Sebastian Iancu wrote:
Thank you all for your suggestions. To conclude on this topic, the
main ideas were that:
- there is no sufficient reasons for an extra value for
version.lifecycle_state to indicate that a version is immutable
- immutable is anyway in real life not '100% immutable', corrections
should/might be allowed under certain conditions (up the the application)
- immutable state functionality can be achieved using ATTESTATION
(that gives the seal and context) and perhaps EHR_ACCESS (that gives
the read-only policy)
Regards,
Sebastian
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
