You have requested a machine translation of selected content from our databases. This functionality is provided solely for your convenience and is in no way intended to replace human translation. Neither SPIE nor the owners and publishers of the content make, and they explicitly disclaim, any express or implied representations or warranties of any kind, including, without limitation, representations and warranties as to the functionality of the translation feature or the accuracy or completeness of the translations.
Translations are not retained in our system. Your use of this feature and the translations is subject to all use restrictions contained in the Terms and Conditions of Use of the SPIE website.
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.
The alert did not successfully save. Please try again later.
Sheel Kishore, Satjeet S. Khalsa, Eric R. Feingold, Sridhar B. Seshadri, Ronald L. Arenson, "PACS software testing," Proc. SPIE 1653, Medical Imaging VI: Image Capture, Formatting, and Display, (1 May 1992); https://doi.org/10.1117/12.59492