Yes and no... we used to think that templates would be only local, but it is now clear that governments want a way to standardise whole data-sets, which is what an (ADL 1.5) template is - effectively an archetype that grabs bits of other archetypes and puts them together to create a specific data set, e.g. mixture of data captured in a specific kind of consultation, or lab result, or a discharge summary or whatever. These templates are very likely to be standardised, and offer a much better way to do this than the current way of doing it which is generally via ad hoc XML schemas. An ADL 1.5 template can be expressed as an XSD of course, but this is a downstream tool generated schema, not a hand-designed one.
Further it turns out that a lot of institutions really do want to share templates, so a shareable formalism is actually important here. The ADL 1.5 spec is moving along ;-) I agree with the 'mind-altering' comment. - thomas On 01/12/2010 18:30, Tim Cook wrote: > IMO templates are an implementation specific issue and should not be > part of the reference model. Archetypes that express a concept as a > maximal dataset are sufficient for interoperability. Local templates > are just that; local templates. Certain implementations may share > templates between applications but I dare say any attempt to 'standard' > across implementations is wheel-spinning. > > If people are expecting magic pop-out-of-the-box applications then they > are taking something mind-altering. :-) > > My 2 cents, > > Tim > * * -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101201/7d6f72a7/attachment.html>
