I noticed with interest that one of the older Service Model documents (2003)
mentions an interface between the Prodigy DSS and the OpenEHR architecture.
The section was blank.
Is there any other pertinent information as I am about to start an MSc
dissertation looking at exactly this piece of work?
The interaction between openEHR and decision support has been a major design requirement from the mid-1990s. We have used Prodigy as the basis for decisions as it was the most comprehensive at the time.
I am interested in the VirtualEHR offered by the openEHR kernel being able to plug-in the decision support modules that the clinician wants to use. You will understand that the kernel is able to query and write to the EHR, and will throw events when archetypes are loaded (the clinician is about to record something) and when they are populated IN MEMORY.
This is an extraordinary opportunity for standardisation of decision support in applications. I would be interested in working with others on this approach.
The first decision would be to decide how the plug-in might work - within Ocean we use .Net and there are provider patterns that make this relatively straightforward. The open source group are looking at Eclipse for the Java code and I think that this design requirement is the best reason to have the Kernel written in Eclipse.
This is really good news. There is lot of interest now in using CDSS to ensure prescribing safety. In fact, list of safety functionality is being compiled at the request of CfH. They can be converted to ‘safety functions’ and used as constraints in openEHR archetypes for reuse. One issue is the quality of data as inputs to concrete rules but a separate ‘DS engine’ can perhaps handle it. I noted with interest openEHR kernel as a plug-in to the DS modules. I like the idea of Eclipse plug-in. Being open source lot of people can experiment and come up with good ideas.
For your information.
Slowly I’m preparing an European project for the 7th Framework program around the topic: the EHR.
Clinical decision support and a common open source EHR-engine is part of it.
Eurorec (the European Institute for the Health Record) might become the main developer and submitter.
Lets generate a set of research questions that we can write into the project proposal.