Hy! I like this. CDA work is active here in Austria, and I would be very happy to see anything that connects CDA to archetypes.
You might then have to deal with nested archetypes, like how does a specific piece of information (an existing archetype) look within a CDA section (to be developed in the exercise you suggest) ? Could this be done on some examples, eg. discharge information, laboratory reports, radiology reports, medication? These are part of the Austrian EHR and would possibly attract an Austrian workforce with a bit of support. I myself can speak for the laboratory report, and we would try to participate actively and contribute. See you around, Stefan Sauermann Von: openehr-clinical-bounces at openehr.org [mailto:openehr-clinical-bounces at openehr.org] Im Auftrag von Sam Heard Gesendet: Montag, 18. August 2008 07:07 An: Openehr-Technical; openEHR-Clinical Betreff: Differential display Dear All (cross post) We are working in an environment where many applications and CDA messages have information that is displayed as text and repeated information in structured form. This also arises in applications which have a formatted document plus structured information (typically in primary care). I am proposing that we have a section archetype to manage this. The archetype display script would not display any information about the section itself (it would be invisible) and would display the first subsection but not the second. The section archetype would be: * Differential display * Display * Entries here will display * Non-display * Entries here will not display This does mimic the CDA approach but does have the added benefit that the displayed information can be structured as well (a requirement from our customers who want to mix the textural content and structured medication orders (ie not duplicate these in the textural display). If this archetype arrived somewhere where it was not known the generic display script would show the non-display information (twice). This would be unlikely to cause errors especially as there would be a heading Non-display. So that is the approach that we have considered. There is an alternative - just have a non-display section. This has the advantage that it could be added when required on an adhoc basis. The major problem that I can see is that it would not be clear which part of the record held the information that was redundant (ie where it was being displayed). I would be interested in people's views of this approach to the redundant structured data problem that arises from CDA and word processor style record applications. Cheers, Sam Cheers, Sam -- Dr Sam Heard Chief Executive Officer Director, openEHR Foundation Senior Visiting Research Fellow, University College London 214 Victoria Avenue Chatswood, NSW, 2067 Phone: +61 2 9415 4994 Mobile: +61 4 1783 8808 21 Chester Cres London E8 2PH Phone: +44 20 7249 7085 Mobile: +44 77 9871 0980 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20080818/152a41ef/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 5828 bytes Desc: not available URL: <http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20080818/152a41ef/attachment.jpg>
