21CSC205P Database Management

Systems

Project Report

Register No. : RA2211003050152

Name of the Student : SHRIKAVIN B

Semester : IV

Programme : B.Tech. COMPUTER SCIENCE AND

ENGINEERING

Academic Year : 2023-2024

SRM INSTITUTE OF SCIENCE AND TECHNOLOGY

TIRUCHIRAPPALLI
TIRUCHIRAPPALLI COLLEGE OF ENGINEERING AND TECHNOLOGY
 SRM INSTITUTE OF SCIENCE AND TECHNOLOGY
TIRUCHIRAPPALLI
TIRUCHIRAPPALLI
COLLEGE OF ENGINEERING AND TECHNOLOGY

REGISTER NO: RA2211003050152

BONAFIDE CERTIFICATE

Certified as the bonafide record of work done by

SHRIKAVIN B , Register No.

RA2211003050152 of II / IV (Semester/Year),

B.Tech COMPUTER SCIENCE AND ENGINEERING Programme in the

project-based course 21CSC205P, Database Management Systems at SRM Institute

of Science and Technology, Tiruchirappalli Campus during the Academic Year

2023-2024.

Faculty In-charge Head of the Department

Submitted for the End Semester Examination held on

Examiner-1 Examiner-2
 SRM Institute of Science and Technology
Faculty of Engineering and Technology
School of Computing
Department of Computational Intelligence
VISION AND MISSION OF THE DEPARTMENT
Vision
To become a world-class department in imparting high-quality knowledge and providing students
with a unique learning and research experience in Computer Science and Engineering.

Mission

1. To impart knowledge in cutting edge technologies in part with industrial standards.

2. To collaborate with renowned academic institutions in research and development.
3. To instill societal and ethical responsibilities in all professional activities.

Program Educational Objectives (PEO)

PEO - 1 Graduates will be able to perform in technical/managerial roles ranging from design,
development, problem solving to production support in software industries and R&D sectors

PEO - 2 Graduates will be able to successfully pursue higher education in reputed institutions.

PEO - 3 Graduates will have the ability to adapt, contribute and innovate new technologies and
systems in the key domains of Computer Science and Engineering.
PEO - 4 Graduates will be ethically and socially responsible solution providers and
entrepreneurs in Computer Science and other engineering disciplines.

PEO - 5 Graduates will possess the additional skills in core computer science discipline with
knowledge of Hardware, Software, Programming, Logic & Reasoning.

Mission of the Department to Program Educational Objectives (PEO) Mapping

H – High correlation, M – Medium Correlation, L – Low Correlation

Program Outcomes as defined by NBA (PO)

Engineering Graduates will be able to:
1. Engineering knowledge: Apply the knowledge of mathematics, science, engineering
fundamentals, and an engineering specialization to the solution of complex engineering
problems.
2. Problem analysis: Identify, formulate, review research literature, and analyze complex
engineering problems reaching substantiated conclusions using first principles of mathematics,
natural sciences, and engineering sciences.
3. Design/development of solutions: Design solutions for complex engineering problems and
design system components or processes that meet the specified needs with appropriate
consideration for the public health and safety, and the cultural, societal, and environmental
considerations.
4. Conduct investigations of complex problems: Use research-based knowledge and research
methods including design of experiments, analysis and interpretation of data, and synthesis of
the information to provide valid conclusions.
5. Modern tool usage: Create, select, and apply appropriate techniques, resources, and modern
engineering and IT tools including prediction and modeling to complex engineering activities
with an understanding of the limitations.
6. The engineer and society: Apply reasoning informed by the contextual knowledge to assess
societal, health, safety, legal and cultural issues and the consequent responsibilities relevant to
the professional engineering practice.
7. Environment and sustainability: Understand the impact of the professional engineering
solutions in societal and environmental contexts, and demonstrate the knowledge of, and need
for sustainable development.
8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities and
norms of the engineering practice.
9. Individual and team work: Function effectively as an individual, and as a member or leader
in diverse teams, and in multidisciplinary settings.
10. Communication: Communicate effectively on complex engineering activities with the
engineering community and with society at large, such as, being able to comprehend and write
effective reports and design documentation, make effective presentations, and give and receive
clear instructions.
11. Project management and finance: Demonstrate knowledge and understanding of the
engineering and management principles and apply these to one’s own work, as a member and
leader in a team, to manage projects and in multidisciplinary environments.
12. Life-long learning: Recognize the need for, and have the preparation and ability to engage
in independent and life-long learning in the broadest context of technological change.

PSO – Program Specific Outcomes (PSO)

Mapping Program Educational Objectives (PEO) to Program Learning Outcomes (PLO)

H – High correlation, M – Medium Correlation, L – Low Correlation

COURSE DESIGN

Course Learning At the end of this course, learners will be able to:
Outcomes (CLO):
CO – 1 Acquire knowledge on DBMS architecture and languages
CO – 2 Acquire knowledge on Relational languages and design a database
CO – 3 Implement the Database structure with SQL
CO – 4 Removal of anomalies using Normalization concepts
CO – 5 Visualizing storage structure, handling concurrency, Failure and
recovery principles, NoSQL concept

CLO-PO Mapping

CLO Program Outcomes (PO)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Engineering Knowledge

Design & Development

Project Mgt. & Finance

Modern Tool Usage

Life Long Learning

Individual & Team
Society & Culture
Problem Analysis

Analysis, Design,

Communication
Environment &
Sustainability
Research

PSO – 3
PSO - 1

PSO - 2
Ethics

Work

CO1 - 2 - - - - - - - - - - 2 1 -
CO2 1 2 - - - - - - - - - - 2 1 -
CO3 1 - 2 - - - - - - - - - 2 1 -
CO4 1 - - - - - - - - - - - 2 1 -
CO5 1 2 - - - - - - - - - - 2 1 -
 Report Evaluation:

Test
Date Artifacts Total
Components Mark Split-up
Marks

Marks to be evaluated based on

1 (a) 23.01.2024 Project Title selection, presentation
Abstract Project title – 2 Marks
04
Presentation – 2 Marks

Problem understanding, Marks to be evaluated based on

Identification of Entity and presentation and demo
1 (b)
07-02-2024
Relationships, Problem Identification – 1 Marks
Construction of DB using Presentation – 2 Marks
ER Model for their project 06 Demo - 2 Marks
Viva - 1 Marks

