<aside> 🧪
Independent portfolio project — simulated data only
This case study uses 100 entirely simulated outpatient records. No real patient or confidential NHS data was used, and the dashboard has not been deployed or tested in an NHS service.
</aside>
Outpatient teams may need to coordinate referrals, appointments, clinical documentation and outstanding actions across several workflows. I created an Excel-based prototype to explore how structured data and exception reporting could make incomplete or inconsistent records easier to identify.
Project question: How can an outpatient pathway tracker turn row-level administrative data into a concise view of workload, status and data-quality exceptions?
Illustrative users
Simulated scope
The model contains identifiers, referral and appointment details, pathway milestones, status fields and derived quality indicators.
| Field group | Examples | Purpose |
|---|---|---|
| Identifiers | Referral ID, Patient ID | Record control and duplicate checks |
| Referral context | Date, source, specialty, consultant | Workload and ageing analysis |
| Appointment | Type, format, booked status, date | Booking progress and completeness checks |
| Milestones | Note uploaded, patient contacted, check-in, check-out | Outstanding-action logic |
| Derived fields | Days since referral, priority, data-quality flag | Exception reporting and dashboard KPIs |