Prefetching Offers Prospects for a Quick Responding PACS

Poppel, Bas M. van; Lodder, H.; Elsakkers, P. H.; Koens, M. L.; Bakker, A. R.

doi:10.1007/978-3-662-00807-2_75

Cited by 7 publications

(3 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

Section: Backgroundsmentioning

confidence: 99%

“…age, medical history, treating specialism) and examination data (e.g. date, type, body part) which is sent to the PACS triggered by hospital events, such as patient admission and (radiological) appointments [3].The textual database of the PACS, which could contain a limited number of mainly radiology related data of a group of selected patients should be kept in consistency with the database of the RIS/HIS. Various PACS-RIS/HIS interfaces have been realized at PACS implementationsites around the world [4,5,6,7].…”

mentioning

confidence: 99%

See 1 more Smart Citation

<title>Prototyping a PACS-RIS/HIS interface in Europe</title>

et al. 1992

View full text Add to dashboard Cite

Currently a large european project in the area of PAS research and prototyping is being performed. The EurIPACS project is subdivided into a dozen topics. One of these topics is involved in the integration of PACS, RIS and HIS on conceptual, functional and technical level. Within the scope of this topic, which is called HIPIN (HIs/ris-Pacs INtegration), a prototype PACS-RIS/HIS interface will be specified, designed, realized, clinically implemented and evaluated. The interface software, together with the computer configuration on which it runs, is called the HIPIN box. This HIPIN box will be designed in such a way that it can be applied (with minimal adaptations) to interface any RISIHIS with any PACS in a multi-vendor environment. Two incarnations of the HIPIN box will be realized and will be implemented in the clinical routines of a Belgian and a German hospital. The functionalityof the interface will be focussed to support the clinical requirements in these hospitals. The HIPIN box will support communication facilities, integration of the textual databases, and data-protection measures. Furthermore, it will contain intelligent modules to control image file archival and migration (prefetching). BACKGROUNDSIt is widely recognized now that PACS can only be implemented successfully when it is sufficiently well interfaced with the existing hospital information system environment [1,2]. This environment in most cases consists of an RIS and an HIS. Various kinds of integration are needed: Information integration, e.g.:-Patient demographic data from the HIS are needed in the PACS for the identification of the image files, -The user of the PACS workstation needs to be able to view the clinical data in the RIS/HIS of the patient, whose images are displayed on the workstation. Functional integration, e.g.: -The PACS workstation user needs various HIS functions such as patient selection, radiology report retrieval and authorization, request appointment for radiology exam. System integration, e.g.: -Prefetching and other intelligent PACS image management strategies need information from the RIS/HIS, such as patient data (e.g. age, medical history, treating specialism) and examination data (e.g. date, type, body part) which is sent to the PACS triggered by hospital events, such as patient admission and (radiological) appointments [3].The textual database of the PACS, which could contain a limited number of mainly radiology related data of a group of selected patients should be kept in consistency with the database of the RIS/HIS. Various PACS-RIS/HIS interfaces have been realized at PACS implementationsites around the world [4,5,6,7]. However, until now these were limited in functionalityand/or clinical application. Recently, three large hospital-wide PACS projects have been announced, MDIS/USA, SMZO/Vienna, and Hammersmith/London. Sufficient integration of PACS and RIS/HIS is considered critical within all these projects [8]. O-8194-0806-9/921$4.OO SPIE Vol. 1654 Medical Imaging VI: PACS Design and Evaluation (1992) / 551 ...

show abstract

Section: Backgroundsmentioning

confidence: 99%

mentioning

confidence: 99%

<title>Prototyping a PACS-RIS/HIS interface in Europe</title>

et al. 1992

View full text Add to dashboard Cite

show abstract

“…Necessary information include the image acquisition date, current and previous image modality, current and previous body parts represented, patient location, and patient history. These information, feeding PACS pre-fetch algorithms, would greatly improved image data transfer performances 5 The problem of how to realize the integration or the interface between the RIS and the PACS in a radiological department has been explored in a general way in some earlier work 6, Some implementations are further discussed elsewhere 7,8 In this paper, we describe the solutions for the implementation of the interface between the PACS database and the RIS in our department. The PACS database and the RIS are first presented as well as a general introduction about the problems and solutions for the interconnection of heterogeneous databases.…”

mentioning

confidence: 99%

<title>Issues and solutions for interfacing a PACS database with an RIS</title>

Breant¹,

Taira²,

Tashima³

et al. 1992

SPIE Proceedings

View full text Add to dashboard Cite

We describe the interfacing methods between our departments RIS (Radiological Information System) and PACS database. Sharing information has become an increasingly important issue for both systems. RIS study information should be available at the PACS workstation to complete the image description. Patient scheduling, admission and discharge information are critical to PACS for improving image routing and storage management algorithms. The design of the interface between the RIS and the PACS database involves the development of some standardization methods. These include the network communication protocol between the two database servers, the language mapping operations, the database result format and the error handling. The implementation of the interface is in two steps. In the first one, a subset of RIS data is automatically transmitted to the PACS database when some relevant events occur in the RIS. In a second phase, the user at the PACS workstation can directly initiate queries to the RIS. The PACS SQL server (UNIX based) sends SQL network requests as ASCII text to the RIS MUMPS database server (VAX based). The RIS server translates the SQL requests to MUMPS, executes the statements and returns ASCII results to the SQL server. We have been able to exchange information between the RIS and the PACS display programs. RIS text reports can be displayed on PACS workstations. RIS information can be used into pre-fetch algorithms.

show abstract