2006 IGT Workshop Workflow Breakout - Revision history

Marianna: /* Four questions to be considered per topic */

2010-11-03T19:32:41Z

Four questions to be considered per topic

Marianna at 19:31, 3 November 2010

2010-11-03T19:31:23Z

Aylward at 19:41, 27 September 2007

2007-09-27T19:41:02Z

Aylward: /* Workflow */

2007-01-22T02:25:33Z

Workflow

Aylward: /* Workflow */

2007-01-22T02:23:48Z

Workflow

Aylward: /* Attendees: */

2007-01-22T01:15:32Z

Attendees:

Andy: Update from Wiki

2006-12-18T13:23:16Z

Update from Wiki

New page

[[IGT:October_2006_IGT_Workshop#Agenda|Back to workshop agenda]]

== Questions to be answered in the report-out session: ==

* Identify 3 main challenges in this area
* Identify 3 specific problems that can be solved by a collaborative effort between academic and industry partners
* Identify a problem that the NCIGT can help address in the next year

== Attendees: ==

== Agenda: ==

=== Scope of discussion: ===

==== Workflow ====

# A small number of workflow templates can capture the majority clinical cases [http://scholar.google.com/scholar?hl=en&lr=&q=paggetti+2001&btnG=Search Paggetti 2001]
# Workflows are effectively modeled as [http://en.wikipedia.org/wiki/State_diagram State Diagrams], [http://en.wikipedia.org/wiki/Petri_nets Petri Nets] and [http://scholar.google.com/scholar?hl=en&lr=&q=ramchandani+1974&btnG=Search Timed Petri Nets][http://scholar.google.com/scholar?hl=en&lr=&q=merlin+farber+1976&btnG=Search [1]]
## Each state has associated with it a finite set of events that invoke transitions to new states
## They provide an easy transition towards software implementation
# Workflows are not system architectures
# [http://en.wikipedia.org/wiki/Workflow_management Workflows] are '''already there''', as a reality of the way humans perform activities
## Acknowledging its existance, when designing software, results in more realistic and safer software

==== Why look at workflow ====

# Improved application design
# Simplified application design
# Produce safer software, better suited for clinical applications
# Basis for testing: inputs/outputs/states
# Encapsulate technologies for research and integration
# Define a language that spans implementation toolkit

==== The Complexity Delusion ====

# At first sigth Workflows appear to be complex
# It is not the workflow analysis the one that creates complexity
# The complexity level is already there in the nature of the process itself
# Workflows reveal the real level of complexity that previously was hidden from view

==== Opening question ====

# What are the current/pending workflow-related projects?
## Goals
## Methods
## Strengths / weaknesses
## Schedule

==== Four questions to be considered per topic ====

# Where is the field
# Other fields using workflows
## Real-Time systems [http://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=5399 [2]]
## Embedded systems [http://www.springerlink.com/content/4x73upy88pr5d8cr/ [3]]
# Where can research have the most impact
# Where is industry / academic partnering needed / beneficial
# What is the timeline for the research (1 yr, 3 yr, 5 yr)

=== Topics: ===

==== What do we want from a workflow specification ====

# File for dynamic load / save (create applications)
# Specialize systems for a particular application (e.g., use method “MI registration with params X” at state “register images”)
# Test systems
## e.g. system should move from state A to state B given event C
## e.g. system '''should not''' move from state K to state M given even D
# Non-programmatic description of a system (“Our system does this…”)
# An API standard for states/transitions for method/device sharing (e.g., wrap IGSTK, wrap Slicer)

==== Workflow granularity ====

# Effect-level (patient) workflow = Guide needle to tumor
# Task-level (physician) workflow = Acquire an ultrasound image of tumor
# Data-level (system) workflow = Record tracker coordinates

==== Source of workflows ====

# OR observations
# Interviews
# Abstraction
# Component-level simulations

==== Level of detail in workflows ====

# Complete
## Logging / play-back specific cases
# Abstract
## Language for describing a system of method and devices
## Language for describing a network of abstract components

==== Primary/secondary/tertiary users of workflow descriptions ====

# Application development
## For FDA approval
## In the clinic
## In research labs
# Testing
## New applications
## Existing applications
## Methods / Devices
# Research
## Developing methods / devices
## Developing new toolkits

==== Role of patient safety ====

# Somethings should '''never''' happen: explicit workflow make possible to forbid some paths
# Error conditions
## Tracker unplugged – vs – track ultrasound probe
# Determinism
## Guarantee each event is handled and transition occurs successfully
# Patient safety
## Vs ease-of-use (new applications)
## Vs ease-of-extension (new states)
## Vs specialization (new components/devices)
## Vs development (infra-structure)

==== Workflow challenges ====

# Recording events in OR [Cleary]: Short lasting, repetitive, rapid, multi-parameter, simultaneous
# Handling/enumerating error conditions
# Deriving common states from multiple recordings
# Deriving common states from different procedures
# Workflow validation
# System testing using workflows
# File formats for workflows (UML2’s Activity Diagrams)
# Managing multiple workflows simultaneously
## Synchronization
## Data passing
# Workflows –vs– C++: Not traditional programming style
# Quantifying physicians time and mental effort
# Accruing error / uncertainty
# Accruing required accuracy
# Accruing risk to the patient / outcome

==== Concepts of Workflow ====

# Storyboarding
## How to illustrate handling error conditions

== References ==

[[Media:IGT_Workflow_Paper_SPIE_Cleary.pdf| Siddoway, et al., "Workflow in Interventional Radiology." SPIE 2006 (PDF)]]

* [[IGT:October_2006_IGT_Workshop|Return to the IGT Workshop page]]
* http://en.wikipedia.org/wiki/Petri_nets
* http://en.wikipedia.org/wiki/Workflow_management

<br />

== Minutes ==

== Summary Report ==

[[Media:Aylward_Workflow_Breakout_Report.ppt|Breakout report presentation]] (Stephen Aylward)

← Older revision		Revision as of 19:41, 27 September 2007
Line 1:		Line 1:
	[[IGT:October_2006_IGT_Workshop#Agenda\|Back to workshop agenda]]		[[IGT:October_2006_IGT_Workshop#Agenda\|Back to workshop agenda]]
		+
		+	== Follow-on tcon ==
		+
		+	* http://wiki.na-mic.org/Wiki/index.php/IGT:_Workflow:_TCon_-_Nov_28%2C_2006

	== Questions to be answered in the report-out session: ==		== Questions to be answered in the report-out session: ==

@@ Line 77: / Line 77: @@
 # Other fields using workflows
 ## [http://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=5399 Real-Time systems]
-## [http://www.springerlink.com/content/4x73upy88pr5d8cr/Embedded_systems Embedded systems]
+## Embedded systems
 # Where can research have the most impact
 # Where is industry / academic partnering needed / beneficial

@@ Line 1: / Line 1: @@
 [[IGT:October_2006_IGT_Workshop#Agenda|Back to workshop agenda]]
@@ Line 39: / Line 40: @@
 # A small number of workflow templates can capture the majority clinical cases
 #* "Analyzing the requirements for modeling IGS systems we concluded that four models is enough to model interaction."
-#** DG Trevisan, J Vanderdonckt, B Macq, C Raftopoulos, "Modeling Interaction for Image-Guided Procedures" SPIE Medical Imaging, 2003
+#** DG Trevisan, J Vanderdonckt, B Macq, C Raftopoulos, "Modeling Interaction for Image-Guided Procedures" SPIE Medical Imaging, 2003. [http://www.isys.ucl.ac.be/bchi/publications/2003/Trevisan-SPIE2003.pdf PDF]
 # Workflows are effectively modeled as [http://en.wikipedia.org/wiki/State_diagram State Diagrams], [http://en.wikipedia.org/wiki/Petri_nets Petri Nets] and [http://scholar.google.com/scholar?hl=en&lr=&q=ramchandani+1974&btnG=Search Timed Petri Nets][http://scholar.google.com/scholar?hl=en&lr=&q=merlin+farber+1976&btnG=Search [1]]
 ## Each state has associated with it a finite set of events that invoke transitions to new states
@@ Line 76: / Line 76: @@
 # Where is the field
 # Other fields using workflows
-## Real-Time systems [http://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=5399 [2]]
+## [http://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=5399 Real-Time systems]
-## Embedded systems [http://www.springerlink.com/content/4x73upy88pr5d8cr/ [3]]
+## [http://www.springerlink.com/content/4x73upy88pr5d8cr/Embedded_systems Embedded systems]
 # Where can research have the most impact
 # Where is industry / academic partnering needed / beneficial
@@ Line 167: / Line 167: @@
 == References ==
-[[Media:IGT_Workflow_Paper_SPIE_Cleary.pdf| Siddoway, et al., "Workflow in Interventional Radiology." SPIE 2006 (PDF)]]
+Siddoway, et al., [[Media:IGT_Workflow_Paper_SPIE_Cleary.pdf| Workflow in Interventional Radiology.]] SPIE 2006.
 * [[IGT:October_2006_IGT_Workshop|Return to the IGT Workshop page]]
-* http://en.wikipedia.org/wiki/Petri_nets
+* [http://en.wikipedia.org/wiki/Petri_nets Petri Net]
-* http://en.wikipedia.org/wiki/Workflow_management
+* [http://en.wikipedia.org/wiki/Workflow_management Workflow Management]
 == Minutes ==

@@ Line 1: / Line 1: @@
- [[IGT:October_2006_IGT_Workshop#Agenda|Back to workshop agenda]]
+[[IGT:October_2006_IGT_Workshop#Agenda|Back to workshop agenda]]
 == Questions to be answered in the report-out session: ==
@@ Line 8: / Line 8: @@
 == Attendees: ==
 == Agenda: ==