1 / 14

- Application Hosting and Data Interchange Standardization for Medical Workstations -

This document outlines a standardized API for exchanging data between applications, focusing on hosting applications launching hosted ones. It describes data inputs and outputs using DICOM semantics, meta-data for application description, application types, expected input/output data, and resources needed. It also touches on plug-in concepts, driver requirements for molecular imaging, potential workflows, deployment strategies, and various use cases for post-processing and analysis in medical imaging. The document suggests staging for access to DICOM datasets, non-interactive & interactive application services, and standard workflow descriptions. It invites participation in creating this new standard. -

danielfreeman
Download Presentation

- Application Hosting and Data Interchange Standardization for Medical Workstations -

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. Application Hosting Lawrence Tarbox, Ph.D. Mallinckrodt Institute of Radiology Washington University in St. Louis School of Medicine

  2. Targets • Standardized API for Interchanging Data Between Two Applications • Hosting Application launches a Hosted Application • Data inputs and outputs described using DICOM Semantics • Meta-data to Describe an Application • Type of application • Expected input data • Output data generated • Resources needed by the application • Version, license restrictions, etc.

  3. … A B C D E F Typical Plug-in Concept

  4. A A A A A Extended Plug-in Concept … C B D E

  5. Initial Driver – Molecular Imaging • A ‘bright dot’ in the image is not sufficient • Ideal is a quantitative number, with normal ranges derived from population, as now done in lab analysis • Newer agents will require more sophisticated analysis: • Agent uptake/decay rates • Pre/post comparisons • Comparisons with surrounding tissue • Calibration • … • Hundreds of new agents anticipated

  6. Potential Workflow

  7. Cached Apps Translated to Native Code forThis Workstation Workstation Request ID of latest version, based on agent ID, etc. If app not cached, transmit Latest Version Application Server Apps in Portable Intermediate Language Possible Deployment Strategy

  8. Other Use Cases • SOP Class Specific Post Processing • Screening Plug-Ins • Customized Reporting and Display • Print Composing • Mammography Image Storage • Analysis of Image Data in Repositories • Multi-Site Collaborative Research

  9. Custom Research/University Prototype OEM Classes(e.g. watsyn™, IDL) Custom Classes Prototype Plug-In Development Environment API (Plug) API (Socket) Hosting Application (e.g. Medical Workstation) Research Support

  10. API (Plug) API (Socket) Hosting Application (e.g. Medical Workstation) Commercialization Hosted Application (Plug-in)

  11. Development Scenarios Commercial Post-Processing IndustryStandardPlug-in Researchers and UniversityCollaborators Plug-inDevelopmentPlatform PrototypePlug-In Vendor Internal Vendor Specific Applications Vendor Specific Development Platform Base Services and Libraries

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

  13. Work Cycle • Define Use Cases • Derive Requirements • Review available technology • Create draft for public comment • Freeze for trial use • Revise after feedback from implementers • Ballot

  14. Volunteers Solicited WG 23 welcomes your input. We would be even happier with your assistance in creating this new standard. • Join the mailing list • Join us Friday for our meeting (Salon Terrace I) • Join us at future meetings

More Related