Difference between revisions of "Portable Hosted Applications in Radiology"

Latest revision as of 15:24, 20 September 2010

1. Proposed Workitem: Portable Hosted Applications in Radiology

Proposal Editor: Chris Lindop
Editor: An Applications Development Engineer
Date: N/A (Wiki keeps history)
Version: N/A (Wiki keeps history)
Domain: Radiology

2. The Problem

In many Radiology environments today, there is a need to extend the functional capability of an imaging platform with capabilities provided by a seperate application. Many systems today provide hosting with proprietary API solutions. This requires an application developer to adapt their platform to each of the propriatry APIs developed by each of the hosting platform vendors. In many cases portability is inhibited by these propriatry methods.

3. Key Use Case

Post-processing clinical applications are an everyday necessity to many of the procedures being done today. Post-acquisition, these applications may be utilized at many different points within the workflow. The application may be utilized immedeately while the technologist is on the scanner and waiting for the next patient. The application may be utilized on a stand-alone workstation adjacent to the scanner in the acquistion room. There may be a seperate workstation in an analysis lab. Or it may be the radiologist reading the study who may need to run this application.

The clinical need is to have all of these plaforms to be capable of hosting the same application. In today's clinical environemnt, these various platforms may be provided by several vendors. There needs to be a common API for these hosting machines and applications to support this trans-platform portability.

This common API needs to identify the specific set of fundamental capabilities that would gaurentee interoperability between the various hosting machines and applications ensuring their clinical relavence within the workflow.

The application needs to be installed easilly on the hosting platform that the user intends on performing the clinical analysis.

4. Standards and Systems

DICOM Supplement 118 Hosted Applications

5. Discussion

The key to making this profile effective is to define a minimum API set that would make a hosted application interoperable in any clinical environment.

@@ Line 14: / Line 14: @@
 ==3. Key Use Case==
-A Radiologist requires a new capability for prost-processing image analysis.  The new capability is provided by only one application today.  The application is installed easilly on the hosting platform that the Radiology uses everyday.  The hosting platform and the hosted application are developed by 2 autonomous development groups.  It's behaviour is seamless on the Radiologist hosting platform.
+Post-processing clinical applications are an everyday necessity to many of the procedures being done today.  Post-acquisition, these applications may be utilized at many different points within the workflow.  The application may be utilized immedeately while the technologist is on the scanner and waiting for the next patient.  The application may be utilized on a stand-alone workstation adjacent to the scanner in the acquistion room.  There may be a seperate workstation in an analysis lab.  Or it may be the radiologist reading the study who may need to run this application.
+The clinical need is to have all of these plaforms to be capable of hosting the same application.  In today's clinical environemnt, these various platforms may be provided by several vendors.  There needs to be a common API for these hosting machines and applications to support this trans-platform portability.
+This common API needs to identify the specific set of fundamental capabilities that would gaurentee interoperability between the various hosting machines and applications ensuring their clinical relavence within the workflow.
+The application needs to be installed easilly on the hosting platform that the user intends on performing the clinical analysis.
 ==4. Standards and Systems==
@@ Line 23: / Line 30: @@
 ==5. Discussion==
-The key to making this profile effective is to define a minimum API set that would make a hosted application interoperable in any Radiology environment.
+The key to making this profile effective is to define a minimum API set that would make a hosted application interoperable in any clinical environment.