System Overview

GlobeMed Healthcare Management System

Foundation & Overview Document

Project Name: GlobeMed Healthcare Management System

Repository: https://github.com/isharax9/healthcare-system (opens in a new tab)

Author: Ishara Lakshitha

Purpose: Academic/Educational - Design Patterns Implementation

1. Project Introduction

The GlobeMed Healthcare Management System is a comprehensive Java-based desktop application designed to demonstrate advanced software engineering principles through practical implementation of specific design patterns. This system serves as both a functional healthcare management solution and an educational resource for understanding enterprise-level software architecture with targeted pattern implementations.

Key Features

  • Patient Record Management with state restoration using Memento Pattern
  • Appointment Scheduling with complex interaction mediation using Mediator Pattern
  • Billing & Insurance Processing with flexible workflow using Chain of Responsibility Pattern
  • Role-Based Access Control with dynamic permissions using Decorator Pattern
  • Medical Report Generation with extensible operations using Visitor Pattern
  • Security Implementation through multiple complementary patterns

2. System Objectives

Primary Educational Objectives

  • Targeted Pattern Implementation: Demonstrate real-world application of 6 specific design patterns
  • Problem-Solving Architecture: Each module addresses specific healthcare domain problems
  • Clean Architecture: Showcase proper separation of concerns and layered architecture
  • Security Through Design: Role-based access control with comprehensive data protection

Functional Objectives

  • Complete Healthcare Workflow: Patient registration to billing completion
  • Multi-Role User Support: Doctors, Nurses, and Administrative staff with distinct capabilities
  • Data Integrity & Recovery: State management with undo functionality
  • Flexible Processing: Configurable workflow chains for billing operations
  • Comprehensive Reporting: Extensible report generation system

3. Technology Stack

Core Technologies

ComponentTechnology / Version
LanguageJava
Development KitJDK 21
DatabaseMySQL 9.3.0
UI FrameworkJava SE Swing
PDF GenerationiTextPDF Library, pdfBox Library
Build ToolApache Maven

Dependencies & Libraries

<!-- Database Connectivity -->
<dependency>
    <groupId>com.mysql</groupId>
    <artifactId>mysql-connector-j</artifactId>
    <version>8.2.0</version>
</dependency>
 
<!-- PDF Generation -->
<dependency>
    <groupId>com.itextpdf</groupId>
    <artifactId>itextpdf</artifactId>
    <version>5.5.13.3</version>
</dependency>
 
<!-- PDF Utilities -->
<dependency>
    <groupId>org.apache.pdfbox</groupId>
    <artifactId>pdfbox</artifactId>
    <version>2.0.29</version>
</dependency>

4. Architecture Overview

Entity-Relationship Diagram (EER)

EER.png

Complete Application UML Class Diagram

Complete Application UML Class Diagram.png

(You can find the High Res images in the Github Project Repo)

System Architecture Type

Layered Architecture with Pattern-Specific Module Design

┌─────────────────────────────────────────┐
│             Presentation Layer          │
│     (UI Panels, Controllers, Dialogs)   │
├─────────────────────────────────────────┤
│              Business Layer             │
│  (Pattern Implementations, Domain Logic)│
├─────────────────────────────────────────┤
│            Data Access Layer            │
│         (DAOs, Database Manager)        │
├─────────────────────────────────────────┤
│             Database Layer              │
│          (MySQL Database)               │
└─────────────────────────────────────────┘

5. System Requirements

Minimum System Requirements

  • Operating System: Windows 10+, macOS 10.14+, Linux (Ubuntu 18.04+)
  • Java Runtime: JRE 21 or higher
  • Memory: 4GB RAM minimum, 8GB recommended
  • Storage: 100MB for application, 1GB for data
  • Database: MySQL 8.0+ or MariaDB 10.3+

