<aside> 🧪
Independent portfolio case study — simulated only. This project develops an earlier fictional appointment-screen prototype into a proposed outpatient booking workflow and test plan. No NHS patient data, internal screenshots, Epic or Cerner configuration, system integration, formal UAT, clinical approval or service improvement results are claimed.
</aside>
Project type: Independent EPR / clinical systems analysis exercise Focus: Outpatient booking, amendments and cancellations Version: 1.0 · Prepared: November 5, 2026 Status: Workflow/UAT plan complete; separate synthetic state-machine tests executed (8/8 passed after a v0 defect fix). EPR system UAT, integration, security verification and user sign-off remain NOT RUN.
A booking can be clear on screen but still cause problems if the information behind it is not consistent. This case study looks at a common outpatient task: checking an appointment, changing it or cancelling it. The aim is to make the next action clear to the user and show how the same action would need to be handled safely in a staff-facing EPR workflow.
The starting point was Rethinking an appointment screen, a small fictional before-and-after prototype. That exercise improved labels, status messages and confirmation steps. This follow-on project adds workflow mapping, requirements, proposed data rules, test cases and a risk review.
Relevant professional context: Previous NHS outpatient work using Epic and current administrative work using Cerner, alongside earlier nursing experience and an MSc in Health Informatics. Those roles inform the questions asked here; this is not work carried out for an NHS Trust.
Skills demonstrated through the case study: Process mapping · Requirements and acceptance criteria · Traceability · UAT planning · Exception handling · Clinical safety awareness · Clear documentation
In scope
Out of scope
Assumptions for this exercise: One fictional outpatient booking per appointment ID; an authorised user; all dates and identifiers invented; a successful amendment keeps the same appointment ID and a change history. A real Trust might use different identifiers, states and booking policies. Those details would need confirming before implementation.