Revision as of 21:54, 12 October 2017 edit Biogeographist (talk \| contribs) Extended confirmed users 15,955 edits capitalization per MOS:CAPS; removed red links: WP:WTAF; removed links from 'See also' section that are already in article body, per WP:NOTSEEALSO; removed unclear phrase ← Previous edit		Revision as of 04:37, 1 April 2018 edit undo JCW-CleanerBot (talk \| contribs) Bots 137,122 edits m →Use of third party workflow engine as a guideline execution engine: task, replaced: BMC Med Res Methodol. → BMC Med Res Methodol using AWB Next edit →
Line 21: == Use of third party workflow engine as a guideline execution engine == Some commercial [[electronic health record]] systems use a [[workflow engine]] to execute clinical guidelines. RetroGuide<ref name=eval>{{Cite journal \| last1 = Huser \| first1 = V. \| last2 = Narus \| first2 = S. P. \| last3 = Rocha \| first3 = R. A. \| doi = 10.1016/j.jbi.2009.06.001 \| title = Evaluation of a flowchart-based EHR query system: A case study of RetroGuide \| journal = Journal of Biomedical Informatics \| volume = 43 \| issue = 1 \| pages = 41–50 \| year = 2010 \| pmid = 19560553 \| pmc =2840619}}</ref> and HealthFlow<ref name=hf2010>{{citation\|pmc=3079703\|title=Implementation of workflow engine technology to deliver basic clinical decision support functionality\|journal=BMC Med Res Methodol.\|year=2011\|volume= 11\|page= 43\|doi=10.1186/1471-2288-11-43\|pmid=21477364\|vauthors=Huser V, Rasmussen LV, Oberg R, Starren JB}}</ref> are examples of such an approach. == See also ==

Guideline execution engine: Difference between revisions