A couple of words of advice: normally, EHR and demographics 'databases'
would be separated for security and operational reasons. EHRs are not
normally 'inside' any demographic entities. This section
<http://www.openehr.org/releases/BASE/latest/docs/architecture_overview/architecture_overview.html#_design_of_the_openehr_ehr>in
the openEHR Architectural Overview may be helpful; also this one
<http://www.openehr.org/releases/BASE/latest/docs/architecture_overview/architecture_overview.html#_overview_4>.
If you are cohosting what are logically separate EHR repositories on a
cloud service, openEHR does not say anything much about how to organise
them, although you should consider carefully implementing an 'EHR /
subject cross-reference' service as briefly described here
<https://openehr.atlassian.net/wiki/display/spec/openEHR+Service+Model#openEHRServiceModel-EHRandRelatedServices>.
You also need to consider how to implement RBAC, and 'legitimate
relationship' so that only the right people can see the right EHRs.
- thomas
On 26/11/2015 22:36, Dmitry Baranov wrote:
Hi, I have a lot of practical questions to ask :)
Let's imagine that I have an EHR database which is shared by several
organizations, and each organization manages one or more EHR systems, and each
EHR system manages it's own hierarchy of folders. Something like that:
- Database
[C] ACME company (1.1.1.1)
[S] EHR System 1 (1.1.1.1.1)
- Root folder 1
- Folders
- Items
- Root folder 2
- Folders
- Items
[S] EHR System 2 (1.1.1.1.2)
- Root folder 1
- Folders
- Items
- Root folder 2
- Folders
- Items
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
