2 THE INFORMATION SYSTEM
DESCRIPTION
2.1 Necessity
Internal medicine can be considered as basics for
many specialties and needs large amounts of
paraclinical explorations performed by different
devices that generates visual and numerical data
(radiology, echography, endoscopies, tomography,
electrocardiogram, MRI, histological cups etc.) used
for diagnosis and for follow-up of treatment or
evolution. Numerical information is given by
functional and biological assays while various
imagistic devices provide image data. That is why
internal medicine departments usually accumulates
huge quantities of medical data, including thousands
of image files, millions of numerical values and
thousands of written reports. As a result, a complex
application to manage and query a database
containing information and images from medical
domain is needed.
Oracle has been chosen because of the qualities
and the functions that it provides. The application
was developed under Oracle Jdeveloper. It provides
a completely integrated Java environment for
development, implementation and execution of the
multilevel Internet applications. JDeveloper gives
the possibility to build applications integrated with
the Oracle Databases servers. The Java applications
can be executed on all the 3 levels of the Internet
Computing architecture: client, application server
and databases server (Oracle Application
Development Framework, 2006).
2.2 The Database Structure
Applying the normalization process (Elmasri, 1994),
the database proposed for this on-line application
will be described further on. The database contains a
number of tables created when installing the
application. The tables contain a series of codes that
makes easier the work of updating patient
information and the investigations. These tables are:
medical units, users groups and users.
The data confidentiality is ensured by user name
and password that are provided separately for each
unit. In order to increase the data security, the
password is encrypted. Each doctor has access to
information regarding his own patients, but he can
share some data that can be seen by other specialists.
He can also access both statistical and scientific data
regarding all patients in database but in this case the
identification data about patients is hidden and the
ID number, name and address are blinded. At
information management level, anonimizing all
information concerning clinical data ensures
confidentiality; diagnosis, paraclinical information,
treatments are also blinded and only statistical data
can be viewed. On the other hand, the office
secretary can see personal information about patients
and referring doctors, but no diagnosis and treatment
elements are accessible. Other tables are:
- Diagnosis table.
- Analyses table codifies paraclinical and
biological data.
- Clinical examination table.
- Patient groups table.
The following tables are the most important in
the database because they store information about
patients, examinations, investigations and results:
- Patients table is used for storing information
about patient’s visits: personal ID number,
name, doctor, county, city, address, phone/fax
number, email and program – if any.
- A patient might have several examinations, for
each of them storing in the Consulting Table,
the diagnosis, date and treatment. Each
examination might contain one or several
clinical examinations (it is stored code,
description, a series of analyses identified by
code and obtained value).
- Images table stores information about still
images that were obtained from a patient
during his whole disease history.
This table has two special fields in order to store
the images and to realize the content based visual
query: image, having ORDSYS.ORDIMAGE type
and image_sign, having the ORDSYS.
ORDIMAGESIGNATURE type. InterMedia uses
objects to describe multimedia databases:
ORDAudio for audio data; ORDImage static
images; ORDVideo for video sequences and
ORDDoc for heterogeneous data (Oracle, 2007). At
the insertion in the database of the multimedia data
using interMedia, the metadata for still images is
automatically extracted (Oracle, 2007).
2.3 The Main Functions
2.3.1 Patient’s Information Management
This function is one of the main functions in the
application, and the information about patients has
the following organization:
ICEIS 2008 - International Conference on Enterprise Information Systems
418