HA: Medinfo2010 Clinical Modelling Tutorial
So 2007. It feels really sad. Ogi ??: openehr-implementers-bounces at openehr.org [mailto:openehr-implementers-bounces at openehr.org] ?? ? Heather Leslie ??: Monday, 20 September 2010 4:23 PM : For openEHR clinical discussions; For openEHR technical discussions; For openEHR implementation discussions : Medinfo2010 Clinical Modelling Tutorial Hi everyone, Mission accomplished!! There was good representation of openEHR activity at Medinfo2010, and most of us should have arrived home this weekend. There were over 1000 attendees with a small exhibition. We had openEHR devotees from UK, Sweden, Portugal, Japan, New Zealand, Germany, and Australia - hope I haven't missed anybody. Shinji Kobayashi and I experienced some of South Africa's informal redistribution of wealth from our luggage in transit - Shinji parted from his camera; me from my jewels:( * A full day Clinical Modelling workshop was held on Saturday September 11 as one of the pre-conference tutorial sessions at Medinfo2010 in Cape Town, South Africa - Clinician-driven EHRs - the openEHR Approach. * A 90 minute openEHR Developers forum was held on Monday September 13 - run by Shinji Kobayashi, Rong Chen, Ricardo Cruz-Correia. * Scientific Demo: REST Based Services and Storage Interfaces for openEHR Implementations - Erik Sundvall, Mikael Nystr?m, et al * Christian Kohl (DE) presented 'Facilitating secondary use of medical data by using openEHR archetypes' - relating to his work on a prototype for use in Clinical trials utilising archetypes and templates. * Zilics (Brazil) were demonstrating their archetype-enabled EHR as part of the interoperability showcase. (Have I missed anyone?) _ The Clinical Modelling workshop was held 9am-5pm - an introduction to openEHR and clinical modelling in the morning, followed by examples and practical lessons learned and discussion in the afternoon. Attendees numbered ~30, and included a few return visitors who were first exposed to openEHR at Medinfo2007 in Brisbane, or those who had had some exposure via other routes, seeking to know more. However, most were newcomers, seeking an initial understanding and overview. Attendees came from Canada, UK, Korea, Hong Kong, Brazil, US, Netherlands, Nigeria, Sweden, Switzerland, new zealand, france, South Africa, and Austria, in no particular order. We were one of the few tutorials to proceed on the day, and the only one running over a full day, so in those terms we were somewhat of a success before we started! All powerpoint presentations have been uploaded to the Medinfo page on the openEHR wiki http://www.openehr.org/wiki/display/resources/MedInfo+2010+-+South+Africa - 6 presenters from 6 countries! * An introduction to openEHR by Ian McNicoll (UK) * A Knowledge tools demonstration using Archetype Editor, Template Designer and CKM and discussion of knowledge governance - myself (AU). * Practical implementation presentations - warts and all: * GastrOs Endoscopy Application - Koray Atalag (NZ) http://www.oceaninformatics.com/Media/docs/3-EndoscopyApplication-Atalag-52efe752-1a3a-4ba6-a90b-3ea2a7e4815d.pdf * Intractable Disease Surveillance in Japan - Shinji Kobayashi (JP) * 3 projects - Legacy Content, Clinical Guidelines Quality Repository in Sweden - Rong Chen (SE) (presented on his behalf by Ricardo Cruz-Correia) * Legacy Integration in Portugal - Ricardo Cruz-Correia (PT) __ Interestingly mentions of openEHR and archetype work filtered through other parts of the conference and presentations. At one point Ian McNicoll's work on the laboratory archetypes for structured histopathology reporting for the Australasian College of Pathologists was referenced in a HL7 CDA paper on the same topic, and a paper on a trial of 13606 in Brazil's Minas Gerais used CKM archetypes as the basis for their own archetype development! Others will possibly have similar experiences. __ The Developers Forum was attended by around 30 people as well - I'll let the organisers report back themselves... Cheers Heather -- Dr Heather Leslie MBBS FRACGP FACHI Director of Clinical Modelling Ocean Informatics http://www.oceaninformatics.com/ Phone (Aust) +61 (0)418 966 670 Skype - heatherleslie Twitter - @omowizard -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20100920/77310247/attachment.html
existence and assumed value
Hi Bert, Assumed value is different to default value (see the AOM spec for definition of assumed value, default value is further defined in the new 1.5 AOM spec). If an element has a assumed value defined and its value is not present, the assumed value should not be used in the data, it remains not present. The meaning of not present is the assumed value from a clinical perspective, but does not get injected into the data. Compare with a default value which does get injected into the data when the value is not originally present. My understanding is that assumed values are most usually used in state, not data (e.g. assumed value of blood pressure position is sitting). Heath -Original Message- From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- bounces at openehr.org] On Behalf Of Bert Verhees Sent: Monday, 20 September 2010 12:15 AM To: For openEHR technical discussions Subject: existence and assumed value Hi all, I noticed that the JAVA ADL-parser marks a CObject existence as required if it is not specified in ADL If there is also an assumed value specified, then this is, in my opinion conflicting, because the function of the assumed value is to use it when there an attribute is not used (page 21 AOM.pdf). Or am I wrong? Thanks for your attention Bert ___ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
existence and assumed value
Just to concur with Heath. These are intended to describe the clinical assumption that it would be safe to make, usually about patient state, if the data was NOT specifically recorded. i.e if patient position was not recorded in a blood pressure reading, it would be safe to assume the patient was sitting, or if the oxygen level was not recorded in the ambient oxygen archetype, it would be safe to assume that the patient was breathing air. In practice, we have very few examples in the CKM archetypes to date, where it is safe to make such clinical assumptions. Ian Dr Ian McNicoll office / fax? +44(0)141 560 4657 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com ian at mcmi.co.uk Clinical Analyst? Ocean Informatics Honorary Senior Research Associate, CHIME, University College London openEHR Archetype Editorial Group Member BCS Primary Health Care SG Group www.phcsg.org / BCS Health Scotland On 20 September 2010 09:10, Heath Frankel heath.frankel at oceaninformatics.com wrote: Hi Bert, Assumed value is different to default value (see the AOM spec for definition of assumed value, default value is further defined in the new 1.5 AOM spec). If an element has a assumed value defined and its value is not present, the assumed value should not be used in the data, it remains not present. ?The meaning of not present is the assumed value from a clinical perspective, but does not get injected into the data. ?Compare with a default value which does get injected into the data when the value is not originally present. My understanding is that assumed values are most usually used in state, not data (e.g. assumed value of blood pressure position is sitting). Heath -Original Message- From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- bounces at openehr.org] On Behalf Of Bert Verhees Sent: Monday, 20 September 2010 12:15 AM To: For openEHR technical discussions Subject: existence and assumed value Hi all, I noticed that the JAVA ADL-parser marks a CObject existence as required if it is not specified in ADL If there is also an assumed value specified, then this is, in my opinion conflicting, because the function of the assumed value is to use it when there an attribute is not used (page 21 AOM.pdf). Or am I wrong? Thanks for your attention Bert ___ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical ___ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
existence and assumed value
Thanks Heath for your explanation, that is indeed something completely different as I was thinking. So, it is something we do not need to worry about when processing archetyped data on the backend, You just made may day, saves me some time Bert Op 20-09-10 10:10, Heath Frankel schreef: Hi Bert, Assumed value is different to default value (see the AOM spec for definition of assumed value, default value is further defined in the new 1.5 AOM spec). If an element has a assumed value defined and its value is not present, the assumed value should not be used in the data, it remains not present. The meaning of not present is the assumed value from a clinical perspective, but does not get injected into the data. Compare with a default value which does get injected into the data when the value is not originally present. My understanding is that assumed values are most usually used in state, not data (e.g. assumed value of blood pressure position is sitting). Heath -Original Message- From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- bounces at openehr.org] On Behalf Of Bert Verhees Sent: Monday, 20 September 2010 12:15 AM To: For openEHR technical discussions Subject: existence and assumed value Hi all, I noticed that the JAVA ADL-parser marks a CObject existence as required if it is not specified in ADL If there is also an assumed value specified, then this is, in my opinion conflicting, because the function of the assumed value is to use it when there an attribute is not used (page 21 AOM.pdf). Or am I wrong? Thanks for your attention Bert ___ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical ___ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
existence and assumed value
Hi Bert, maybe also this links could be helpful.. http://old.nabble.com/%22state%22-and--%22protocol%22-structures-are-mandatory%2C-when-defined--td29174701.html and http://www.openehr.org/wiki/display/dev/Existence+of+Attributes+%28AOM,+ADL+and+XML%29 Leo BertV wrote: Hi all, I noticed that the JAVA ADL-parser marks a CObject existence as required if it is not specified in ADL If there is also an assumed value specified, then this is, in my opinion conflicting, because the function of the assumed value is to use it when there an attribute is not used (page 21 AOM.pdf). Or am I wrong? Thanks for your attention Bert ___ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical -- View this message in context: http://old.nabble.com/existence-and-assumed-value-tp29752510p29759320.html Sent from the openehr-technical mailing list archive at Nabble.com.
