🩺 1.
SYSTEM REQUIREMENTS
➤ Functional Requirements:
1. Patient Management – Register, update, and search patient records.
2. Doctor Management – Manage doctor information and specialties.
3. Appointment Scheduling – Book and manage appointments.
4. Medical Records – Store diagnoses, prescriptions, and lab results.
5. Billing System – Manage invoices, payments, and insurance.
6. Ward/Bed Management – Track admissions, discharges, and bed availability.
7. Pharmacy Inventory – Track drugs, stock, and dispensation.
8. User Access Control – Different roles: Admin, Doctor, Nurse, Receptionist, Lab Tech.
9. Reports – Generate patient reports, financial reports, drug usage, etc.
➤ Non-Functional Requirements:
Security: Role-based access control, data encryption.
Performance: Fast queries for search and reports.
Scalability: Should support future expansion (e.g., more departments).
Backup/Recovery: Regular backups and disaster recovery.
🧠 2. CONCEPTUAL DESIGN (EER Diagram)
Main Entities:
Patient
Doctor
Appointment
Department
Medical_Record
Prescription
Drug
Bill
Admission
Ward
Bed
User
Key Relationships:
A Patient can have many Appointments
A Doctor can handle many Appointments
Each Appointment can result in a Medical_Record
Medical_Record can have many Prescriptions
Prescription includes multiple Drugs
Patient can be admitted into a Bed in a Ward
A Bill is generated for each Appointment or Admission
User has roles (Admin, Doctor, Nurse, etc.)
🖼️EER Diagram (Textual Form)
plaintext
CopyEdit
Patient (PatientID, Name, DOB, Gender, Address, Phone) Doctor (DoctorID, Name,
Specialty, Phone, DepartmentID) Department (DepartmentID, Name) Appointment
(AppointmentID, PatientID, DoctorID, Date, Time, Status) Medical_Record
(RecordID, AppointmentID, Diagnosis, Notes) Prescription (PrescriptionID,
RecordID, Date) Drug (DrugID, Name, Dosage, StockQty) Prescription_Drug
(PrescriptionID, DrugID, Quantity) Ward (WardID, Name, Capacity) Bed (BedID,
WardID, Status) Admission (AdmissionID, PatientID, BedID, AdmitDate,
DischargeDate) Bill (BillID, PatientID, Amount, Status, Date) User (UserID,
Username, Password, Role, EmployeeID)
🧾 3. LOGICAL DESIGN (Relational Schema)
Example Tables:
sql
CopyEdit
CREATE TABLE Patient ( PatientID INT PRIMARY KEY, Name VARCHAR(100),
DOB DATE,
Gender CHAR(1),
Address TEXT,
Phone VARCHAR(15) );
CREATE TABLE Doctor ( DoctorID INT PRIMARY KEY,
Name VARCHAR(100),
Specialty VARCHAR(100),
Phone VARCHAR(15),
DepartmentID INT );
CREATE TABLE Appointment ( AppointmentID INT PRIMARY KEY,
PatientID INT,
DoctorID INT,
Date DATE, Time TIME,
Status VARCHAR(20),
FOREIGN KEY (PatientID)
REFERENCES Patient(PatientID),
FOREIGN KEY (DoctorID) REFERENCES Doctor(DoctorID)
🗄️4. PHYSICAL DESIGN
Storage:
Use MySQL/PostgreSQL for the database.
Normalize up to 3NF to avoid redundancy.
Use indexing on PatientID, DoctorID, AppointmentID.
Performance Enhancements:
Partitioning large tables like Medical_Record by year.
Materialized Views for frequent reports.
Triggers for automatic bill calculation upon appointment completion.
Security:
Passwords stored using hashing (e.g., bcrypt).
Define user roles using a Role table.
Enable audit logs for sensitive operations.
📌 Sample EER Diagram (Visual)
Would you like me to generate and share an image of this EER diagram?
If so, I’ll include:
Entity shapes with attributes.
Relationships with cardinality (1:1, 1:N, N:M).
Subclasses (e.g., User → Doctor, Nurse, Admin if needed).
Let me know if:
You want it in PDF, PNG, or Word format.
You need code to populate sample data.
You want a web-based or mobile version of the system later.
ARE
AREA OF INTREST : INVETORY MANAGEMENT
