0% found this document useful (0 votes)
74 views16 pages

Case Study On: Clinic Management System

This document describes a case study for automating a clinic management system. It discusses features like increased efficiency and cost effectiveness. It outlines the entities in the system - patients, doctors, clinics and records. Attributes for each entity are listed along with an E-R diagram showing relationships. The document discusses anomalies in data storage and provides examples. It describes normalization to 1NF, 2NF and 3NF to resolve anomalies. Queries are presented to retrieve relevant information from the normalized tables such as patient name by address or doctor name by qualification.

Uploaded by

Sabin Khadka
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
74 views16 pages

Case Study On: Clinic Management System

This document describes a case study for automating a clinic management system. It discusses features like increased efficiency and cost effectiveness. It outlines the entities in the system - patients, doctors, clinics and records. Attributes for each entity are listed along with an E-R diagram showing relationships. The document discusses anomalies in data storage and provides examples. It describes normalization to 1NF, 2NF and 3NF to resolve anomalies. Queries are presented to retrieve relevant information from the normalized tables such as patient name by address or doctor name by qualification.

Uploaded by

Sabin Khadka
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

Case Study On

Clinic Management System


Sabin Khadka
2017006101
CSE-A
Presentation outline:

 Introduction
 Features
 Project description
 E-R diagram
 Normalization
 Conclusion
 Queries
Introduction:

 This case study is for automation of tiny clinic management.


 It can be used in any clinic, pharmacy or dispensary for maintaining patient
details and there results.
 This gives the details of patients, doctors and clicnic.
Features:

o Highly efficient for smaller clinic management


o Less manual effort
o Cost effective
o Increased patient care.
Project Description:

 This project includes the registration of patients, storing their details and
their records.
 It has 4 entities. They are patient, Doctor, Clicnic and Record.
 Patient attributes:[patient_id, patient_name, phone, Address]
 Doctor attributes:[Doctor_id, Doctor_name, Qualification]
 Clinic attributes: [ Clinic_id, Clinic_name, clinic_address]
 Record attributes: [record_id, date of examination, problem]
Cont..
 Here,
 Patient_id, Doctor_id, Record_id and Clinic_id are composite keys.
 (patient_id, Doctor_id,Record_id, Clinic_id)→[patient_id, Patient_name, Address,
Phone, Doctor_id, Doctor_name, Qualification, Record_id, Date of examination,
Problem, Clinic_id, Clinic_name, Clinic_Address]

 PATIENT_ID is taken as foreign key.


 Functional dependencies are shown below:
 Patient_id → [patient_id, patient_name, Address, Phone]
 Doctor_id →[Doctor_id, Doctor_name, Qualifiacation]
 Record_id →[ Record_id, Date of examination, Problem]
 Clinic_id → [Clinic_id, Clinic_name, Clinic_address]
Clinic_name
Patient_id

Clinic_id Clinic_addresess
Patient_nameme


Address Admitted Clinic
Patients
to

Phone

Has
Has

Record_id

Problem
Records Doctor

Doctor_id Qualification
Date of Examine

Doctor_name

 E-R Diagram of Clinic Management System.


Example: let us assume following table. The anomalies present in the table
are:
Patie Patie Addr Pho Doct Doct Qualifi Clin Clinic Cl Reco DO proble
nt nt ess ne or or cation ic name ini rd T m
c
id nam id nam id id
e e a
d
dr
es
s
1801 Sam sarla 9800 001 Davi MBBS 101 ABC S 2000 1st Fever
hi 0 d ar jan
la
hi
1802 Bill Bara 9811 04 Dan MBBS 104 ABC S 2001 15th Malaria
1 ny ar feb
la
hi
1803 Nisha Jhap 9822 03 Lara HA 103 ABC S 2002 16th Wound
a 2 ar ma
la
y
hi
1804 Tara KTM 9833 02 jenny MBBS 102 ABC S 2007 19th Cancer
3 ar de
la
c
The anomalies in the table can be:

 1. update Anomaly: It exists when one or more instance of duplicated data is


updated, but not all.
 2. Insert Anomaly: it Occurs when certain attributes cannot be inserted into the data
base without the presence of other attributes.
 3. Delete Anomaly: it exists when certain attributes are lost because of the deletion of
other attribute.

 SOLUTION: The solution for this anomalies is solved through Normalization.


1 NF: A relational schema is in 1 NF if it contains the atomic values in its cell.

Patient Patient Address Phone Doctor Doctor Qualification Clinic Clinic Clinic Record DOT problem

id name id name id name address id

1801 Sam sarlahi 98000 001 David MBBS 101 ABC Sarlahi 2000 1st jan Fever

1802 Bill Bara 98111 04 Danny MBBS 104 ABC Sarlahi 2001 15th Malaria

feb

1803 Nisha Jhapa 98222 03 Lara HA 103 ABC Sarlahi 2002 16th Wound

may

1804 Tara KTM 98333 02 jenny MBBS 102 ABC Sarlahi 2007 19th Cancer

dec
2 NF: A relational schema is in 2 NF if it is in 1 NF and if every non prime attribute are fully functional
dependent on primary key.

Patient_id Patient_name Address Phone

1801 Sam Sarlahi 98000

1802 Bill Bara 98111

1803 Nisha Jhapa 98222

1804 Tara KTM 98333

Patient_id Doctor_id Doctor_name Qualification

1801 001 David MBBS

1802 04 Danny MBBS

1803 03 Lara HA

1804 02 jenny MBBS


Cont..
Patient_id Record_id Date of Examine problem

1801 2000 1st jan Fever

1802 2001 15th feb Malaria

1803 2002 16th may Wound

1804 2007 19th dec Cancer

clinic_id Clinic_name Clinic_address

101 ABC Sarlahi


-The following table is already in 3 NF as no
non prime attribute are transitively
dependent on primary keys.
 Conclusion:
 The project Clinic Management System is for monitoring the work on clinic.
It takes care of all the requirement of an average clinic and is capable to
provide easy and effective storage of information related to patients that
come to the clinic.
Queries:

 Q.1) Find the patient_id and patient_name whose address is Sarlahi.


= select patient_id and patient_name
from patient
where Address=“Sarlahi”.
Output: patient_id Patient_name

1801 Sam

Q.2) Find the name of patient who has a problem of Malaria.


= Select p.patient_name
Patient_name
from patient p and Record R
Bill
where p.patient_id=R.patient_id and R.problem=“Malaria”.
 Q.3) Find the Name of all Doctors whose Qualification is MBBS.
 = Select Doctor_name
 from Doctor
 where Qualification=“MBBS”

Doctor_name

David

Danny

Jenny


THANK YOU ………..

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy