Integrating Legacy Laboratory Information Systems into a Client-Server World: The University of Minnesota Clinical Workstation (CWS) Project

K. E. Willard; B. H. Sielaff; D. P. Connelly

doi:10.1055/s-0038-1634602

Methods of Information in Medicine, Inhaltsverzeichnis

Methods Inf Med 1995; 34(03): 289-296
DOI: 10.1055/s-0038-1634602

Original Article

Integrating Legacy Laboratory Information Systems into a Client-Server World: The University of Minnesota Clinical Workstation (CWS) Project

Authors

K. E. Willard

¹Medical Decision Support Group, Division of Laboratory Information Systems, Department of Laboratory Medicine & Pathology, University of Minnesota Hospital and Clinic, University of Minnesota, Minneapolis MN, USA
B. H. Sielaff

¹Medical Decision Support Group, Division of Laboratory Information Systems, Department of Laboratory Medicine & Pathology, University of Minnesota Hospital and Clinic, University of Minnesota, Minneapolis MN, USA
D. P. Connelly

¹Medical Decision Support Group, Division of Laboratory Information Systems, Department of Laboratory Medicine & Pathology, University of Minnesota Hospital and Clinic, University of Minnesota, Minneapolis MN, USA

Abstract

Abstract:

The development of an innovative clinical decision-support project such as the University of Minnesota’s Clinical Workstation initiative mandates the use of modern client-server network architectures. Preexisting conventional laboratory information systems (LIS) cannot be quickly replaced with client-server equivalents because of the cost and relative unavailability of such systems. Thus, embedding strategies that effectively integrate legacy information systems are needed. Our strategy led to the adoption of a multi-layered connection architecture that provides a data feed from our existing LIS to a new network-based relational database management system. By careful design, we maximize the use of open standards in our layered connection structure to provide data, requisition, or event messaging in several formats. Each layer is optimized to provide needed services to existing hospital clients and is well positioned to support future hospital network clients.

Keywords:

Legacy Systems - Integration - Client-server - Open Systems - HL7 - TCP - Object-Oriented Programming - Laboratory Information Systems

Volltext

Referenzen

References
1 Sinha A. Client-server computing. Communications of the ACM 1992; 35: 77-98.
2 Southwick K. Selling the client server cure. Upside 1994; 1: 41-54.
3 Galitz WO. User Interface Design. Wellesley MA: QED Publishing; 1993
4 Benest ID, Duki D. High level user-interface objects. In: Designing and Using Human-Computer Interfaces and Knowledge – Based Systems. Salvendy G, Smith MJ. eds. Amsterdam: Elsevier Science Publ; 1989: 597-604.
5 Jean FC, Lavril M, Lamaitre D, Sauquet D, Degoulet P. A software engineering approach for medical workstations development. Int J Biomed Comput 1994; 34: 249-60.
6 Tang PC, Patel VL. Major issues in user interface design for health professional workstations: summary and recommendations. Int J Biomed Comput 1994; 34: 139-48.
7 Sengupta S, Clayton PD, Molholt P. et al. IAIMS and sharing. Int J Biomed Comput 1994; 34: 339-48.
8 Van Mullingen EM, Timmers T, Brand J. et al. HERMES: a health care workstation integration architecture. Int J Biomed Comput 1994; 34: 267-75.
9 Sielaff BH, Connelly DP, Scott EP. ESPRE: A knowledge-based system to support platelet transfusion decisions. IEEE Trans Biomed Eng 1989; 36: 541-6.
10 Connelly DP, Sielaff BH, Scott EP. ESPRE-Expert system for platelet request evalution. Am J Clin Pathol 1990; 94 (Suppl. 01) S19-24.
11 Sielaff BH, Scott EP, Connelly DP. Design and preliminary evaluation of an expert system for platelet request evaluation. Transfusion 1991; 31: 600-6.
12 Johnson R. National Report on Computers and Health. 1994 15. 2-3.
13 Replication Server: A Component of Sybase System ZO. Technical Report Sybase Inc.; Emeryville CA: 1993
14 Health Level Seven: An application protocol for electronic data exchange in healthcare environments. Version 2.1, Health Level Seven, PO Box 66111 Chicago Illinois 60666-9998:
15 Smith S, Dennis B. HL7: Facilitating multiple approaches to systems integration. Comput Healthcare 1991; 2: 59-6l.
16 Cahill BP, Holmen JR, Bartleson PL. Mayo Foundation Electronic Results Inquiry, The HL7 Connection. AMIA 1992; 516-20.
17 McDonald CJ. Standards for the electronic transfer of clinical data. In: Proc Annual Symp Comput Appl Med Care. 1990; 14: 9-14.
18 Connelly DP, Sielaff B, Willard KE. The clinical workstation as a means of improving laboratory use. Clin Chem Acta. (in press).
19 Gentry D. Spreading the Wealth: Distributed Objects and Portable Distributed Objects. NXAppp 1993; 1: 1-4.
20 Kim J. The DESS System: HL-7 to SQL using object oriented techniques. Health Computer Sciences Technical Report. University of Minnesota; 1992
21 Stevens WR. Advanced Programming in the Unix Environment. Reading MA: Addison Wesley; 1992
22 Tolchin SG, Barta W. Local network and distributed processing issues in the Johns Hopkins Hospital. J Med Syst 1986; 10: 339-53.
23 Willard KE, Hallgren JH, Connelly DP. W3 based medical information systems vs custom client server applications. In: Proc 2nd Internat WWW Conf 1994; 641-51.
24 Connelly DP, Lasky LC, Keller RM, Morrison DS. A system for graphical display of clinical laboratory data. Amer J Clin Pathol 1982; 78: 729-37.
25 Connelly DP, Dean DW, Hultman BK. Physician oriented result reporting in an intensive care environment. In: MEDINFO 86. Amsterdam: Elsevier Science Publ; 1986: 810-2.
26 Tolchin SG, Barta W. Overview of an architectural approach to the development of the Johns Hopkins Hospital Distributed Clinical Information System. J Med Syst 1986; 10: 321-38.
27 Annevelink J, Young CY, Tang PC. Heterogenous database integration in a physician workstation. In: Proc Annual Symp Comput Appl Med Care. 1991; 368-72.
28 Kim W. Object oriented database systems: strengths and weaknesses. J Object Oriented Programming 1992; 4: 27-34.
29 Loomis ME. Object oriented database management systems versus relational. J Object Oriented Programming 1992; 4: 40-9.