Applying the object paradigm to a centralized database for a cardiology division.

In order to master the overwhelming quantity of data produced by the different laboratories of our Cardiology Division, we are presently developing a centralized database. Our aim is to improve the quality of diagnoses and therapies by constituting patient centered medical files integrating logically the results of the results of the different examinations and allowing for a rapid access to the patient data. The database has to be accessible from an heterogeneous set of PC, MacIntoshes and UNIX workstations. It must have an ergonomic graphic user interface and generate reports which can be sent to the patient physician. It is well known that the requirements for a medical database make its conceptual analysis very difficult. As medical knowledge continually evolves, the examination protocols change and, therefore, the data sets have to be updated. The maintenance of classical databases is usually expensive because it requires specialized staff to alter the database structure and to adapt the user interface. To allow for flexibility, modularity, code reusability and reliability, the object paradigm was applied to a classical relational database. Thanks to the combination of both data structure and behavior in single entities, it is possible to build generic user interfaces which can be easily tailored to the needs of every laboratory of our Cardiology Division.