Cnit272 5
Cnit272 5
Cnit272 5
Project
Instructor
Section
Assignment Number
Semester
Deadline
The system helps hospitals meet the specific needs by enabling them to manage their patients
with ease and precision. The system handles a wide range of clinic activities, from patient
records to delivering check-ups patients, while ensuring timely and cost-effective operations.
Main Functionality:
The development of this system uses the iterative development approach. With incremental
enhancements added at each phase. Collaborating closely with clinicians, the development team
gathers requirements, designs the system architecture, implements functionalities, and conducts
rigorous testing to ensure seamless deployment.
1) The system should ensure data security. This includes data encryption and access controls
to safeguard sensitive data in the database.
2) The system grants user roles and permissions. This system must offer user roles at
different levels such as hospital managers or patients, with appropriate access levels to
maintain data confidentiality and integrity.
3) The system must of offer appointment scheduling. This system must provide a platform
for patients to book for services in good time and update about their treatment plans to be
viewed by their specific clinical personnels.
4) The system must generate reports. Report generation on information such as medicine
stock, booking status and patient population are crucial to aid decision-making and
performance evaluation.
Page 3 of 11
The clinic management System will enhance the quality of clinical operations and business logic.
By automation of these processes, information access to healthcare providers and patients, the
system ensures better services to clinical service providers.
The entity-relationship model for this system contains complex features. This section explores
the entities, attributes, relationships, and the cardinalities for the system’s database:
Entities
1. Patient:
The patient entity has attributes as follows: patient_id as the primary key,first_name,
last_name, email, phone_number and address
2. Appointment:
This entity has attributes as follows: appointment_id (primary key), appointment_date,
patient_id (foreign key), doctor_id (foreign key), status and total_fee.
3. Doctor: The doctor entity has doctor_id (primary key), first_name, last_name,
specialization, email and phone_number.
4. Treatment:
This entity has treatment_id (primary key), treatment_name, description and fee.
1. Appointment-Patient (One-to-Many):
For instance, a patient with many appointments, but each appointment only associated
with only one patient.
2. Appointment-Doctor (One-to-Many):
For instance, one doctor can have many appointments, but only one appointment is
associated with only one doctor.
Multiple treatments can be part of multiple appointments, and each appointment can have
multiple treatments.
1. Patient table:
The primary key is patient_id.
2. Appointment table:
The primary key is appointment_id.
3. Doctor table:
The primary key is doctor_id.
4. Treatment table:
The primary key is treatment_id.
Supertype/Subtype Relationships:
The relational schema for the Logistics Management System is designed as follows:
The relational schema for the Clinic Management System is designed as follows:
last_name
phone_number
address
appointment_date
status
total_fee
first_name
last_name
specialization
phone_number
treatment_name
description
fee
Functional dependencies:
Referential integrity:
Relational Schema:
THE SQL DATABASE
CONCLUSION
This management system provides the solution for automation of clinical operations. This project
helped us to learn about development of a well-designed database. The designing of the Entity-
Relationship model, relational schema, and SQL queries to manage patients, healthcare
providers, treatment, and data security were the main takeaway.
Through the implementation of the database, this system enhances clinical processes and reduces
manual errors. The EER model helped us to understand the designing of a relational schema and
defining various tables and constraints in the database.
Throughout the project, we learned crucial aspects like data security, user roles and permissions,
treatment tracking, and report generation to meet the specific requirements and business rules of
clinical setup. The iterative approach ensured that the development of this system followed the
right steps and phases to deliver the program in time and provided a user-friendly interface.
I. REFERENCES
Brumm, B. (2019). Beginning Oracle SQL for Oracle Database 18c: From Novice to
Professional. Apress.