> The root of an patient-EMD is the EHR (with rootfolder), and there is > the patient linked to. > If an EHR system is shared by more organizations, there share also > patients, I guess. Else I don't get the point from sharing.
1. It often occurs that few medical institutions share same building, same territory and same database server (as for example a hospital, an out-patient clinic and a laboratory), but they are different legal persons. 2. It is easier to administer and support > There is no root where all patients/EHRs are together, so there is no > organization-root. > As said, it is patient centric. EHR management system is patient-centric from the physician's point of view, but it is definitely organization-centric from the DBA/sysadmin/software developer point of view, I believe. For example, a clinician can act as an in-patient clinic surgeon in the morning and as traumatologist in the out-patient clinic in the nighttime. Such a functional role is related to a surgeon logon context, and logon context is definitely bound to an organization. Logically splitted database may share patient information between organizations, or may not, it doesn't matter > Beside treatments, a patient can have longer term professional > relationships with healthcare professionals, you can arrange that with > party-relationships and roles. Those information exists outside the EHR, > but is connected the the patients and healthcare professionals. See in > the demographic reference-model where you can find attributes to store > this information, in the PARTY class (base of > person(patient/healthcare-professional) and organization, I think. I discovered the demography.xsd just yesterday, accidentally, on LiU github :) For some reason it is missing here - http://www.openehr.org/releases/1.0.2/reference-models/openEHR/XSD/ -- Regards, Dmitry _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
