Translator Disclaimer
1 May 1992 PACS software testing
Author Affiliations +
A PACS in clinical use must provide a high degree of reliability in terms of uptime and data integrity. For a number of reasons, this is difficult to achieve. There may exist, on a PACS network, a multitude of imaging and display sub-systems each with its own interface peculiarities and requirements. Because a PACS is usually a multi-vendor system, the interface problems are complex. Furthermore, once a PACS is in clinical use, the nature of the process level interactions are complicated and random. To improve overall system reliability requires not only rigorous component testing but also a complete system evaluation. A testing methodology for the evaluation of a multi-vendor PACS is being developed at our institution. Key features of this methodology include the design of component and system stress tests, and system boundary tests that stimulate the depletion of critical resources. Preliminary results from running such tests at the University of Pennsylvania Medical Center are presented.
© (1992) COPYRIGHT Society of Photo-Optical Instrumentation Engineers (SPIE). Downloading of the abstract is permitted for personal use only.
Sheel Kishore, Satjeet S. Khalsa, Eric R. Feingold, Sridhar B. Seshadri, and Ronald L. Arenson "PACS software testing", Proc. SPIE 1653, Medical Imaging VI: Image Capture, Formatting, and Display, (1 May 1992);


Performance of the Mayo-IBM PAC system
Proceedings of SPIE (May 15 1994)
Detailed description of the Mayo/IBM PACS
Proceedings of SPIE (July 01 1991)
PACS subsystems performance: centralized versus distributive
Proceedings of SPIE (September 08 1993)
Initial clinical experience with ultrasound PACS
Proceedings of SPIE (May 12 1995)
Sizing a PACS
Proceedings of SPIE (May 15 1994)

Back to Top