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: > 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 > <http://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 at mcmi.co.uk <mailto:ian at mcmi.co.uk> > > Clinical Analyst - Ocean Informatics ian.mcnicoll at oceaninformatics.com > <mailto:ian.mcnicoll at oceaninformatics.com> > > Member of BCS Primary Health Care Specialist Group ? www.phcsg.org > <http://www.phcsg.org> > > > 2008/11/6 Olof Torgersson <oloft at chalmers.se <mailto:oloft at 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, Sweden > > email: oloft at chalmers.se <mailto:oloft at chalmers.se> > phone: +46 31 772 54 06 > > > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org <mailto:openEHR-technical at openehr.org> > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > ------------------------------------------------------------------------ > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >
