On Thu, 2010-12-02 at 00:50 +0000, Thomas Beale wrote: > > Tim, > > if someone designs a template that has say a more limited set of > Snomed or other codes on a field than the original archetypes had, > then querying the data may be enabled with the template at hand, since > it would tell you what (reduced) set of code values could be possible > in that field.
So are you introducing some mind reading into this situation? Otherwise I cannot see any other outcome. Because what you are telling me is that it is somehow meaningful in discovering the rational for choosing a Snomed code from a set as opposed to choosing the same Snomed code from some subset. Hopefully, my healthcare provider is choosing their codes based on science. Therefore they choose the correct one either way. Of course if the correct one was subsetted out; that just equals BAD TEMPLATE. But if there is some business case for this mind reading adventure. I believe you'll need the luck of this guy http://www.youtube.com/user/failblog?blend=2&ob=4#p/u/85/woCCTm5m3qY to get any real information. > This is one of the most common uses of templates we are finding. So somehow knowing the possible choices somehow affects the actual code in the field you are querying? > I can imagine other thing, e.g. coding of fields that were just > DV_TEXT in the archetype. While I still think that this is a bad idea anyway. After all; it is either free text or coded text. Pick one. I still don't understand how knowing what set was available is meaningful to the code chosen. > In ADL 1.5-land, a template is just another layer of archetyping, with > some extra features. I still fail to see the need. It seems to me to be a useless layer of complexity. But, I am still interested in a use case where templates are 'needed' to 'fully interpret' the data. > This is distinct from any 'visual template' stuff, which I agree > should be a distinct artefact and probably formalism. And this level is dependent on implementation choices. Only applications built using the same framework can share these templates. If an entity is going to dictate presentation options and layout then they are likely (IMO) going to do so in the context of the same framework. --Tim -------------- 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/20101201/7d36406a/attachment.asc>
