Chapter 1

Introduction

Laboratory Management system patient record Page 1

 1.1Introduction:
Laboratory Management system Patient record (LMSPR) is an automated system that is used to
manage patient information and its administration. It is meant to provide the Administration and
Staff, with information in real-time to make their work more interesting and less stressing.

Nowadays, Many application system to interact with user .it is because many organization want
computerize record keeping rather than manual system .patient management system is an example
of computerize system that will be developed for administrator to managed the record of patient
several modules will be application to the lab management system

Numbers of patient record detail that are stored in system .searching for information with respect to
certain criteria could be difficult .we make use of database to provide the required details instead
manual system. The information regarding patients can be stored in database .it can update the table
,field (patient details, patient added , patient record delete searching ) enter the id no of patient and
found the detail of patient

According Jauntz the emergence of computer based information system has changed the world a
great deal, both large and small system have adopted the new methodology by use of personal
computer; to fulfil several roles in the production of information therefore computerizing the
documentation of patient record to enable easier manipulation of the input process and output will
bring us to this existing new world of information system.

According tang In examine the document system that in existence at the hospital that is mostly
manual much importance has been placed on creating a system that document the inpatient record
using a computerized database system with a secure procedure for accessing it.

Laboratory Management system Patient record (LMSPR) are extensive, coordinating information
system to mange patient data in hospital with the administrator process. Manual system has this
problem Maintain the customer’s record. Time consuming. Updating problems. Manage large
amount of data to insert. It was not offer a user friendly work envoirment Health care canters depend
on patient information for the efficient administrator process, for batter management the principle
objective of PMS is to streamline the stream of data from the hospital toward decision making for
patient planning and management in an enhanced and effective ways.

Laboratory Management system patient record Page 2

1.2 Problem Statement:

The absence of a well established information system to serve patient and staff has led to inconveniences.
This has tantamount to the loss of patient and staff records. This is basically because of the weakness of the
existing system which includes over reliance on paper based work. Paper files consume a lot of the office
space, slow recording, processing and retrieval of patient details. Accessing and sharing of information by
different departments is difficult due to poor information management.

Hard to manage the record of patient for example if record found anyone patient it is very difficult to search
their record in manual system. it is also very difficult to edits or delete record in manually system . The
record data easily lost if the administrator uses manual system. So this issue will create another bog system
to the administrator. Manual system has this problem Maintain the customer’s record. Time consuming.
Updating problems. Manage large amount of data to insert. It was not offer a user friendly work envoirment

1.3 Motivation:

Today, Many application system to interact with the user it is because many organization want computer
record keeping rather than manual system patient management system .In Pakistan other hospital keep
record of patient computerized system but zainab hospital used manual system now this hospital want keep
record in computerized system it is main motive of this project .

1.4 Objectives:

Main Objectives Our major objective is to develop an operational Patient Management System for zainab
hospital. A goal or objective is a project it is roughly similarly to purpose of aim, the anticipated result
which guides reaction or an end . It is the user friendly application which reduces the burden and helps to
manage all sections of laboratory like patient reports etc., which improve the processing efficiency.
Including safe data store about patient reports as well as fast searching, delete and update of report It deals
with the automating this project embarks specific objective as fellow

1. To developed the manual laboratory management system into computerize base laboratory
management system
2. To develop the computerized lab management system such as testing blood simple off different
diseases, keeping record of patient.
3. To developed the lab administrator easy to managed data ,troubleshooting keep record of patient
Laboratory Management system patient record Page 3
 4. Admin can view patient record.

5. Admin can upload report pattern.

6. Admin can add physician staff.

7. Admin can add blood test record.

8. Admin can received report from physician and can view detail

9. Physician can view record of patient

10. Physicain can generate report of patient

1.5 Scope of project:

This project is basically designed for zainab hospital. This hospital provides a lot of services to patients
which includes; Daily treatment of patients, Admission of patients, Keeps records about inpatients and
outpatients respectively, The following are the language confined within the system to enable
development and implementation. The database implementation was achieved using My SQL for the
database development, server side scripting was done in java embedded in html, and java web server
wills facilitate simultaneous processing. This system can be used by only team member and
administrator of a particular hospital .The database can be used by team members in order to search, edit
and add patient detail. The database can be accessed only after installing the software on local system
This software can be used by only a single user at any instant. The system usage is confined to usage by
single organization.

1.6 SDLC MODEL:

A framework is that describe the activities performed at each stage of a software development project.
SDLC is the process of the understanding how an information system (IS) can support business need,
designing the system built it and delivering it to user. The SDL composed have four phase (planning,
Analysing, Design implementation) .The SDLC traces the history (lifecycle) of a developing
information system .structure designed methodology is waterfall developing with waterfall developing
,analyst and user process is sequence from the next mapped out and evaluated planning analysing design
and implementation system.

Laboratory Management system patient record Page 4

1.6.2SDLC MODEL:

1.6.2 .1 Agile Model:

Speed up or bypass one or more life cycle phases .usually less formal and reduced scope .used for time
.critical application. used in organization that employ descomplain methods. By breaking the product into
cycle ,the Agile model quickly deliver a working product and is considered a very realistic developing
approach .The model produced ongoing released ,each with small incremental changed from the previous
released .At each iteration ,the product is tested this model is emphasis ,interaction, as the customer
,developer and tester worked together throughout the project

1.6.2.2 V-shaped Model:

A variant of the waterfall that emphasize the verification and validation of the product .Testing of the
product is planned in parallel with a corresponding phase of development. Also now as the verification and
validation model , the V-shaped model grew out the waterfall and is characterized by a corresponding
testing phase for each developed stage

1.6.2.3 Rapid Model

RAD reduced cycle time and improved productivity with fewer people means lower costs .Time-box
approach mitigates cost schedule risk. Customer involved throughout the complete cycle minimizes risk of
not achieving customer satisfaction and business needs .

1.6.2.4 Incremental Model

Risk finding ,schedule program complexity, or need for realization of banifites.Most of the requirements
now up-front but are expected to det basic functionality to the market early on projects which have lengthy
development schedules .On a project with new technology

1.6.2.5.Spiral Model:

Provide early indication insurmountable risk without much cost. Users see the system early because of rapid
prototyping tools .critical high-risk functions are developed first . the design does not have to be perfect
users can be closely tied to all life cycle steps . early and frequent feedback from user .

Laboratory Management system patient record Page 5

1.6.2.6 Waterfall Model:

Waterfall model is easy to understand and easy to use .provide structure to inexperienced
staff milestones are well understood sets requirement stability. works well when quality is more important
than cost

1.7 Chose Model:

Waterfall SDLC Model :

waterfall Sdlc model is perfect for the system because this system required quick respond and satisfy the
user and required changing in this system patient management system is motive to advance technique .This
system required quick search result

1.8 Procedure:
The project procedure that used in development of the system is the System development Life Cycle
(SDLC). SDLC is the process of the understanding how an information system (IS) can support business
need, designing the system built it and delivering it to users. The SDLC composed have four phases.
Planning, Analysis, Design and Implementation. The SDLC traces the history(lifecycle) of a developing
information system. Structured designed methodology is waterfall development with waterfall
development, analyst and user proceed is sequence from the next can mapped out an evaluated Planning
analysis Design and implementation system

1.8.1 Planning:
In planning system, to develop a new system which is first step to identify a need for the laboratory
management system and also plane how to develop the functional requirements of a system. This will
include determining whether a business problem.

1.8.2Requirment Analysis:

In this phase, I have analyzed considers the current system and investigates any problem associated with it.
There are many problems with current system due to manual work. Other sources of information about
system and the new requirement would be investigated at this time.

Laboratory Management system patient record Page 6

1.8.3Designing:

After the requirements have been determined, the necessary specifications for the hardware software people
and data resources and the information products that will satisfy the functional requirement of the proposed
system can be determined. I will create the system design by review the work with the scope to ensure the
design meets the objective and requirement of the patient record keeping System.

 User Interface Design is concerned with how admin search record of patient information to the
system and with how the system presents information back to them.
 Data Design is concerned with how the data is represented and stored within the system. Finally,
Process Design is concerned with how data moves through the system, and with how and where it is
validated, secured and/or transformed as it flows into, through and out of the system.
 System design phase, documentation describing the three sub-tasks is produced and made available
for use in the next phase.
1.8.4 Coding:
At this stage each unit is design through coding .for this process a specific language is required like html,php
and bootstrap. At this stage we designed all modules like Admin ,physician and patient separately by using
software tool
1.8.5 Testing:
At this stage unite is test to check if it is performing the same functionality for which it is design. Each and
every function is test and remove error. if the system is performing accurate functionality for which it is
designed than it is delivered to the requirement of customer
1.8.6 Implementation:

The implementation phase is described as those activities that begin when the system design has been
completed. These phases are producing software code according to plan, analysis and system design that
have been done. Coding and debugging is the act of creating the final system. The requirement
documentation should be referred to throughout the rest of the system development process to ensure the
developing project aligns with the needs and requirements or scope. The system also is tested to evaluate its
actual functionality in relation to expected or intended functionality

Laboratory Management system patient record Page 7

1.9 Software Tools:

One of the most difficult tasks after system requirements are known is determining Whether particular
software is capable of meeting the system requirements or Not. For those that do so further scrutiny is
needed to determine the desirability in comparison With other conditions. The choice of software is a very
important factor to be considered during. The development phase of the new system because new system is
totally dependent on the software It’s using data to handle and the cost of programming.
These are following software:

 Any windows based operating system.

 APP Sever for running PHP and MYSQL database.
 IDE (Dreamweaver) for developing code
 Adobe Photoshop (designing tools).
1.9.1 App Server:
App server has been developed high professional and easy too install consisting of apache (HTTP web
server) PHP MYSQL and SQL database management system. Such application server client can include
GUI(graphical user interface) running on Pc, a web server and other application server.

1.9.2 SQL:

SQL Server is Microsoft's relational database management system (RDBMS). It is a full featured database
primarily designed to compete against competitors Oracle Database (DB) and MySQL. Like all major
RBDMS, SQL Server supports ANSISQL, the standard SQL language.

1.9.3 PHP:

PHP (recursive acronym for PHP: Hypertext Pre-processor) is a widely-used open source general-purpose
scripting language that is especially suited for web development and can be embedded into HTML.

Laboratory Management system patient record Page 8

1.

Chapter 2
Literature and Analysis

Laboratory Management system patient record Page 9

2.1 Literature:
Medical records form an important part of the management of a patient. it is important for the doctor of
patient of two part reason. The first one is that it will help them in the scientific evaluation of their patient
profile, helping in analyzing the treatment result, and plan treatment protocol. This system also in planning
governmental strategies for future medical care.

The legal system sallies mainly on documentary evidence in a situations . where medical negligence this
is very often the most important evidence deciding on the sentencing or acquittal of the doctor ,With the
increasing use of medical insurance for the doctor for treatment ,the insurance companies also required
proper record keeping to prove the patient demand for medical expense improper record keeping can result
in declining medical claims .

it is dishearten to note that in spite of knowing the important of proper record keeping it is still in a absent
stage in Pakistan it is wise to remember that “poor record defence medical record means no defence ,medical
record include a variety of documentation of patient history , clinical finding diagnostic that test result ,
preoperative care, operation notes , post operative care, and daily notes of a patient progress and
medication .

this computerize system is very important for patient record management system .this system include see
issue of date and time .Administrator can easily search record of patient and delete record of patient .it is
wise to duplicate copy of the referral note with the patient signature .the fact of the patient did note go
immediately on reference as advised could proved by the duplicate copy of the referral note kept by doctor.

The hospital offers 24 hours services to its staff and the entire population. The records of patient in zainab
hospital have over time been run down due to large number of patient ,this led to poor record keeping since
it`s paper base system .the reason why the current system used is manual has led to a variety of problems
and these include ; un necessary duplication of the data especially for impatient and outpatient

A computerize patient management system will be important in light of fact that, there are a considerable
measure of challenges in keeping up a lot of data on paper ,particularly as there is usually no backup for the
data, access to data can be tedious in the event that require for the search of a file , and accuracy is required
in the recording of key data, and the administrator cannot all that is composed on the tremendous measure of
paper to be utilized ,Hence , it is very important for health organization like hospital and clinics to have a
computerized patient management system.

Laboratory Management system patient record Page 10

2.2Existing system:
In kabirwala there is no have computerized system for patient keeping record management system .patient
record keeping managed is manually in file that are time consuming task for admin .manually system is very
difficult to keep record of patient for long time. for the first time we are develop a system that can keep
record of patient in computerized system after analyse this system provide a efficient system for admin this
system provide many benefits .this computerized system save time of admin

2.2.1Hina kashif hospital:

Hine Kashif hospital record maintain of patient in computerized in laboratory . in this laboratory has a
admin . doctor referred the patient to laboratory for different decease .when patient come laboratory admin
record enter of patient of their system . then he test of blood simple .after testing blood simple he generate
report of patient and enter record of patient date, time, month.

2.2.2 state of Art of patient record Management system :

Lian defined a medical record as confidential information kept for each patient by health care professional or
organization. it contain the personal detail of patient such as name, address, date of birth a summary of the
patient medical history and documentation of each event including symptoms, diagnosis. Treatment and
outcome relevant documents and correspondence are also including. This system provide and treatment
provided to ensure appropriate health care information from medical record also provide essential data for
monitoring patient care ,clinical audit and accessing patterns of care and services delivered . the
management information system enables the medical record to form first link in the information chain
producing the personalized aggregate coded data for statistical.

2.2.3 Emmanuel Medical Centre:

It is expensive due to high administrative costs incurred in terms of high stationary costs, printing patient’s
cards, data entry and capture, data analysis and cleaning for storage purposes.Emmanuel Medical Centre
was able to efficiently store and keeps track of their patient’s records; the system provides an easy
mechanism for doctors and nurses to retrieve the prescription they had earlier written so as to avoid making
wrong prescriptions. The management was able to budget and improve the service delivery of the hospital.
The project produces a Patients Records Management System that enabled Emmanuel Medical Centre keeps
track of their patient’s records.
Accessing patient’s files and records at Emmanuel Medical Centre is manually in all the departments,
making it very labour intensive and ineffective. This process involves very large amounts of data, thus

Laboratory Management system patient record Page 11

consuming a lot of time. The cause of data retrieval, loss of information results since the nurse or the person
involve in data search dealt with very many files for different years. This was actually cumbersome and
extremely hectic. This trend was good to be dealt out with for better services to the patients in hospitals.
This process had so many inconsistencies and inconveniences like patients losing their health cards or their
files being misplaced. Therefore an automated system helps to keep track of patient’s records and medical
bills making it easy to determine the state of new and continuing patients.
2.3Purpose system:
Patient management system will have three modules admin, physician, patient. When
doctor referred patient for testing then patient go laboratory for simple testing .admin enter record of patient
like as they enter name ,address, cell no etc admin also give a patient specific id every patient .this id of
patient make unique every patient and this id separate patient each other .then patient go physician for
simple testing .physician generate a report of patient .in this report have information of patient and about his
disease . when admin required search design a user friendly system that will capture, store and retrieve the
stores records. This system designs a database and its application that will generate reports concerning the
evolution of the store. this system develop a secured store system which can access storage with a huge
amount of data designed This is an automated system that keeps track of all patients’ details and enables
easy access, retrieval and storage of the patient’s information. The management was able to budget and
improve the service delivery of the hospital. The system is to ensure security and integrity of information
captured by enhancing restricted login and rights to respective entity given according to regulations and
policies of zainb hospital Patient Management Software (PMS) is software that is regulated as a medical
device. It is software that is used to acquire medical information from a medical device to be used in the
treatment or diagnosis of a patient. It was also used as software that is an adjunct to a medical device and
directly contributed to the treatment of the patient by performing analysis, or providing treatment or
diagnosis functionality that replaced the decision and judgment of a physician. A multi-access system to
allow the patient or the professional to access any service available adapted to his/her better convenience
and needs, including telemonitoring services if required by the patient.
Patient management system has following feature:
a) User friendly
b) Patient update
c) Admin alert
d) Weekly update
e) Quick report generate
f) Quick search operation

Laboratory Management system patient record Page 12

 g) Quick edit operation
h) Time saving
i) Easily enter data
j) Online report search
k) Online blood test search
l) Delete Record easily

2.4Information Gathering :

Information gathering is a process of deeply analyzing the current or existing system . We used the
following methods during data collection: Observation, Interviewing and Questionnaires as our research
methods. Through this we were able to collect raw data on PMS at We went to the hospital and observed
their daily as regards their current system and they were manually recording the patients‟ records as
specified by the receptionists, doctors, pharmacist and cashier. A follow up was made to determine the time
it took to carry out the patient record management. We observed the system‟s weaknesses like it was

2.4.1Interviews:

An interview is a conversation between two or more people (the interviewer and the interviewee) in a
context where the questions are asked by the interviewer to obtain information from the interviewee. We
used the following methods during data collection: Observation, Interviewing and Questionnaires as our
research methods. In this method, there was interaction between us, the researchers and the Staff. Interviews
will be conducted with the medical supridendant and some potential employees to find out what difficulties
they encountered with the existing system.

2.4.2Quetionsenries :

Admin

Q#1. When patient come to blood sampling or testing ?

Ans. When doctor preferred for blood testing.

Q#2 where u have record of patient?

Ans i have a register and put record of patient

Q#3 Do you provide a number card of patient ?

Laboratory Management system patient record Page 13
Ans No we do not provide card of patient

Q#4 when patient record update?

Ans No update record

Q#5 what timing of laboratory open and close?

Ans laboratory timing open and close with hospital timing

Q#6 How patient record search and delete ?

Ans search and delete patient record paper base

Q#7 Do you provide online report testing ?

Ans NO, provide online report testing

Q#8 Do you provide online report searching ?

Ans NO, provide online report searching

Physician:

Q #1 what procedure of blood sampling?

Ans we take blood simple of patient by injection

Q #2 Do you generate report of patient?

Ans yes we make report of patient

Q #3 what information in report about patient?

Ans in this report information about patient disease

Q #4 How much blood take for simple testing?

Ans we take blood 1cc for simple testing

Q #5 Do you have patient record upload?

Ans NO , have patient record upload

Laboratory Management system patient record Page 14

2.5Comparison table :

Content Hina kashif Emmanuel Medical state of Art of Purpose system

hospital patient record
Centre
Management
User friendly yes yes yes yes
Weekly update No yes yes yes
Admin alert No yes yes yes
Security No yes yes yes
Physician alert No No No yes
completeness No yes No yes
comprehensive yes yes yes No
Speed No yes yes yes
Effectiveness No No yes yes
Online test search No No No Yes
Online report search

2.6Feasibility report:

Feasibility report describe how our purposed system is feasible to the

customer .Here are some feasibility are given .

2.7.1Operational Feasibility:

` Purpose system will be operationally feasibility to the users. It will response quickly
it will performs the operations efficiently for which it is developed .if user perform click operation it will
response according to the click.

2.7.2Economically Feasibility:

Purpose system is economically feasible to zainb hospital it will not need

additional server they will add this system as a module to their existing server and we are providing ir to our
hospital free of cost

2.7.3Technical Feasibility:

Purpose systems will technical feasible. if any change will needed to implement in the
system then it will possible without changing or replacing

Laboratory Management system patient record Page 15

 Chapter 3
Design

Laboratory Management system patient record Page 16

3.1 Introduction:
Chapter three majorly focuses on the various basic methodologies for the research
project the study analysis that is carried out, the key elements of the system design methods to be used. The
main goal is to implement a research project that would be used by zainab hospital.
3.2 Data flow diagram (DFD):
Representation of the system was done by use of a Data Flow
Diagram. This describes the design that includes: the structure, behaviour, and interaction of the different
components in the system, the context diagram and the architecture of the system.
KEY SYMBOLS
Symbol Description

External entity It is outside the context of the system and can be any class
of people, organization or another system.

Its function is to supply or receive data. It is the originator

or receiver of information outside the scope of the system
portrayed in the data flowing.

Data flow It shows the movement of data and is a pipeline carrying

data through the system. These show the movement of data
between processes, external entities, and data stores in a
DFD

Process This portrays the transformation of input data flows to

output data flows in DFDs. Incoming data flows are
processed or transformed into outgoing data flows.

Data store A temporary /time delayed repository that processes can

add data to/or retrieve data from.

Laboratory Management system patient record Page 17

3.2.1Context level :
Context level diagram is the most basic data flow diagram. It provides a broad view that is easily
digestible but offers little detail. Context level data flow diagrams show a single process node and its
connections to external entities.

Figure 3.1

A context level data flow diagram (DFD) provides an at-a-glance look at the information
system and ways its changing data with outside entities. they are often use high level
planning The context level is explain the system .system provide different feature of system
.System provide admin access the add patient record ,search record ,update record, manage
physician and view report. Other side system given access of physician that physician can
view patient record and generate report of patient .patient can view report

Laboratory Management system patient record Page 18

3.2.2Level0:

Figure 3.2

3.2.3Level 0:
A level 1 data flow diagram (DFD) is more detailed than a context level DFD but not as detailed as
a level 1 DFD. It breaks down the main processes into subprocesses that can then be analyzed and improved
on a more intimate level.

3.2.4Level 1:
A level 1 data flow diagram (DFD) offers a more detailed look at the process that make up
the information system then a level 1(DFD) does, it can use to plan and record

Laboratory Management system patient record Page 19

  Admin Add patient Process

Figure 3.3

Admin login the system and enter record of patient and submit the record this record stored
in the database and then physician and patient login their system and view record after this
remove the authentication

 Admin update patient record:

Figure 3.4

Laboratory Management system patient record Page 20

Figure 3.4 in admin login the system and go to update page enter required data and click the update
operation press this record stored in the database and change data of the required data .physician login the
system and can view the update record

 Admin search record

Figure 3.5

Figure 3.5 admin and user can search data of patient .they enter login their system and enter the required
data then search the required data

 Admin report pattern

Figure 3.6

Laboratory Management system patient record Page 21

 Physician Blood Test

Figure 3.7

 Physician Blood Report

Figure 3.8

Laboratory Management system patient record Page 22

3.3 Use case:

The system specification describe the functional or non-functional requirement posed system
use case scenario is a description that illustrate step by step ,how a user is intending to use
system essentially capturing the system behaviour from the user point of view .a use case
scenario in this system describe the working of entity

List of Actors:

There are three actors.

 Administrator.

 Physician.

 Patient.

Figure 3.9

3.3.1Admin:

Admin can inter data of patient ,update patient search ,delete record of patient saved the patient record
admin also upload report pattern and add physician record

Laboratory Management system patient record Page 23

3.3.2Physician:

Figure 3.10

Physician:

Physician take simple test of patient and according to simple test he generate report .

3.3.3Patient:

Figure 3.11

Patients will self enter record /information given blood simple and view report

Laboratory Management system patient record Page 24

3.4 Sequence Diagram:

 Admin Sequence diagram

Figure 3.12

3.4.1Admin:
Admin sequence diagram admin first login the system then he can work on other process after login the
system admin can add patient record manage, physician record, update patient record search record, delete
record and view report

Laboratory Management system patient record Page 25

  Physician

Figure 3.13

3.4.2Physician Sequence Diagram:

Physician sequence diagram first physician login system then he can work on other process Physician can
view patient record and simple testing and generate.

Laboratory Management system patient record Page 26

  Patient sequence diagram

Figure 3.14

3.4.3Patient sequence diagram:

Patient give simple for testing and view report

Laboratory Management system patient record Page 27

3.5Database Designing:

3.5.1Project Design:
In order to design a website, the rational database must be designed first. Conceptual design can be divided
in to two parts.

 Data Model
 Process Model

The data model should be focuses on what data should be stored in the data model while the data process
deals with how the data will processed. To put this in the context of the rational database, the data model is
used to design the rational tables. The process model is used to design the quires that will access and
perform operations on those tables.

3.5.2 Data Model:

A data model is a conceptual representation of the data structures that are required by a database. The first
step in designing the database is to develop an Entity Rational Diagram (ERD). ERD serves as a blue print
from which a rational database maybe deduced.

3.5.3 ERD:

ERD is a graphical representation of an information system that shows the retaionalship between people
objects places concepts or events within that system. An ERD is a data modeling technique that can help
define business processes and can be used as the foundation for a rational database.

Key Elements of ERD:

Although they look complex, an erd has three simple components.

 Entities:
 Relationship:
 Attributes:

3.5.4 Entities:

An entity is a thing. In business domain terms, it’s a concept or glossary level term. In rational database term
it is the table. Entity refers to anything about which data is collected. Entities that are involved in Laboratory
Management System patient record are as follows:

Laboratory Management system patient record Page 28

(1)Admin

(2)Patient

(3)Physician

(4)Blood Test

(5)Blood Report

(6)Front desk

(7)Patient History

3.5.5 Attributes:

When each entity, there can be more than one attribute. Attributes provide detailed information about the
concept. In a rational database attributes are represented by the fields where the information inside a record
held.

 Admin

Figure 3.15

Attribute

Admin_id:

(key,required,stored,single valued,simple)

Admin_Name:
(non-key,required,stored,single valued,composit)

Admin_password:

(non-key,required,stored,single valued,simple)

Laboratory Management system patient record Page 29

  Patient

Figure 3.16

Attribute:

Patient_id:

(key,required,stored,single valued,simple)

Patient Name:

(non-key,required,stored,single valued,composit)

Patient Cell:

(non-key,required,stored,multi valued,simple)

Patient Age:

(non-key,required,drived,single valued,simple)

Patient Gender:

(non-key,required,stored,single valued,simple)

Patient Address:

(non-key,required,stored,multi valued,simple)

Patient Type:

(non-key,required,stored,single valued,simple)

Laboratory Management system patient record Page 30

Database Design Phase

ERD representation of entity relationship

Admin and Patient :

A admin may managed one or more patient record .A patient must have one admin

1) A1 p1

A2 P2

A3 P3

Figure 3.17

ADMIN and PATIENT

Admin & Patient

Cardinality: One Mandatory-one Many

Degree: Binary

Relation: One to many

Relationship: Manage record

Laboratory Management system patient record Page 31

  Physician

Figure 3.18

Attribute:

Physician_id:

(key,required,stored,single valued,simple)

Physician Name:

(non-key,required,stored,single valued,composit)

Physician Cell:

(non-key,required,stored,multi valued,simple)

Physician Designation:

(non-key,required,stored,single valued,simple)

Physician user name:

(non-key ,requird,stored,single valued,composit)

Physician Password:

(non-key,required,stored,single valued,simple)

Laboratory Management system patient record Page 32

Database Design Phase

ERD representation of entity relationship

Admin and Physician :

A admin can managed record of physician one or more . A physician must have one Admin

2) A1 Phy1

A2 Phy2

A3 Phy3

Figure 3.19

ADMIN and PHYSICIAN:

Admin & Physician

Cardinality: One Mandatory-one Many

Degree: Binary

Relation: One to many

Relationship: Manage

Laboratory Management system patient record Page 33

  Front desk

Figure 3.20

Front desk Attribute:

Front desk _id:

(key,required,stored,single valued,simple)

Front desk name:

(non-key ,required, stored single valued,composit)

Front desk Cell:

(non-key,required,stored,multi valued,simple)

Front desk type:

(non-key,required,stored,multi valued,simple)

Front desk Detail:

(non-key requird,stored,single valued,simple)

Laboratory Management system patient record Page 34

Database Design Phase

ERD representation of entity relationship

Admin and Front desk :

A Admin can manage record of front desk one or more. A front desk must have one Admin

3) A1 Front1

A2 Front2

A3 Front3

Figure 3.21

ADMIN and FRONT DESK :

Admin & Front desk

Cardinality: One Mandatory-one Many

Degree: Binary

Relation: One to many

Relationship: Manage

Laboratory Management system patient record Page 35

  Blood Test

Figure 3.22

Attribute Blood Test

B_Test id:
(key,required,stored,single valued,simple)

B_Test Name:
(non-key,required,stored,single valued,composit)

B_Test Description:
(non-key,required,stored,single valued, single)

B_Test Cost;
(non-key,required,stored,single valued,simple)

B_Test Delivery Time:

(non-key,required,stored,single valued,simple)

Laboratory Management system patient record Page 36

Database Design Phase

ERD representation of entity relationship

Physician and Blood Test :

A Physician must take blood simple of patient one at a time . A blood simple must have one physician at a
time

4) phy1 B_test1

phy2 B_test2

phy3 B_test3

Figure 3.23

PHYSICIAN and BLOOD TEST

Physician & Blood Test

Cardinality: One Mandatory-one Mandatory

Degree: Binary

Relation: One To one

Relationship: Take

Laboratory Management system patient record Page 37

  Blood Report

Figure 3.24

Blood Report Attribute:

B_report id:
(key,required,stored,single valued,simple)

B_report date:
(non-key,required,stored,single valued,simple)

B_report status:
(non-key,required,stored,single valued,simple)

Database Design Phase

ERD representation of entity relationship

Physician and Blood Test :

A admin Generate report of patient must one at a time . A blood report must have one physician at a time

5) phy1 B_Report1

phy2 B_Report2

phy3 B_Report3

Laboratory Management system patient record Page 38

 Figure 3.25

PHYSICIAN & BLOOD REPORT

Physician & Blood Report

Cardinality: One Mandatory-one Mandatory

Degree: Binary

Relation: One To one

Relationship: Generate

 Patient and Blood Report

Figure 3.26

Laboratory Management system patient record Page 39

Database Design Phase

ERD representation of entity relationship

Patient and Blood Test :

A patient view report must one at a time . A blood report must have one patient at a time

6) p1 B_Report1

p2 B_Report2

p3 B_Report3

PATIENT and BLOOD REPORT:

Patient & Blood Report

Cardinality: One Mandatory-one Mandatory

Degree: Binary

Relation: One To one

Relationship: View

Laboratory Management system patient record Page 40

  Patient and Blood Test

Figure 3.27

Database Design Phase

ERD representation of entity relationship

Patient and Blood Test :

A patient give blood must one at a time . A blood test must have one patient at a time

7) p1 B_Test1

p2 B_Test2

p3 B_Test3

PATIENT and BLOOD TEST

Patient & Blood Test

Cardinality: One Mandatory-one Mandatory

Degree: Binary

Relation: One To one

Relationship: Given

Laboratory Management system patient record Page 41

.Keys
A key is a distinct for each individual entity in an entity set. Key attributes are the attributes whose values are
uniquely identified and do not exist again.

1- Primary Key
The primary key is one or more column in a table used to uniquely identify each row to the table. Primary
key values can’t be null and must be unique across the column. A multicolumn primary key is called
Composite Primary Key.These are following primary keys in my database

Adminid,patientid ,blood_testid,blood _reportid,reported,Frontdesk id,physicianid

2- Foreign key

Foreign key represents relationships between the tables or relations. A foreign key is a column(or a group
of columns) whose values are derived from the primary/unique key of the same or some other tables

These are the following foreign keys in my database:

Patientid, physicianid, blood reported, blood testid.

Laboratory Management system patient record Page 42

ERD (Entity Relationship Diagram)

Figure 3.28

Laboratory Management system patient record Page 43

2: Physical Database Schema:
This schema pertains to the actual storage of data and its form of storage like files, indices, etc.It defines how the
data will be stored in a secondary storage.

Figure 3.29

3.6 Normalization of Database:

Normalization is a process of organizing the data in database to avoid redundancy, insertion anomaly,
update anomaly and deletion anomaly. Normalization is a systematic approach of decomposing tables to
eliminate data redundancy and undesirable characteristics like insertion update and deletion.

Normalization is used for mainly two purpose.

Eliminating redundant (useless) data

Ensuring the data dependencies make senses. I.e. Data is logically stored.

3.7 Problem without Normalization:

Without normalization it is difficult to handle and update the database, without facing data loss.Insertaion
updating and deletion anomalies are very frequent if database is not normalized.

3.8 Updating Anomaly:

Laboratory Management system patient record Page 44
To update address of a customers who occurs twice or more than twice in a table, we will have to update
Customer Address column in all rows else data will become inconsistence.

3.9 Insertion Anomaly:

Suppose for a new customer, we have a customer id name address of a customer but if customer has not null
there, leading to insertion anomaly.

3.10 Deletion Anomaly:

If any customer have purchase only one dress and temporarily he drops it back then we delete this row,
entire customer record will be deleted.

First Normal form:

First normal form (1NF) is a property of a relation in a relational database. A relation is in first normal
form if and only if the domain of each attribute contains only atomic (indivisible) values, and the value of
each attribute contains only a single value from that domain . admin table no value are repeated every table
has own field

Admin Table:

Figure 3.30

Second Normal Form:

A database is in second normal form if it satisfies the following conditions:

 It is in first normal form

 All non-key attributes are fully functional dependent on the primary keyIn this table all non-key
value attribute is depended on the primary key .in this table uname and password is depend on the
admin_id attribute

Laboratory Management system patient record Page 45

 Figure 3.31

3rd Normal form :

A database is in third normal form if it satisfies the following conditions:

 It is in second normal form

 There is no transitive functional dependency
 In this table there are no transitive dependancy this table have only 1 primary key

Figure 3.32

Patient table:

First normal form:

First normal form (1NF) is a property of a relation in a relational database. A relation is in first normal
form if and only if the domain of each attribute contains only atomic (indivisible) values, and the value of
each attribute contains only a single value from that domain. Patient table are no multiple valued every field
its own value

Laboratory Management system patient record Page 46

 Figure 3.33

Second Normal Form:

A database is in second normal form if it satisfies the following conditions:

 It is in first normal form

 All non-key attributes are fully functional dependent on the primary key
 In the patient table all attribute of this table are fully depended on the primary key
 Patient name patient cell, patient age, patient gender patient address ,type is fully depend on the
patient id (primary key)

Figure 3.34

3rd Normal Form :

A database is in third normal form if it satisfies the following conditions:

 It is in second normal form

 There is no transitive functional dependency

Laboratory Management system patient record Page 47

 Figure 3.35

Blood_Test :

First normal form:

First normal form (1NF) is a property of a relation in a relational database. A relation is in first normal
form if and only if the domain of each attribute contains only atomic (indivisible) values, and the value of
each attribute contains only a single value from that domain .

Figure 3.36

Second Normal Form:

A database is in second normal form if it satisfies the following conditions:

 It is in first normal form

 All non-key attributes are fully functional dependent on the primary key

Laboratory Management system patient record Page 48

 Figure 3.37

3rd Normal Form :

A database is in third normal form if it satisfies the following conditions:

 It is in second normal form

 There is no transitive functional dependency

Figure 3.38

Blood Report:

First normal form:

First normal form (1NF) is a property of a relation in a relational database. A relation is in first normal
form if and only if the domain of each attribute contains only atomic (indivisible) values, and the value of
each attribute contains only a single value from that domain .

Figure 3.39

Laboratory Management system patient record Page 49

Second Normal Form:

A database is in second normal form if it satisfies the following conditions:

 It is in first normal form

All non-key attributes are fully functional dependent on the primary key

Figure 3.40

3rd Normal Form :

A database is in third normal form if it satisfies the following conditions:

 It is in second normal form

 There is no transitive functional dependency

Figure 3.41

Laboratory Management system patient record Page 50

Physician Table:
First normal form (1NF) is a property of a relation in a relational database. A relation is in first normal
form if and only if the domain of each attribute contains only atomic (indivisible) values, and the value of
each attribute contains only a single value from that domain .

Figure 3.42

Second Normal Form:

A database is in second normal form if it satisfies the following conditions:

 It is in first normal form

 All non-key attributes are fully functional dependent on the primary key

Figure 3.43

Laboratory Management system patient record Page 51

3rd Normal Form :

A database is in third normal form if it satisfies the following conditions:

 It is in second normal form

 1There is no transitive functional dependency

Figure 3.44

Front desk table:

First normal form:

First normal form (1NF) is a property of a relation in a relational database. A relation is in first normal
form if and only if the domain of each attribute contains only atomic (indivisible) values, and the value of
each attribute contains only a single value from that domain .

Figure 3.45

Laboratory Management system patient record Page 52

Second Normal Form:

A database is in second normal form if it satisfies the following conditions:

 It is in first normal form

 All non-key attributes are fully functional dependent on the primary key

Figure 3.46

3rd Normal Form :

A database is in third normal form if it satisfies the following conditions:

 It is in second normal form

 There is no transitive functional dependency

Figure 3.47

Laboratory Management system patient record Page 53

3.11Main form from Admin side:

Figure 3.48

3.12Main form from User side:

Figure 3.49

Laboratory Management system patient record Page 54

4.Development plan:

Patient management system is required development

Figure 4.1

4.1Requirement phase:

In this phase we required requirement of system user tell we all requirement about
system. Laboratory management system patient record are requirement is

a) User friendly
b) Patient update
c) Admin alert
d) Weekly update
e) Quick report generate
f) Quick search operation
g) Quick edit operation
h) Time saving
i) Easily enter data

Laboratory Management system patient record Page 55

4.2 System designed:

In this phase system designed according the user requirement waterfall model is rule that when developer
move from requirement phase to system designed phase in between the requirement change of user then
developer can move previous phase developer in this designed the structure of system

4.3 Implementation:

In the implementation plan developer implement the system according the system designed in laboratory
management system patient record verify the problem statement chose model according the system and
make class diagram . this system in the implement phase also worked on data flow diagram and sequence
diagram .Make entity relationship diagram

4.4 Testing phase:

In the testing phase system testing use different technique

4.5 Development phase:

In the development phase developer develop the system laboratory management system patient record
developer create database of the system .designed form and front end make the system .create the table in
the database and make table normalization

4.6 Maintenance phase:

In the maintenance phase developer everything the system laboratory management system patient
record the work in sequence .

4.7Development of program:

Tool selection:

1. Hardware

2. Software

Laboratory Management system patient record Page 56

1. Hardware:

Laboratory management System patient record is developed on the inlet core i3 computer this computer
RAM 64 GB supported

Software:
Laboratory management system patient record using software xamp server notepad++

4.8 Platform selection:

Zianab hospital is platform which this system is implemented this hospital

for Gynecologist this hospital is required patient record in computer system this hospital is patient record
managed in manual system .it’s very difficult for hospital this system is provide the Zianab hospital such
system that patient record maintain easily and update delete data of patient

4.9 Selection of tool:

It includes two parts:

First is to get experience in any tool and then develop the project in that particular tool. Second thing is to
select the tool according to the requirements of the project and get expertise in that tool.

And choice of the programming language is the important and definitely depends on upon the problem hand.

4.9.1 Languages:
Many choices are available but I select PHP because it is rapid tool for software development and because it fulfills
the necessities of my project.

4.9.2PHP:
PHP stands for Hypertext Preprocessor. It is an open source server-side scripting language used for the
development of web applications. By scripting language, a program that is script based (lines of code)
written for the automation of tasks.

PHP code may be embedded into HTML code, or it can be used in combination with various web template
systems, web content management system and web frameworks. PHP code is usually processed by a PHP
interpreter implemented as a module in the web server or as a Common Gateway Interface (CGI). It was
originally created by Rasmus Lerdorf in 1994.
Laboratory Management system patient record Page 57
PHP utilities:
Utilities of PHP are given below.

 Simple:

It is very simple and easy to use, compare to other scripting language it is very simple and easy, this is
widely used all over the world.

 Interpreted:

It is an interpreted language, i.e. there is no need for compilation.

 Faster:

It is faster than other scripting language e.g. asp and jsp.

 Open Source:

Open source means you no need to pay for use php, you can free download and use.

 Platform Independent:

PHP code will be run on every platform, Linux, Unix, Mac OS X, Windows.

 Case Sensitive:

PHP is case sensitive scripting language at time of variable declaration. In PHP, all keywords (e.g. if, else,
while, echo, etc.), classes, functions and user-defined functions are NOT case-sensitive.

 Error Reporting:

PHP have some predefined error reporting constants to generate a warning or error notice.


Real-Time Access Monitoring:

PHP provides access logging by creating the summary of recent accesses for the user.


Loosely Typed Language:

PHP supports variable usage without declaring its data type. It will be taken at the time of the
execution based on the type of data it has on its value.


Why I select PHP:

Laboratory Management system patient record Page 58

There was a number of choices of programming languages available for coding to my project but select PHP
due to its large number of features and it is latest language its code are easy to understand and a lot of built
in libraries and it provides suggestion of code. And some other features are:

Working environment

Attractive interface

Fast process

Open source platform

Laboratory Management system patient record Page 59

Laboratory Management system patient record Page 60