HOSPITAL LABORATORY DATABASE MANAGEMENT SYSTEM FOR

AMAOKWE GENERAL HOSPITAL, ISHIAGU IVO LOCAL GOVERNMENT

AREA OF EBONYI STATE

Omini Moses
08148255474, ominiriches@gmail.com
Department of Computer Science, Akanu Ibiam Federal Polytechnic
Unwana, Afikpo.

ABSTRACT
The study focused on Laboratory Database Management System (LDMS) which is an
evolving concept, with new features and functionality being added often. As laboratory
demands change and technological progress continues, the functions of a LDMS will likely
also change. Despite these changes, a LDMS tends to have a base set of functionality that
defines it. The problem encountered in the laboratory by staff couple with nurse’s laxity
(laziness) over their duties, the need arose to develop a software that will be able to solve the
problem. The problem caused by the use of manual method of keeping hospital laboratory
information and the use of manual method of keeping attendance scheme for patients can
only be solved by computerizing the hospital laboratory attendance scheme for user (lab
attendance) and computerizing the hospital laboratory information system. The input to the
system comes with various forms. Each of these forms has the function of collecting specific
data from the Med-Lab, doctors, staff and patients as the case may be. The first form is the
admission form details that enables the system to prompt the Doctors/Nurses to fill a
form that requires details from the patient concerning personal and health. The other forms
are for Lab Scientist, doctors, Nurses, bed management, patient in and out, etc are solely
intended for the administrative use for the staff. Here, the staff can add patients, doctors etc
that can include the services render by the hospital and change other things. After careful
observation and analysis of the existing system, the current system was a stone alone system
handle by the Laboratory Attendants or Technicians in the Hospital Laboratory, hence the use
of Php will be proposed for the design phase, while MySQl will be used as database at the
back-end. The choice of the programming language is relevant because of the interactive
tools and command, text area, and other project properties embedded in the language.

1.0 INTRODUCTION

A laboratory Database Management System (LDMS) is computer software that processes,

stores and manages data from all stages of medical processes and tests (Gibbon, 2006). An
Laboratory Information System (LIS) is a healthcare system that holds clinical data. By
comparison, an LDMS can be deployed in healthcare, too, but it is also used in non-medical
settings, including in environmental testing laboratories, pharmaceutical laboratories and
water treatment plants (Skobelev et al., 2011). An LDMS can be used as a Web tool or
installed on a personal computer or device and stores and manages captured data, as well as
producing reports from that data (Temiello, 2007). Physicians and lab technicians use
laboratory database systems to coordinate varieties of inpatient and outpatient medical
testing, including hematology, chemistry, immunology and microbiology. Basic laboratory
database systems commonly have features that manage patient check in, order entry,
specimen processing, result entry and patient demographics. An LIS tracks and stores clinical
details about a patient during a lab visit and keeps the database stored in its database for
future reference (Royce 2010).

The electronic data capture process of an LDMS or LIS can reduce time spent and cut errors
associated with the transcribing process (Khan et al., 2009). Maintenance of laboratory

1
database systems took on added importance with the introduction of the meaningful
use program. The program is overseen by the Centers for Medicare & Medicaid Services and
consists of sets of criteria split into stage 1, stage 2 and stage 3. Participating healthcare
providers that successfully prove their electronic health record (EHR) systems or EHR
modules such as an LDMS satisfy program criteria are eligible for incentive payments. If an
LIS is tested and certified to meet meaningful use criteria or other health IT certification
standards, it is defined as an EHR module. The exponentially growing volume of data created
in laboratories, coupled with increased business demands and focus on profitability, have
pushed LDMS vendors to increase attention to how their LDMS handles electronic data
exchanges. Attention must be paid to how an instrument's input and output data is managed,
how remote sample collection data is imported and exported, and how mobile technology
integrates with the LDMS (Wood, 2007). The successful transfer of data files in spreadsheet
and other formats, as well as the import and export of data to MySQL, PostgreSQL, and other
databases is a pivotal aspect of the modern LDMS. In fact, the transition "from proprietary
databases to standardized database management systems such as MySQL" has arguably had
one of the biggest impacts on how data is managed and exchanged in laboratories (Wilkerson
et al., 2014). Labs using LDMS boost their level of professionalism and their ability to meet
customer demand in two ways:

 LDMS helps labs produce accurate, reproducible results faster and more reliably
LDMS makes data from sequencing runs easier to store, track, and assess over time
and across experiments so that labs can evaluate and improve operational efficiency.

1.2 Statement of the Problem

