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) > <http://wiki.hl7.org/index.php?title=Virtual_Medical_Record_%28vMR%29> > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20100626/4f09daca/attachment.html>
