Hi Athanasios, Ocean operational template (Template.xsd) and thew proposed TOM changes marry up as Operational Templates. As I understand it the proposed TOM operational template schema is virtually identical to the current Ocean operational template template.xsd.
>>Would the following be correct? >> 1) A template is "archetypeable" which means that it too will have an ID and its own path prefix Yes, all that happens is that the archetyped data carries a template identifier, in addition to the archetypeID. Querying can completely ignore the templating aspect. >> 3) A template must contain "section" elements. These are archetypeable entities. Each section describes a list of archetypeable "Items". No - Section elements are completely optional and only apply to Composition templates - see below. >> 4) A template might contain "subsection" elements if this is required. Yes >> 2) A template must contain a "composition" which contains a list of archetypeable "Items". No - Templates can be applied to any archetype. Many templates will be at Composition level but others just add constraints to Entry or even Cluster archetypes. We call these embedded templates in the Ocean tools and as the name suggests these can be re-used within other templates. Just think of templates as another layer of constraint. In ADL1.5, templates and specialised archetypes are essentially identical. The only difference (yet to be decided) is that templates cannot add new content. Both can further constrain their parent. On 16 March 2012 14:08, Athanasios Anastasiou < athanasios.anastasiou at plymouth.ac.uk> wrote: > Hello everyone > > I was wondering if there are any updates regarding openEHR Templates? > > I am not sure how the material in the TOM (http://www.openehr.org/svn/** > specification/TRUNK/**publishing/architecture/am/**tom.pdf<http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/tom.pdf>) > maps to the currently available XSD at (http://www.openehr.org/** > releases/1.0.2/its/XML-schema/**Template.xsd<http://www.openehr.org/releases/1.0.2/its/XML-schema/Template.xsd> > ) > > Would the following be correct? > > 1) A template is "archetypeable" which means that it too will have an ID > and its own path prefix > > 3) A template must contain "section" elements. These are archetypeable > entities. Each section describes a list of archetypeable "Items". > > 4) A template might contain "subsection" elements if this is required. > > 2) A template must contain a "composition" which contains a list of > archetypeable "Items". > > > Therefore to "build a Template", one would first need to list the > composing archetypes as Items of subsections (if subsections are required). > Then list the subsections as items of sections and finally, list sections > as items of the "Composition". And this concludes at least with the > structural part (?) > > > 3) A template must contain either "Observation" or "Evaluation" elements > (depending on the nature of the template (?)) that describe lists of > "Entry". These elements set the default values of the composing archetypes > individual fields through a series of "Statement"s. (or evaluate > expressions) > > Would this be an accurate description? > > Looking forward to hearing from you > Athanasios Anastasiou > > > > > > > > ______________________________**_________________ > openEHR-technical mailing list > openEHR-technical at lists.**openehr.org<openEHR-technical at > lists.openehr.org> > http://lists.openehr.org/**mailman/listinfo/openehr-** > technical_lists.openehr.org<http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org> > -- Dr Ian McNicoll office +44 (0)1536 414 994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical Modelling Consultant, Ocean Informatics, UK Director/Clinical Knowledge Editor openEHR Foundation www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120319/25dcef71/attachment.html>
