1 / 7

Workflow

Workflow. Outline. Scope Identify current projects How can NCIGT help Topics in workflow. Challenge #1. Reference workflows (Models) Include clinicians in the process Use workflow for communication with clinicians Storyboard Recording workflow improved clinician performance

della
Download Presentation

Workflow

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Workflow

  2. Outline • Scope • Identify current projects • How can NCIGT help • Topics in workflow

  3. Challenge #1 • Reference workflows (Models) • Include clinicians in the process • Use workflow for communication with clinicians • Storyboard • Recording workflow improved clinician performance • Generating workflows • Collection tools under development (Lemke) • Data from Stealthlink directly • Data from interviews • Identify common workflows • Choose a standard language • “Workflow management system” • Basis for teaching using new technology

  4. Challenge #2 • Adapting workflows (Models) • Specialize for site, physician, physician experience, patient • Workflows should be very specific to balance flexibility with patient safety • Limits creativity/problems in the OR? • Dynamic programming?

  5. Challenge #3 • Workflow for validation and comparison • Workflows carry accuracy and time (outcome) predictions • Workflows validated in the OR • Workflows as a foundation for comparison of systems • Compare workflows • Time and accuracy

  6. Challenge #4 • Implementing workflows (Execution) • Execution model is GUI independent • Bridge IGTK, Slicer, and VolView • C++/QT/FLTK are ineffective for workflow-based programming • Burden on developer • Different models • Lemke • Service oriented architecture

  7. Challenge #5 • Data Workflows • No effective solution to process a large number of datasets • Loni • SIMULINK • Kepler / Ptolomy • Batchmake

More Related