I cannot claim to be an implementer of openEHR but I am still interested to understand the proposed use of Tables. Can anyone point me to a place where this is already explained with examples, the abstract discussion is a little hard to follow.
My simple reading of this is that what are currently trees would instead be expressed as a sparsely populated arrays - is that the point? Tom Seabury NHS Data Standards & Products From: openehr-technical-bounces at openehr.org [mailto:[email protected]] On Behalf Of Erik Sundvall Sent: 10 November 2010 16:16 To: For openEHR technical discussions Subject: Re: openEHR-13606 harmonization CR regarding CLUSTER/TABLE etc and ENTRY/OBSERVATION (Was: ISO 21090 data types too complex?) Tom, did I really express myself in such an unclear way or did you not read properly? Or did you respond to the wrong thread somehow? Perhaps i misinterpret your tone and arguments so please clarify if you have problems with the following: 1. tables, clusters etc I did not suggest that we should avoid having a single fixed way of defining table structures in openEHR. I suggested using a new attribute to indicate if a cluster is conceptually/graphically to interpreted as a table, list etc. instead of using separate classes for this purpose. Of course we need strict definitions of allowed values for this attribute (an enumeration or a list in the openEHR terminology, just as in other parts of openEHR presently). Of course specifications should include exactly how to interpret the clusters as rows and columns. Ian and Sam indicate that this would also have the benefit of allowing tables anywhere in a cluster hierarchy instead of only at top level. Do you have any objection against this provided that it is introduced in a well defined manner as described in the previous paragraph? Your argumentation sounds like somebody suggested that tables are not needed in openEHR at all or that they should be defined in random different ways. 2. Observations etc. I suggested that ISO 13606 gets extended with the openEHR ENTRY subclasses. Here I did not suggest changes to openEHR. (Even though I tried to say the class names can be confusing if you for some reason strongly believe that a technical class name only can be used for exactly what your own perception of that English word means.) Perhaps your OBSERVATION examples are just your way of expressing that you support my idea and why it is important to have the ENTRY subclasses to encourage consistency. The part about automatically converting openEHR ENTRY subclass structures to 13606, was definitely not a suggestion to remove them from openEHR. Instead it was more of an enquiry if it was at all possible in a non-destructive way. If it is, then openEHR archetype modeling, queries etc could after auto-conversion be used somewhat safely in a setting where you only have 13606 available. Best regards, Erik Sundvall erik.sundvall at liu.se<mailto:erik.sundvall at liu.se> http://www.imt.liu.se/~erisu/ Tel: +46-13-286733 ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSI recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere For more information and to find out how you can switch, visit www.connectingforhealth.nhs.uk/nhsmail ******************************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101110/26243600/attachment.html>
