/
Reference Model Notes - Alkmaar 2017 SEC Meeting
Reference Model Notes - Alkmaar 2017 SEC Meeting
System id semantics
EHR.system_id should not be settable by the client, should be supplied by system.
=> system has to know its own system id.
What are the rules for merging EHRs from 2 source openEHR systems (system-A and system-B) into system-B or system-C? Current rules: EHR.system_id is always for the system EHR was created in; a 'system' can contain EHRs with different system_ids. I.e. EHR.system_id's meaning is id of creating system.
EHR COMPOSITION merging - where forked VERSIONED_COMPOSITIONs exist, they have to be machine-merged using the change control model; with semantic content-merging (normal manual) occurring as a second step.
Branched versioning
Sebastian Iancu - in Code24 they want to do local branching
, multiple selections available,
Related content
System definition in openEHR
System definition in openEHR
More like this
The openEHR developers' workshop 2019
The openEHR developers' workshop 2019
More like this
The openEHR Developers' workshop 2017
The openEHR Developers' workshop 2017
More like this
openEHR REST APIs
openEHR REST APIs
More like this
Roadmap of the openEHR Java project
Roadmap of the openEHR Java project
More like this
openEHR Master class – EU-China Health Summit 2022
openEHR Master class – EU-China Health Summit 2022
More like this