Heath Frankel wrote: > Greg, > The XML representation of Archetypes are just as normaitive as ADL, the XML > (just like ADL using a different syntax) is a serialisation of the Archetype > Object Model representation of an Archetype. > > The OET files are a proprietary template definition used by the Ocean > Template Designer product. This Template Designer also has a Form Designer > that can take a template definition and automatically build a form. This > form can be output as a Form Definition with control constraints expressed > using the Archetype Object Model constraint object. This form definition > can be used within the Ocean EhrView web components to render this form > using ASP.NET. > > *we should be clear that the schema of templates is only 'proprietary' temporarily. It has been under development and use by Ocean and various users, including the UK NHS. Efforts are underway to finalise a draft specification of the template specification format for openEHR. As anyone will see from an .oet file, the model is relatively simple and is not in any way secret. It has just been a case of using something to see how well it works before proclaiming it a specification (or standard...).
The draft specification should be available within a few weeks. - thomas beale *
