Hi Thomas,
I am now back at Duke in a full time capacity. The work within HL7 is
being lead by Ken Kawamoto from Duke, a colleague of mine. Duke has one fo
the best clinical research enterprises in the world - the Duke Clinical
Research Institute and the new Duke Translational Medical Institute, where
the Duke Center for Health Informatics is based. We have asignificant
weffort committed to defining detailed clinical content. I'd say let's
postpone the decision (as ever) for a couple of years and see if we are as
bad as you think.
Actullay, we have an effort similar to Evelyn's and look forward to working
with her.
W. Ed Hammond, Ph.D.
Director, Duke Center for Health Informatics
Thomas Beale
<thomas.beale at oce
aninformatics.com To
> openehr-technical at openehr.org
Sent by: cc
openehr-technical
-bounces at openehr. Subject
org Re: Decision Support Providers
06/26/2010 11:57
AM
Please respond to
For openEHR
technical
discussions
<openehr-technica
l at openehr.org>
On 26/06/2010 13:57, Ian McNicoll wrote:
There is 'Virtual EMR' project going on in HL7 do to exactly this
sort of work i.e a relatively simple interface/ service against which
decision support cab operate consistently -
http://wiki.hl7.org/index.php?title=Virtual_Medical_Record_(vMR)
The big problem they will face, as ever, is defining the detailed
clinical content in a manageable and scalable fashion.
I think the openEHR approach to content definition has definite
advantages.
If you look at the domain model on which the vMR is designed (
http://wiki.hl7.org/index.php?title=Image:HL7vMR_vMR_Domain_Analysis_Model_v2010-03-22.zip
) you will see that it is a very fixed model of clinical concepts. I am
not sure how they expect that queries for changed versions of these
concepts or different concepts be done. The vMR job is actually the kind of
thing openEHR is really designed to do well, with the following elements:
standard reference model
standard way of representing any clinical or other domain concept -
archetypes & templates
standard way of querying the data - AQL, a-path or other
archetype-based approaches
service interface for making fine-grained changes to data (some
specification proposals at
http://www.openehr.org/wiki/display/spec/vEHR+Service+Specification)
GELLO or something similar then has a place 'above the line' for
representing guidelines that need to be executed against the EHR.
- thomas beale
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
