Hospital Appointment System
➢
Real-world Scenario:
1.
You’re building a backend API for a hospital system where:
Patients can book appointments with doctors.
•
Doctors belong to departments (e.g., Cardiology, Orthopedics).
•
Each appointment has a patient, a doctor, and a scheduled date & time.
•
Patients have medical history records.
•
Appointments are stored in the system and can be retrieved by doctor or patient.
•
Learning Outcomes:
2.
Solidifies understanding of:
OneToMany, ManyToOne, OneToOne
○
DTO + ModelMapper
○
REST API structure
○
Exception Handling using @RestControllerAdvice
○
Avoiding @JsonIgnore —using DTOs instead
○
•
Entities & Relationships
3.
Doctor
➢
id, name, email, mobile, specialization
•
@ManyToOne with Department
•
@OneToMany with Appointment
•
Department
➢
id, name (e.g., "Cardiology", "Orthopedics")
•
@OneToMany with Doctor
•
Patient
➢
id, fullName, age, email, mobile
•
@OneToOne with MedicalHistory
•
@OneToMany with Appointment
•
Appointment
➢
id, appointmentDate, appointmentTime
•
@ManyToOne with Doctor
•
@ManyToOne with Patient
•
MedicalHistory
➢
id, bloodGroup, diseases, allergies
•
@OneToOne with Patient
•
DTO Design
4.
Entity
Field Hidden in DTO
Reason
DoctorDTO
No mobile/email exposed
Privacy
PatientDTO
Hide medical history
Use separate MedicalHistoryDTO
AppointmentDTO
Show doctor name, patient name, date & time
HOSPITAL APPOINTMENT SYSTEM :
19 June 2025
13:08
New Section 1 Page 1
