Tim Cook schreef:
> Hi Bert,
>
> Please note that this is MY understanding of the reference model and is
> subject to change by the expert opinion of others.
>
> On Wed, 2008-04-23 at 16:16 +0200, Bert Verhees wrote:
>
>> Archetypes are in fact RM-objects, I have a way to store RM-objects
>> efficiently.
>>
>
> Okay...good. :-)
>
>
>
>> My question: In what form should I shape the data, so that form is
>> usable with every possible valid archetype?
>>
>
> Ahhhh, I think that this is the crux of the issue.
> My answer is that you "do not".
>
> When data is captured (or changed) it is valid for THAT time and place
> in accordance with the constraints of that version of that archetype.
> That data is is not standalone, it is invalid anywhere else.
>
> In order to maintain the semantic context; that data is tied to that
> archetype, in a composition and submitted as part of a contribution.
>
I agree, that is what I do, what I try to find is a form to hand over
the data, with the archetype. So both, at the same time will be eaten
and stored by the kernel.
For example, I have a very simple archetype, only one data entry
The definition looks like this
definition
PERSON[at0] matches {
identities cardinality matches {0..*; unordered; unique} matches {
PARTY_IDENTITY[at1] matches {
name matches {
DV_TEXT matches {
value matches {"legal identity"}
}
}
}
I want to hand this archetype with data, for example from a webform, or
a message interpreter to my kernel which knows what to do with it.
At this moment, I am thinking about something like this, an XML form
which contains the archetype-ID, and there in, nodes with path and value
Because only leaf-nodes can contain data, there only leafnodes in the
XML-file
For example for this archetype it would be:
<ArchetypedData
archetype_id="openEHR-EHR-CLUSTER.person_demographics.v1draft" >
<ArchetypedDataset path="/identities[at0]/name[at1]/value"
value="Johnsson"/>
</ArchetypedData>
But I don't know if this is sufficient.
Anyway, this XML file will be given to the RM-builder, together with the
ADL-file, and the rm-builder should be able to validate and create good
RM-objects from this.
That is my idea, but I don't know if it is a good idea
Bert
> Compositions are versioned in order to maintain temporal context. A
> contribution is a change set of versioned compositions and these are key
> to describing the validity of the data. See the openEHR EHR Information
> Model reference document at
> http://www.openehr.org/svn/specification/TAGS/Release-1.0.1/publishing/roadmap.html
>
>
>> I hope I made myself clear, it is difficult to ask the right question
>> and get because of that, the right answer.
>>
>>
>
> I agree. Asking the right question is always the hard part of systems
> analysis. :-)
>
>
> I hope this helps.
>
>
> Cheers,
> Tim
>
>
>
