0% found this document useful (0 votes)
13 views

dfth

The document outlines the functionalities of a patient management system, detailing how patients can view their payment history, search for doctors, and update their personal details. It also describes the process for doctors to enter patient prescriptions and includes a data dictionary and design specifications for various database tables. Key tables include Patient, Appointment, Doctor, Prescription, Admin, and Bill, each with specific attributes and constraints.

Uploaded by

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

dfth

The document outlines the functionalities of a patient management system, detailing how patients can view their payment history, search for doctors, and update their personal details. It also describes the process for doctors to enter patient prescriptions and includes a data dictionary and design specifications for various database tables. Key tables include Patient, Appointment, Doctor, Prescription, Admin, and Bill, each with specific attributes and constraints.

Uploaded by

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

7.

PATIENT PATIENT PATIENT : Can view payment history or can


MODULE search for a particular bill also after this
system shall show a bill or history.

Can also See or search for a doctor by


entering dept. name or doctor id if known
after this system will check for the doctor if
found shall show doctor’s profile.

Can also update details after this system


shall ask for re-enter password and after
verifying password shall update details.
8. ADD DOCTOR DOCTOR : Enter Patient Id and after this all
PRESCRIPTION the treatment details and medicine, remark
and advice for the patient after this system
shall show a message for update.

33 | P a g e
CHAPTER 4
DESIGN

4.1 Data Dictionary


4.2 ER Diagram
4.3 Data Design
4.4 Component Level Diagram

34 | P a g e
4.1 DATA DICTIONARY

1. legal_character [a-z| A-Z]


2. Dig it [0-9]
3. special_ch [@|$|#|+|-]
4. Blood [A|B|AB|O]

1. Name first_name + (middle_name) + last_name


2. first_name {legal_character}*
3. middle_name {legal_character}*
4. last_name {legal_character}*
5. P_ID {legal_character + digit}*
6. D_ID {legal_character + digit}*
7. A_ID {legal_character + digit}*
8. Password {legal_character + digit + special_ch}*
9. Address House_no + (Street) + City
10. House_no {legal_character + digit}*
11. Street {legal_character}*
12. City {legal_character}*
13. Mobile No. { digit }*
14. Blood_Group {Blood + special_ch}*
15. Specialization {legal_character}*
16. Consultant Fee { digit }*
17. Medicine {legal_character + digit}*
18. Advice {legal_character + digit}*
19. Remark {legal_character + digit}*

Table 4.1 Data Dictionary

35 | P a g e
4.2 ER DIAGRAM

36 | P a g e
4.3 DATA DESIGN

S NO. COLUMN DATA CONSTRAINTS DESCRIPTION


NAME TYPE

1. P_ID Varchar(50) Primary Key Contains Unique Id


2. Name Varchar(50) - Contains Name
3. DOB Varchar(50) - Contains Date Of
Birth
4. Gender Varchar(50) - Contains Gender
5. Blood Group Varchar(50) - Contains Blood Group
6. Email ID Varchar(50) - Contains Email Id
7. Address Varchar(50) - Contains Address
8. Mobile No. Integer - Contains Mobile No.
9. CGHS/Private Varchar(50) - Contains Category
Table 4.2 Patient

S NO. COLUMN DATA CONSTRAINTS DESCRIPTION


NAME TYPE

1. P_ID Varchar(50) Primary Key Contains Unique Id


Patient
2. Specialization Varchar(50) - Contains Name of the
Department in which
Patient wants to visit
3. Doctor’s Name Varchar(50) - Contains Doctor
Name Patient Wants
To Visit
4. Consultant Fee Integer - Contains Consultant
Fee Of Doctor
5. Date Date - Contains Date For
The Appointment
6. Time Time - Contains Time For
The Appointment
Table 4.3 Appointment

37 | P a g e
S NO. COLUMN DATA CONSTRAINTS DESCRIPTION
NAME TYPE

1. D_ID Varchar(50) Primary Key Contains unique ID


2. Age Integer - Contains age
3. Gender Varchar(50) - Contains gender
4. Specialization Varchar(50) - Contains
specialization
5. Experience Varchar(50) - Contains experience
of the doctor
(In months)
6. Language Varchar(50) - Contains in how
many languages
doctor can speak.
7. Mobile No. Integer - Contains mobile
number
8. Email ID Varchar(50) - Contains Email Id
9. Schedule Varchar(50) - Contains day and
time for which the
doctor is available
Table 4.4 Doctor

S NO. COLUMN DATA CONSTRAINTS DESCRIPTION


NAME TYPE

1. D_ID Varchar(50) - Contains unique ID


2. P_ID Varchar(50) Primary Key Contains unique ID
3. Medicine Varchar(50) Contains name of the
medicine.
4. Remark Varchar(50) Contains Remark
given by the doctor
for the patient.
5. Advice Varchar(50) Contains any advice
for the patient.
Table 4.5 Prescription

38 | P a g e
S NO. COLUMN DATA CONSTRAINTS DESCRIPTION
NAME TYPE

1. A_ID Varchar(50) Primary Key Contains unique ID.


2. Name Varchar(50) - Contains Name
3. DOB Varchar(50) - Contains Date Of
Birth
4. Gender Varchar(50) - Contains Gender
5. Email ID Varchar(50) - Contains Email Id
6. Mobile No. Integer - Contains Mobile No.
7. Address Varchar(50) - Contains Address
Table 4.6 Admin

S NO. COLUMN DATA CONSTRAINTS DESCRIPTION


NAME TYPE

1. P_ID Varchar(50) - Contains unique ID.


2. Bill No. Varchar(50 Primary Key Contains number of
the bill.
3. Date Varchar(50 - Contains Date of The
bill.
4. Time Varchar(50 - Contains Time of the
bill generated.
5. Amount Int - Contains amount of
the bill.
Table 4.7 Bill

39 | P a g e

You might also like