We are using EHRbase for our CDR which is going ok albeit we have only a tiny number of EHRs on it (<10), and only for an anticipatory care plan application supporting ReSPECT.
This is pretty much testing the ground for us as we need to scale up to manage 6 million citizens health and care records, so we need very much to make it work and be solid, safe and meet our requirements!
One recurring requirement is to handle ‘drafts’, that is compositions that are being worked on by users but not yet complete. In practical terms this is because they want to start a thing, be distracted by lunch or some clinical emergency, and come back to it later or tomorrow.
ReSPECT is using this template:
Which makes use of this composition:
I understand (I think!) that the proper way to manage that is by using lifecycle_state, which can be ‘complete’, ‘incomplete’ or ‘deleted’.
Does EHRBase support this particular attribute?
If so, I guess we could use it to manage this in our interface and application.
Alternatively, the composition we are using has an element ‘Status’ in Context which we could perhaps use to do a similar workflow, exposing that element in the UI and designing a process to allow the user to mark the composition as ‘in draft’ or ‘complete’.
This achieves the same aim, but not in quite so elegant a fashion.
Does all that seem sensible, and can @birger.haarbrandt give me any help re EHRbase supporting lifecycle_state?
Thanks, if that makes any sense!
Dr Paul Miller
NES Digital Service