Hi,
Sorry if this is the wrong forum.
Is there a description somewhere of the oet-files produced by the Ocean Informatics Template Designer?
I would like to use the templates in an application as a basis for input forms, but then I need
a specification of the file-contents.
Regards
Olof Torgersson
Hi Olef,
I’m sure someone from Ocean with more detailed technical knowledge will give a more precise answer but you might consider using the forthcoming formal openEHR Operational Template specification for this sort of exercise. I have been working with Derek Hoy’s Clinical Templates project (www.ClinTemplate.org), which uses a simple web-based approach to gathering clinical data entry requirements and at present uses a custom internal XML format. We are lookng (fairly quickly) to use the openEHR operational Template specificaction (OPT) as the back-end formalism. We think this approach will be much easier as the Oet files only contain the constraints on underlying archetypes (effectively a diff) whilst the OPT format contains the underlying archetypes themeselves and can be easily used to generate XSDs or other artefacts.
see http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes
The openEHR specification is very close to completion.
It would be interesting to know more about your project. We are aware of a requirement for a data-entry/UI requirements gathering tool which, though based on openEHR templates, goes somewhat beyond their natural domain in capturing further UI requirements and rules. The Clinical Templates work has more of a focus on generic infomation standards capture, rather than specific local data-entry but there is considerable cross-over.
Regards,
Ian
Dr Ian McNicoll
office / fax +44(0)141 560 4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian@mcmi.co.uk
Clinical Analyst - Ocean Informatics ian.mcnicoll@oceaninformatics.com
Member of BCS Primary Health Care Specialist Group – www.phcsg.org
2008/11/6 Olof Torgersson <oloft@chalmers.se>
Thanks for your reply. Clinical templates seems like an interesting project.
Considering my project, I've been working for several years in a project
where we have developed
tools that let clinicans define their clinical models/templates
themselves. These templates are then read by software that instantiates
them into
tools for data-entry. We currently have GUI:s for Web, a desktop
application and PDA. The tools have been used for entering data during
some 15-20000 examaninations in several projects, mostly within the
field of oral medicine.
In spirit our approach is similar to the ideas with archetypes and
templates used in openEHR.
Since we are using our own formats to model clinical data, which no-one
alse can use, we are looking into adopting openEHR.
One could say that I'm conducing a feasibility study, where being able
to create archetypes and templates and then read them into our
software is a first necessary step.
regards
Olof
Ian McNicoll skrev:
Olof,
In http://svn.openehr.org/ref_impl_java/BRANCHES/trunk-zm-merge/ you
will find the XSDs that describe the OET format. These XSDs were based
on a draft version of the Template specification and may not be up to
date with the current version of the specification, but it is a start
point. This link points to a java implementation of the openEHR models
that was donated by Zilics. There is also a Template parser that you can
use to read the OET files representing templates and transform them in
Java objects.
If you're trying to implement an input interface from templates, you can
also use the metadata feature of this implementation. You can use
metadata to associate GUI-Hints to archetypes or templates, what will
help you to create useful interfaces automatically.
Please, see this post:
http://lists.chime.ucl.ac.uk/mailman/private/ref_impl_java/2008-November/000975.html
for more information on what is available.
Fabiane
It has already been agreed between openEHR and NHS to publish the current specification of the .oet files as an openEHR working specification, for the interim period until the new template model is finalised. Please DONT FORGET that the new specification will be different! If you want to play or even implement seriously, there will be changes involved at some point in the near future. However, the size of the template model is small and such changes should be easy to accommodate.
Ian McNicoll wrote:
Hi Olof,
Ocean currently does what you are intending to do here but we do not use the .OET file. As mentioned by others, the .OET only represents the references to archetypes and the additional constraint rules to apply to those archetypes. To utilise this for anything of use you need to combine the template, archetypes and rules together in memory before applying any additional logic to the template definition. BTW, the latest OET schema is always deployed with the Template Design in the schemas folder.
As indicated by Ian, the Operational Template is what is intended to be used for software operations beyond the knowledge design process. The Ocean Template Designer has an Operational Template export function (File/Export/ as Operational Template). This features is continuing to be debugged with new template use case so depending on what version of the Template Designer you have, the resulting Operational Template may still have some issues. Using the latest Beta release (https://wiki.oceaninformatics.com/confluence/display/TTL/Template+Designer+Beta+Release) is recommended and to return to for Beta updates on a regular basis. I can provide you with the current Operational Template schema that extends the Archetype schema. This schema (see https://wiki.oceaninformatics.com/confluence/display/TTL/Template+Designer+Resources) is relatively close to the new Template Object Model draft (available on the Wiki) but will be updated in the next couple of months to align with this new draft. Any migration from this OPT format to the new TOM will be much smaller than transitioning from OET to the TOM.
From this OPT you can produce all sorts of artefacts, we produce an abstract form definition from which we can produce web forms in ASP.Net, Template Data Schemas (XML Schema), Template Data Objects (c# classes), HTML Documentation, Composition Prototypes (empty composition data instances). The OPT is a pivotal artefact bridging between the Knowledge Designs and Operational Software.
Heath
Hi,
See below.
Has anyone done anything in Java with relation to operational templates?
I know of the zilics-models available in the svn-repository, but they are for oet-templates I believe.
Regards
Olof
Vidarebefordrat brev:
There’s nothing much yet at trunk-zm-merge, but the code at
http://svn.openehr.org/ref_impl_java/SANDBOX/zilics-models/
seems to be doing a lot of what we are looking for.
regards
Olof
6 nov 2008 kl. 17.17 skrev Fabiane Bizinella Nardon:
Hi,
I read the Template OM linked in the previous email(from wiki)
http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes
, but I couldn’t find complete information about Methods, their input values and outputs, etc. In donated java code from Zilic company, there’s no documentation either.
Can anyone suggest another resource?
I need to understand all those methods in detail to be able to create a GUI based on Templates for my application.
Regards
Pariya
Hi Olef,
I’m sure someone from Ocean with more detailed technical knowledge will give a more precise answer but you might consider using the forthcoming formal openEHR Operational Template specification for this sort of exercise. I have been working with Derek Hoy’s Clinical Templates project (www.ClinTemplate.org), which uses a simple web-based approach to gathering clinical data entry requirements and at present uses a custom internal XML format. We are lookng (fairly quickly) to use the openEHR operational Template specificaction (OPT) as the back-end formalism. We think this approach will be much easier as the Oet files only contain the constraints on underlying archetypes (effectively a diff) whilst the OPT format contains the underlying archetypes themeselves and can be easily used to generate XSDs or other artefacts.
see http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes
The openEHR specification is very close to completion.
It would be interesting to know more about your project. We are aware of a requirement for a data-entry/UI requirements gathering tool which, though based on openEHR templates, goes somewhat beyond their natural domain in capturing further UI requirements and rules. The Clinical Templates work has more of a focus on generic infomation standards capture, rather than specific local data-entry but there is considerable cross-over.
Regards,
Ian
Dr Ian McNicoll
office / fax +44(0)141 560 4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian@mcmi.co.ukClinical Analyst - Ocean Informatics ian.mcnicoll@oceaninformatics.com
Member of BCS Primary Health Care Specialist Group – www.phcsg.org
2008/11/6 Olof Torgersson <oloft@chalmers.se>
Hi,
Sorry if this is the wrong forum.
Is there a description somewhere of the oet-files produced by the Ocean Informatics Template Designer?
I would like to use the templates in an application as a basis for input forms, but then I need
a specification of the file-contents.Regards
Olof Torgersson
Olof Torgersson
Associate Professor
Department of Computer Science and Engineering
Chalmers University of Technology and Göteborg University
SE-412 96 Göteborg, Swedenemail: oloft@chalmers.se
phone: +46 31 772 54 06
openEHR-technical mailing list
openEHR-technical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
openEHR-technical mailing list
openEHR-technical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
Regards
Pariya
PhD Student
Interaction Design Division
Department of Computing Science and Engineering
Chalmers University of Technology
Email: hajar.kashfi@chalmers.se
Office:+46 (0)31 7725407
Mobile Phone: +46 (0)707222815
Web: http://www.cs.chalmers.se/~hajar.kashfi/
Visit: Room Simula B, House Svea, Campus Lindholmen
Postal adress:
Email: hajar.kashfi at chalmers.se
Phone: +46 31 772 5407
Office: Room Simula B, House Svea, Campus Lindholmen
Postal Address: Chalmers University of Technology, SE- 412 96 Gothenburg, Sweden