Prior to the problem encountered in the laboratory by staff couple with nurse’s laxity
(laziness) over their duties, the need arose to develop a software that will be able to solve the
problem. The problem caused by the use of manual method of keeping hospital laboratory
information and the use of manual method of keeping attendance scheme for patients can
only be solved by computerizing the hospital laboratory attendance scheme for user (lab
attendance) and computerizing the hospital laboratory information system. The problems
that this project is set to solve in the manual method of keeping outpatient information
are:

1. Improper documentation of laboratory equipment, drugs, and media/ payment record.

2. Traditional practicum registration
3. Traditional data
4. No resource repository for accessing modules and all of practicum administration
5. No online information media for laboratory news
6. Storing and retrieving data associated with projects, whether they were conducted
yesterday or last year.

1.3 Objectives of the study

i. To provide end-to-end database management of samples, tests, and results for next-
generation genomics labs
ii. To accommodate different users with role-based interfaces to optimize lab efficiency
iii. To be easy for lab staff to configure and customize
iv. To offer out-of-the-box reports as well as the ability to create custom reports
v. To enable a lab to get up and running quickly on its preferred instrumentation.

1.4 Significance of the Study

2
The Laboratory Database Management System (LDMS) is an evolving concept, with new
features and functionality being added often. As laboratory demands change and
technological progress continues, the functions of a LDMS will likely also change. Despite
these changes, a LDMS tends to have a base set of functionality that defines it. That
functionality can roughly be divided into five laboratory processing phases, with numerous
software functions falling under each:
(1) The reception and log in of a sample and its associated customer data,
(2) The assignment, scheduling, and tracking of the sample and the associated
analytical workload,
(3) The processing and quality control associated with the sample and the utilized
equipment and inventory,
(4) The storage of data associated with the sample analysis,
(5) The inspection, approval, and compilation of the sample data for reporting
and/or further analysis.
1.5 Scope of the Study
The scope of this study is centered on designing an Computerized Hospital Laboratory
Database Management System staff, laboratory attendance and for patients. In fact it involves
all parts of medical field in terms of record keepings for patient’s records and all other aspect
of field.
However, this project has been limited to GLMPD (General Laboratory Management/Patient
Department) which includes the following areas:
1. Recording of Laboratory Experiment/patient health record
2. Acceptance of Specimen/health report of Patient
3. Provisional of General Diagnosis for patient/Doctors prescription and treatment.
1.6 Definition of Terms
 Computer: This is an electronic device that can accept data information of inputs,
process the data and it have the ability to store the data and also retrieves it for
future use.
 Data: These are groups of non-random symbols such as words, figures, values
which represent event and things that have taken place.
 Database: This is the collection of related files.
 Hospital: This is a health facility where people who are ill or injured are
given medical treatments and care.
 Information: this is a data that has been processed into a form which is
 meaningful to the recipient and which is of perceived value in either current or
prospective decisions or action by the recipient.
 Management: This is the process of getting activities completed efficiently with and
through other people.
 Storage: This is a processing of storage data and information using storage media.

2.0 LITERATURE REVIEW

2.1 Laboratory Database Management System

A Laboratory Database Management System (LDMS) is software that allows you to

effectively manage samples and associated data to improve lab efficiency (Wilkerson et al.,
2014). By using a LDMS, your lab can automate workflows, integrate instruments, and

3
manage samples and associated information. Labs using LDMS boost their level of
professionalism and their ability to meet customer demand in two ways:

 LDMS helps labs produce accurate, reproducible results faster and more reliably
LDMS makes data from sequencing runs easier to store, track, and assess over time
and across experiments so that labs can evaluate and improve operational efficiency
(Skobelev, 2011).

Modern genomics research generates an unprecedented amount of data. Faced with

increasing data volumes and sample throughput along with near-continual changes in
technology labs seeking to streamline lab operation and cut costs must in turn modernize their
approach to managing, tracking, and centralizing genomics data (Wood, 2007). The
definition of a LDMS is somewhat controversial: LDMSs are dynamic because the
laboratory's requirements are rapidly evolving and different labs often have different needs.
Therefore, a working definition of a LDMS ultimately depends on the interpretation by the
individuals or groups involved. According to Alan (2008) highlighted this problems of
LDMS, is perceived by an analyst, a laboratory manager, an information systems manager,
and an accountant, "all of them correct, but each of them limited by the users' own
perceptions.
2.1.1 Advantages of Laboratory Database Management System

i. Provide end-to-end information management of samples, tests, and results for next-
generation genomics labs
ii. Accommodate different users with role-based interfaces to optimize lab efficiency
iii. Be easy for lab staff to configure and customize
iv. Offer out-of-the-box reports as well as the ability to create custom reports
v. Enable a lab to get up and running quickly on its preferred instrumentation
vi. A good commercial LDMS will help you present your lab in a professional manner to
collaborators and granting bodies by enabling you to manage samples and workflows
from end-to-end, ensuring the highest quality traceable results, and substantially
improving overall lab efficiency and operations (Tomiello, 2007).

