ABSTRACT
This article considers the 26 years history of an integrated hospital information system (HIS). The system emerged from an experimental government sponsored project in the Leiden University Hospital and is now the leading HIS in The Netherlands. The evolution during these 26 years is presented and discussed in this article with an emphasis on the organisational setting and financing besides the aspects functionality, technology/architecture and evaluation aspects. Recently HISCOM was acquired by the BAAN-group completing the evolution and bringing the HIS to the international health care IT market.
Subject(s)
Hospital Information Systems , Computer Communication Networks , Computer Systems , Costs and Cost Analysis , Database Management Systems , Financing, Government , History, 20th Century , Hospital Information Systems/economics , Hospital Information Systems/history , Hospitals, University/history , Information Systems , Netherlands , Nursing , SoftwareABSTRACT
In this paper the conception of the federated healthcare record server to support shared diabetes care is described. Business process modelling is applied to describe the shared care for diabetes patients. Typical dialogues between the different users (patient, internist, GPs, and diabetic nurses) are analysed and described in terms of use cases. Next to this modelling three incremental steps are defined to realise the record server based upon results of standardisation. It proves to be successful to design and build this record server on modern technologies like CORBA and JAVA.
Subject(s)
Diabetes Mellitus/therapy , Medical Records Systems, Computerized , Patient Care Team/organization & administration , Computer Communication Networks , Feasibility Studies , Hospital Information Systems , Humans , Netherlands , Patient Identification Systems , Programming LanguagesABSTRACT
A growing demand for integrating stand-alone information systems with an HIS can be observed. Different forms of integration can be distinguished: technical integration, user interface integration, and integration of the information service. The integration of the information service appears to be especially difficult. An integrated information service can only be achieved when the applications use each other's information services. We will discuss three approaches for letting applications belonging to another system utilize the necessary information service of a host system. The first approach makes use of the user interface, and the necessary information service has to be extracted from the service to a user. Another, often used, approach is the extension of the applications with coupling modules. The coupling modules communicate messages and translate them into the context of the application. The applications are modified scarcely and the coupling modules have to supply the necessary information services. When the coupling problem is more complex (e.g., a larger set of data is to be exchanged interactively), a growing effort will be needed for these adapting modules. A better approach is to split the application into building blocks. Applications are composed of building blocks. The application, which should deliver the integrated information service, is also composed of such building blocks. The building blocks are designed to offer information services that can be used by other systems as well. If we succeed in decomposing the applications into suitable building blocks, an integrated information service could be more easily achieved.
