💡 Tip: Right-click any image and select "Open image in new tab" to view at maximum quality

💡 Tip: You can view this Diagrams more comfortably with 📖 Complete Project Documentation

Complete system architecture showing all components, design patterns, and their relationships

Database schema and table relationships for the healthcare management system

Implementation of Memento pattern for patient history tracking and Prototype pattern for record templates

Mediator pattern implementation for handling appointment conflicts and scheduling logic

Chain of Responsibility pattern for processing insurance claims and payment workflows

Decorator pattern implementation for flexible role-based access control system

Visitor pattern for extensible report generation and data analysis capabilities

Security architecture using Decorator pattern for permissions and DAO pattern for secure data access

🚀 Built with Enterprise Patterns: Memento, Mediator, Chain of Responsibility, Decorator, Visitor, and DAO patterns for maintainable, scalable architecture

graph TB
    A[🖥️ UI Layer - Swing Components] --> B[🎮 Controller Layer - MVC Pattern]
    B --> C[💼 Business Logic Layer]
    C --> D[🗄️ Data Access Layer - DAO Pattern]
    D --> E[🐬 MySQL Database]
    
    F[📝 Memento Pattern] --> G[👤 Patient History]
    H[🤝 Mediator Pattern] --> I[📅 Appointment Scheduling]
    J[⛓️ Chain of Responsibility] --> K[💰 Insurance Processing]
    L[🎨 Decorator Pattern] --> M[🔐 User Permissions]
    N[👁️ Visitor Pattern] --> O[📊 Report Generation]
    
    style A fill:#e1f5fe
    style B fill:#f3e5f5
    style C fill:#e8f5e8
    style D fill:#fff3e0
    style E fill:#ffebee

// Role-based access with Decorator Pattern
IUser user = new BaseUser(username, role, doctorId);
user = new AdminRole(user);  // Adds admin permissions
user = new DoctorRole(user); // Adds doctor permissions

// Check permissions
if (user.hasPermission("PATIENT_MANAGEMENT")) {
    // Access granted
}

// History tracking with Memento Pattern
RecordHistory history = new RecordHistory(patientRecord);
history.save();           // Create snapshot
patientRecord.update();   // Make changes
history.undo();          // Restore previous state

// Prototype pattern for templates
PatientRecord template = TemplateManager.getTemplate("BASIC_PATIENT");
PatientRecord newPatient = template.clone();

// Conflict resolution with Mediator Pattern
SchedulingMediator mediator = new SchedulingMediator();
AppointmentResult result = mediator.scheduleAppointment(
    patient, doctor, dateTime, duration
);

if (result.hasConflict()) {
    List<TimeSlot> alternatives = result.getAlternatives();
}

// Chain of Responsibility for claims
ClaimProcessor basicProcessor = new BasicClaimProcessor();
ClaimProcessor premiumProcessor = new PremiumClaimProcessor();
ClaimProcessor vipProcessor = new VIPClaimProcessor();

basicProcessor.setNext(premiumProcessor).setNext(vipProcessor);
ClaimResult result = basicProcessor.process(claim);

💡 Note: This project uses Java 17+ features for optimal performance and compatibility across different environments..

1. 📥 Clone the Repository

   git clone https://github.com/isharax9/healthcare-system.git
   cd healthcare-system

2. 🗄️ Database Setup

   # Start MySQL and create database
   mysql -u root -p

   CREATE DATABASE globemed_db CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
   USE globemed_db;
   SOURCE globemed_db.sql;

3. ⚙️ Configure Database Connection

   Update src/main/java/com/globemed/db/DatabaseManager.java:

   private static final String JDBC_URL = "jdbc:mysql://localhost:3306/globemed_db";
   private static final String USERNAME = "your_username";  // Update this
   private static final String PASSWORD = "your_password";  // Update this

4. 🔧 Build and Run

   # Clean and compile the project
   mvn clean compile
   
   # Run the application
   mvn exec:java -Dexec.mainClass="com.globemed.Main"
   
   # Create executable JAR
   mvn clean package
   
   # Run the executable JAR
   java -jar target/healthcare-system-1.0-SNAPSHOT-executable.jar

The project includes automated CI/CD pipelines that generate native executables for all major platforms:

Important: Automated releases are temporarily disabled. Use manual tag-based releases.

• Manual Process: Create version tags to trigger releases (git tag v1.0.1 && git push origin v1.0.1)
• Cross-Platform Builds: Automatic builds for Windows, macOS, and Linux on tag push
• Release Packaging: Tagged releases automatically create distributable packages
• GitHub Actions: Fully automated build pipeline with artifact uploads
• Complete Control: Manual control over release timing and versioning

📋 Release Guide: Follow the Manual Release Guide for step-by-step instructions on creating releases. 🔐 CI/CD Configuration: For automated builds with database integration, see the GitHub Secrets Setup Guide to configure repository secrets properly.

# Build for all platforms (requires platform-specific runners)
mvn clean package -DskipTests

# Create Windows installer (requires Windows with jpackage)
jpackage --input target --name "GlobeMed Healthcare System" --main-jar healthcare-system-1.0-SNAPSHOT-executable.jar --main-class com.globemed.Main --type exe

# Create macOS app (requires macOS with jpackage)  
jpackage --input target --name "GlobeMed Healthcare System" --main-jar healthcare-system-1.0-SNAPSHOT-executable.jar --main-class com.globemed.Main --type dmg

# Create Linux packages (requires Linux with jpackage)
jpackage --input target --name "globemed-healthcare-system" --main-jar healthcare-system-1.0-SNAPSHOT-executable.jar --main-class com.globemed.Main --type deb

