@Bert Persistent records are a well know pattern in ehrs and it's
usefulness should not be under question. Of course systems that focus on
primary care might not implement them. But for hospital or even regional /
national records need a wider view of the patient, persistent shows their
value.
@Bj
Dear All,
Please remove me from this listserv.
Best,
Danny
On Sat, Aug 19, 2017 at 6:18 AM Bert Verhees wrote:
> I agree that merging is (normally) only interesting for persistent
> compositions, that are the only kind of compositions which are candidat for
> simultaneously editing (branching
I notice the versioning discussion.
Is see three different topics; (non-)Persistent, versioning and
synchronisation/consolidation.
I see no use of non-persistant flags.
I see two reasons for versioning.
Synchronisation,consolidation is too complex for now.
ERS systems document events.
Each docum
We are using persistent compositions a lot in our system. These are
compositions with content that lasts and might be updated several times. To
make persistent compositions usable we have introduced “scope”. Examples of
scopes is episode of care, period of care, ward stay, etc. A persistent
com