2.1.2 Challenges of LDMS

Some of the most common challenges include:

 Coping with the ongoing and significant rise in the throughput and volume of data
associated with sequencing runs
 Finding scalable methods to organize and track samples and associated data
 Maintaining connections between samples and associated data from the moment
samples enter the lab to when data is reported
 Reducing the amount of time spent processing and manually managing samples
 Storing and retrieving data associated with projects, whether they were conducted
yesterday or last year
 Maintaining in-house solutions such as Microsoft Excel or homegrown systems that are
easy to use and relevant to the instruments and protocols necessary to move research
programs forward

2.2 LabWare’s Industry Leading LDMS

LabWare LDMS has been the industry’s most technically advanced Laboratory Information
Management System since its introduction to the market, and it continues to hold that
position today (Vaughan, 2006). Your business will benefit from capabilities such as
browser-based deployment, external-facing web portals, and fully configurable web services

4
while at the same time having the richest catalogue of modular laboratory management
software functionality from which to draw when deciding how to implement your LDMS
system (Wood, 2007).
2.3 Instrument and application integration
Modern LDMS offer an increasing amount of integration with laboratory instruments and
applications. A LDMS may create control files that are "fed" into the instrument and direct its
operation on some physical item such as a sample tube or sample plate. The LDMS may then
import instrument results files to extract data for quality control assessment of the operation
on the sample. Access to the instrument data can sometimes be regulated based on chain of
custody assignments or other security features if need be.
Modern LDMS products now also allow for the import and management of raw assay
data results (Gibbon 2006). Modern targeted assays such as qPCR and deep sequencing can
produce tens of thousands of data points per sample. Furthermore, in the case of drug and
diagnostic development as many as 12 or more assays may be run for each sample. In order
to track this data, a LDMS solution needs to be adaptable to many different assay formats at
both the data layer and import creation layer, while maintaining a high level of overall
performance. Some LDMS products address this by simply attaching assay data as BLOBs to
samples, but this limits the utility of that data in data mining and downstream analysis
(Mclelland, 2008).
2.4 Electronic data exchange
The exponentially growing volume of data created in laboratories, coupled with increased
business demands and focus on profitability, have pushed LDMS vendors to increase
attention to how their LDMS handles electronic data exchanges (Skobelev, 2006). Attention
must be paid to how an instrument's input and output data is managed, how remote sample
collection data is imported and exported, and how mobile technology integrates with the
LDMS. The successful transfer of data files in spreadsheet and other formats, as well as the
import and export of data to MySQL, and other databases is a pivotal aspect of the modern
LDMS (O’Leary, 2012). In fact, the transition "from proprietary databases to standardized
database management systems such as MySQL" has arguably had one of the biggest impacts
on how data is managed and exchanged in laboratories (McLelland, 2008). In addition to
mobile and database electronic data exchange, many LDMS support real-time data exchange
with Electronic Health Records used in core hospital or clinic operations (Khan, 2009).
2.5 Client-side options
A LDMS has utilized many architectures and distribution models over the years. As
technology has changed, how a LDMS is installed, managed, and utilized has also changed
with it. The following represents architectures which have been utilized at one point or
another.
2.5.1 Thick-client
A thick-client LDMS is a more traditional client/server architecture, with some of the system
residing on the computer or workstation of the user (the client) and the rest on the server
(Wood, 2007). The LDMS software is installed on the client computer, which does all of the
data processing. Later it passes information to the server, which has the primary purpose of
data storage. Most changes, upgrades, and other modifications will happen on the client side
(Wilkerson et al., 2014). This was one of the first architectures implemented into a LDMS,
having the advantage of providing higher processing speeds (because processing is done on
the client and not the server). Additionally, thick-client systems have also provided more
interactivity and customization, though often at a greater learning curve. The disadvantages
of client-side LDMS include the need for more robust client computers and more time-
consuming upgrades, as well as a lack of base functionality through a web browser. The
thick-client LDMS can become web-enabled through an add-on component (Skobelev, 2011).