⚠️ Security Note: Change these default credentials immediately in production environments!

1. Navigate to Patient Records tab
2. Add New Patient: Fill in demographic and insurance information
3. Update Records: Modify existing patient information with automatic history tracking
4. Search Patients: Use filters to quickly locate patient records

1. Go to Appointments tab
2. Schedule New: Select patient, doctor, and available time slot
3. Manage Existing: View, reschedule, or cancel appointments
4. Conflict Resolution: System automatically detects and prevents double-booking

1. Access Billing module
2. Create Bills: Generate charges for services rendered
3. Process Insurance: Automatic calculation of coverage and patient responsibility
4. Payment Tracking: Record payments and manage outstanding balances

1. Navigate to Reports section
2. Select Report Type: Choose from financial, patient, or operational reports
3. Set Parameters: Define date ranges and filters
4. Generate & Export: Create PDF reports for analysis or printing

-- Patient Management
patients (patient_id, name, dob, gender, address, phone, email, insurance_plan_id)
insurance_plans (plan_id, plan_name, coverage_percent, deductible)

-- Appointment System  
appointments (appointment_id, patient_id, doctor_id, appointment_datetime, status)
doctors (doctor_id, name, specialization, phone, email)

-- Billing & Finance
billing (bill_id, patient_id, service_description, amount, status)
payments (payment_id, bill_id, amount_paid, payment_date, payment_method)

-- Staff Management
staff (staff_id, name, role, department, hire_date, salary)
users (user_id, username, password_hash, role, staff_id)

• One-to-Many: Patient → Appointments, Patient → Bills
• Many-to-One: Appointments → Doctor, Bills → Insurance Plan
• One-to-One: User → Staff (for authentication)

The application supports flexible database configuration through environment variables, system properties, or configuration files.

📚 Multiple Configuration Guides Available:

• Environment Setup Guide - Local development setup
• GitHub Secrets Setup Guide - CI/CD and repository configuration
• Contributing Guide - Development workflow

Set the following environment variables:

# Linux/macOS
export DB_URL="jdbc:mysql://localhost:3306/globemed_db"
export DB_USERNAME="your_username" 
export DB_PASSWORD="your_password"

# Windows Command Prompt
set DB_URL=jdbc:mysql://localhost:3306/globemed_db
set DB_USERNAME=your_username
set DB_PASSWORD=your_password

# Windows PowerShell
$env:DB_URL="jdbc:mysql://localhost:3306/globemed_db"
$env:DB_USERNAME="your_username"
$env:DB_PASSWORD="your_password"

When running the application:

java -jar healthcare-system-1.0-SNAPSHOT-executable.jar \
     -Ddb.url="jdbc:mysql://localhost:3306/globemed_db" \
     -Ddb.username="your_username" \
     -Ddb.password="your_password"

# Or with Maven
mvn exec:java -Ddb.url="jdbc:mysql://localhost:3306/globemed_db" \
              -Ddb.username="your_username" \
              -Ddb.password="your_password"

Edit src/main/resources/application.properties:

# Database Configuration
db.url=jdbc:mysql://localhost:3306/globemed_db
db.username=root
db.password=your_password
db.driver=com.mysql.cj.jdbc.Driver

# Application Settings
app.name=GlobeMed Healthcare System
app.version=1.0-SNAPSHOT
app.theme=light

# Report Settings
reports.output.path=./reports/
reports.logo.path=./assets/logo.png

The application uses the following priority order for configuration:

1. Environment Variables (highest priority)
2. System Properties
3. Application Properties File (lowest priority)

This allows for flexible deployment across different environments without code changes.

The system supports custom themes through the UI. Users can toggle between:

• 🌞 Light Theme: Default professional appearance
• 🌙 Dark Theme: Reduced eye strain for extended use

# Run all tests
mvn test

# Run specific test class
mvn test -Dtest=PatientDAOTest

# Generate test coverage report
mvn jacoco:report

# Database integration tests
mvn verify -Pintegration-tests

# UI component tests
mvn test -Dtest=*UITest

public class PatientService {
    public PatientRecord createPatient(PatientData data);
    public List<PatientRecord> searchPatients(SearchCriteria criteria);
    public PatientRecord updatePatient(String patientId, PatientData data);
    public void deletePatient(String patientId);
}

public class AppointmentService {
    public Appointment scheduleAppointment(AppointmentRequest request);
    public List<Appointment> getAppointmentsByDate(LocalDate date);
    public void cancelAppointment(int appointmentId);
    public List<TimeSlot> getAvailableSlots(String doctorId, LocalDate date);
}

public class BillingService {
    public MedicalBill createBill(BillRequest request);
    public PaymentResult processPayment(PaymentRequest request);
    public List<MedicalBill> getOutstandingBills(String patientId);
    public void generatePDFBill(MedicalBill bill, OutputStream output);
}

We welcome contributions! Please follow these guidelines:

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Commit changes (git commit -m 'Add amazing feature')
4. Push to branch (git push origin feature/amazing-feature)
5. Open a Pull Request

• Follow Java coding conventions
• Add JavaDoc comments for public methods
• Write unit tests for new features
• Ensure Maven build passes
• Update documentation for new features

Please include:

• 🐛 Clear description of the issue
• 📝 Steps to reproduce the problem
• 🖥️ Environment details (OS, Java version, MySQL version)
• 📸 Screenshots if applicable

• Development Team: GlobeMed Healthcare Solutions
• Lead Developer: @isharax9
• Architecture: Design Patterns implementation for enterprise healthcare

• Java Community for excellent documentation
• iText team for PDF generation capabilities
• MySQL for robust database support
• Apache Maven for build automation