latest archetype & template drafts

Implementers (archive)
1

You can see the progress at
http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes

This page has updated explanations for changes in ADL/AOM 1.5, and also
links to the most recent archetype and template drafts. The template
draft still has major parts to be done, but the modelling is nearly
worked out. The operational template section will be next to be completed.

There are also a bunch of UML and other diagrams on the page which will
give people quick access to the changes.

comments welcome.

- thomas beale

2

Hi Thomas,

I see you’re seeing problems with node_id in C_Primitive and C_Domain_Type, I’ve a problem in ArchetypeInternalRef too.

This is my issue:

In the AOM specs, every CObject has a mandatory node_id attribute, included the ArchetypeInternalRef.

I make an archetype using Oceans Archetype Editor and the node with the reference looks like this (I think this is a valid ADL node):

CLUSTER[at0008] occurrences matches {0..1} matches { – Pelvis
items cardinality matches {0..*; unordered} matches {
use_node ELEMENT occurrences matches {0..3} /data[at0001]/events[at0002]/data[at0003]/items[at0004]/items[at0012]
}
}

But the use_node internal reference has no node_id, so, in the AOM structure parsed from the ADL, the ArchetypeInternalRef to /data[at0001]/events[at0002]/data[at0003]/items[at0004]/items[at0012] has no node_id.

This problem complicates our binder implementation to support Internal Refs :frowning:

Cheers,
Pablo.

3

pablo pazos wrote:

4

Hi Thomas,

With your input I can state that the problems are in the tools because:

  1. It is not possible to define a node_id for a internal ref on Oceans Archetype Editor.
  2. When an archetype is parsed o AOM with the Java Ref Impl ADL parser, the node_id of the reference is always empty, so the node_id is not inferred from the target id.

Is this correct?

Best regards,
Pablo.

6

Great, let me know if you find the problem.

Now that you’re revising the editor, wanted to tell you about another issue.
If you define a constraint of external terminology for a text (like coded as ICD10), the editor will not let you specify the terminology id.

I had to do this example with notepad and is parsed ok by the java ref impl:

DV_CODED_TEXT matches {
defining_code matches {[icd10::ac0002]} – Diagnostico de trauma
}

ac0002 is the id on the constraint_definitions of this constraint.

Thanks a lot!

Pablo Pazos Gutierrez
http://sites.google.com/site/pablopazosgutierrez/