# Presentation: 685250

## XIP: The eXtensible Imaging Platform Development Program

**Fred Prior, Ph.D.**
**Mallinckrodt Institute of Radiology**
**Washington University in St. Louis**

## caBIG will facilitate sharing of infrastructure, applications, and data

- caBIG will facilitate sharing of infrastructure, applications, and data

**Cancer Biomedical Informatics Grid**

## In Vivo Imaging Workspace

**Goals of the workspace**
- Advance imaging informatics on multiple fronts
- Model methods to extract meaning from in vivo imaging data and establish databases to test and validate these methods
- Create, optimize, and validate software tools
- E.g. eXtensible Imaging Platform

## 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. 

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 allows the research community to create custom image analysis and viewing applications for clinical trials using both caGRID and DICOM.

**XIP **is an **open source** environment for rapidly developing medical imaging applications from an extensible set of modular elements.
- 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 **allows the research community to create custom image analysis and viewing applications for clinical trials** using both caGRID and DICOM.**

## XIP Application

**XIP Application**

**(Can be replaced with any  DICOM WG23-compatible Host)**

- XIP Host Adapter

- XIP Modules
- Host Independent

**WG23**

**XIP Host**

**WG23**

**WG23**

- Web-based Application

- Medical Imaging Workstation

- Standalone Application

- Distribute

- Distribute

- DICOM, HL7, & otherservices per IHE

**caGRID Services via****Imaging Middleware**

- XIP Application Builder

- XIP Class Library
- Auto Conversion Tool

- Host-Specific Plug-in Libs

**WG23**

- Distribute

**ITK**

**VTK**

**XIP LIB**

**. . .**

## Open Inventor®

- Open Inventor®  is an object-oriented 3D toolkit for interactive graphics programming.
- It presents a programming model based on the Model/View/Controller design pattern and the concept of Pipelines.
- Open Inventor® modules represent** ****Engines, Nodes**** and ****Manipulators**
_**Engines**_** **enable the creation of processing **pipelines**
_**Nodes**_ support the concept of **scene graphs**, which are hierarchical structures of objects describing what needs to be visualized in 2D/3D
_**Manipulators**_ handle input devices, measurements and coordinate transforms in response to **user interaction**

## Sets of Open Inventor ® objects that XIP applications may utilize

**Sets of Open Inventor **®** objects that XIP applications may utilize**
- Stock Open Inventor**®** objects for 3D graphics, modeling, UI, etc.
- Standard XIP objects for retrieving data from, and storing data to XIP or DICOM WG-23 Hosts via the DICOM WG-23 interfaces
- XIP objects that extend Open Inventor**®** objects with functions optimized for medical imaging applications
- VTK classes wrapped into Open Inventor**®** objects to support visualization
- ITK classes wrapped into Open Inventor**®** objects to support image processing
- Custom objects supplied by developers to extend XIP
**Many XIP Libraries are host-independent, but if dependent on host services: **
- XIP libraries have internal dynamic ‘adapter’ libraries to allow for easy switching between XIP hosts or platforms (i.e. simply swap the dynamic library)
- The XIP Application always sees the same Open Inventor**®** objects regardless of host
**XIP libraries may be auto-generated from existing class libraries (e.g. ITK, VTK), or may be custom-built from new or existing code**

- Libraries

## Slide 8

## Interconnected Open Inventor ® engines, nodes, and manipulators from XIP Libraries

**Engines** enable the creation of processing pipelines and animation
**Nodes** support the concept of scene graphs, which are hierarchical structures of objects describing what needs to be visualized in 2D/3D
**Manipulators** handle input devices, measurements and coordinate transforms in response to user interaction via a simple event model
**Focused on the processing logic, not the infrastructure or data format**
**Skinnable GUI engine for different look-and-feel on different platforms**

- Applications

## Host

- 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 caGRID interactions and security
- Manages access to DICOM networks, objects, and services
- Maps images and associated meta-data between
- 	their native form and a common form useable by
- 	the XIP application
**Handles workflow issues**
- IHE General Purpose Worklist support
**Supports any application that follows DICOM WG-23 **
**	****Application Hosting Interface Standard**

**DICOM WG23 Plug-in Framework**

-  WG-23 addresses clinical integration and vendor inter-operability by defining standardized “plugs” and “sockets” (APIs)
- caBIG XIP addresses an open-architecture, integrated development environment for rapid prototyping & collaboration based onWG 23 APIs.  It will be a reference implementation of those APIs

***Unix, Mac, PC***

***Internet Server***

***Commercial Vendor #2***

- ...

***Commercial Vendor #1***

****** ****Clinical ******

****** ****Prototype & Collaboration ******

***XIP developed Application***

-  Standard API

**Notes:**
For those of you that were not able to attend Fred Prior’s talk, I’ll first desc

## XIP Architecture

**XIP Architecture**

**XIP Host**

## Slide 13

## In Summary...

- The eXtensible Imaging Platform will make it easier and less expensive to access specific post-processing applications at multiple sites, simplifying clinical trials.
- Imaging applications developed by research groups will more easily be accessible within the clinical operating environment, simplifying workflows and speeding data processing and analysis.
- Once validated, the software should be readily transitioned into products through streamlined FDA approval processes due to the re-use of tested libraries and open source development processes that have already been used in approved devices.

## XIP Development Team

** ****Washington University in St. Louis**
- Lawrence Tarbox
- Jaroslaw Krych
- David Maffitt
- Paul Koppel
- Steve Moore
- Fred Prior
- Others
** ****Other Consultants**
- Kitware
- Siteman Cancer Center
** ****Related Projects**
- IVI Middleware
- AIM
- Open InventorTM
- ITK & VTK
- NCIA
- MIRC

** ****Siemens Corporate Research**
- Gianluca Paladini
- Thomas Moeller
- Daphne Yu
- Klaus Engel
- Ravi Kumar
- John Pearson
- Others
** ****NCI caBIG IVI**
- Eliot Siegel
- Vikram Purohit
- Others
** ****Booz Allen Hamilton**
- Paul Mulhern
- Others