PubMed Health⌕ Search

Biomedical subjects

R Mendenhall

Publications and source records attributed to R Mendenhall.

3 recordsLinked to original sources

Study status consistency and duplicate-read protection in a distributed architecture.

UNLABELLED: This presentation will discuss the benefits and pitfalls of implementing a study status and duplicate-read protection mechanism within a distributed picture archiving and communication system (PACS) architecture. There are many advantages to a distributed PACS network in which image studies are proactively pushed to reading stations before they are required by a radiologist. The absence of a central server, which serves on demand, makes managing study status and protecting against duplicate reads challenging. The system to manage study status and read access must be efficient, robust, and easy to administer. A system is presented that accomplishes these goals while maintaining the advantages of a distributed architecture. METHODS: The basic workflow of the system is that image studies acquired at a modality device are automatically sent to an archive server. Using a set of advanced routing rules, the archive automatically routes studies to diagnostic workstations where studies are candidates for diagnostic read. The workstations display a list of all local studies available for reading. A monitor application running on the workstations coordinates access to studies for diagnostic read. Once the status of a study has been changed, the workstations on the networks and the archive are notified, which causes the study to be automatically removed from any list on a workstation where it might be a read candidate. RESULTS: Implementation of this system provides a balanced workflow throughout the system while minimizing the need for costly high-speed network hardware. Additionally studies are read as soon as they are available by the next available radiologist. This workflow is enabled without the need for specific interaction by any of the radiologists on the network. By having the images available at the workstation in an organized worklist, this methodology increases the efficiency of the radiologist. CONCLUSION: The implementation of this system enables a radiology department, or even a specialty group within a department, to gain the benefit of a distributed system as well as the benefits provided by a central-server architecture. This can be done very cost effectively with minimal configuration overhead and hardware requirements.

Computer Systems↗

Designing fault-tolerant distributed archives for picture archiving and communication systems.

PURPOSE: Distributed archives in a picture archiving and communication system (PACS) environment can provide added fault tolerance and fail-over capability, as well as increased load capacity at a more economical price than traditional 'high-availability" systems. Systems can be configured with varying levels of fault tolerance, depending on the amount of redundancy desired. There is, however, a direct correlation between the level of hardware redundancy and cost to implement. This presentation details the system design for fault-tolerant distributed archives as well as several options for redundancy, referencing implementation of a fault-tolerant archive system at the University of Utah. METHODS: The distributed archive system described here is based on Image Devices' image archive software, which can be implemented on multiple individual archive servers in order to distribute archive functionality and operational load. The configuration and implementation of the individual servers together make up the distributed archive system and does not impact the ability of the system to be scaled to meet future requirements. Several implementation and configuration options exist, including the ability for servers to maintain replicated databases containing patient and image information. Thus, each archive can be aware of all information and the location of this information within the distributed archive system. RESULTS: The goal is to produce systems that will still be operational in the event of any single point of failure, ie, a network connection failure between facilities or the failure of a single archive server within the distributed system. During normal operation, workload for image acquisition, image routing and image query requests will be distributed between the archive servers. If the system is deployed in a multifacility environment, each archive server can be configured to be responsible for the acquisition and image distribution management within that server's local facility. If the system is deployed in a single facility environment, load can be distributed evenly between the archive servers based on an understanding of the workload requirements generated be each acquisition and display device in the system. In the event that an archive server fails, other archive servers within the system will have the ability to provide some or all of the failed server's functionality. The degree of fail-over capability is dependent on the archive server's configuration as well as hardware redundancy employed. Three levels of fault-tolerant design can be achieved with this system architecture: (1) duplicate work capability only; (2) duplicate work capability and short-term image cache; (3) duplicate work capability, short-term image cache, and longterm image archival. Using the basic fault-tolerant design above, we have implemented a multifacility distributed archive system at the University of Utah. This system was implemented at a fraction of the cost of true "high-availability" archive architectures yet provides constant up time for the PACS system. If the network connection between the two locations goes down, each site is still fully functional for soft-copy read, as well as image acquisition and distribution. If either of the archive servers goes down, the image sources are redirected to the other archive server. The operational server then handles image distribution for both locations. Access to images in the short-term image cache is available to both archive servers and is not affected by loss of the network connection or remote server. Because there is ony one long-term archive device, the ability to retrieve images from long-term storage is the only function compromised by a network or server failure. CONCLUSION: By implementing distributed archives in a PACS environment, it is possible to achieve a highly fault-tolerant system without the expense of high-availability hardware and software. The design concepts outlined here can be applied to any PACS system that supports distributed archive functionality.

Computer Systems↗