Skip to Navigation | Skip to Content

openEHR-Implementers mailing list archives

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: Medinfo 2010




Message: 2
Date: Wed, 12 Aug 2009 15:17:03 +0100
From: Ian McNicoll <Ian.McNicoll@oceaninformatics.com>
Subject: Re: Medinfo 2010
To: For openEHR implementation discussions
       <openehr-implementers@openehr.org>
Message-ID:
       <d52774ce0908120717j574224d8kf1074d32c2a54fcd@mail.gmail.com">d52774ce0908120717j574224d8kf1074d32c2a54fcd@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

This project sounds very exciting but I wonder if the use of an EHR Extract
will fire up sufficient clinical/managerial interest.

As an alternative how about considering a patient's path from an Emergency
visit, looking up/importing data from a GP-held summary (or even a Google
Health summary), Tony's Soap stuff then eventual discharge letter. Being
able to do this seamlessly across different 'vendors' and platforms would be
compelling, especially if the contents could be changed at the whim of one
of us annoying clinicians e.g Revise an archetype by adding some new
elements, rerun the pathway and see how each individual system should be
able to handle the change, including those who do not have access to the
newer archetype.

This could make use of the CKM 'top 20 archetypes' work' (and anything
else), which will be at the heart of almost all clinical communications -
ADR, medication, Diagnosi, lab tests etc.

Or is this too adventurous...

Ian

Dr Ian McNicoll
office / fax  +44(0)141 560 4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian@mcmi.co.uk

Clinical Analyst  Ocean Informatics ian.mcnicoll@oceaninformatics.com
BCS Primary Health Care Specialist Group www.phcsg.org


 
I agree that extract is a dull word.

The problem we still seem to be missing key pieces.  The xml e.g.

http://www.openehr.org/svn/ref_impl_java/SANDBOX/ehr-bank/src/res/xml/blood-glucose-sample.xml

does not seem to have any patient identifiers.  Without the basic functionality of being able to even match a patient its hard to get the data into the system in the first place.  I have several questions around the archetype identifiers when we get there.

I think we need a simple step by step test case which walks through the process and identifies what data is being sent where.  The actual protocols are not important but the content and how patients, visits and clinical content is *matched* is important.


--
Gregory Caulton
Principal at PatientOS Inc.
personal email: caultonpos@gmail.com
http://www.patientos.com
corporate: (888)-NBR-1EMR || fax  857.241.3022