5
Although there is a claim of improved security through the use of a thick-client LDMS
(Skobelev, et al., 2011), this is based on the misconception that "only users with the client
application installed on their PC can access server side information". This secrecy-of-design
reliance is known as security through obscurity and ignores an adversary's ability to mimic
client-server interaction through, for example, reverse engineering, network traffic
interception, or simply purchasing a thick-client license. Such a view is in contradiction of
the "Open Design" principle of the National Institute of Standards and Technology's Guide to
General Server Security which states that "system security should not depend on the secrecy
of the implementation or its components" (Tomiello, 2007), which can be considered as a
reiteration of Kerckhoffs's principle.
2.5.2 Thin-client
A thin-client LDMS is a more modern architecture which offers full application functionality
accessed through a device's web browser. The actual LDMS software resides on a server
(host) which feeds and processes information without saving it to the user's hard disk (Khan,
2009). Any necessary changes, upgrades, and other modifications are handled by the entity
hosting the server-side LDMS software, meaning all end-users see all changes made. To this
end, a true thin-client LDMS will leave no "footprint" on the client's computer, and only the
integrity of the web browser need be maintained by the user. The advantages of this system
include significantly lower cost of ownership and fewer network and client-side maintenance
expenses (Wood, 2007). However, this architecture has the disadvantage of requiring real-
time server access, a need for increased network throughput, and slightly less functionality. A
sort of hybrid architecture that incorporates the features of thin-client browser usage with a
thick client installation exists in the form of a web-based LDMS (Wilkerson et al., 2014).
Some LDMS vendors are beginning to rent hosted, thin-client solutions as "software as a
service" (SaaS). These solutions tend to be less configurable than on-premises solutions and
are therefore considered for less demanding implementations such as laboratories with few
users and limited sample processing volumes. Another implementation of the thin client
architecture is the maintenance, warranty, and support (MSW) agreement. Pricing levels are
typically based on a percentage of the license fee, with a standard level of service for 10
concurrent users being approximately 10 hours of support and additional customer service, at
a roughly N450.000 per hour rate.[4]Though some may choose to opt out of an MSW after the
first year, it's often more economical to continue the plan in order to receive updates to the
LDMS, giving it a longer life span in the laboratory (O’Leary, 2012).
2.4.3 Web-enabled
A web-enabled LDMS architecture is essentially a thick-client architecture with an added
web browser component. In this setup, the client-side software has additional functionality
that allows users to interface with the software through their device's browser (Freidman,
208). This functionality is typically limited only to certain functions of the web client. The
primary advantage of a web-enabled LDMS is the end-user can access data both on the client
side and the server side of the configuration. As in a thick-client architecture, updates in the
software must be propagated to every client machine. However, the added disadvantages of
requiring always-on access to the host server and the need for cross-platform functionality
mean that additional overhead costs may arise.
2.4.4 Web-based
A web-based LDMS architecture is a hybrid of the thick- and thin-client architectures. While
much of the client-side work is done through a web browser, the LDMS may also require the
support of desktop software installed on the client device. The end result is a process that is
apparent to the end-user through a web browser, but perhaps not so apparent as it runs thick-
client-like processing in the background. In this case, web-based architecture has the
advantage of providing more functionality through a more friendly web interface. The
disadvantages of this setup are more sunk costs in system administration and reduced

6
functionality on mobile platforms (O’Leary, 2012). The disadvantage of a thick client is in
the installation and update phases of the applications. Users who want the security, high
speed and functionality of a thick client may use Microsoft ClickOnce Technology. This
enables the user to install and run a Windows-based smart client application by clicking a
link in a web page (Friedman, 2008). The software does not need to be installed at each user
workstation one by one. ClickOnce applications can be self-updating; they can check for
newer versions as they become available and automatically replace any updated files (Royce,
2010).
2.4.5 Configurability of Laboratory Database of Management System
LDMS implementations are notorious for often being lengthy and costly. This is due in part
to the diversity of requirements within each lab, but also to the inflexible nature of LDMS
products for adapting to these widely varying requirements. Newer LDMS solutions are
beginning to emerge that take advantage of modern techniques in software design that are
inherently more configurable and adaptable particularly at the data layer than prior solutions.
This means not only that implementations are much faster, but also that the costs are lower
and the risk of obsolescence is minimized.
2.5 Distinction between a LDMS and LIS
Until recently, the LDMS and Laboratory Information System (LIS) have exhibited a few key
differences, making them noticeably separate entities. A LDMS traditionally has been
designed to process and report data related to batches of samples from biology labs, water
treatment facilities, drug trials, and other entities that handle complex batches of data. A LIS
has been designed primarily for processing and reporting data related to individual patients in
a clinical setting. A LDMS may need to satisfy good manufacturing practice (GMP) and meet
the reporting and audit needs of the regulatory bodies and research scientists in many
different industries. A LIS, however, must satisfy the reporting and auditing needs of health
service agencies e.g. the hospital accreditation agency, HIPAA in the US, or other clinical
medical practitioners. A LDMS is most competitive in group-centric settings (dealing with
"batches" and "samples") that often deal with mostly anonymous research-specific laboratory
data, whereas a LIS is usually most competitive in patient-centric settings (dealing with
"subjects" and "specimens") and clinical labs. An LIS is regulated as a medical device by the
FDA, and the companies that produce the software are therefore liable for defects. Due to
this, an LIS cannot be customized by the client.
2.6 Content Management System
Content Management System (CMS) is an application which is used for managing several
methods related with web publishing. Based on Douglas et al., (2006) a CMS generally
can be customized by adding or subtracting specific feature, so that only several
features needed which will be published to the user. Currently, CMS is widely used to
create bulletin board, online trading website, community website, online photo gallerym
and so on. Fraser and Stephen (2002) explained that Content Management System consists
of at least three elements:
 Content Management Application (CMA). CMA will manage application
