All is already versioned, my question is about how to commit compos and if
it makes sense to have two different versioned compositions for the same
persistent compo archetype.
Sent from my LG Mobile
------ Original message------From: Bert VerheesDate: Sat, Apr 2, 2016 15:01To:
[email protected];Subject:Re: Composition commit and change
types I guess you need to version it, if you want it to be according
the specs.
That means, when you use it for a medication-list, you will get many
versions of the same compositions for a patient.
But if you do not version it, that means that the concept of
replaying the Past in case of legal investigation will not be possible.
Bert
On 02-04-16 07:59, [email protected] wrote:
Hi all, I'm testing some cases in the EHRServer
and I want to confirn some grey areas.
If the EHR receives a commit of a persistent
composition and the change type is creation, should the EHR create a
new composition?
i.e. I don't see an EHR having two different
medication lists, is that possible?
I guess persistent compos can only be created one time
per archetype (one medication list, one problem list, one
vaccination list, etc. per patient), and after the creation, all
commits should be modification. Does this make any sense?
If this is OK, to avoid errors from client
applications, I would return an error when a creation is committed for
a persistent compo archetype that already has a conpo instance.
And about the first commit. Should, lets say, the
medication list be created when the first medication is recorded or
can it be created empty? What do other implementations out there do?
Thanks a lot!
_______________________________________________openEHR-technical mailing
[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