Marks to be evaluated based on demo

Design of Relational
and viva voce
Schemas, Creation of
2 28-02-2024 Demo - 4 Marks
Database and their Tables
10 Viva voce – 3 Marks
for their project
Report - 3 Marks

Marks to be evaluated based on demo

Writing the complex queries
and viva voce
based on the concepts of
27-03-2024 Demo - 4 Marks
3 constraints, sets, joins,
10 Viva - 3 Marks
views, Triggers and Cursors
Report -3 Marks
 Marks to be evaluated based on demo
Analyzing the pitfalls, and viva voce
27-03-2024 identifying the dependencies Demo - 4 Marks
4 and applying normalizations 10 Viva - 3 Marks
Report - 3 Marks

Marks to be evaluated based on demo

Implementation of and viva voce
27-03-2024 concurrency control and Demo - 4 Marks
5
recovery mechanisms. 10 Viva - 3 Marks
Report - 3 Marks
Marks to be evaluated based on
presentation and demo
Module Description and Final Presentation - 2
6 15-04-2024
Functionalities 10 Demo - 2 Marks
Viva - 3 Marks
Report - 3 Marks
Marks to be evaluated based on
Database Connectivity and presentation and demo
Final Presentation - 2
7 15-04-2024 Embedded SQL 10
Demo - 2 Marks
operations Viva - 3 Marks
Report - 3 Marks
Marks to be evaluated based on
presentation and demo
PL/SQL procedures to
Final Presentation - 2
8 29-04-2024 Operate on the database 10
Demo - 2 Marks
of your project Viva - 3 Marks
Report - 3 Marks
Marks to be evaluated based on
presentation and demo
Final Presentation - 2
9 29-04-2024 Front End Design 10
Demo - 2 Marks
Viva - 3 Marks
Report - 3 Marks
Marks to be evaluated based on
presentation and demo
Report Generation using
Final Presentation - 2
10 07-05-2024 Crystal Reports/Report 10
Demo - 2 Marks
Generation Tool Viva - 3 Marks
Report - 3 Marks
LABORATORY EXPERIMENTS MAPPED WITH CLO, PO, PSO

Sl. CLO PO / PSO

Title of the Experiments
No. Mapping Mapping
1 (a) Project Title selection, Abstract 1 2
(b) Problem understanding, Identification of Entity
and Relationships, Construction of DB using ER
Model for your project
2 Design of Relational Schemas, Creation of Database 1,2 1,2
and Tables for your project
3 SQL Queries based on the concepts of constraints, 3 1,3
sets, joins
4 Applying Normalization for your project 4 1

5 Concurrency control and Recovery mechanisms for 5 1,2

your project
6 Module Description and Functionalities 1,2 1,2

7 Database Connectivity and Embedded SQLoperations 1,2 1,2

8 PL/SQL procedures to Operate on the database of 2,3 1,2,3

your project
9 Front End Design, Sample Code for each module, 5 1,2
Screen Shots for each module
10 Report Generation using Crystal Reports/Report 5 1,2
Generation Tool
 INDEX
Expt. Date of Name of the Page Marks Signature
No. Experiment Experiment No. (50) of Faculty

1 07-02-2024 (a) Project Title selection,

Abstract

(b)Problem understanding,
Identification of Entity and
Relationships, Construction
of DB using ER Model for
your project
2 28-02-2024 Design of Relational
Schemas, Creation of
Database and Tables for your
project
3 27-03-2024 SQL Queries based on the
concepts of constraints, sets,
joins
4 27-03-2024 Applying Normalization for
your project
5 27-03-2024 Concurrency control and
Recovery mechanisms for
your project
6 15-04-2024 Module Description and
Functionalities
7 15-04-2024 Database Connectivity and
Embedded
SQL operations
8 29-04-2024 PL/SQL procedures to
Operate on the database of
your project
9 29-04-2024 Front End Design, Sample
Code foreach module, Screen
Shots for eachmodule
10 07-05-2024 Report Generation using
Crystal Reports/Report
Generation Tool
11 07-05-2024 Online Course Completion
Certificate
EXP.NO: 1

COVID-19 TESTING MANAGEMENT SYSTEM

ABSTRACT

COVID19 Testing Management System is one of the most essential tools that are mostly used in Testing
Lab; it is mostly used to manage COVID19 medical lab related activities.In this project we tried to develop a
computerized and web based COVID19 Testing management system. Our main intention is to allow this
application to be used in most retailing COVID19 lab, where a small point of customization will be required to
each COVID19 lab in the implementation period. This system is designed to overcome all challenges related to
the management of diagnostic that were used to be handled locally and manually.

The system is an online COVID19 lab manager application that brings up various COVID19 test working online.
Using this system, it will help us to records all transaction made at the daily tests; recognize all customers,
employees, etc. It will manage all activities around the COVID19 lab that increases productivity and maximize
profit, it will also minimizing the risk of getting loss because all transactions are recorded to the system.

PROBLEM STATEMENT

In light of the ongoing global COVID-19 pandemic, the existing infrastructure of testing labs faces significant
challenges in efficiently managing the ever-increasing volume of tests. The manual processes currently in place
are prone to errors, delays, and inefficiencies, posing risks to both patients and healthcare providers. Below are
some key points outlining the issues faced by testing labs:

1. Inadequate Infrastructure: Many testing labs operate with outdated or insufficient infrastructure, leading
to bottlenecks in sample processing, reporting, and data management.
2. Manual Processes: Current practices rely heavily on manual data entry, paperwork, and communication,
which are time-consuming and error-prone. This increases the likelihood of inaccuracies in test results,
patient records, and financial transactions.
3. Limited Scalability: With the surge in demand for COVID-19 testing, labs struggle to scale their
operations to meet the growing needs of the population. Manual processes hinder the ability to efficiently
process a large number of tests within a short timeframe.
4. Lack of Centralized Information: The absence of a centralized system for managing test data, patient
information, and lab resources makes it challenging to track and trace COVID-19 cases accurately. This
 poses risks to public health and impedes efforts to control the spread of the virus.