Development Requirements

  • JDK: OpenJDK 21 or Oracle JDK 21+
  • Build Tool: Apache Maven 3.8+
  • Database: MySQL Server 9.3.0+ with admin privileges
  • IDE: IntelliJ IDEA 2023+, Eclipse 2023+, or VS Code with Java extensions

6. Project Structure

Package Organization by Design Pattern

com.globemed/
├── Main.java                           # Application Entry Point
├── patient/                           # Part A: Memento & Prototype Patterns
│   ├── PatientRecord.java             # Originator (Memento) + Prototype
│   ├── PatientRecordMemento.java      # Memento class
│   └── RecordHistory.java             # Caretaker for undo functionality
├── appointment/                       # Part B: Mediator Pattern
│   ├── Appointment.java               # Domain entity
│   ├── Doctor.java                    # Domain entity
│   └── AppointmentScheduler.java      # Mediator for complex scheduling
├── billing/                          # Part C: Chain of Responsibility
│   ├── MedicalBill.java              # Request object
│   ├── Handler.java                  # Abstract handler interface
│   ├── ValidationHandler.java        # Concrete handler
│   ├── InsuranceHandler.java         # Concrete handler
│   └── FinalBillingHandler.java      # Concrete handler
├── auth/                             # Part D: Decorator Pattern
│   ├── IUser.java                    # Component interface
│   ├── BaseUser.java                 # Concrete component
│   ├── UserRoleDecorator.java        # Abstract decorator
│   ├── DoctorRole.java               # Concrete decorator
│   ├── AdminRole.java                # Concrete decorator
│   └── AuthService.java              # Authentication service
├── reports/                          # Part E: Visitor Pattern
│   ├── Visitable.java                # Element interface
│   ├── ReportVisitor.java            # Visitor interface
│   ├── PatientSummaryReportVisitor.java   # Concrete visitor
│   ├── FinancialReportVisitor.java        # Concrete visitor
│   └── AgedReceivablesReportVisitor.java  # Concrete visitor
├── staff/                            # Supporting entities
│   └── Staff.java                    # Staff management
├── insurance/                        # Supporting entities
│   └── InsurancePlan.java            # Insurance coverage
├── db/                              # Data Access Layer (DAO Pattern)
│   ├── DatabaseManager.java         # Connection management
│   ├── PatientDAO.java              # Patient data operations
│   ├── SchedulingDAO.java           # Appointment data operations
│   ├── BillingDAO.java              # Billing data operations
│   └── StaffDAO.java                # Staff data operations
├── controller/                      # MVC Controllers
│   ├── PatientController.java       # Patient management logic
│   ├── AppointmentController.java   # Appointment management logic
│   ├── BillingController.java       # Billing management logic
│   ├── ReportController.java        # Report generation logic
│   └── StaffController.java         # Staff management logic
├── ui/                             # User Interface Layer
│   ├── MainFrame.java              # Main application window
│   ├── LoginDialog.java            # Authentication interface
│   ├── PatientPanel.java           # Patient management UI
│   ├── AppointmentPanel.java       # Appointment management UI
│   ├── BillingPanel.java           # Billing management UI
│   ├── ReportPanel.java            # Report generation UI
│   └── StaffPanel.java             # Staff management UI
└── utils/                          # Utility Classes
    ├── BillPrinter.java            # PDF generation utilities
    └── TextReportPrinter.java      # Report formatting utilities

7. Core Application Modules & Design Patterns

7.1 Part A: Patient Record Management

  • Patterns Used: Memento, Prototype
  • Key Classes: PatientRecord (Originator), PatientRecordMemento, RecordHistory (Caretaker)
  • Implementation:
    • Memento pattern captures patient state for undo functionality
    • Prototype pattern enables efficient patient template creation
  • Problem Solved: State restoration without breaking encapsulation

7.2 Part B: Appointment Scheduling

  • Pattern Used: Mediator
  • Key Class: AppointmentScheduler (Mediator)
  • Implementation:
    • Centralizes complex scheduling logic
    • Manages interactions between Patients, Doctors, and Schedules
    • Handles conflict detection and booking validation
  • Problem Solved: Reduces coupling between scheduling components

