Hospital Management System

Hospital Management System (Java 21 · Maven)

Overview

A Java-based Hospital Management System demonstrating object‑oriented programming principles (inheritance, polymorphism, encapsulation). The system manages doctors, patients, treatments, departments, and provides an interactive console interface for basic operations and testing.

---

Key Features

• Doctor Management: Three doctor types (Contract, Fixated, Training) with different payment models.
• Patient Management: Support for internal (inpatient) and outpatient tracking, each with a treatment history.
• Treatment System: Differentiates treatments that require hospitalization (internal) from outpatient treatments, with cost tracking.
• Department & Clinic Organization: Structured departments and clinics (e.g., Ambulance, Surgery, DigestiveClinic).
• Date Management: DateManager utility wrapping java.time to standardize parsing/formatting and date operations.
• Interactive Console UI: Menu-driven interface to add, view, and remove entities, and to exercise core functionality.

---

Project Layout

hospital-management/
├─ pom.xml
├─ src/main/java/com/example/hospital/
│  ├─ Main.java
│  ├─ util/
│  │  └─ DateManager.java
│  ├─ model/
│  │  ├─ doctor/
│  │  │  ├─ Doctor.java
│  │  │  ├─ ContractDoctor.java
│  │  │  ├─ FixatedDoctor.java
│  │  │  └─ TrainingDoctor.java
│  │  ├─ patient/
│  │  │  ├─ Patient.java
│  │  │  ├─ InternalPatient.java
│  │  │  └─ OuterPatient.java
│  │  ├─ treatment/
│  │  │  ├─ Treatment.java
│  │  │  ├─ InternalTreatment.java
│  │  │  └─ OuterTreatment.java
│  │  ├─ department/
│  │  └─ clinic/
│  └─ repository/
│     ├─ DoctorRepository.java
│     ├─ PatientRepository.java
│     └─ TreatmentRepository.java
└─ README.md

---

Requirements

• Java 21
• Maven 3.8+ (or a compatible version)

---

Build & Run

1. Build the project:

mvn clean package

2. Run the executable JAR (if using the shade plugin to produce a fat JAR):

java -jar target/hospital-management-1.0.0.jar

Ensure mainClass in pom.xml is set to com.example.hospital.Main.

---

Core Class Overview

Doctors (model.doctor)

• Doctor (base): unique id, name, specialty, and an abstract calculateMonthlyPayment() method.
• ContractDoctor: hourly rate multiplied by hours worked in the month.
• FixatedDoctor: fixed monthly salary plus optional bonus.
• TrainingDoctor: stipend-based payment.

Patients (model.patient)

• Patient (base): personal info and a treatment history list.
• InternalPatient: admission/discharge dates, ward, and lengthOfStayDays() calculation.
• OuterPatient: outpatient record linked to a primary doctor id.

Treatments (model.treatment)

• Treatment (base): date, description, cost, and requiresHospitalization() abstract method.
• InternalTreatment: includes bedDays and requires hospitalization.
• OuterTreatment: outpatient treatment without hospitalization.

Departments & Clinics

• Department and Clinic act as grouping constructs for doctors and related activities. Example subclasses include AmbulanceDepartment and DigestiveClinic.

Repositories

• Simple in-memory repositories: DoctorRepository, PatientRepository, and TreatmentRepository using Map/HashMap. These are intentionally simple so they can be replaced with persistent implementations later.

---

Design and Engineering Considerations

• OOP Principles: Separation of concerns, encapsulation of state, and inheritance to reduce duplication.
• Extensibility: New doctor types, treatments, departments, or clinics can be added without major refactoring.
• Persistence Strategy: In-memory storage is used for simplicity. For production use, integrate with JPA/Hibernate or other persistence layers (e.g., Postgres/MySQL).

---

Contributing

Contributions are welcome: bug fixes, design improvements, and tests. Create a new branch, apply changes, and open a Pull Request describing your changes.

---

Connect with me

instagram : https://www.instagram.com/zain_moh17

Gmail : zyn68640@gmail.com