EPIC 2025

The Problem

This project began as a real operational challenge I faced at Montefiore Hospital during the Epic Go-Live: coordinating 120+ trainers across 7 locations, managing classroom assignments, tracking learner progress, and producing reports — all through a custom Microsoft Access database that one person understood how to operate.

EPIC 2025 is the modernisation of that system: a governed, web-first platform that preserves all the operational fidelity of the original while introducing proper access controls, audit trails, real-time reporting, and self-service APIs for distributed teams.

What Changed

• Data model: Legacy Access tables migrated to SQL Server with normalised schema, governed ETL pipelines, and referential integrity enforced at the database level.
• Access control: Full RBAC implementation — site coordinators, lead trainers, read-only observers — with audit logs on every state change.
• Reporting: Real-time dashboards replacing the previous daily Excel exports. Completion rates, trainer utilisation, and room occupancy available live.
• API layer: FastAPI REST endpoints give distributed teams self-service access to their own scheduling data without going through a central admin.
• CI/CD: GitHub Actions pipeline with automated testing and staged deployments replacing the previous "deploy by emailing a .mdb file" workflow.

Why This Matters

The original system worked — until the one person who knew how to use it wasn't available. EPIC 2025 bakes institutional knowledge into governed infrastructure: every workflow is documented, every role is explicitly modelled, every data change is traceable.

This is the same principle I apply to LMS administration: the platform should be operable by anyone on the team, not just whoever built it.