content components, including picture, text, and so on.
 Meta-content Management Application (MMA). MMA will manage information
carried by application content components.
 Content Delivery Application (CDA). CDA will pick content components, read
the information within, and render the result for user consumption.
One of several various kind CMS is used and implemented for laboratory. It is called
LDMS (Laboratory Database Management System). LDMS, based on Crandall et al.,
(2007) can be explained briefly as a combination between software and computer

7
hardware used in laboratory to manage laboratory sample, user, instrument, standard and
other functionalities using database, report generator and computer network capabilities.

3.0 SYSTEM DESIGNAND ANALYSIS

3.0 Methodology
Research Methodology is the idea within which research is arranged or done according
to plan. This methodology is on the basis of critical examination undertaken, with the
act to find new facts and information that would enhance patient empowerment and
improve the quality of care in terms of efficiency and effectiveness. This methodology used
examines the methods that are necessary to achieve these required subjects, facts and other
relevant information connected to the project research with reduced expenses on effort, time
and money.
3.1 System investigation
System investigation will involves a detailed study of the existing system to identify some
basic database requirements. This will requires a contribution from the users of the existing
system. During the investigation of the existing system, a thorough study will be carried out
on the manual process of Laboratory Database Management System. The activity will give
rise to data that will be collected to facilitate the research work. These data in turn would
from the bases for the effective design of the proposed system after a thorough analysis of the
data have been done.
3.2 Method of Data Collection
The source of data collection used for this project work are categorized into primary
and secondary source of data collection.
3.2.1 Primary Source
These are method of data collection collected from the doctors, Laboratory Attendance,
Laboratory Scientists and nurses in Amaokwe General Hospital Ishiagu. Also more data
from patient, attendants and patrons of the hospital including personal interviews and
observation. Some of the staffs were interviewed to share their feelings and experiences
about the manual system of planning and processing workers and patient care duty. They
stressed that the manual system has not helped them much.
3.2.2 Secondary Source
This includes the use of several Newspapers, Magazines, Journals and surfing the
internet with related articles on Laboratory Database Management System downloads to
enlighten my understanding with a clearer view or picture.
3.3 Analysis of the Existing System
The electronic patient management system is a system that is been carried out in terms of
manual operation, a system in which all the methods of hospital administration is a
manual approach. The approach is such that the hospital staff will record duty information
on a paper or register and kept in a file. Critical analysis of this system reveals that it is
a system prone to a lot of errors and it is not effective. Searching for workers duty
information is time consuming and boring. The system is in such a way that the office is full
of files. This tends to make the office untied. Careful analysis also shows that because of the
complexities of the manual system, information stored is difficult to retrieve. Also because of
the inconsistency of the manual system, at times files are lost because of mismanagement.

8
 AMAOKWE GENERAL HOSPITAL
ISHIAGU

GENERAL OPERATION MANAGEMENT

CHIEF MEDICAL DIRECTOR

Laboratory Lab. Scientist Lab. Attendance

Accountant Acc Manager Cashier Computer Operator

Consultant Consultant personnel Doctors Nurses

Pharmacist Workers

Metron Chief Metron Nurses Mid-Wives

Store Personnel Store Keeper Workers Drivers

Security Chief Security Security Personnel Gates Man

Figure 3.1: Organizational Chart

The organization chart of Amaokwe General Hospital is a function that shows the direction
and chains of commands from the top to the least in office and who is responsible and
answerable to each other to enhance effective communication in the hospital Laboratory for
delivery of an effective and efficient policy.

