Making the PACS workstation a browser of image processing software: a feasibility study using inter-process communication techniques
- 151 Downloads
To enhance the functional expandability of a picture archiving and communication systems (PACS) workstation and to facilitate the integration of third-part image-processing modules, we propose a browser–server style method.
In the proposed solution, the PACS workstation shows the front-end user interface defined in an XML file while the image processing software is running in the background as a server. Inter-process communication (IPC) techniques allow an efficient exchange of image data, parameters, and user input between the PACS workstation and stand-alone image-processing software. Using a predefined communication protocol, the PACS workstation developer or image processing software developer does not need detailed information about the other system, but will still be able to achieve seamless integration between the two systems and the IPC procedure is totally transparent to the final user.
A browser–server style solution was built between OsiriX (PACS workstation software) and MeVisLab (Image-Processing Software). Ten example image-processing modules were easily added to OsiriX by converting existing MeVisLab image processing networks. Image data transfer using shared memory added <10 ms of processing time while the other IPC methods cost 1–5 s in our experiments.
The browser–server style communication based on IPC techniques is an appealing method that allows PACS workstation developers and image processing software developers to cooperate while focusing on different interests.
KeywordsPACS workstation Image processing Functional expandability Client–server communication Inter-process communication
Unable to display preview. Download preview PDF.
- 1.Ratib O (2009) Imaging informatics: from image management to image navigation. Yearb Med Inform 167–172Google Scholar
- 2.MeVisLab. Medical image processing and visualization. http://www.mevislab.de/
- 3.3D Slicer. http://slicer.org/
- 4.Toussaint N, Souplet J, Fillard P (2007) MedINRIA: medical image navigation and research tool by INRIA. In: Proceedings of MICCAI’07 workshop on interaction in medical image analysis and visualizationGoogle Scholar
- 6.MeVis Medical Solution AG (2009) Getting started: first steps with MeVisLab. http://www.mevislab.de/developer/documentation/
- 7.Apple Inc. (2007) Distributed objects programming. http://developer.apple.com/mac/library/documentation/Cocoa/Conceptual/DistrObjects/DistrObjects.html
- 8.Stevens WR (1998) UNIX network programming. Interprocess communications, vol 2, 2nd edn. Prentice-Hall, Englewood CliffsGoogle Scholar
- 9.Wang C, Smedby Ö (2009) MeVisHub user guide. http://mevislabmodules.svn.sourceforge.net/viewvc/mevislabmodules/trunk/Community/General/Sources/ML/MLOsiriXImporter/
- 14.Dikkers R, Willems TP, de Jonge GJ, Marquering HA, Greuter MJW, van Ooijen PMA, van der Weide MCJ, Oudkerk M (2009) Accuracy of noninvasive coronary stenosis quantification of different commercially available dedicated software packages. J Comput Assist Tomogr 33: 505–512CrossRefPubMedGoogle Scholar