Hi, Free text versus structured data and information debate: - Like Ian said: Archetypes and templates take away problems from the IT-domain and leave them for those in healthcare. When those in health need, want decision support they will have to use more structured info. In the end they will solve their own problems.
- We, in the archetype world, will have to show the way. Timo's thoughts are providing ways to think. Archetypes used must be able to serve many purposes: recording, retrieval, exchange, archiving and re-use for among others decision support. - The boundary problem has to be solved. Davids 'grey zone' must be reduced to a manageable small zone. We can not change the past and must find ways to deal with pre- historic (pre-archetype) data. In order to solve it we must look forward and reduce the 'grey zone' by acknowledging that most post-coordination (using modifiers in Snomed-space instead of Archetype/Template space) must end. Gerard On Jun 3, 2008, at 7:43 AM, Sam Heard wrote: > Terminology > A final part of the equation is the area that David Markwell has > been working on in the NHS in the UK. He is investigating how to > generate computable terminology code phrases from an archetype: that > is, how to post-coordinate information captured in an archetype for > inferencing in the terminology space. This has benefit in linking > with the pre-archetype data and may allow complex research to be > undertaken in the future using ontological tools and engines. > > So we need to keep the balance between freedom and structure, > recognising (as Ian McNicoll says) that good archetypes take the > problem out of the technical space to where it becomes a human (and > potentially soluble) issue. > > Cheers, Sam -- <private> -- Gerard Freriks, MD Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252544896 M: +31 620347088 E: gfrer at luna.nl Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080603/d583d302/attachment.html>
