I will also just note that the reason the template model specifications have not been finalised in openEHR is that we thought it was necessary to really put them to the test - in the NHS environment - and make sure they worked. This is been fruitful - quite a few challenges came up and we have improved the model in various ways. The model is not complex at all, and we will get a draft up as soon as humanly possible for both the Template specification (which is what an .oet file is) and an 'operational template', which is very nearly the same as a big archetype (in ADL or XML, doesn't matter which). I hope people accept the preference not to put up untested paper specifications too early! When these new specifications are done, the current .oet files will probably need to be migrated - an XSLT tool will be provided for this, and our tools (which are not the only ones of course) will migrate all current files silently to the new form. Anyone who looks at the current .oet files should see that they are very simple files and that this migration will be quite trivial.
Some of the other adjustments being made due to the experience of archetypes and templates in the NHS environment are a better of version identification, lifecycle and so on. All improvements due to this work will be available on openEHR.org as we get the time to document them. - thomas beale Heath Frankel wrote: >> Good. I can happily help with this. >> >>>> C) Same as (B) but for the CSV files. >>>> >>>> >>> These are from templates so they require the kernel. >>> >> Ah good so I can transform with XSLT from the .oets >> > [Heath Frankel] > The transforms cannot be done from .oets as they do not have the details of > the archetypes, only references and further constraints of archetypes. In > addition, the .oet files are currently a proprietary format used by the > Ocean Template Designer since there is no finalised specification for > templates in openEHR. > > Having said that, Ocean has developed an Operational Template generator that > effectively compiles the .oet and archetypes into a single constraint > definition which can be serialised to XML and be used for these kind of > transformations. This Operational Template utilises the existing Archetype > Object Model and R1.0.1 XML schema with minor extensions based on the draft > openEHR Template specification (with minor modifications that will be > provided as implementation feedback to the specification author for > consideration). This approach has already been used by Ocean to generate > XML Schema's for a specific template using XSLT from a compiled and > serialised Operation Template. This resolves both problems identified > above. > > Heath > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > -- please change your address book entry for me to Thomas.Beale at OceanInformatics.com *Thomas Beale* /Chief Technology Officer/ Ocean Informatics <http://www.oceaninformatics.com/> Chair Architectural Review Board, /open/EHR Foundation <http://www.openehr.org/> Honorary Research Fellow, University College London <http://www.chime.ucl.ac.uk/> * *
