"It provides a means of versioning FOLDER structures over
time, which is useful in the EHR, Demographics service or anywhere else
where Folders are used to group things."
But the only location I found in the Reference Model where it is
possible to start a directory is the EHR.
Maybe I missed the other locations, can someone please help me out here.
Although it is not explicitly stated, you could easily use a Folder directory in a demographic service that was managing Party objects. The Folders are just contained in their own VERSIONED_FOLDER object.
Hi Thomas, I understand the verionedfolder object. A way to keep track
to versions of a specific folder-object.
But what I don't understand is how to create a
folder/directory-structure in a demographic service, because I cannot
find a directory-root to start from as there is in the EHR-class.
I can off course always start a root and give it a fancy name, and
document it so that my customers know that it exists. Is that what is
possibly meant in the documentation? A kind of an undocumented
extension?
that would be what I would do; the current spec does not say how to do
this. I don't even know if it is useful in the demographic service
It is just that it is mentioned in the specifications of the reference
model, like I quoted, two emails ago.
So there is, (as I understand what you say), no extra location for a
directory-structure arranged in the reference model.
I was afraid I was missing something, and was preparing for an
intensively reading of several the documents again.
I would know some places of useful directory-services, connected to
OpenEHR. But indeed, that is outside the reference model.
I think that when more implementation experience is available with openEHR demographics, we can think about adding to the demograhphic part of the RM for this purpose
>
> that would be what I would do; the current spec does not say how to do
> this. I don't even know if it is useful in the demographic service
Well, Tom, I can see many times that VERSIONED components are important
in the demographics area. For one, think environmental aspects...
It is just that it is mentioned in the specifications of the reference
model, like I quoted, two emails ago.
Bert, I must point out that the demographics section (which has been
paid little attention too) **IS** a component of the reference model.
So there is, (as I understand what you say), no extra location for a
directory-structure arranged in the reference model.
I was afraid I was missing something, and was preparing for an
intensively reading of several the documents again.
While the document may be short on examples here. I think
implementation experience (as you note) shows that this is important.
I would know some places of useful directory-services, connected to
OpenEHR. But indeed, that is outside the reference model.
How so? The demographics components are EXPLICITLY in the RM.
Hi Tim, Thanks for your reply, I am afraid there is a matter of misunderstanding.
I quoted a text from a RM document which said something about the possibilities of having folders/directory in the demographic IM.
But in the demographic IM is no such entry arranged. That was my question.
that would be what I would do; the current spec does not say how to do
this. I don't even know if it is useful in the demographic service ;-)
Well, Tom, I can see many times that VERSIONED components are important
in the demographics area. For one, think environmental aspects...
well PARTYs are already versioned, but I imagine you are thinking of recording more ‘state’ data to do with the computing system? We have actually documented this idea somewhere, have to look it up
Tim Cook wrote:
> Hi Bert,
>
>
> > > that would be what I would do; the current spec does not say how to do
> > > this. I don't even know if it is useful in the demographic service
> > >
>
> Well, Tom, I can see many times that VERSIONED components are important
> in the demographics area. For one, think environmental aspects...
>
>
well PARTYs are already versioned,
True. But PARTY's are not PLACES.
but I imagine you are thinking of recording more 'state' data to do
with the computing system? We have actually documented this idea
somewhere, have to look it up
Hmmm, I can't think of where. If you find it then I won't just think it
was in my head.
There are two kinds of 'environment' data I can think of. One is version
info of software used to create EHRs, etc. This is mentioned in section
4.2.3 in the EHR IM.
Places - the current demographic model is designed to record Parties
that may have any number of addresses, contact methods etc. An
Organisation is a kind of Actor. This way of modelling treats
Organisations as active Actors of some kind.
There is currently no explicit element of the model that just records
e.g. an Address or physical location not connected to an Organisation.
To record this in the EHR, COMPOSITION.context (type = EVENT_CONTEXT)
may be what you want.
But - I am interested to know the requirements here.
