Sam Heard wrote: > Dear All, > > We have been discussing the issue of templates and whether we keep an > identifier of a template in the data. My concern has been that this ID > might be seen as an absolute constraint on the data, whereas the > precedence of constraint must be: > > 1. The data must conform to the reference model > 2. The data must conform to the archetypes > 3. The data must be complete > 4. The template can be invoked to ease data entry. > > What this means is that when data is already present, even if it does > not conform to a template (which may have been used as a guide when > entering data) it must be allowed. Clearly an application may restrict > data entry to the template (this is an application issue) but it cannot > impose a template on data already gathered. > > Keeping a template identifier in the EHR is then a statement only that a > template of some sort was used in creating the data. This template may > be in a form that is generally available (eg ADL) or a specific local > template implementation - there is no need to use a generalisable form > of template within the openEHR framework - though it has advantages. > > Having said that, it is clear that it may be useful and I would suggest > that we consider an optional string attribute at the composition level > that allows recording the id of a template used to form the composition. > > What do others think?
Sam, I agree keeping template identification information in EHRs is useful. And it could be useful not only in Composition but also in other classes like Entry and Party level classes. If so, maybe we should even consider to create a class Templated with all the details regarding usage of the template, e.g access control, and include it as optional attribute named "templateDetails" in root class Locatable so that Composition and other Locatable subclasses can get template support. On the other hand, if Template is modeled as subclass of Archetype (it looks like a template is kind of specialized archetype) and TemplateID is subclassing ArchetypeID, we could very well stay with the current Locatable definition and have template support straight away. Regards, Rong > > Cheers, Sam > -- > > > Dr. Sam Heard > MBBS, FRACGP, MRCGP, DRCOG, FACHI > > CEO and Clinical Director > Ocean Informatics Pty. Ltd. > <http://www.oceaninformatics.biz/>Adjunct Professor, Health Informatics, > Central Queensland University > Senior Visiting Research Fellow, CHIME, University College London > Chair, Standards Australia, EHR Working Group (IT14-9-2) > /Ph: +61 (0)4 1783 8808/ > /Fx: +61 (0)8 8948 0215/ > > > - If you have any questions about using this list, please send a message > to d.lloyd at openehr.org - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
