Hi David, Thanks for the reply.
On Thu, 2010-12-02 at 22:54 +0100, David Moner wrote: > Maybe I do not have the knowledge to give a valid clinical example but > it is reasonable to think that constraining an archetype in the way a > template does can influence the interpretation of the data. What is reasonable is subjective; but okay. > Imagine you have a set of archetypes and you define a template > constraining some items to not allowed. Okay. > You use that template to fill > some data and then you require the collaboration of a physician from > an external organisation. You share the archetypes but not the > template. And then the other physician fills some more data (including > the one you marked as not allowed) and returns it to you. Okay. > There is the > problem, when you revise the data using again your own template you > will never see part of the new data and that can affect your > interpretation of it. It that *is* a problem then ==> Bad application design. > That's why structural templates must be also shared in some cases. #1. You do not revise data in a health record. You version it with additional information. #2. Any well designed archetype / template combination is going to use the same 'data structure'. Irregardless of the available options. #3. The templates you use should only restrict data entry. It should not filter existing data of the same structure. If it does; there goes interoperability. Along with the entire premise for the use of and purpose of archetypes. --Tim -- *************************************************************** Timothy Cook, MSc Project Lead - Multi-Level Healthcare Information Modeling http://www.mlhim.org LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook Academic.Edu Profile: http://uff.academia.edu/TimothyCook You may get my Public GPG key from popular keyservers or from this link http://timothywayne.cook.googlepages.com/home -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101202/ac36e9d1/attachment.asc>
