Lawrence Tarbox, Ph.D. Washington University in St. Louis School of Medicine Mallinckrodt Institute of Radiology, Electronic Radiology Lab.

Slides:



Advertisements
Similar presentations
Connecting to Databases. relational databases tables and relations accessed using SQL database -specific functionality –transaction processing commit.
Advertisements

CACORE TOOLS FEATURES. caCORE SDK Features caCORE Workbench Plugin EA/ArgoUML Plug-in development Integrated support of semantic integration in the plugin.
SSRS 2008 Architecture Improvements Scale-out SSRS 2008 Report Engine Scalability Improvements.
Goals Give you a feeling of what Eclipse is.
1 Software & Grid Middleware for Tier 2 Centers Rob Gardner Indiana University DOE/NSF Review of U.S. ATLAS and CMS Computing Projects Brookhaven National.
DICOM and Integrating the Healthcare Enterprise: Five years of cooperation and mutual influence Charles Parisot Chair, NEMA Committee for advancement of.
Network Management Overview IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
A DICOM Import Module for XIP Alex Shnayder Lafayette College Easton, PA Supervisor: Dr. Dave Channin We gratefully acknowledge the support of: Pat Mongkolwat,
Integrating XIP into a FOSS clinical workstation Final Presentation Max Meltser Advisors: David Channin, Pat Mongkolwatt With much help from Vlad Kleper.
Presented by IBM developer Works ibm.com/developerworks/ 2006 January – April © 2006 IBM Corporation. Making the most of Creating Eclipse plug-ins.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 2 – Components.
Distributed Systems: Client/Server Computing
Post Acquisition Workflow (PAWF) Kevin O’Donnell Toshiba Medical Research Institute.
September, 2005What IHE Delivers 1 Portable Data for Imaging - PDI IHE Vendors Workshop 2006 IHE IT Infrastructure Education Robert Horn, Agfa Healthcare.
The cancer Biomedical Informatics Grid™ (caBIG™): In Vivo Imaging Workspace Projects Fred Prior, Ph.D. Mallinckrodt Institute of Radiology Washington University.
Application Hosting Lawrence Tarbox, Ph.D. Chair WG 23 Mallinckrodt Institute of Radiology Washington University in St. Louis School of Medicine.
Annual SERC Research Review - Student Presentation, October 5-6, Extending Model Based System Engineering to Utilize 3D Virtual Environments Peter.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
Submitted by: Madeeha Khalid Sana Nisar Ambreen Tabassum.
Lawrence Tarbox, Ph.D. Washington University in St. Louis School of Medicine Mallinckrodt Institute of Radiology, Electronic Radiology Lab 12/1/
By Mihir Joshi Nikhil Dixit Limaye Pallavi Bhide Payal Godse.
S New Security Developments in DICOM Lawrence Tarbox, Ph.D Chair, DICOM WG 14 (Security) Siemens Corporate Research.
 Cloud computing  Workflow  Workflow lifecycle  Workflow design  Workflow tools : xcp, eucalyptus, open nebula.
