Archive for the ‘RetroGuide’ Category

RG progress update

June 25, 2009

The summary report has now the flowchart and links to xpdl files.

Also the complexity of our flowcharts is growing.

scr 2009-06-25, 10_29_40

RetroGuide and other DSS projects

June 18, 2009

There is a good article about a DSS engine: (SAGE)

P. Ram, D. Berg, S. Tu, G. Mansfield, Q. Ye, R. Abarbanel, and N. Beard, “Executing Clinical Practice Guidelines Using the SAGE Execution Engine,” Medinfo, vol. 2004, pp. 251-5, 2004

RetroGuide can model DSS logic and execute it retrospectively(with some contrains) and prospectively.

For example Ram’s example here

scr 2009-06-18, 11_55_32

would looke like this in XPDL (TIBCO – for colors):

scr 2009-06-18, 11_54_39

SAGE’s decision maps can be similarly represented as subflows. Rule-in and Rule-out contructs would require additional flowchart logic, but it could be generally done.

RetroGuide installation manual posted on SourceForge

April 7, 2009

Basic steps involved in making RetroGuide run at given institution is now posted on SourceForge


Representing clinical processes in XML process definition language (XPDL)

April 7, 2009

Abstract of our talk at spring AMIA 2009 conference:

Representing clinical processes in XML process definition language (XPDL)


Sharing of decision support logic is important. We have evaluated the ability of XML process definition language to capture clinical processes. Several XPDL-compliant workflow editors were used to model 16 clinical processes. XPDL standard represents a viable cross-industry technological alternative to healthcare specific decision logic representation standards.


Previous reports have noted the general lack of stand-alone, vendor-independent guideline engines [1, 2]. In addition, articles have noted that many guideline formalisms do not explicitly model relevant care participants and do not separate workflow logic from the decision logic. Outside of healthcare, workflow technology (WT) is widely used for modeling and execution of processes. XML Process Definition Language (XPDL) is a robust, 10-year old standard which has been adopted by all major WT vendors and capable of modeling complex workflow patterns and decision logic [3]. A critical question is whether XPDL-compliant workflow products are able to capture clinical processes. As a preliminary assessment of this we have evaluated the ability of several XPDL-based systems to model various healthcare processes.


We modeled 16 clinical processes from the domains of decision support, quality improvement and medical research with three XPDL-compliant workflow editors (Enhydra JaWE, TIBCO Business Studio and Microsoft Visio extended with an XPDL plug-in).  The modeled workflows were then executed retrospectively against a large clinical data warehouse (RetroGuide project [4]). A set of reports generated by our external applications during process execution reflect how well the human-modeled process models match real healthcare EHR data.


Although all editors were able to represent the processes, there were differences among the editors. Despite the existence of the XPDL standard, different workflow editors may differ in graphical presentation of the same workflow pattern. These seemingly minor differences can have major effect on both the human readability and ease of implementation. For example, JaWE workflow editor does not require the use of additional condition nodes to implement exclusive choice pattern [3] and differs from others in implementing workflow transition conditions. 


The XPDL workflow language has been previously shown to be adequate to represent general activity graphs [5]. XPDL directly supports modeling process participants. It can be easily extended with external technologies and employs a user-friendly flowcharting paradigm. This work confirms its ability to capture actual clinical scenarios. Major advantage of use of XPDL for representing clinical processes is its wide use outside of healthcare. History has shown (e.g., in the case of network protocols or databases) that development of interoperable healthcare systems is easier when it appropriates technology developed outside healthcare.




  • 1. Peleg M, Tu SW. Decision support, knowledge representation and management in medicine. Methods of Information in Medicine, vol. 45, pp. 72-80, 2006
  • 2. Peleg M. Chapter 13: Guidelines and Workflow Models, in Clinical Decision Support: The Road Ahead, R. A. Greenes, Ed., 1st ed, 2007
  • 3. Russell AH, van der Aalst WMP, Mulyar N. Workflow Control-Flow Patterns: A Revised View. BPM Center Report BPM-06-22, 2006.
  • 4. Healthcare Workflow, [accessed: Dec 1, 2008]
  • 5. Tu SW, Campbell J, Musen MA. The structure of guideline recommendations: a synthesis. Proc AMIA Symp, pp. 679-83, 2003
  • RetroGuide example: Executing an analytical healthcare workflow process

    January 16, 2009

    Below are some examples execution of a  workflow process against EHR data.

    Only very limited parts shown.

    Diabetes example: (summary report)



    Osteoporosis example: (detailed report)


    RetroGuide v3.3

    January 15, 2009

    Major milestone: Shark engine can call RGEAs (RG External Applications) from within the engine. All interface problems have been solved. The loop of executing a drawing is now fully closed !

    Example: Diabetes QI measure

    December 10, 2008

    Diabetes QI measure


    Main diagram:








    Example: Chronic kidney disease progression

    December 10, 2008

    Most workflow products do not support multiple start point.
    In guideline community it is called multiple entry points into the guideline.
    This is not so far possible directly. You have to consolidate all start points into one and then put arrows (which has impact on clinician-friendliness of the flowchart).


    Same-schema-integration of RetroGuide and i2b2

    November 19, 2008

    i2b2 is a biomedical informatics project around EHR and genomic data. (

    RG schema can be saved into i2b2 form.
    The BLOB in observation table can be used to store XML data from columns of RG schema which i2b2 does not have.

    The demo data do not provide examples of the BLOB structure.

    Workflow editor test drive: JaWE 1.4x

    October 21, 2008

    See example: