Sent from my iPad
Begin forwarded message:
From: Ian McNicoll <Ian.McNicoll@oceaninformatics.com>
Date: 7 de setembro de 2011 03h38min45s BRT
To: For openEHR technical discussions <openehr-technical@openehr.org>
Cc: openehr clinical <openehr-clinical@openehr.org>
Subject: Re: openEHR Transition Announcement (about regional/national openehr organizations)
Reply-To: For openEHR clinical discussions <openehr-clinical@openehr.org>
Thanks Pablo,
I am aware of the very excellent work being done around the world,
often with insufficient publicity and I too think that regional
support should be added to the White Paper but we should discuss
further what sort of top-down assistance might be realistic to achieve
in the short-term.
We all hope that the suggested changes lead to more resources becoming
available but it would be difficult to assume that this will be the
case, given that membership and access to Foundation materials will
continue to be free of charge.
So, my question back, is
"What sort of support would you like to see, given that significant
central resourcing is not likely in the short term?"
I know Thomas has some ideas about ramping up the software repository
and I am very keen on the idea of a non-CKM archetype/ template
'nursery' (more elsewhere) and I could imagine that one or both might
be useful at regional level.
Would it be sufficient for the Foundation to give 'official status' to
regional affiliates e.g. openEHR Japan, or are there other practical
suggestions as to how best to support regional affiliates?
Ian
Dr Ian McNicoll
office +44 (0)1536 414 994
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll@oceaninformatics.com
Clinical Modelling Consultant, Ocean Informatics, UK
openEHR Clinical Knowledge Editor www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
BCS Primary Health Care www.phcsg.org
On 6 September 2011 16:38, pablo pazos <pazospablo@hotmail.com> wrote:Hi,Not so long ago we have discussed about a governance and organization modelto the openEHR community, and we have talked about regional/national openEHRcommunities(http://www.openehr.org/wiki/display/oecom/Foundation+Organisational+Structure).I can't find this mentioned in the whitepaper.I think if we want to have a global impact on the ehr scene, we need tosupport those communities also, and define ways to coordinate the work ofthe community as a whole.What do you think?--Kind regards,Ing. Pablo Pazos GutiérrezLinkedIn: http://uy.linkedin.com/in/pablopazosgutierrezBlog: http://informatica-medica.blogspot.com/Twitter: http://twitter.com/ppazos________________________________Date: Mon, 5 Sep 2011 02:00:45 +0100From: thomas.beale@oceaninformatics.comTo: openehr-announce@openehr.orgSubject: [openEHR-announce] openEHR Transition AnnouncementDear All,I am writing on behalf of the new Transitional Board of openEHR to share ourplans to take openEHR to a new level of operations; a new structure,business model and governance. Our vision is the creation of a thrivingcommunity that works collaboratively to benefit humanity through efficientand effective electronic health records (EHRs) that support the highestquality health care for the least effort.Until now, the openEHR Foundation has functioned as an owner of intellectualproperty, governed by University College London and Ocean Informatics, withboard members Prof David Ingram (UCL), Prof Dipak Kalra (UCL) and Dr SamHeard (Ocean).With the support of the considerable community of Members and via engagementof a new category of sponsoring organisational Member known as 'Associates'- Companies, Universities and Governments - the Transitional Board proposesa number of changes:The openEHR Foundation becomes an operational non-profit organisation withpaid key staff and resources;The Board (of governance) of the Foundation is extended to up to 10 peoplewith a shift to election by the openEHR Associates;Members who participate are recognised by their peers, may take ondecision-making roles, and have the right to commit changes to the keydevelopment assets of the Foundation.The Members will participate individually and, through qualification by peerrecognition, will control the development within the three Programmes thatare building the key assets:The openEHR specifications of the logical health record and attendantservices as well as the methods for describing the content using archetypes(Detailed Clinical Models) and templates; andThe openEHR archetypes and templates to be used within systems and formessage content between systems to achieve interoperability; andThe openEHR software projects, to provide open source development of toolsto support the uptake and use of the specifications and templates.A group of Members will be needed to bootstrap each of these programmes anddetermine the working arrangements that are suitable to the products thatthey are managing at the current stage of development.The Associates will determine who governs the Foundation by nominating andvoting on new members of the Board. The Board will appoint key Operationalstaff and will approve the leader of each of the Programmes. The ProgrammeLeaders will be appointed by Qualified Members working in that Programme,subject to Board approval. We believe this will create the right balancebetween the 'ground up' creation of openEHR through participation of Membersand 'top down' governance.The first step is to share with you a white paper providing more detail onthe proposals and to ensure that the Members are reasonably satisfied thatthis is the right direction to head.Some key activities have been proceeding in the background and are reachinga point of maturity. It has taken us some time to gather more clinicalchampions in this endeavour and companies that can use and work with thetools in their early stages of development. It has also taken quite sometime for Thomas Beale to work out how to provide a seamless pathway betweendefinition of archetypes, specialisation of archetypes to ensure developmentscalability, to meet jurisdictional requirements, and templates that allowtailoring for actual use in specific settings. The result is ADL/AOM 1.5. Hehas, as usual, been totally committed to this work and it is probably veryimportant for me to say, it is "no mean feat".There is a lot to do. Most important are:Begin to showcase development teams and software using openEHR successfullyin clinical settings;Finalise ADL/AOM 1.5, including its succinct XML expression, and integrateit into existing and emerging tools;Update the openEHR reference model to version 1.1 bringing our collectiveknowledge to bear on the new features and changes while ensuring backwardcompatibility;Begin an open source software project for tools, web-based if possible, toauthor archetypes, templates and terminology reference sets directlyinteracting with the Clinical Knowledge Manager and equivalent repositoryand review tools; andEstablish a mechanism for Associates to formally endorse archetypes (andpossibly in the longer term templates) for international use.The Board has been changed to manage the transition until we are in aposition to take nominations from Associates. Prof. David Ingram will becomePresident and remain on the Board. Dr Bill Aylward from Moorfield's EyeHospital (the Open Eyes Project) will join Dr Ian McNicoll with his longadvocacy of health care computing (British Computer Society) and Dr JussaraRotzsch who has been involved in establishing openEHR as the Braziliannational EHR model. Professor Dipak Kalra and I will remain and I becomeChair of the Board initially. The new Board will now actively seekAssociates to engage in this important work and to provide secure governanceinto the future.At present many of our key participants are being drawn into nationalprogrammes. Whilst this is encouraging, we need to bring this work, whereappropriate, back to the international community as quickly as possible. Itis clear that governance that is acceptable to these national programs andindustry is a very important step. It is also our belief that standard SDOprocesses are not suitable for our work and we have instead modelled ourfuture on collaborative engineering efforts. Our products must be fit forpurpose, stable and have an update cycle that is in tune with our domain.Free membership for participants and free access to the assets of theFoundation remains a fundamental principle going forward. Our commitment toopen specifications, open software and open clinical models, unrestrictiveto commercial use, remains unchanged.We hope you will join with us enthusiastically in the next phase ofdevelopment of the Foundation and comment freely on the attached paper.There will be many views on what we need to do and how we might best achieveit. The Board is very interested in alternative ways to balance the needs ofindustry and governments with those of the developers and users of thesystem.Let's make the future of eHealth work efficiently for all.Yours sincerely, Sam HeardAcknowledgements: Thank you to David Ingram, Dipak Kalra, Thomas Beale,Martin van der Meer and Tony Shannon for assisting in the planning.openEHR Transition White Paper_______________________________________________ openEHR-announce mailinglist openEHR-announce@openehr.orghttp://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-announce_______________________________________________openEHR-technical mailing listopenEHR-technical@openehr.orghttp://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
_______________________________________________
openEHR-clinical mailing list
openEHR-clinical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
0 comentários:
Postar um comentário