RE: latest archetype & template drafts

[pablo pazos <pazospablo@hotmail.com>]

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/

---

Date: Mon, 21 Dec 2009 21:50:19 +0000
From: thomas.beale@oceaninformatics.com
To: openehr-implementers@openehr.org
Subject: Re: latest archetype & template drafts

On 19/12/2009 07:54, pablo pazos wrote:

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? 

Pablo,

I have a feeling this problem is solved in more recent versions of the ADL parser, but not the one being used by the archetype editor. I will create an issue. In the meantime, try loading the archetype in the latest ADL workbench and saving it again - I think the node_id will appear.

- thomas

---

Keep your friends updated— even when you’re not signed in.

_______________________________________________
openEHR-implementers mailing list
openEHR-implementers@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-implementers