Hi Bert,
there is no 'policy' about treating the Demographics specification as
'inferior'. The practical point about demographics is that it is often
not implemented because many clinical IT environments already have an
MPI, so an openEHR EHR system typically implements the
PARTY_PROXY.external_ref pointers
<http://www.openehr.org/releases/RM/latest/docs/common/common.html#_generic_package>from
the EHR data instead.
But some environments need an openEHR demographic service, and I predict
more will, even when they have an MPI, because the MPI data is not
versioned or extensible.
Release 1.0.3 of the ITS component will have XSDs for everything. This
release is likely to be out by the end of the year or very soon afterward.
- thomas
On 27/11/2015 08:33, Bert Verhees wrote:
I think it is very easy to solve.
The premise is that several legal entities are sharing patients, and
also share an EHR system, and you want to distinguish which treatment
is given by which legal institution.
It is easy, build your system so, that all compositions are also
placed in folders pointing to the legal institutions which gave the
treatment.
As you maybe know, a composition can be in several folders
simultaneously.
So you can have a folder-system representing legal institutions that
share the EHR-system, and folder systems on medical reasons.
In this way it is easy to organize authorizations related to the legal
entities, and also other queries
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/
That is something funny, demographics are something which are treated
as a stepchild, not only in OpenEHR, but also in EN13606. In EN13606,
demographics can't even be archetype.
In OpenEHR, I remember a message on the list, some years ago, I
thought written by Sam Heard, that it should be replaced by non
semantical generic structures, which also exist in OpenEHR.
But fact is indeed that there is always something with it.
In LinkEHR-archetype-editor they have a demographics.xsd, you can
download it when you download their editor. In LinkEHR they also have
a demographics.xsd for EN13606, although this should not be
archetypable at all.
I would be interested what people think about this way demographics
are treated as a kind of inferior information-structure.
I think we need an answer from the OpenEHR foundation as it must be a
defined policy to do it this way.
Bert
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
