Thank you, Thomas Now I understand that I:
1) can store list of actors (organizations, users, roles etc) in some external storage 2) shall avoid to store whatever demographic information in an EHR storage - except for PARTY identifiers (issued by some external system) 3) can connect participants in both systems by their IDs > 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 in the openEHR Architectural > Overview may be helpful; also this one. > > 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. > > You also need to consider how to implement RBAC, and 'legitimate > relationship' so that only the right people can see the right EHRs. > > - thomas -- Regards, Dmitry _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
