Evidence map›Paper›PMID 21477364›Full record

ArticleBMC medical research methodology2011

Implementation of workflow engine technology to deliver basic clinical decision support functionality.

Vojtech Huser, Luke V Rasmussen, Ryan Oberg, Justin B Starren

Abstract read
In one paragraph

Article in BMC medical research methodology, 2011. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 10 papers, 1 of them a synthesis that pooled it.

0numbers the graph read from it
0cells of the map it votes in
10citing papers in PubMed, 1 pooled it
–field-weighted citation impact
1 · What the graph read from it

What it found

Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.

The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.

2 · The registry

The trial behind it

Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.

Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.

3 · Its place in the literature

Who cites it

10 citing papers in PubMed, 1 synthesis or guideline pooled it.

  1. Pooled it
  2. Article
  3. Imaging Informatics: 25 Years of Progress.Yearbook of medical informatics · 2016
    Article
  4. Article
  5. Review
  6. DEWEY: the DICOM-enabled workflow engine system.Journal of digital imaging · 2014
    Article
  7. An adaptable architecture for patient cohort identification from diverse data sources.Journal of the American Medical Informatics Association : JAMIA · 2013
    Article
  8. Article
  9. Article
  10. Article
4 · The record

Corrections and comments

PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.

5 · Who and what money

Authors and funding

4 authors.

Vojtech HuserBiomedical Informatics Research Center, Marshfield Clinic, Marshfield, WI, USA. vojtech.huser@gmail.com
Luke V Rasmussen
Ryan Oberg
Justin B Starren

Funding

INSTITUTIONAL CTSA (UW-MADISON): CLINICAL TRIALSUL1RR025011 · NCRR · UNIVERSITY OF WISCONSIN-MADISON · PI DREZNER, MARC KENNETH · 2007 to 2011
$29.5M
NCRR NIH HHS 1UL1RR025011NCRR NIH HHS UL1 RR025011
6 · The paper itself

Abstract

backgroundWorkflow engine technology represents a new class of software with the ability to graphically model step-based knowledge. We present application of this novel technology to the domain of clinical decision support. Successful implementation of decision support within an electronic health record (EHR) remains an unsolved research challenge. Previous research efforts were mostly based on healthcare-specific representation standards and execution engines and did not reach wide adoption. We focus on two challenges in decision support systems: the ability to test decision logic on retrospective data prior prospective deployment and the challenge of user-friendly representation of clinical logic.

resultsWe present our implementation of a workflow engine technology that addresses the two above-described challenges in delivering clinical decision support. Our system is based on a cross-industry standard of XML (extensible markup language) process definition language (XPDL). The core components of the system are a workflow editor for modeling clinical scenarios and a workflow engine for execution of those scenarios. We demonstrate, with an open-source and publicly available workflow suite, that clinical decision support logic can be executed on retrospective data. The same flowchart-based representation can also function in a prospective mode where the system can be integrated with an EHR system and respond to real-time clinical events. We limit the scope of our implementation to decision support content generation (which can be EHR system vendor independent). We do not focus on supporting complex decision support content delivery mechanisms due to lack of standardization of EHR systems in this area. We present results of our evaluation of the flowchart-based graphical notation as well as architectural evaluation of our implementation using an established evaluation framework for clinical decision support architecture.

conclusionsWe describe an implementation of a free workflow technology software suite (available at http://code.google.com/p/healthflow) and its application in the domain of clinical decision support. Our implementation seamlessly supports clinical logic testing on retrospective data and offers a user-friendly knowledge representation paradigm. With the presented software implementation, we demonstrate that workflow engine technology can provide a decision support platform which evaluates well against an established clinical decision support architecture evaluation framework. Due to cross-industry usage of workflow engine technology, we can expect significant future functionality enhancements that will further improve the technology's capacity to serve as a clinical decision support platform.

Indexed as

Decision Support Systems, ClinicalElectronic Health RecordsSoftware DesignWorkflowComputer SystemsDecision Making, Computer-AssistedHumansLogic

Identifiers

PMID21477364
PMCPMC3079703

What OpenQuestion holds

Textmetadata
LicenceCC BY
Read underepoch 390

Registered trials

None linked

Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.