Thanks for a very timely and provocative debate. I think the original question came from Dereks reply to my earlier blog posting. The reasons for slow adoption have been discussed here already and recent discussions on the technical lists highlight the challenges in aligning the health IT standards community in any one direction.
My own perspectives on the challenges include; Complexity.. we are dealing with a very complex system in healthcare. This is an ecosystem not a machine so none of us has complete control or understanding of the space. http://frectal.com/book/chaos-complex-complicated-simple-and-cynefin/ Change requires; -People..people have different backgrounds, agendas, goals etc in this field. They can really struggle for a common language at times (eg datatypes dare i say!). Its easy to say the other guy doesn't quite understand my world. Rather we all need to make an effort to the whole that makes life that little bit easier for everyone else. Politics is the tricky "process by which groups of people make collective decisions". It seems clear that there are too many SDOs/standards bodies in eHealth with overlapping but unaligned efforts. We need to address that. As Tom mentions the openEHR is in discussion with IHTSDO toward that end. I have invited comments/thoughts on that in recent months.. -Process.. again many folk work differently so joining efforts up is a challenge (again back to joint working needed + more on process anon, w.r.t. progressive developments in Sweden..) -IT- I agree with many others that we particularly need better tools, shared tools, particularly those that help join the clinical frontline with the international health IT standards space. (See this story as to where my own efforts in the NHS got stuck..) http://frectal.com/book/healthcare-change-the-way-forward/healthcare-change-why-%E2%80%9Copen-source%E2%80%9D-is-part-of-the-recipe/ As has been highlighted we need a means to resource that tooling development, which the health community can both contribute to and benefit from. -Value.. we need to aim to offer value right at the clinical frontline.. that must prove their utility in the wild as Olusegun put it. As indicated, we await progress on a funding an approach to tackling these key challenges with IHTSDO.... meanwhile please keep up the provocative debate. Regards, Tony Dr Tony Shannon Consultant in Emergency Medicine, Leeds Teaching Hospitals Clinical Lead for Informatics, Leeds Teaching Hospitals Chair, Clinical Review Board, openEHR Foundation tony.shannon at nhs.net +44.789.988.5068 ________________________________________ From: openehr-clinical-bounces at openehr.org [openehr-clinical-bounces at openehr.org] On Behalf Of segunodujebe at yahoo.com [[email protected]] Sent: 05 November 2010 09:27 To: For openEHR clinical discussions Subject: Re: Why is OpenEHR adoption so slow? Hello All, It has been quite interesting following this string of discussion. A lot of passion is coming out which indicates a mixture of frustration and hope. But let me say OpenEHR is a wonderful idea.Yes the initial intent was future proofing but we can't wish away interoperability as a major deliverable! As far as standards go, it is not always the best that gets wide adoption! The key to ubiquity is reaching critical mass quickly and that depends on utility: utility in the wild, not in the research lab. There must be some well-scoped demonstrable platform that everybody can work toward delivering-that will be supported by the community. Not just siloed implementations. This platform will stand the best chance if it is open-sourced.Then it can be a trigger for adoption. I don't think clinicians have time to wonder what standards are running their EHRs.They just want them to work. As hard as HL7 seems, it has utility! Like the adage goes if you are winking in the dark, only you know it. To overtake other standards, the openEHR community must learn from the Apache Foundation or OSGi for instance. The route to viral adoption is open-sourcing of an implementation. Cambio most likely may lead in this since theirs is based on Java. May Ocean should! The other thing is the Service Model which can be used not only for testing but for serving instances of implementations. I hope my ramble made some sense. Dr Olusegun Odujebe Lagos, Nigeria Sent from my BlackBerry wireless device from MTN -----Original Message----- From: pablo pazos <[email protected]> Sender: openehr-clinical-bounces at openehr.org Date: Thu, 4 Nov 2010 22:21:07 To: openehr clinical<openehr-clinical at openehr.org>; openehr technical<openehr-technical at openehr.org>; openehr implementers2<openehr-implementers at openehr.org> Reply-To: For openEHR clinical discussions <openehr-clinical at openehr.org> Subject: RE: Why is OpenEHR adoption so slow? _______________________________________________ openEHR-clinical mailing list openEHR-clinical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical _______________________________________________ openEHR-clinical mailing list openEHR-clinical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical ******************************************************************************************************************** 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 ********************************************************************************************************************
