Re: Decision Support Providers
Hi Chunlan, We share very similar interest then ;-) What I meant really is clinical knowledge in the form of machine-readable formats, more specifically: 1. Orders of medication, lab/imaging investigation requests in the form of openEHR archetypes/templates; 2. Decision support rules in the form of formal rule language; 3. Process definitions in the form of workflow language for coordinating guideline steps 4. Queries for triggering CDS events and process steps in the form of AQL 5. Terminology/ontology resources for necessary reasoning in the background knowledge Now we can in fact express these artifacts in the form of formal standards or publicly available specifications backed up by open source software implementations. Regarding your question on guidelines, you can probably find some input from my previous posts. Cheers, Rong On 30 June 2010 07:51, Chunlan Ma <chunlan.ma@oceaninformatics.com> wrote: > Hi Rong, > > Thanks for your comments. I've been following this thread for my > personal > interest. Briefly a CDS links clinical data (such as clinical > observations) > with clinical knowledge (such as guidelines or rules) to assist health > professionals in decision makings. > > You indicated that you are in favour of developing CDS content based > on > standardised EHR models ... Can you please clarify what CDS content > means? > Is it the clinical data, or clinical knowledge, or both? > > What're your comments about the approach of using archetypes & > templates to > represent clinical guidelines and rules? Did you experience many > issues with > this approach? > > Cheers, > Chunlan _______________________________________________ openEHR-clinical mailing list openEHR-clinical@openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical