DATABASE MANAGEMENT SYSTEM

CSE 301

LABORATORY MANAGEMENT

SUBMITTED TO: SUBMITTED BY:

Ms. Chavi Amarnath

Roll No.-RC2801A17

Section- C2801

Reg. No.-10805162
 Acknowledgement

I devote all my achievements to the almighty ‘GOD’ for granting me strength, art, skill and
spirit to accomplish this project work .I am extremely thankful to Ms.Chavi for guiding me
about this project from time to time whenever I needed their help. She cleared my doubts to
satisfaction, explaining each and every point in simplest possible way .I am also thankful to
my ‘Parents’ for their encouragement and kind cooperation throughout courses of this project.
I am also thankful to my very good friends for helping me to get best ideas, for gathering
data, for accumulation of information and other valuable things. They also assisted me to how
I analyze, evaluate and present it in the best possible way under the available means.
Amarnath
 ABSTRACT

Database design is a complicated and important work; it determines the success or failure of the
system, so it needs considering a combination of factors and handling properly. In designing the
database of laboratory management system, use data-driven concept and increase proper
redundancy, which meet the needs of flexible management, large storage requirements of the
user. The realization of the system has accumulated great experiences for developments of
enterprise application system which develop in the PC server and have a large amount of data.

Inadequate attention to the analysis and design of data structures and the associated data
processing found in laboratories prior to the introduction of a Laboratory Management System
can result in a computer system that does not fully satisfy user requirements. The resulting
system may be inefficient and inflexible or even error prone with ‘open ended’ maintenance.
What is needed is a method with clear guidelines, employing proven techniques and intrinsic
documentation in order to fully identify, map, validate and optimize the laboratory functions,
events and data. In a highly regulated environment this would be an aid to computer system
validation.
 CONTENTS

1. Introduction To The Project

2. Requirements For Developing The Laboratory Management

a. Hardware Requirements

b. Software Requirements

3. After Normalization

4. List Of All The Attributes

5. Views

6. Creating Views

7. Pl/Sql

8. Conclusion

9. References
 INTRODUCTION TO THE PROJECT

The purpose of an analytical laboratory is to provide measurement support, generate information,

and solve problems. This often involves processing many samples and requests and produces
large numbers of test results and reports. In an attempt to increase efficiency, many analytical
laboratories have computerized their logbooks, focusing on tracking jobs, samples, tests and
results. With this information accessible via a computer, it is then possible to provide many
additional functions such as methods management, test results, archiving, and calculation,
comparison to specifications, control charting and verification of instrument performance.

Requirements for developing the Laboratory Management

Hardware Requirements

• Intel Pentium 4 Processor or higher

• Intel motherboard

• Monitor

• Keyboard

• 1 GB RAM or higher

• 80 GB Hard Disk or more

Software Requirements

• Operating system: Windows

• MS office tools

• PL/SQL

List of all the Attributes:

1. patient_id

2. patient name

3. patient address

4. patient_sex

5. patient_age

6. testname

7. patient_contno

8. test_charges

9. sample_id

10. test_reports

11. emp_id

12. emp_name

13. emp_address

14. emp_contno

15. patient_report
 16. billno/id

17. advance_amtpaid

18. amt_due

19. balance_amt

After Normalization:

2NF

Create table patient_detail(patient_id varchar(20),patient_name

varchar(20),patient_address varchar(20),patient_sex varchar(10),patient_test
varchar(20),patient_age number(10),patient_contno number(20),patient_report
varchar(20))

Patient_detail
• patient_id Varchar(20)
• patient_name Varchar(20)
• patient_address Varchar(20)
• patient_sex Varchar(10)
• patient_test Varchar(20)
• patient_age number(10)
• patient_contno Number(20)
• patient_report Varchar(20)

Create table tests(test_name varchar(20),test_charges varchar(20))

Tests
• test_name Varchar(20)
• test_charges Number(20)
Create table employee(emp_id varchar(20),emp_name varchar(20),emp_address
varchar(20),emp_contno number(20))

Employee
• emp_id Varchar(20)
• emp_name Varchar(20)
• emp_address Varchar(20)
• emp_contno nunber(20)

Create table billing(bill_id varchar(20),advance_amtpaid number(20),amt_due

number(20),balance_amt number(10))

Billing
• billno/id Varchar(20)
• advance_amtpaid Number(20)
• amt_due Number(20)
• balance_amt Number(20)

Create table sampling(patient_id varchar(20),sample_id varchar(20),sample_report

varchar(20))

Sampling
• patient_id Varchar(20)
• sample_id Varchar(20)
• sample_report Varchar(20)

VIEWS:

SQL VIEWS are data objects, and like SQL Tables, they can be queried, updated, and dropped. A
SQL VIEW is a virtual table containing columns and rows except that the data contained inside a
view is generated dynamically from SQL tables and does not physically exist inside the view
itself. Even though a SQL VIEW is treated like a data object in SQL, no data is actually stored
inside of the view itself. The view is essentially a dynamic SELECT query, and if any changes
are made to the originating table(s), these changes will be reflected in the SQL VIEW
automatically.
Creating views

• Create view vpatient(patient_name,age,test) as select

patient_name,patient_age,patient_test from patient_detail

• Create view vemp(employee_name) as select emp_name from employee

PL/SQL

PL/SQL stands for Procedural Language extension of SQL.

PL/SQL is a combination of SQL along with the procedural features of programming languages.
It was developed by Oracle Corporation in the early 90’s to enhance the capabilities of SQL.

The PL/SQL Engine:

Oracle uses a PL/SQL engine to processes the PL/SQL statements. A PL/SQL code can be stored
in the client system (client-side) or in the database (server-side).

A stored procedure or in simple a proc is a named PL/SQL block which performs one or more
specific task. This is similar to a procedure in other programming languages. A procedure has a
header and a body. The header consists of the name of the procedure and the parameters or
variables passed to the procedure. The body consists or declaration section, execution section and
exception section similar to a general PL/SQL Block. A procedure is similar to an anonymous
PL/SQL Block but it is named for repeated usage.

We can pass parameters to procedures in three ways.

1) IN-parameters
2) OUT-parameters
3) IN OUT-parameters

A procedure may or may not return any value.

General Syntax to create a procedure is:

CREATE [OR REPLACE] PROCEDURE proc_name [list of parameters]

IS
Declaration section
BEGIN
Execution section
EXCEPTION
Exception section
END;

A cursor is a temporary work area created in the system memory when a SQL statement is
executed. A cursor contains information on a select statement and the rows of data accessed by it.
This temporary work area is used to store the data retrieved from the database, and manipulate
this data. A cursor can hold more than one row, but can process only one row at a time. The set of
rows the cursor holds is called the active set.

There are two types of cursors in PL/SQL:

Implicit cursors:

These are created by default when DML statements like, INSERT, UPDATE, and DELETE
statements are executed. They are also created when a SELECT statement that returns just one
row is executed.
Explicit cursors:

They must be created when you are executing a SELECT statement that returns more than one
row. Even though the cursor stores multiple records, only one record can be processed at a time,
which is called as current row. When you fetch a row the current row position moves to next row.

Both implicit and explicit cursors have the same functionality, but they differ in the way they are accessed.

Conclusion

This project is designed to meet the requirements of a LABORATORY MANAGEMENT.

• We need to enter the data only once.

• Retrieve very specific information from vast amounts of data swiftly and simply, using
the extensive queries

• Eliminate a significant amount of paper records, and you will eliminate the occurrence of
lost or misfiled data, worksheets and files. Save time previously spent searching for data
or retrieving lost information.

• Establish read-only access for personnel outside the lab. This feature allows authorized
personnel to directly pursue their own questions dynamically, effectively eliminating non-
productive data search, retrieval, and copying time.

• Significantly reduce data transcription error, since manual data entry is limited to specific
sample characteristics at login and to those results not available from direct data import.
Virtually all other data entry is done using selections from predefined pull-down lists and
menus.
 References

• http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=5455275

• http://ieeexplore.ieee.org/Xplore/login.jsp?url=http%3A%2F%2Fieeexplore.ieee.org
%2Fiel5%2F5454173%2F5454428%2F05455275.pdf%3Farnumber
%3D5455275&authDecision=-203

• http://www.umsl.edu/~sauterv/analysis/LIMS_example.html

• http://www.freepatentsonline.com/6725232.html

• http://www.starlims.com/LIMS_For_DNA_Forensic.htm

• http://www.computer.org/portal/web/csdl/doi/10.1109/ICISE.2009.491