Biomedical subjects

D Sauquet

Publications and source records attributed to D Sauquet.

10 recordsLinked to original sources

PubMed1998

Middleware for healthcare information systems.

Middleware is now a commonly used expression and anyone building distributed applications is referring to "middleware services". Nevertheless this notion lacks of sound theoretical foundation. This paper tries to clarify the relationship between the components of distributed environments, especially in healthcare, and to establish some classification aiming at gaining a common understanding of the functionalities and interdependency of the existing modules of distributed environments.

Computer Communication Networks↗

PubMed1998

Rationale and design considerations for a semantic mediator in health information systems.

Rapid development of community health information networks raises the issue of semantic interoperability between distributed and heterogeneous systems. Indeed, operational health information systems originate from heterogeneous teams of independent developers and have to cooperate in order to exchange data and services. A good cooperation is based on a good understanding of the messages exchanged between the systems. The main issue of semantic interoperability is to ensure that the exchange is not only possible but also meaningful. The main objective of this paper is to analyze semantic interoperability from a software engineering point of view. It describes the principles for the design of a semantic mediator (SM) in the framework of a distributed object manager (DOM). The mediator is itself a component that should allow the exchange of messages independently of languages and platforms. The functional architecture of such a SM is detailed. These principles have been partly applied in the context of the HELIOS object-oriented software engineering environment. The resulting service components are presented with their current state of achievement.

Computer Communication Networks↗

PubMed1995

Legacy systems: managing evolution through integration in a distributed and object-oriented computing environment.

Legacy systems are crucial for organizations since they support key functionalities. But they become obsolete with aging and the apparition of new techniques. Managing their evolution is a key issue in software engineering. This paper presents a strategy that has been developed at Broussais University Hospital in Paris to make a legacy system devoted to the management of health care units evolve towards a new up-to-date software. A two-phase evolution pathway is described. The first phase consists in separating the interface from the data storage and application control and in using a communication channel between the individualized components. The second phase proposes to use an object-oriented DBMS in place of the homegrown system. An application example for the management of hypertensive patients is described.

Computer Communication Networks↗

PubMed1994

A software engineering approach for medical workstations development.

Multimedia medical workstations represent the natural tool for accessing the hospital information system environment. They are complex medical systems that have to gather, in a single framework, a large collection of components dealing with multimedia medical objects. To remain current with both medical practice and with advances in the computer science field, they have to allow the iterative addition of new functions to the set of existing ones. In this paper, after a survey of commonly required medical workstation functional components, we shall try to discuss how a software engineering approach can streamline the development of a medical workstation. Different software engineering tools needed to build the functional components of a workstation are described. Their integration in a single dedicated environment is considered through four perspectives: data, presentation, communication and control. Benefits and limitations of an object-oriented approach are discussed.

Computer Communication Networks↗

PubMed1994

The HELIOS Medical Connection Services.

This paper presents the design and implementation of the HELIOS software component that deals with integration of medical applications in health information networks. The problem of interoperability between health information systems based on different data exchange syntaxes is first discussed. A meta-model, relying on CEN TC251 recommendations, is then presented as a possible solution to this problem and a message description language including these recommendations is proposed. Using this meta-model, the Medical Connection Services that comprises a generic message processing automaton, a resource manager and a mapper is able either to interpret messages expressed in a given syntax (e.g., EDIFACT, ASTM) and map them to the application objects or to automate the translation of the messages in another syntax. Special focus is given on the position of the Medical Connection Services within the HELIOS integration strategy (i.e., through data, presentation and communication). The problem of semantic heterogeneity is then discussed.

Computer Communication Networks↗

PubMed1994

The HELIOS Unification Bus: a toolbox to develop client/server applications.

In the medical domain, new developments commonly rely on client/server architectures. But face to distributed environments, the software developers encounter a tremendously increasing complexity when building integrated applications. This paper presents the HELIOS Unification Bus (HUB), a communication integration framework for the HELIOS medical software engineering environment that allows the exchange of data between components that can be hosted on heterogeneous machines linked by a network. The HUB is developed as a C++ toolbox over UNIX and TCP/IP. It includes a message routing entity called router and a generic application programming interface (API), implemented as a C++ library, that allows to build easily software components compliant with the standardised HELIOS language. Messages conveyed by the bus are composite objects that are serialized to be transmitted over the bus using the ASN.1 ISO presentation protocol. The article describes the use of the bus to ease the development and execution of distributed medical applications and its role from the communication integration standpoint.

Computer Communication Networks↗

PubMed1994

Using a meta-model to build a connection service in an object oriented medical application development environment.

Interoperability is a key issue in distributed health information systems. This paper presents the design and implementation of the Connection Service (CS) component of the HELIOS medical software engineering environment. An exchange message meta-model based on CEN TC251 recommendations and a message description language are proposed. Using this meta-model, the CS is able either to interpret messages expressed in a given syntax (e.g., EDIFACT, ASTM) and map them to the application objects or to automate the translation of the messages in another syntax. It is concluded that this meta-model approach contributes to the management of semantic heterogeneity.

Computer Communication Networks↗

PubMed1987

Integrating management and expertise in a computerised system for hypertensive patients.

An expert system has been integrated to the data management system of the ARTEMIS programme for hypertensive patients. The patient database, which has been used since 1975, contains the medical records of about 20,000 patients. Information is interactively entered by physicians, nurses and secretaries on video display units. The computerised medical record has replaced the traditional handwritten medical record. The database management system is used to produce different summary reports (inpatient and outpatient care) and personalized recall letters which are mailed to the patients before their appointments. Suggestions provided by the expert system include additional information to be obtained (complementary patient interrogation, biological or radiological investigations, etc.), possible causes of hypertension, and medical prescriptions. The information base allows the description of both static knowledge (in the form of a semantic network) and dynamic knowledge (in the form of production rules). The inference system sequentially uses a combination of forward and backward chaining and performs both exact and approximate reasoning. The diagnostic performance of the expert system was evaluated in 100 cases of hypertension (50 of essential hypertension and 50 of secondary hypertension. Concordance between the diagnosis proposed by the expert system and the one proposed by the specialist was achieved in 92% of secondary hypertension cases and 88% of essential hypertension cases. It is suggested that the integration of data and knowledge management might enhance the overall acceptance by medical staff of a computerised system, and facilitate the validation of a knowledge base.

Database Management Systems↗

PubMedDate not supplied

Towards specialised middleware for healthcare information systems.

Middleware is now a commonly used expression and anyone building distributed applications is referring to 'middleware services'. Nevertheless this notion lacks of sound theoretical foundation. This paper tries to clarify the relationship between the components of distributed environments, especially in healthcare and to establish some classification aiming at gaining a common understanding of the functionality and interdependency of the existing modules of distributed environments. A case study is presented and the potential benefits of using a middleware approach are discussed.

Computer Communication Networks↗

PubMedDate not supplied

An approach for the evaluation of software engineering environments in medicine.

This article examines several criteria for the evaluation of software engineering environments (SEE) in medicine. The study is restricted to the evaluation of the SEE itself, not of its by-products which are the medical applications developed with the SEE. Basic principles for an evaluation methodology are presented. They consist in determining the evaluation objectives and judging a SEE according to criteria which are grouped into three broad categories--functional, generic and environmental. Each category reflects a particular domain of evaluation of the SEE. Methods of measurement and questions highlighting these specific areas are mentioned. Criteria are extracted from the list of objectives that follows the HELIOS European AIM project of the Commission of the European Communities. Special emphasis is drawn on the criteria for which the medical specificity and usefulness of a SEE can be approach. For this purpose a method of measurement of such appropriateness is proposed.

Attitude to Computers↗