Re: Adding a new method to the Archetype class

[Thomas Beale <thomas.beale@oceaninformatics.com>]

On 30/01/2010 05:04, pablo pazos wrote:

Hi Thomas,

I was thinking about your example with blood presure:

/data/events[at0006]/data/items[at0004] - human readable form: /data/events[any event]/data/items[Systolic]

/data/events[at0031]/data/items[at0004] - human readable form: /data/events[Postural change]/data/items[Systolic]

You say that the meaning of each node is given by the path, because it determines the context of each node.

But if you have diferent meanings, I think that different ontology terms are needed for each node, but the ontology terms are indexed by the nodeID, instead of the node path.

the ontology section of the archetype defines the 'meaning' of each at-code. The meaning of each node is inferred from its path - i.e. you need to think of a path as a post-coordination of terms.

I've an Instruction archetype with a constraint of DvText in the archetype, this example is like the one mentioned by Rong, this node has no nodeID, its path is /narrative, so I can't find a term in the ontology to show the label for this field on the GUI, because I need the nodeID.

well there are quite a few single-valued attributes in the model, like CARE_ENTRY.protocol, the narrative one you mention and so on. They don't need at-codes, because they don't have siblings - siblings can only exist under container attributes (like CLUSTER.items for example). So the correct path for an object under the 'narrative' attribute is simply '/narrative' (relative to the Instruction root).

May be the ontology mapping must be something like ont[lang][pathToAOMNode] instead of ont[lang][AOMnodeID], What do you think?

the point of the ontology is to define the at-code meanings - as I say, the node meanings are inferred. Note that in the bindings section you can use at-codes or paths, enabling external terms to be bound to particular paths, e.g. 5 min ave systolic BP or so.

hope this helps

- thomas

_______________________________________________
Ref_impl_java mailing list
Ref_impl_java@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/ref_impl_java