5. Resource Management Challenges: Manual scheduling of appointments, allocation of testing kits, and
assignment of staff resources are prone to errors and inefficiencies. This can lead to delays in testing,
increased waiting times for patients, and decreased overall productivity.
6. Compliance and Reporting: Meeting regulatory requirements and reporting standards is essential for
testing labs. Manual record-keeping makes it difficult to ensure compliance with regulatory guidelines and
to generate accurate reports for public health authorities.
7. Data Security Concerns: Paper-based systems lack adequate security measures to protect sensitive patient
information and test results. This leaves testing labs vulnerable to data breaches, privacy violations, and
regulatory penalties.

ENTITY - RELATIONSHIP DIAGRAM

EXP.NO:2

RELATIONAL SCHEMA

DATABASE CREATION

1. Creating admin table named “tbladmin”

CREATE TABLE `tbladmin` (

`ID` int(11) NOT NULL AUTO_INCREMENT,
`AdminName` varchar(120) DEFAULT NULL,
`AdminuserName` varchar(20) NOT NULL,
`MobileNumber` int(10) NOT NULL,
`Email` varchar(120) NOT NULL,
`Password` varchar(120) DEFAULT NULL,
`AdminRegdate` timestamp NULL DEFAULT current_timestamp(),
PRIMARY KEY (`ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
Dumping data for table `tbladmin`

INSERT INTO `tbladmin` (`ID`, `AdminName`, `AdminuserName`, `MobileNumber`, `Email`, `Password`,

`AdminRegdate`) VALUES
(2, 'Admin', 'admin', 1234567890, '[email protected]', 'f925916e2754e5e03f75dd58a5733251', '2021-04-19
18:30:00');

AdminNam Adminuser MobileNum AdminReg

ID e Name ber Email Password date
2 Admin admin 1234567890 admin@gm f925916e27 2021-04-19
ail.com 54e5e03f75 18:30:00
dd58a57332
51

2.Creating patients table named “tblpatients”

CREATE TABLE `tblpatients` (

`id` int(11) NOT NULL AUTO_INCREMENT,
`FullName` varchar(120) DEFAULT NULL,
`MobileNumber` bigint(12) DEFAULT NULL,
`DateOfBirth` date DEFAULT NULL,
`GovtIssuedId` varchar(150) DEFAULT NULL,
`GovtIssuedIdNo` varchar(150) DEFAULT NULL,
`FullAddress` varchar(255) DEFAULT NULL,
`State` varchar(200) DEFAULT NULL,
`RegistrationDate` timestamp NOT NULL DEFAULT current_timestamp(),
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Dumping data for table `tblpatients`

INSERT INTO `tblpatients` (`id`, `FullName`, `MobileNumber`, `DateOfBirth`, `GovtIssuedId`,
`GovtIssuedIdNo`, `FullAddress`, `State`, `RegistrationDate`) VALUES
(1, 'Anuj kumar', 1234567890, '1999-02-01', 'Driving License', '342545445345', 'A83748 New Delhi India',
'Delhi', '2021-04-27 17:31:22'),
(2, 'Sarita', 6547893210, '1990-05-09', 'Pancard', 'HHHGHGH8888jh', 'H 826273 Noida', 'Uttar Pradesh',
'2021-04-27 18:04:57'),
(4, 'Garima Singh', 4598520125, '2005-01-08', 'Pancard', 'DDDKJKJ454545H', 'A-1234 Patna', 'Bihar',
'2021-05-08 05:49:44'),
(5, 'Amit Singh', 2536987410, '2007-06-01', 'PANCARD', 'HJGGHG76767HGGH', 'H 37334 New Delhi', 'Delhi',
'2021-05-08 09:25:50'),
(6, 'Rahul Yadav', 1234567899, '2003-06-05', 'Driving License', '5435345', 'ABC 123 XYZ Street Noida', 'Uttar
Pradesh', '2021-05-08 09:29:22');

GovtIs Registr
MobileNu DateOfBirt GovtIs suedId FullAdd ationDa
id FullName mber h suedId No ress State te
1 Anuj 1234567890 1999-02-01 Driving 342545445345
A83748 Delhi 2021-04
Kumar License New -27
Delhi 17:31:22
India
2 Sarita 6547893210 1990-05-09 Pancar HHHG H Uttar 2021-04
d HGH88 826273 Pradesh -27
88jh Noida 18:04:57
4 Garima 4598520125 2005-01-08 Pancar DDDKJ A-1234 Bihar 2021-05
Singh d KJ4545 Patna -08
45H 05:49:44
5 Amit 2536987410 2007-06-01 PANCA HJGGH H 37334 Delhi 2021-05
Singh RD G76767 New -08
HGGH Delhi 09:25:50
6 Rahul 1234567899 2003-06-05 Driving 5435345 ABC 123 Uttar 2021-05
Yadav License XYZ Pradesh -08
Street 09:29:22
Noida
3.Creating phlebotomist table named “tblphlebotomist”

CREATE TABLE `tblphlebotomist` (

`id` int(11) NOT NULL AUTO_INCREMENT,
`EmpID` varchar(100) DEFAULT NULL,
`FullName` varchar(120) DEFAULT NULL,
`MobileNumber` bigint(12) DEFAULT NULL,
`RegDate` timestamp NULL DEFAULT current_timestamp(),
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Dumping data for table `tblphlebotomist`

INSERT INTO `tblphlebotomist` (`id`, `EmpID`, `FullName`, `MobileNumber`, `RegDate`) VALUES

(3, '12587493', 'Amit Singh', 9876543212, '2021-05-03 04:51:44'),
(4, '105202365', 'Rahul', 8529631470, '2021-05-03 04:52:06'),
(5, '10802364', 'Sanjeev Tomar', 1234567890, '2021-05-08 09:34:11');

id EmpID FullName MobileNumber RegDate

3 12587493 Amit Singh 9876543212 2021-05-03 04:51:44

4 105202365 Rahul 8529631470 2021-05-03 04:52:06

5 10802364 Sanjeev Tomar 1234567890 2021-05-08 09:34:11

4.Creating reporttracking table named “tblreporttracking”

CREATE TABLE `tblreporttracking` (

`id` int(11) NOT NULL AUTO_INCREMENT,
`OrderNumber` bigint(40) DEFAULT NULL,
`Remark` varchar(255) DEFAULT NULL,
`Status` varchar(120) DEFAULT NULL,
`PostingTime` timestamp NULL DEFAULT current_timestamp(),
`RemarkBy` int(5) DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Dumping data for table `tblreporttracking`

INSERT INTO `tblreporttracking` (`id`, `OrderNumber`, `Remark`, `Status`, `PostingTime`, `RemarkBy`)

VALUES
(1, 450040675, 'The Phlebotomist is on the way for collection.', 'On the Way for Collection', '2021-05-06
04:36:22', 2),
(6, 450040675, 'Sample collection.', 'Sample Collected', '2021-05-06 19:15:25', 2),
(7, 450040675, 'Sample sent to the lab.', 'Sent to Lab', '2021-05-06 19:15:48', 2),
(9, 450040675, 'Report uploaded.', 'Delivered', '2021-05-06 20:01:48', 2),
(10, 617325549, 'The phlebotomist is on the way to sample collection.', 'On the Way for Collection', '2021-05-07
04:44:38', 2),
(11, 617325549, 'Sample collected successfully.', 'Sample Collected', '2021-05-07 04:46:46', 2),
(12, 617325549, 'Sample sent to the lab.', 'Sent to Lab', '2021-05-07 04:51:25', 2),
(13, 617325549, 'Report uploaded.', 'Delivered', '2021-05-07 04:57:20', 2),
(14, 250482553, 'On the way for sample collection.', 'On the Way for Collection', '2021-05-08 09:31:42', 2),
(15, 250482553, 'Sample collected successfully', 'Sample Collected', '2021-05-08 09:32:06', 2),
(16, 250482553, 'Sample sent to lab', 'Sent to Lab', '2021-05-08 09:32:26', 2),
(17, 250482553, 'Report Uploaded', 'Delivered', '2021-05-08 09:32:51', 2);
id OrderNumber Remark Status PostingTime RemarkBy
1 450040675 The On the Way for 2021-05-06 2
Phlebotomist Collection 04:36:22
is on the way
for collection.
6 450040675 Sample Sample Collected 2021-05-06 2
collection. 19:15:25
7 450040675 Sample sent Sent to Lab 2021-05-06 2
to the lab. 19:15:48
9 450040675 Report Delivered 2021-05-06 2
uploaded. 20:01:48
10 617325549 The On the Way for 2021-05-07 2
phlebotomist Collection 04:44:38
is on the way
to sample
collection.
11 617325549 Sample Sample Collected 2021-05-07 2
collected 04:46:46
successfully.
12 617325549 Sample sent Sent to Lab 2021-05-07 2
to the lab. 04:51:25
13 617325549 Report Delivered 2021-05-07 2
uploaded. 04:57:20
14 250482553 On the way On the Way for 2021-05-08 2
for sample Collection 09:31:42
collection.
15 250482553 Sample Sample Collected 2021-05-08 2
collected 09:32:06
successfully
16 250482553 Sample sent Sent to Lab 2021-05-08 2
to lab. 09:32:26
17 250482553 Report Delivered 2021-05-08 2
Uploaded. 09:32:51
5.Creating table testrecord named “tbltestrecord”

CREATE TABLE `tbltestrecord` (

`id` int(11) NOT NULL,
`OrderNumber` bigint(14) DEFAULT NULL,
`PatientMobileNumber` bigint(14) DEFAULT NULL,
`TestType` varchar(100) DEFAULT NULL,
`TestTimeSlot` varchar(120) DEFAULT NULL,
`ReportStatus` varchar(100) DEFAULT NULL,
`FinalReport` varchar(150) DEFAULT NULL,
`ReportUploadTime` varchar(200) DEFAULT NULL,
`RegistrationDate` timestamp NULL DEFAULT current_timestamp(),
`AssignedtoEmpId` varchar(150) DEFAULT NULL,
`AssigntoName` varchar(180) DEFAULT NULL,
`AssignedTime` varchar(100) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Dumping data for table `tbltestrecord`

INSERT INTO `tbltestrecord` (`id`, `OrderNumber`, `PatientMobileNumber`, `TestType`, `TestTimeSlot`,
`ReportStatus`, `FinalReport`, `ReportUploadTime`, `RegistrationDate`, `AssignedtoEmpId`, `AssigntoName`,
`AssignedTime`) VALUES
(1, 450040675, 1234567890, 'Antigen', '2021-05-01T04:05', 'Delivered',
'2c86e2aa7eb4cb4db70379e28fab9b521620331308.pdf', '07-05-2021 01:31:48 AM', '2021-04-27 17:31:23',
'12587493', 'Amit Singh', '06-05-2021 10:05:22 AM'),
(2, 617325549, 6547893210, 'RT-PCR', '2021-05-01T05:10', 'Delivered',
'2c86e2aa7eb4cb4db70379e28fab9b521620363440.pdf', '07-05-2021 10:27:20 AM', '2021-04-27 18:04:58',
'105202365', 'Rahul', '07-05-2021 10:13:41 AM'),
(4, 740138296, 1234567890, 'RT-PCR', '2021-05-05T14:40', 'Assigned', NULL, NULL, '2021-04-27 19:10:30',
'105202365', 'Rahul', '07-05-2021 03:52:05 PM'),
(5, 716060226, 4598520125, 'CB-NAAT', '2021-05-15T14:22', NULL, NULL, NULL, '2021-05-08 05:49:46',
NULL, NULL, NULL),
(6, 599452326, 2536987410, 'CB-NAAT', '2021-05-20T19:00', NULL, NULL, NULL, '2021-05-08 09:25:50',
NULL, NULL, NULL),
(7, 250482553, 1234567899, 'Antigen', '2021-05-11T15:00', 'Delivered',
'2c86e2aa7eb4cb4db70379e28fab9b521620466371.pdf', '08-05-2021 03:02:51 PM', '2021-05-08 09:29:22',
 '12587493', 'Amit Singh', '08-05-2021 03:00:47 PM');

Pati
ent
Mo
bile Repo Assig
Orde Nu TestT Repo Final rtUpl Regis nedto Assig Assig
rNu mb TestT imeSl rtStat Repo oadTi tratio EmpI ntoN nedTi
id mber er ype ot us rt me nDate d ame me
1 450040675
1234567890
Antig 2021- Delive 2c86e 07-05 2021- 12587493 Amit 06-05
en 05-01 red 2aa7e -2021 04-27 Singh -2021
T04:0 b4cb4 01:31: 17:31: 10:05:
5 db703 48 23 22
79e28 AM AM
fab9b
52162
03313
08.pdf
2 617325549
6547893210
RT- 2021- Delive 2c86e 07-05 2021- 105202365Rahul 07-05
PCR 05-01 red 2aa7e -2021 04-27 -2021
T05:1 b4cb4 10:27: 18:04: 10:13:
0 db703 20 58 41
79e28 AM AM
fab9b
52162
03634
40.pdf
4 740138296
1234567890
RT- 2021- Assig NULL NULL 2021- 105202365Rahul 07-05
PCR 05-05 ned 04-27 -2021
T14:4 19:10: 03:52:
0 30 05
PM
5 716060226
4598520125
CB- 2021- NULL NULL NULL 2021- NULL NULL NULL
NAAT 05-15 05-08
T14:2 05:49:
2 46
6 599452326
2536987410
CB- 2021- NULL NULL NULL 2021- NULL NULL NULL
NAAT 05-20 05-08
T19:0 09:25:
0 50
7 250482553
1234567899
Antig 2021- Delive 2c86e 08-05 2021- 12587493 Amit 08-05
en 05-11 red 2aa7e -2021 05-08 Singh -2021
T15:0 b4cb4 03:02: 09:29: 03:00:
0 db703 51 22 47
79e28 PM PM
fab9b
52162
04663
71.pdf
EXP.NO:3

CONSTRAINTS
• Creating tables with primary key constraints:
CREATE TABLE Patients (
PatientID INT PRIMARY KEY,
FullName VARCHAR(120),
MobileNumber BIGINT(12),
DateOfBirth DATE,
-- Other patient details
);

CREATE TABLE TestRecords (

RecordID INT PRIMARY KEY,
OrderNumber BIGINT(14),
-- Other test record details
);

• Adding foreign key constraints:

ALTER TABLE TestRecords
ADD CONSTRAINT FK_PatientID FOREIGN KEY (PatientID)
REFERENCES Patients(PatientID);

SETS
• Union of two tables to get unique records:
SELECT * FROM Lab1_TestRecords
UNION
SELECT * FROM Lab2_TestRecords;

• Intersection of two tables:

SELECT * FROM Lab1_TestRecords
INTERSECT
SELECT * FROM Lab2_TestRecords;
JOINS
• Inner join between tables to link patient information with test records:
SELECT Patients.FullName, TestRecords.OrderNumber
FROM Patients
INNER JOIN TestRecords ON Patients.PatientID = TestRecords.PatientID;

• Left join to get all patient records along with their test records, even if they haven't taken tests:
SELECT Patients.FullName, TestRecords.OrderNumber
FROM Patients
LEFT JOIN TestRecords ON Patients.PatientID = TestRecords.PatientID;
EXP.NO:4

APPLYING NORMALIZATION FOR MY PROJECT

1. First Normal Form (1NF):

• Ensure that each column contains atomic values.
• There should be no repeating groups within rows.
• Each table should have a primary key.
Action:
• All tables already satisfy the requirements of 1NF.
2. Second Normal Form (2NF):
• Ensure that non-key attributes are fully functionally dependent on the entire primary key.
Action:
• No composite keys are present, so all tables automatically meet the requirements of 2NF.
3. Third Normal Form (3NF):
• Eliminate transitive dependencies, where non-key attributes are dependent on other non-key attributes.
Action:
• Identify and eliminate transitive dependencies in the tables.
Normalization Actions:
(a) tblpatients:
• No transitive dependencies present. Already in 3NF.
(b) tbladmin:
• No transitive dependencies present. Already in 3NF.
(c) tblphlebotomist:
• No transitive dependencies present. Already in 3NF.
(d) tblreporttracking:
• No transitive dependencies present. Already in 3NF.
(e) tbltestrecord:
• Transitive dependency: AssigntoName depends on AssignedtoEmpId.
• Create a new table phlebotomist_info with columns AssignedtoEmpId, AssigntoName.
• Remove AssigntoName from tbltestrecord and reference AssignedtoEmpId with a foreign key.
(f) After Normalization:
• tbltestrecord:
• id (PK)
 • OrderNumber
• PatientMobileNumber
• TestType
• TestTimeSlot
• ReportStatus
• FinalReport
• ReportUploadTime
• RegistrationDate
• AssignedtoEmpId (FK)
• AssignedTime
• phlebotomist_info:
• AssignedtoEmpId (PK)
• AssigntoName
4. Boyce-Codd Normal Form (BCNF):
• BCNF is an extension of 3NF.
• In BCNF, every determinant (attribute whose value determines another value in the same row) is a candidate
key.

5. Fourth Normal Form (4NF):

• In 4NF, there should be no multi-valued dependencies.
• If a table has multi-valued dependencies, we decompose it into smaller tables to remove them.

6. Fifth Normal Form (5NF):

• In 5NF, there should be no join dependencies.
• If a table has join dependencies, we decompose it into smaller tables to remove them.
Normalization Actions:
1. tblpatients:
• No multi-valued or join dependencies present. Already in BCNF, 4NF, and 5NF.
2. tbladmin:
• No multi-valued or join dependencies present. Already in BCNF, 4NF, and 5NF.
3. tblphlebotomist:
• No multi-valued or join dependencies present. Already in BCNF, 4NF, and 5NF.
4. tblreporttracking:
• No multi-valued or join dependencies present. Already in BCNF, 4NF, and 5NF.
EXP.NO:5

Implementation of Concurrency control and Recovery mechanisms:

1. Concurrency Control:

• Locking Mechanisms: Implement locks to control access to critical resources such as patient records, test results,
and administrative functions. Use shared locks for read operations and exclusive locks for write operations to
prevent conflicts.
• Timestamp-based Concurrency Control: Assign timestamps to transactions and use them to order and schedule
concurrent transactions. Ensure that transactions with conflicting operations are executed in the correct order to
maintain consistency.
• Optimistic Concurrency Control: Given that the system deals with a significant number of read operations,
consider optimistic concurrency control techniques such as validation checks at the time of commit to detect
conflicts.
• Multi-Version Concurrency Control (MVCC): Maintain multiple versions of test records to allow concurrent
transactions to access data without blocking. Use timestamps or version numbers to ensure data consistency.

2. Recovery Mechanisms:

• Transaction Logging: Log all database modifications, including patient registrations, test orders, and test results.
Use a robust logging mechanism to ensure that changes are recorded before they are applied to the database.
• Checkpointing: Periodically save the current state of the database to stable storage to provide a starting point for
recovery in case of a system crash. Consider scheduling checkpoints during off-peak hours to minimize disruption.
• Transaction Rollback: Implement mechanisms to rollback incomplete transactions in case of failures or user
aborts. Ensure that partial changes made by aborted transactions are undone to maintain database consistency.
• Undo/Redo Logging: Log both undo and redo information to support database recovery. In the event of a crash,
use redo logs to reapply committed transactions and undo logs to rollback uncommitted changes.
• Savepoints: Allow transactions to define savepoints to mark intermediate states. This enables users to rollback to a
specific point in case of errors without losing all transaction progress.

3. Isolation Levels:

• Define appropriate isolation levels to control the visibility of data changes to concurrent transactions. Given the
sensitivity of patient data, consider using a higher isolation level such as Serializable to ensure strict data
consistency.
• Ensure that transactions are executed in a consistent manner, considering factors like data integrity, confidentiality,
and performance.

4. Distributed Database Considerations:

• If your system is distributed across multiple testing labs or facilities, ensure that concurrency control and recovery
 mechanisms are designed to work in a distributed environment.
• Implement distributed deadlock detection algorithms to detect and resolve deadlocks between distributed
transactions.
• Use distributed commit protocols such as Two-Phase Commit (2PC) to coordinate transaction commits across
distributed nodes and ensure atomicity and consistency.
EXP.NO:6

Module Description and Functionalities

Module 1: Admin Management

• Description: This module allows administrators to manage user accounts, view system logs, and configure
system settings.
• Functionalities:
• Create, update, and delete admin accounts.
• View and search system logs for audit purposes.
• Configure system settings such as email notifications and test parameters.
Module 2: Patient Management
• Description: This module enables healthcare professionals to manage patient information, including
registration, updating records, and scheduling tests.
• Functionalities:
• Register new patients and capture their personal information, contact details, and identification
documents.
• Update patient records with additional information such as medical history and test results.
• Schedule COVID19 tests for patients based on doctor referrals or self-request.
Module 3: Test Management
• Description: This module facilitates the management of COVID19 tests, including test scheduling, sample
collection, lab processing, and result reporting.
• Functionalities:
• Schedule test appointments for registered patients and assign them to available time slots.
• Record sample collection details, including the phlebotomist responsible and collection time.
• Track the status of tests from sample collection to result delivery, including sample processing and lab
reports.
Module 4: Phlebotomist Management
• Description: This module allows the management of phlebotomist profiles and assignments for sample
collection.
• Functionalities:
• Create and manage phlebotomist profiles, including contact information and work schedules.
• Assign phlebotomists to test appointments based on availability and geographical location.
• Track the performance and workload of phlebotomists to optimize scheduling and resource allocation.
Module 5: Reporting and Analytics
• Description: This module provides reporting tools and analytics to monitor COVID19 testing activities, trends,
and performance metrics.
• Functionalities:
• Generate reports on test volumes, turnaround times, and positivity rates for different demographics and
geographical regions.
• Analyze trends in test results over time to identify emerging patterns and hotspots.
• Visualize data using charts, graphs, and maps to facilitate decision-making and public health
interventions.
Module 6: Security and Access Control
• Description: This module ensures the security of patient data and system functionality through access control
mechanisms and user authentication.
• Functionalities:
• Implement role-based access control (RBAC) to restrict access to sensitive information and system
features based on user roles and permissions.
• Enforce strong authentication mechanisms, such as two-factor authentication (2FA), to verify user
identities and prevent unauthorized access.
• Encrypt sensitive data at rest and in transit to protect patient confidentiality and comply with data
protection regulations.
Module 7: Integration and Interoperability
• Description: This module facilitates integration with external systems and interoperability with healthcare
infrastructure to streamline data exchange and workflow automation.
• Functionalities:
• Integrate with electronic health record (EHR) systems to exchange patient information and test results
seamlessly.
• Implement standardized interfaces and protocols, such as HL7 and FHIR, to ensure compatibility with
third-party applications and medical devices.
• Enable data exchange with public health agencies and reporting platforms to support epidemiological
surveillance and outbreak response efforts.
EXP.NO:7

DATABASE CONNECTIVITY

<?php
//time zone
date_default_timezone_set('Asia/Kolkata');
//database connection
$con=mysqli_connect("localhost","root","","covidtmsdb");
if(mysqli_connect_errno()){
echo "Connection Fail".mysqli_connect_error();
}

?>

SQL CONNECTION
-- phpMyAdmin SQL Dump
-- version 4.9.0.1
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: May 08, 2021 at 03:05 PM
-- Server version: 10.3.15-MariaDB
-- PHP Version: 7.2.19

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

SET AUTOCOMMIT = 0;
START TRANSACTION;
SET time_zone = "+00:00";

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;

/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8mb4 */;

--
-- Database: `covidtmsdb`
--

-- --------------------------------------------------------

--
-- Table structure for table `tbladmin`
--

CREATE TABLE `tbladmin` (

`ID` int(11) NOT NULL,
`AdminName` varchar(120) DEFAULT NULL,
`AdminuserName` varchar(20) NOT NULL,
`MobileNumber` int(10) NOT NULL,
`Email` varchar(120) NOT NULL,
`Password` varchar(120) DEFAULT NULL,
`AdminRegdate` timestamp NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `tbladmin`
--

INSERT INTO `tbladmin` (`ID`, `AdminName`, `AdminuserName`, `MobileNumber`, `Email`, `Password`,

`AdminRegdate`) VALUES
(2, 'Admin', 'admin', 1234567890, '[email protected]', 'f925916e2754e5e03f75dd58a5733251', '2021-04-19
18:30:00');

-- --------------------------------------------------------

--
-- Table structure for table `tblpatients`
--

CREATE TABLE `tblpatients` (

`id` int(11) NOT NULL,
`FullName` varchar(120) DEFAULT NULL,
`MobileNumber` bigint(12) DEFAULT NULL,
`DateOfBirth` date DEFAULT NULL,
`GovtIssuedId` varchar(150) DEFAULT NULL,
`GovtIssuedIdNo` varchar(150) DEFAULT NULL,
`FullAddress` varchar(255) DEFAULT NULL,
`State` varchar(200) DEFAULT NULL,
`RegistrationDate` timestamp NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `tblpatients`
--

INSERT INTO `tblpatients` (`id`, `FullName`, `MobileNumber`, `DateOfBirth`, `GovtIssuedId`,

`GovtIssuedIdNo`, `FullAddress`, `State`, `RegistrationDate`) VALUES
(1, 'Anuj kumar', 1234567890, '1999-02-01', 'Driving License', '342545445345', 'A83748 New Delhi India',
'Delhi', '2021-04-27 17:31:22'),
(2, 'Sarita', 6547893210, '1990-05-09', 'Pancard', 'HHHGHGH8888jh', 'H 826273 Noida', 'Uttar Pradesh',
'2021-04-27 18:04:57'),
(4, 'Garima Singh', 4598520125, '2005-01-08', 'Pancard', 'DDDKJKJ454545H', 'A-1234 Patna', 'Bihar',
'2021-05-08 05:49:44'),
(5, 'Amit Singh', 2536987410, '2007-06-01', 'PANCARD', 'HJGGHG76767HGGH', 'H 37334 New Delhi', 'Delhi',
'2021-05-08 09:25:50'),
(6, 'Rahul Yadav', 1234567899, '2003-06-05', 'Driving License', '5435345', 'ABC 123 XYZ Street Noida', 'Uttar
Pradesh', '2021-05-08 09:29:22');

-- --------------------------------------------------------

--
-- Table structure for table `tblphlebotomist`
--

CREATE TABLE `tblphlebotomist` (

`id` int(11) NOT NULL,
`EmpID` varchar(100) DEFAULT NULL,
`FullName` varchar(120) DEFAULT NULL,
`MobileNumber` bigint(12) DEFAULT NULL,
`RegDate` timestamp NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `tblphlebotomist`
--

INSERT INTO `tblphlebotomist` (`id`, `EmpID`, `FullName`, `MobileNumber`, `RegDate`) VALUES

(3, '12587493', 'Amit Singh', 9876543212, '2021-05-03 04:51:44'),
(4, '105202365', 'Rahul', 8529631470, '2021-05-03 04:52:06'),
(5, '10802364', 'Sanjeev Tomar', 1234567890, '2021-05-08 09:34:11');

-- --------------------------------------------------------

--
-- Table structure for table `tblreporttracking`
--

CREATE TABLE `tblreporttracking` (

`id` int(11) NOT NULL,
`OrderNumber` bigint(40) DEFAULT NULL,
`Remark` varchar(255) DEFAULT NULL,
`Status` varchar(120) DEFAULT NULL,
`PostingTime` timestamp NULL DEFAULT current_timestamp(),
`RemarkBy` int(5) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `tblreporttracking`
--

INSERT INTO `tblreporttracking` (`id`, `OrderNumber`, `Remark`, `Status`, `PostingTime`, `RemarkBy`)

VALUES
(1, 450040675, 'The Phlebotomist is on the way for collection.', 'On the Way for Collection', '2021-05-06
04:36:22', 2),
(6, 450040675, 'Sample collection.', 'Sample Collected', '2021-05-06 19:15:25', 2),
(7, 450040675, 'Sample sent to the lab.', 'Sent to Lab', '2021-05-06 19:15:48', 2),
(9, 450040675, 'Report uploaded.', 'Delivered', '2021-05-06 20:01:48', 2),
(10, 617325549, 'The phlebotomist is on the way to sample collection.', 'On the Way for Collection', '2021-05-07
04:44:38', 2),
(11, 617325549, 'Sample collected successfully.', 'Sample Collected', '2021-05-07 04:46:46', 2),
(12, 617325549, 'Sample sent to the lab.', 'Sent to Lab', '2021-05-07 04:51:25', 2),
(13, 617325549, 'Report uploaded.', 'Delivered', '2021-05-07 04:57:20', 2),
(14, 250482553, 'On the way for sample collection.', 'On the Way for Collection', '2021-05-08 09:31:42', 2),
(15, 250482553, 'Sample collected successfully', 'Sample Collected', '2021-05-08 09:32:06', 2),
(16, 250482553, 'Sample sent to lab', 'Sent to Lab', '2021-05-08 09:32:26', 2),
(17, 250482553, 'Report Uploaded', 'Delivered', '2021-05-08 09:32:51', 2);

-- --------------------------------------------------------

--
-- Table structure for table `tbltestrecord`
--

CREATE TABLE `tbltestrecord` (

`id` int(11) NOT NULL,
`OrderNumber` bigint(14) DEFAULT NULL,
`PatientMobileNumber` bigint(14) DEFAULT NULL,
`TestType` varchar(100) DEFAULT NULL,
`TestTimeSlot` varchar(120) DEFAULT NULL,
`ReportStatus` varchar(100) DEFAULT NULL,
`FinalReport` varchar(150) DEFAULT NULL,
`ReportUploadTime` varchar(200) DEFAULT NULL,
`RegistrationDate` timestamp NULL DEFAULT current_timestamp(),
`AssignedtoEmpId` varchar(150) DEFAULT NULL,
`AssigntoName` varchar(180) DEFAULT NULL,
`AssignedTime` varchar(100) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `tbltestrecord`
--

INSERT INTO `tbltestrecord` (`id`, `OrderNumber`, `PatientMobileNumber`, `TestType`, `TestTimeSlot`,

`ReportStatus`, `FinalReport`, `ReportUploadTime`, `RegistrationDate`, `AssignedtoEmpId`, `AssigntoName`,
`AssignedTime`) VALUES
(1, 450040675, 1234567890, 'Antigen', '2021-05-01T04:05', 'Delivered',
'2c86e2aa7eb4cb4db70379e28fab9b521620331308.pdf', '07-05-2021 01:31:48 AM', '2021-04-27 17:31:23',
'12587493', 'Amit Singh', '06-05-2021 10:05:22 AM'),
(2, 617325549, 6547893210, 'RT-PCR', '2021-05-01T05:10', 'Delivered',
'2c86e2aa7eb4cb4db70379e28fab9b521620363440.pdf', '07-05-2021 10:27:20 AM', '2021-04-27 18:04:58',
'105202365', 'Rahul', '07-05-2021 10:13:41 AM'),
(4, 740138296, 1234567890, 'RT-PCR', '2021-05-05T14:40', 'Assigned', NULL, NULL, '2021-04-27 19:10:30',
'105202365', 'Rahul', '07-05-2021 03:52:05 PM'),
(5, 716060226, 4598520125, 'CB-NAAT', '2021-05-15T14:22', NULL, NULL, NULL, '2021-05-08 05:49:46',
NULL, NULL, NULL),
(6, 599452326, 2536987410, 'CB-NAAT', '2021-05-20T19:00', NULL, NULL, NULL, '2021-05-08 09:25:50',
NULL, NULL, NULL),
(7, 250482553, 1234567899, 'Antigen', '2021-05-11T15:00', 'Delivered',
'2c86e2aa7eb4cb4db70379e28fab9b521620466371.pdf', '08-05-2021 03:02:51 PM', '2021-05-08 09:29:22',
'12587493', 'Amit Singh', '08-05-2021 03:00:47 PM');

--
-- Indexes for dumped tables
--

--
-- Indexes for table `tbladmin`
--
ALTER TABLE `tbladmin`
ADD PRIMARY KEY (`ID`);

--
-- Indexes for table `tblpatients`
--
ALTER TABLE `tblpatients`
ADD PRIMARY KEY (`id`);

--
-- Indexes for table `tblphlebotomist`
--
ALTER TABLE `tblphlebotomist`
ADD PRIMARY KEY (`id`);

--
-- Indexes for table `tblreporttracking`
--
ALTER TABLE `tblreporttracking`
ADD PRIMARY KEY (`id`);

--
-- Indexes for table `tbltestrecord`
--
ALTER TABLE `tbltestrecord`
ADD PRIMARY KEY (`id`);

--
-- AUTO_INCREMENT for dumped tables
--

--
-- AUTO_INCREMENT for table `tbladmin`
--
ALTER TABLE `tbladmin`
MODIFY `ID` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;

--
-- AUTO_INCREMENT for table `tblpatients`
--
ALTER TABLE `tblpatients`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=7;

--
-- AUTO_INCREMENT for table `tblphlebotomist`
--
ALTER TABLE `tblphlebotomist`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6;

--
-- AUTO_INCREMENT for table `tblreporttracking`
--
ALTER TABLE `tblreporttracking`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=18;

--
-- AUTO_INCREMENT for table `tbltestrecord`
--
ALTER TABLE `tbltestrecord`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=8;
COMMIT;

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
EXP.NO:8

PL/SQL procedures to Operate on the database of my project

1. Insert Procedure
CREATE OR REPLACE PROCEDURE InsertPatient(
p_fullname IN VARCHAR2,
p_mobile_number IN NUMBER,
p_date_of_birth IN DATE,
p_govt_issued_id IN VARCHAR2,
p_govt_issued_id_no IN VARCHAR2,
p_full_address IN VARCHAR2,
p_state IN VARCHAR2
) AS
BEGIN
INSERT INTO tblpatients (FullName, MobileNumber, DateOfBirth, GovtIssuedId, GovtIssuedIdNo,
FullAddress, State, RegistrationDate)
VALUES (p_fullname, p_mobile_number, p_date_of_birth, p_govt_issued_id, p_govt_issued_id_no,
p_full_address, p_state, SYSDATE);
COMMIT;
END;
/

2. Update Procedure
CREATE OR REPLACE PROCEDURE UpdatePatientAddress(
p_patient_id IN NUMBER,
p_new_address IN VARCHAR2
) AS
BEGIN
UPDATE tblpatients
SET FullAddress = p_new_address
WHERE id = p_patient_id;
COMMIT;
END;
/

3. Delete Procedure
CREATE OR REPLACE PROCEDURE DeletePatient(
p_patient_id IN NUMBER
) AS
BEGIN
DELETE FROM tblpatients
WHERE id = p_patient_id;
COMMIT;
END;
/
4. Retrieval Procedure

CREATE OR REPLACE PROCEDURE GetPatientsByState(

p_state IN VARCHAR2
) AS
BEGIN
FOR patient_rec IN (SELECT * FROM tblpatients WHERE State = p_state) LOOP
DBMS_OUTPUT.PUT_LINE('Patient ID: ' || patient_rec.id || ', Name: ' || patient_rec.FullName || ', Mobile: '
|| patient_rec.MobileNumber);
END LOOP;
END;
/

5. Advanced Procedure

CREATE OR REPLACE PROCEDURE GenerateTestReport(

p_order_number IN NUMBER,
p_report_status IN VARCHAR2,
p_final_report IN VARCHAR2,
p_report_upload_time IN VARCHAR2
) AS
BEGIN
UPDATE tbltestrecord
SET ReportStatus = p_report_status,
FinalReport = p_final_report,
ReportUploadTime = TO_DATE(p_report_upload_time, 'DD-MM-YYYY HH24:MI:SS')
WHERE OrderNumber = p_order_number;
COMMIT;
END;
/
EXP.NO:9

FRONT END

1. ADMIN LOGIN

2. ADMIN DAHSBOARD
3. USER DASHBOARD

4. MANAGE PHLEBOTOMIST
5. TEST

6. REPORT
7. CUSTOMER DASHBOARD

8. TEST REGISTRATION
EXP.NO:10

REPORT GENERATION
EXP.NO:11

ONLINE COURSE COMPLETION CERTIFICATE

CONCLUSION
The COVID19 Testing Management System serves as a crucial solution for the effective management of
activities within COVID19 testing laboratories. Developed as a web-based application, its primary objective is
to streamline operations while accommodating the unique requirements of each testing facility. By digitizing
and automating processes such as patient registration, test tracking, and report generation, the system aims to
enhance efficiency and accuracy in diagnostic management. Throughout its development, particular emphasis
was placed on overcoming challenges associated with manual handling of diagnostic procedures. Transitioning
to an online platform has not only centralized data but also facilitated real-time monitoring of test progress,
ensuring prompt delivery of results to patients. The modular design of the system allows for scalability and
customization, making it adaptable to diverse testing environments.