7.3 Part C: Billing and Insurance Claims

  • Pattern Used: Chain of Responsibility
  • Key Classes: ValidationHandler, InsuranceHandler, FinalBillingHandler
  • Implementation:
    • Multi-step billing workflow
    • Each handler performs specific processing
    • Flexible chain configuration
  • Problem Solved: Extensible processing pipeline for complex billing rules

7.4 Part D: Managing Medical Staff Roles and Permissions

  • Pattern Used: Decorator
  • Key Classes: IUser (Component), BaseUser, DoctorRole, AdminRole (Decorators)
  • Implementation:
    • Dynamic permission assignment at runtime
    • Flexible role composition
    • Layered permission system
  • Problem Solved: Role-based access control without rigid inheritance

7.5 Part E: Generating Medical Reports

  • Pattern Used: Visitor
  • Key Classes: ReportVisitor, PatientSummaryReportVisitor, FinancialReportVisitor
  • Implementation:
    • Separates report logic from data models
    • Extensible report types
    • Traverses object structures for data collection
  • Problem Solved: Add new report types without modifying core models

7.6 Part F: Security Considerations

  • Patterns Discussed: Decorator, DAO
  • Implementation:
    • Decorator pattern provides access control foundation
    • DAO pattern centralizes database security
    • Parameterized queries prevent SQL injection
  • Problem Solved: Comprehensive security through design patterns

8. Getting Started

8.1 Prerequisites

# Verify Java installation
java --version  # Should show Java 21+
 
# Verify Maven installation
mvn --version   # Should show Maven 3.8+
 
# Verify MySQL installation
mysql --version # Should show MySQL 8.0+

8.2 Database Setup

-- 1. Create database
CREATE DATABASE globemed_db;
 
-- 2. Import schema
mysql -u root -p globemed_db < globemed_db.sql
 
-- 3. Verify tables
USE globemed_db;
SHOW TABLES;

8.3 Application Compilation

# 1. Clone/Extract repository
cd healthcare-system
 
# 2. Compile project
mvn clean compile
 
# 3. Run application
mvn exec:java -Dexec.mainClass="com.globemed.Main"

8.4 Design Pattern Testing Flow

  1. Patient Management (Memento/Prototype): Create patient → Edit → Use Undo functionality
  2. Appointment Scheduling (Mediator): Book appointments → Observe conflict resolution
  3. Billing Processing (Chain of Responsibility): Process bills → See multi-step validation
  4. Role Management (Decorator): Login with different roles → Observe permission differences
  5. Report Generation (Visitor): Generate various reports → See extensible report system

8.5 Default Login Credentials

RoleUsernamePasswordDesign Pattern Demo
Adminadmin1101Full Decorator permissions
Doctordoc1101Doctor-specific decorations
Nursenurse1101Limited permission decorations

9. User Interface (UI) Screenshots

Login Page UI

image.png

Admin POV Native UI Theme

image.png

Admin POV FlatLaf UI Theme

image.png

Admin POV Patient Management

image.png

Admin POV Appointments

image.png

Admin POV Billing

image.png

Admin POV Reports

image.png

Admin POV Staff Management

image.png

Nurse POV

image.png

Doctor POV

image.png

Next Documentation Phases

The subsequent documents will provide detailed analysis of each design pattern implementation:

  • Document 02: Part A - Patient Record Management (Memento & Prototype Patterns)
  • Document 03: Part B - Appointment Scheduling (Mediator Pattern)
  • Document 04: Part C - Billing & Insurance Claims (Chain of Responsibility Pattern)
  • Document 05: Part D - Staff Roles & Permissions (Decorator Pattern)
  • Document 06: Part E - Medical Report Generation (Visitor Pattern)
  • Document 07: Part F - Security Implementation & Additional Patterns
IntroductionPatient Record Management