XIP: The eXtensible Imaging Platform Development Program Fred Prior, Ph.D. Mallinckrodt Institute of Radiology Washington University in St. Louis.
Imaging Workspace An Overview and Roadmap Eliot L. Siegel, MD Imaging Workspace Lead SME January 23, 2008.
Jaeki Song ISQS6337 JAVA Lecture 16 Other Issues in Java.
THE GITB TESTING FRAMEWORK Jacques Durand, Fujitsu America | December 1, 2011 GITB |
Digital Object Architecture
XIP™ – the eXtensible Imaging Platform A rapid application development and deployment platform Lawrence Tarbox, Ph.D. September, 2010.
Lawrence Tarbox, Chair WG-23 Status Report – SPIE 2008.
©Ian Sommerville 2000 Software Engineering, 6th edition. Slide 1 Component-based development l Building software from reusable components l Objectives.
DICOM Security Lawrence Tarbox, Ph.D. Chair, WG 14 Mallinckrodt Institute of Radiology Washington University in St. Louis School of Medicine.
K. Harrison CERN, 20th April 2004 AJDL interface and LCG submission - Overview of AJDL - Using AJDL from Python - LCG submission.
Access Across Time: How the NAA Preserves Digital Records Andrew Wilson Assistant Director, Preservation.
The National Biomedical Imaging Archive (NBIA) In Action: An Introduction for Users A Tool Demonstration from caBIG® Presented by: Eliot Siegel, MD Maryland.
IPlant Collaborative Tools and Services Workshop iPlant Collaborative Tools and Services Workshop Collaborating with iPlant.
The Future of the iPlant Cyberinfrastructure: Coming Attractions.
February 8, 2005IHE Europe Educational Event 1 Integrating the Healthcare Enterprise Basic Security Robert Horn Agfa Healthcare.
1 Geospatial and Business Intelligence Jean-Sébastien Turcotte Executive VP San Francisco - April 2007 Streamlining web mapping applications.
NOVA Networked Object-based EnVironment for Analysis P. Nevski, A. Vaniachine, T. Wenaus NOVA is a project to develop distributed object oriented physics.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Portable Data for Imaging - PDI Robert Horn Agfa Healthcare.
NA-MIC National Alliance for Medical Image Computing UCSD: Engineering Core 2 Portal and Grid Infrastructure.
Copyright © 2008 Siemens Corporate Research – All rights reserved1/12 eXtensible Imaging Platform (Xip) Sylvain Jaume – Sep 2008 Siemens Corporate Research.
© 2007 IBM Corporation SOA on your terms and our expertise Software WebSphere Process Server and Portal Integration Overview.
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
GAAIN Virtual Appliances: Virtual Machine Technology for Scientific Data Analysis Arihant Patawari USC Stevens Neuroimaging and Informatics Institute July.
Clinical Collaboration Platform Overview ST Electronics (Training & Simulation Systems) 8 September 2009 Research Enablers  Consulting  Open Standards.
Enterprise Solutions Chapter 10 – Enterprise Content Management.
Medical Imaging Lection 3.
XIP™/AVT Project Plans 2012 A report to the caBIG® In-Vivo Imaging Workspace Lawrence Tarbox, Ph.D.. December 2011.
Application Hosting Lawrence Tarbox, Ph.D. Mallinckrodt Institute of Radiology Washington University in St. Louis School of Medicine.
DICOM Security Andrei Leontiev, Dynamic Imaging Presentation prepared by: Lawrence Tarbox, Ph.D. Chair, WG 14 Mallinckrodt Institute of Radiology Washington.
March 2004 At A Glance The AutoFDS provides a web- based interface to acquire, generate, and distribute products, using the GMSEC Reference Architecture.
Integrating the Healthcare Enterprise The IHE Process: Developing Standards-based Solutions Kevin O’Donnell Co-chair, IHE Radiology Planning Committee.
TTCN-3 Testing and Test Control Notation Version 3.
Imaging Workspace An Overview and Roadmap Eliot L. Siegel, MD Imaging Workspace Lead SME January 23, 2008.
V7 Foundation Series Vignette Education Services.
NA-MIC National Alliance for Medical Image Computing Core 1b – Engineering Data Management Daniel Marcus Washington University.
ISC321 Database Systems I Chapter 2: Overview of Database Languages and Architectures Fall 2015 Dr. Abdullah Almutairi.
ECLIPSE RICH CLIENT PLATFORM Part 1 Introduction.
Business System Development
The Components of Information Systems
Tools and Services Workshop Overview of Atmosphere
The Client/Server Database Environment
Fred Prior, Ph.D. Mallinckrodt Institute of Radiology
The Components of Information Systems
Analytic Workflow: From Images to Reports
Lawrence Tarbox, Ph. D. Washington University in St
Information System Building Blocks
Presentation transcript:

Lawrence Tarbox, Ph.D. Washington University in St. Louis School of Medicine Mallinckrodt Institute of Radiology, Electronic Radiology Lab

Provocative Statement DICOM WG-23 hopes to fundamentally change the way the medical imaging world thinks in regards to the distribution and deployment of medical imaging applications.

Status Quo  Medical imaging workstations generally are closed systems.  There is no common, standardized method for adding new functionality to a medical workstation.  The key stakeholders who wish to see new functionality added often are not the workstation provider.  New ‘cool’ tools often require adding entire workstations to a site’s infrastructure.

From the SIIM 2007 Workflow Demonstrations  Cardio Workflow – Dr. Anwer Quershi “… going back and forth to various workstations and the use of different equipment is disruptive and slows treatment …”  Nuclear Workflow – Dr. Eliot Siegel “... This case illustrates the disruptions that can be introduced due to multiple systems and the need to go back and forth....”

A Brave New World? Separate the provision of infrastructure from the application.  Infrastructure providers concentrate on the movement and storage of data and results, and on workflow management.  Application providers concentrate on the processing and analysis of that data, providing results back to the infrastructure. Minimize the ‘reinvention of the wheel’.

Proposed Solution  Create a mechanism where applications written by one party could be launched and run on systems created by multiple other parties.  Allow launched applications to efficiently access images and other resources controlled by the hosting system.  Provide a framework for exchanging information about those applications.  Support both research and clinical environments.

Typical Plug-in Concept … A E BCD F

DICOM WG-23 Goal Portable applications that ‘ plug into ’ any host that implements the standardized ‘ socket ’ Syngo Cedara caBIG Advantage Agfa any WG23 Host

Idealized Goals A Standardized API that is:  Easy to learn and use  Language independent  Platform independent  Based on publicly available technology  Extensible  Secure

Reality Check “Life is a compromise”  Language and platform independence often translates into reduced performance.  Choice of development environment often restricts portability. The real goal is to come as close to the ideal as practical, and minimize the impact where we fall short. Take one step at a time.

Suggested Staging  Stage one – Access to DICOM Datasets and Results Recording  Stage Two – Access to Non-Interactive Application Services (e.g. print, archive)  Stage Three – Access to Interactive Application Services (e.g. GUI, ‘skins’, rendering)  Stage Four – Standard Workflow Descriptions, and Interactions Between Hosted Software

Targets for Stage One  Basic Launch and Control of a Hosted Application  Load, Unload, Start, Abort  Simple Interchange of Data Between a Hosting System and Hosted Applications  File-based data exchange for existing applications  Model-based data exchange for new applications  Manual Configuration  Java and.net technology bindings

Model-Based Data Exchange Data Objects Conversion Bulk Data (e.g. voxels) Abstract Data Subset Full Native Data

Abstract vs. Native Models  Abstract Models  Includes data common to multiple formats (e.g. DICOM, Analyze)  Application need not know the format of the native data  Does include references to the native data from which the abstract model was derived  Native Models  Gives full access to all information available in the native data  Allows an application to just access those parts of the native data that are of interest  Bulk Data Access  File name (URI) plus offset (for performance)

Pushing for Adoption  Standardization being done via DICOM with participation from both medical imaging vendors and users  Open-source, commercial friendly reference implementation being created  XIP – the eXtensible Imaging Platform  WG-23 participants (vendors and the XIP developers) exchange test implementations to insure interoperability

WG23 / XIP Relationship WG-23 addresses clinical integration and vendor inter-operability by defining standardized “plugs” and “sockets” (APIs) WG-23 addresses clinical integration and vendor inter-operability by defining standardized “plugs” and “sockets” (APIs) caBIG XIP addresses an open- architecture, open-source, integrated environment for rapid application development based on WG 23 APIs caBIG XIP addresses an open- architecture, open-source, integrated environment for rapid application development based on WG 23 APIs Unix, Mac, PCInternet ServerCommercial Vendor #2 … Commercial Vendor #1  Clinical   Prototype & Collaboration  XIP developed Application Standard API

 The eXtensible Imaging Platform (XIP™) is the image analysis and visualization tool for caBIG.  XIP is an open source environment for rapidly developing medical imaging applications from an extensible set of modular elements.  XIP may be used by vendors to prototype or develop new applications.  Imaging applications developed by research groups will be accessible within the clinical operating environment, using a new DICOM Plug-in interface first implemented in XIP.  XIP serves as a reference implementation of the DICOM WG-23 Application Hosting interfaces. What is the ?

Major Parts of the  XIP Reference Host  XIP Libraries  XIP Reference Applications  XIP Development Tools The top 3 combine to form an XIP Workstation

XIP Application (Can be replaced with any DICOM WG23- compatible Host) XIP Host Adapter XIP Modules Host Independent WG 23 XIP Host WG 23 Web-based Application Medical Imaging Workstation Standalone Application Distribute DICOM, HL7, & other services per IHE caGRID Services via Imaging Middleware XIP Application Builder XIP Class Library Auto Conversion Tool Host-Specific Plug-in Libs WG 23 Distribute ITKVTK XIP LIB... XIP Development Process

An Application Developer may use the XIP Builder tool from Siemens Corporate Research to create the app’s scene graph and processing pipelines from XIP Libraries

The XIP Builder tool can be used to test and debug the scene graph

Application Developer controls the scene graph by creating a GUI program (e.g. via Java Swing)

Provides the infrastructure in which XIP or DICOM WG-23 Applications run Authenticates user Manages installation, launching, and termination of XIP Applications Provides data and services to XIP Applications Accepts status information and results back from XIP Applications Deals with auditing and controls access to services and data Isolates the XIP application from the nature of databases, archives, networks, and possibly image data formats Manages access to DICOM networks, objects, and services Creates Abstract Models from input data Handles workflow issues IHE General Purpose Worklist support Supports any application that follows the DICOM WG-23 Application Hosting Interface Standard

Summary  XIP provides the ability to create rapidly create applications customized to specific tasks.  The DICOM WG-23 Application Hosting interfaces allow those applications to run on any workstation that supports the standard interfaces  XIP includes a reference host implementation  Other vendors may eventually host applications  XIP with DICOM WG-23 represent new paradigm for writing and distributing medical imaging applications