9
3.3.1 Input Analysis
This deals with the process used to feed data to the system for processing. Here the inputs to
the system are through staff record form, and attendance scheme for Laboratory Unit
form. All these are through which data are supplied to the system which are Employee name,
employee number, sex, age, marital status, address, phone number, L.G.A, State, Job
description, salary, qualification, starting time, ending time, date, work description, and
remark (if any).
3.3.2 Process Analysis
Once the inputs are collected, the obtained data are processed properly for effective use. The
data/information processed is stored in the computer for subsequent use.
3.3.3 Output Analysis
This involves the resultant documentation generated after the processing of
data/information supplied to the system. The output here can be:
1. Printed roster card
2. Store Laboratory Scientist/Attendance data
3.4 Limitations of the Existing System
A lot of problems are associated with the existing system. The existing system
involves the use of manual method to store duty data/information. The system has proved
defective as the objective of the system has also failed. Among the problems
associated with the existing system include the following:
1. Time wasted in searching/sorting for workers duty information.
2. Poor security and protection.
3. Misplacement and mismanaging of checkup and treatment files.
4. A lot of time being wasted by patient while on queue.
3.4.1 Justification for the New System
It is expected that the introduction of the new system, a lot of positive changes will be
noticed. The numerous problem associated with the manual system will be minimized,
if not totally put to an end. The hospital staff that previously had difficulties in
carrying out their work will now have to appreciate it. Head Lab Scientist supervise
Laboratory activities in a variety of settings. While some patient diagnosis specimen is
usually required, the Laboratory supervisor’s new duties to a Laboratory Attendance,
and ensuring that each member of the Hospital Laboratory team is adequately trained. Head
Laboratory Scientist are ultimately responsible for the performance of the Lab
Attendance on their team. This means that they must ensure that ensure that Hospital
Laboratory records are correctly maintained, that report is correctly given at the shift
change, and that equipment and other supplies are in stock.
3.5 System Design
Files are necessary in monitoring of patients Diagnostic Medical Result record since there are
many patients whose Diagnostic Medical Result records must be kept for references purpose.
This fact has given rise to the creation and maintenance of several files within the company.
Below are various files and their uses:
 Request File: This file contains the request from Doctors who wish to access patient
diagnostic/medical result based on their conditions.

10
  Diagnostic File: this is the file that contains information about Laboratory Test and
Result of the Patient.
 Return File: After the Doctors Examination and Recommendations must have been
sent carried out, return forms are sent back to the pharmacy specifying the types
of drugs, cost, dosage and the receipt.
 Complaint File: This file used to help all complaints from Nurses and Medical
Doctors which wish to access patient file on revisit.
3.5.1 Input Design and Specification
The input to the system comes with various forms. Each of these forms has the function of
collecting specific data from the Med-Lab, doctors, staff and patients as the case may be.
The first form is the admission form details that enables the system to prompt the
Doctors/Nurses to fill a form that requires details from the patient concerning personal and
health. The other forms are for Lab Scientist, doctors, Nurses, bed management, patient in
and out, etc are solely intended for the administrative use for the staff. Here, the staff can
add patients, doctors etc that can include the services render by the hospital and change other
things.
Patient Form

Name of Patient
Sex:
Date of Birth:
State of Origin:
Nationality:
Phone No:
Blood Group:
Genotype:
Address:
Guidance:
Patient ID No:
Health Record:

Submit

Fig. 3.2: Patient Form

The patient form is a table to fill patient personal data to be able to gain admission into the
hospital for proper registration process both for inpatient and outpatient. The Patient
Form is an important prerequisite for Medical Diagnosis by Laboratory Scientist in the
Hospital programme. As can be seen from the form above, the Lab-Attendance will now give
the report/result of the patient and transfer information to the Doctor. The Doctor will now
provide details from personal interrogation. This record will help the Hospital staff to

11
administer drug, monitor, supervise and pay close attention to patients even after they
have been discharged.

Laboratory-Diagnostic Form

Name of Lab-Scientist:
Position:
Phone No:
Staff ID No:
Name of Patient:
Patient ID No:
Health Record:
Laboratory Result:
Lab-Attendance Recommendations:

Submi Fig 3.3: Laboratory-Diagnostic Form

t
The Laboratory Diagnostic Form is a table to fill in the result/report of the Patient from
Medical Laboratory Unit of the Amaokwe General Hospital. The Lab-Attendance will
include his/her and results obtain from the lab, as well as recommendations.
DOCTORS FORM

Dr. ID No:
Name:
State:
Address:
Phone No:
Email Address:
Specialization:
Qualification:
Report/Counseling: Submit

12
 Fig 3.4: Doctors Form
The Doctors form, as mentioned earlier, is primarily used by the hospital
administrators to add Doctors that are employed with the hospital, and can accept patients for
proper treatment and admission. Looking at the form above, there has been provision made
for personal details of the Doctors and specialization before saving to the database.
HOSPITAL SERVICE FORM (LAB FORM)

Blood Test:
Genotype:
Hiv/Aid Test:
Pregnancy Test:
STI Test:
Eye Test:
Maternity Test:
X-ray:
Lab-Attendance Recommendations:

Submit

Fig 3.6: Hospital Service Form (Lab Form)

The Hospital Service form is mainly used to add more hospital services that patients must
come for them to be able to get efficient medical diagnosis from Laboratory Unit/care and
treatment in case there be a new service that is mostly needed and can be guaranteed.
3.5.2 Information Flow Diagram

General Operation
Manager

Chief Medical Doctor

Metron

Nurses

Cashier

Computer13Operator

Workers etc.
 Fig. 3.7: Information Flow Diagram
The Information Flow Chart shows how the information are kept and transferred to
various department heads for easy accessibility.

3.6 Database Design

MySQL was used for this system because of its simplicity and easy to use and since my
project is not a commercial as well as the language programme used is attached with it
already. It consists tables. As it would be clumsy outlining all these tables, the three most
prominent and important tables are described below:
1. Patient form: a table to fill patient personal data to be able to gain admission into
the hospital for proper registration process both for inpatient and outpatient.
2. Laboratory-Diagnostic Form: The Laboratory Diagnostic Form is a table to fill in
the result/report of the Patient from Medical Laboratory Unit of the Amaokwe
General Hospital. The Lab-Attendance will include his/her and results obtain from
the lab, as well as recommendations.
3. Doctors Form: The Doctor form can accept patients for proper treatment and
admission. Looking at the form above, there has been provision made for personal
details of the Doctors and specialization before saving to the database.
3.7 System Flow Chart

14
 Fig 3.8 System Flow Chart
The figure above is a system flow chart. The system flow chart is a valuable presentation
aid because it shows how the system’s major components fit together. In effect, it serves as
a system road map. The system flow chart shows the key inputs and outputs associated
with the program. The shape of the symbols indicate the types of input or output devices.

3.7.1 Program Flow Chart

Start

Input experiment parameters

Process laboratory samples

Search results

Is result Yes
Display result
available
?

No

Is result Yes
positive? Display result

No

Is result Yes
Display result
negative?

No

Display laboratory
data

15 Stop
Fig. 3.9: Program Flow Chart
B

Display Lab-Scientist
Information Form

Fill the Form

Submit the Form

View all Lab-Attendance

Fill more
Form

Stop

Display Doctors Information

Form

Fill the Form

Submit the Form

View all Doctors

Fill more
Form

Exit

16
 D

Display Patients Information

Form

Fill the Form

Submit the Form

Reply Display

Fill more
Form

Exit

Display Schedule Form

Fill the Form

Process the Form

Reply Display

Process
Form

Exit
17
 Fig. 3.9: Program Flowchart

Laboratory Database Management System

System Driver

Registration Department DBMS Report Quit

Sub Sub Sub Sub

System System System System

Add Record
Laboratory Staff
Register Lab-
Scientist
Del. Record
List of Lab. Cases
Register Doctor Pharmacy Update Rec.
List of Department

Register Patient Billing View Rec.

List of Services

Create User
List of Lab-Scientist
Exit
Exit

Exit Exit

Fig. 10: Top Down Design of the System

Top-down Design: In a top-down approach an overview of the system is formulated,
specifying but not detailing any first-level subsystems. Each subsystem is then refined in yet
greater detail, sometimes in many additional subsystem levels, until the entire specification is
reduced to base elements. Once these base elements are recognized then we can build these as
computer modules, which will put up together to make a possible working system.

18
System Block Diagram
The diagram show the sequence of operation of the new Laboratory Database Management
System and the different stages or steps involved in it.

Input Lab Technician Info

Sample Experimental

Conduct Experiment

Sample Results
Fig. 11: System Block Diagram

4.0 SYSTEM IMPLEMENTATION, TESTING AND INTEGRATION

4.1 Choice of Development Tools
The development tools are defined as the basic required devices that are used during
the design of the computer based processing and publishing system to enable the
programmer design an effective and efficient of software. There were five components that
were needed to be added in the system when the development of the system was yet at an
initial stage . These components can be referred to as the software development tool. The
under listed tools were chosen and used because of their features and ease of accessibility.
These tools are briefly discussed below:
4.1.1 Operating System
The programming work was carried out on one computer which ran windows XP, Window 7
and 8 as the operating system. In the final implementation.
4.1.2 Choice of programming Language
After careful observation and analysis of the existing system, the current system was a stone
alone system handle by the Laboratory Attendants or Technicians in the Hospital Laboratory,
hence the use of Php will be proposed for the design phase, while MySQl will be used as
database at the back-end. The choice of the programming language is relevant because of the
interactive tools and command, text area, and other project properties embedded in the
language.
4.2 Hardware and Software Requirements
4.2.1 Hardware Requirement
The hardware components of a computer system refers to the physical part that
makes-up the computer system. For an effective operation, the system can be
implemented provided the following hardware components are at least met. The
following hardware is required for the efficient work of the system:

19
Hp Laptop with following configurations;
1. Storage: 500 gigabyte of storage.
2. Memory: 4GB of ram and above.
8. Printer: Optimal (Colored/black and white)
4.2.2 Software Requirements
Computer software is a collection of computer programs and related data that provides
the instructions for telling a computer what to do and how to do it. In other words,
software is a set of programs, procedures, algorithms and its documentation concerned
with the operation of a data processing system. Program software performs the function of
the program it implements, either by directly providing instructions to the computer
hardware or by serving as input to another piece of software. The following list of
software are needed for adequate implementation of the system
1. Window windows 8 and above
2. PHP
3. MYSQL
4. Anti-virus program (updated).

4.3 System Implementation

Implementation is the realization of an application or execution of a plan, idea, model,
design, specification, standard, algorithm or policy. It is also the realization of a technical
specification or algorithm as a program, software component or other computer system
through programming and deployment. The purpose of system implementation is to
make the new system available to a prepared set of patients and members of staff of
Amaokwe General Hospital, and also positioning an on-going support and maintenance
of the system within the hospital. This entails that all steps would be taken to educate
both the patient, doctors etc on the use of the new system and confirming that all data
required at the start of operations is available and accurate , and validating that the business
functions that interact with the new system are functioning properly.
4.4 Project Schedule
The project is expected to kick-start after official approval by the project Supervisor from
Department of Computer Science Technology, Federal College of Agriculture Ishiagu,
Ebonyi State. The Project will last for a period of 5-6months under working condition.
Conclusion

A Laboratory Database Management System (LDMS) is software that allows you to

effectively manage samples and associated data to improve lab efficiency. By using a LDMS,
your lab can automate workflows, integrate instruments, and manage samples and associated
database. A good commercial LDMS will help you present your lab in a professional manner
to collaborators and granting bodies by enabling you to manage samples and workflows from
end-to-end, ensuring the highest quality traceable results, and substantially improving overall
lab efficiency and operations.

20
 BIBLIOGRAPHY
Crandall, Karen S.; & Auping, Judith V. (2007). Laboratory Information Management
System (LIMS)-A Case Study. Ohio, USA: National Aeronautics and Space
Administration (NASA). 18 p.
Douglas, Robert T.; Little, Mike; & Smith, Jared W. (2006). Building Online Communities
with Drupal, phpBB, and Wordpress.USA : Apress. 561p.8.
Fraser, Stephen R.G. (2002). Real World ASP.NET : Building a Content Management
System. USA : Apress. 405 p.9.
Friedman, Bruce (2008). "LIS vs. LIMS: It's Time to Blend the Two Types of Lab
Information Systems". Lab Soft News. Retrieved 7 November 2012.
Gibbon, Dr. Gerst. (2006). A Brief History of LIMS. USA : Laboratory Automation and
Information Management (Journal Issue 32, 2006).
Gibbon, G.A. (2006). "A brief history of LIMS" (PDF). Laboratory Automation and
Information Management. 32 (1): 1–5.
Khan, Masood N.; Findlay, John W. (2009). "11.6 Integration: Tying It All
Together". Ligand-Binding Assays: Development, Validation, and Implementation in
the Drug Development Arena. John Wiley & Sons. p. 324.
McLelland, Alan (2008). "What is a LIMS - a laboratory toy, or a critical IT
component?" (PDF). Royal Society of Chemistry. p. 1.
O'Leary, Keith M. (2012). "Selecting the Right LDMS: Critiquing technological strengths
and limitations". Scientific Computing. Pp.98
Royce, John R. (2010). "Industry Insights: Examining the Risks, Benefits and Trade-offs of
Today's LDMS". Scientific Computing.
Skobelev; D. O. T. M. Zaytseva; A. D. Kozlov; V. L. Perepelitsa; A. S. Makarova
(2011). "Laboratory Database management systems in the work of the analytic
laboratory"(PDF). Measurement Techniques. 53 (10): 1182–1189.
Skobelev; D. O., T. M. Zaytseva; A. D. Kozlov; V. L. Perepelitsa; A. S. Makarova
(2011). "Laboratory database management systems in the work of the analytic
laboratory"(PDF). Measurement Techniques. 53 (10):1182–1189.
Tomiello, Kathryn (2007). "Regulatory compliance drives LIMS". Design World. Pp.89.
Retrieved 7 November 2012.
Vaughan, Alan (2006). "LIMS: The Laboratory ERP". LIMSfinder.com. Retrieved 7
November 2012.
Wilkerson, Myra; Henricks, Walter; Castellani, William; Whitsitt, Mark; Sinard, John (2014-
08-04). "Management of Laboratory Data and Database Exchange in the Electronic
Health Record". Archives of Pathology & Laboratory Medicine. 139: 139-147.
Wood, Simon (2007). "Comprehensive Laboratory Informatics: A Multilayer
Approach" (PDF). American Laboratory. p. 1.

21