Hi Thomas, This example is very helpful, thanks. About Diego's questions and your answers on other emails, as I understand I have to "merge/resolve" the ontology section too, so all needed codes are there without ambiguity.Is the " component_ontologies" a constructor from ADL1.5? About the new nodeId codes with archetype ids, this should be transparent to software applications or at some point do I have to differentiate between normal at codes and archid codes?E.g. I see descriptions for normal at codes in termDefinitions but for those nodeIds with archetype id the codes are defined in component_ontologies section. Maybe there are other cases where those codes should be treated differently. It would be nicer to don't interpret the internal structure of nodeID for implementation simplicity.
-- Kind regards, Ing. Pablo Pazos Guti?rrez LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos Date: Wed, 2 May 2012 09:16:37 +0100 From: [email protected] To: openehr-technical at lists.openehr.org Subject: Re: Questions about ADL/AOM 1.5, archetype flattening and operational templates Hi Pablo, when archetypes are flattened, their ids replace the at-codes at the root points. This example shows the flattened version of the EHR_EXTRACT template test archetype. You can see the archetype ids, also a remaining open slot. It's not a proper OPT, so the top root node does not yet have the archetype id substituted. On 01/05/2012 00:22, pablo pazos wrote: Hi, I'm reading this page trying to understand how to implement archetype flattening and operational template support to our EHRGen project: http://www.openehr.org/wiki/pages/viewpage.action?pageId=196633#openEHRADL%26AOM1.5-TemplatesandSpecialisedArchetypes-Source%2Cflatandoperationalformsofarchetypessupported What I don't get is: when you have a flat archetype (e.g. without slots, internal refs and only with the specialized nodes) or an operational template (also flat), where is the reference to the original archetype nodes in the flattened AOM object for the resolved references (slots, internal refs, etc.)? For example: Archetype A: [at0000] OBS -> [at0001] HISTORY -> [at0002] EVENT (slot to archetype B) Archetype B: [at0000] EVENT -> [at0001] ITEM_TREE -> ... Flattened: (Archetype A) [at0000] OBS -> [at0001] HISTORY -> [at0002] EVENT -> (Archetype B) [at0000] EVENT -> [at0001] ITEM_TREE -> ... If I use the flattened archetype in my application, I would like to know what is the original archetype that constrained my EVENT, because could create queries based on the paths of that archetype. Maybe there's another way of doing the same that I can't see yet. Thanks a lot! -- Kind regards, Ing. Pablo Pazos Guti?rrez openEHR community in spanish: http://openehr.org.es LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos _______________________________________________ openEHR-technical mailing list openEHR-technical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120502/dab01362/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: ijghheei.png Type: image/png Size: 31538 bytes Desc: not available URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120502/dab01362/attachment-0001.png>
