This is where you lobby your government to actually put some funds where it would help ;-)
Dr Lavanian wrote: > Jesus, > You have hit the nail on the head. What one needs is a solution. > Something, as follows, is what most of us are looking for: > > 1. Download the exe, zip or rar file > 2. unRAR or unzip and execute it > 3. App runs and opens a help file. > 4. Help file takes you thru the steps of set up users and permissions > 5. Set up a few users load some patient data and get productive > > Much later.... > > 6. Take time out to read through the tutorials to tinker with the > program to write clinical pathways, modify programming logic and the UI. > > Now that is what I would love. > > With warm regards, > > Dr D Lavanian > MBBS,MD > Certified HL7 Specialist > Member- American Medical Informatics Association > Member- HIMSS > Senior Consultant and Domain Expert - Healthcare Informatics and > TeleHealth > Former Vice President - Healthcare Products, Bilcare Ltd > Former Vice President - Software Division, AxSys Healthtech Ltd > Former Co-convener Sub committee on Standards , Governmental Task > force for Telemedicine > Former Vice President - Telemedicine (Technical), Apollo Hospitals Group > Former Deputy Director Medical Services, Indian Air Force > Mobile: +91-9970921266 > > ----- Original Message ----- > *From:* Jesus Bisbal <mailto:jesus.bisbal at upf.edu> > *To:* For openEHR technical discussions > <mailto:openehr-technical at openehr.org> > *Sent:* Monday, February 02, 2009 2:44 PM > *Subject:* Re: Wisdom of the Crowds > > Dear Tim, > Following on Heathers email, I only wanted to stress the > importance of bullet number 1: "after creating archetypes, now what?" > But I fear that my "now what?" is rather different. > I may not be completely up-to-speed, but I would say that the > software released in openEHR, to date, does not allow to manage > actual clinical data which adheres to these hundreds of archetypes > available in the repository. I mean making persistent clinical > data, which adheres to those archetypes, through the openEHR > implementation. The persistent layer does not exist yet, or am I > mistaken? > A few months ago I was working on the java implementation of > openEHR, and I exchanged a few emails with Rong. > For people to be able to test and be interested in using > openEHR, or another "two-level modeling" paradigm implementation > for that matter, they need to be able to see it, and without the > persistence layer, they can not see something actually somewhat > usable (I'm sure it?s very _useful_, it?s just not _usable_ right > now). > A very simple "hello world" example, showing the whole life > cycle of a very, very simple EHR is essential, I believe. If it > has been created over that last few months and I missed, please > correct me. > Best regards, > > Jes?s Bisbal > > ------------------------------------------------------------------------ > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > -- *Thomas Beale Chief Technology Officer, Ocean Informatics <http://www.oceaninformatics.com/>* Chair Architectural Review Board, /open/EHR Foundation <http://www.openehr.org/> Honorary Research Fellow, University College London <http://www.chime.ucl.ac.uk/> * *
