<aside> 🧪

Independent simulated portfolio project — not NHS system testing

All appointment records, rules, test results and workflows are fictional. The checks below were executed against a small standalone mock rule evaluator, not Epic, Cerner or an NHS environment. No patient information, internal screenshots, system configuration, clinical approval or live service outcomes are included.

</aside>

Prepared: October 30, 2026 · Version: 0.1 · Author: Jeongmi Lim · Status: Demonstration prototype; stakeholder review not undertaken

Executive summary

Problem explored: In outpatient administration, an appointment may be booked but lack a date, a departure may be recorded inconsistently, or an action arising from the visit may not have a clear owner. This exercise asks how a simple, traceable set of checks and staff-facing procedures could support reliable handoffs without replacing clinical judgement.

Project objective: Design an illustrative outpatient EPR workflow improvement, translate requirements into testable acceptance criteria, run a small synthetic rules demonstration, and outline the additional UAT and safety assurance needed before any real deployment.

Relevant experience: In professional roles, I have worked with Epic and Cerner as an NHS outpatient administrator and previously worked as a nurse. This page is a separate, independent simulation—not work commissioned, implemented, validated or endorsed by an NHS Trust.

Target roles: EPR Application Support · Clinical Systems Analyst · EPR Trainer · Digital Transformation · Clinical Informatics

1 · Scope and users

In scope: Booking-state consistency; attendance milestones; follow-up task ownership; information completeness review flags; administrative exception worklists; UAT scenario design.

Out of scope: Clinical triage, prescribing, diagnosis, automated discharge decisions, real Epic/Cerner customisation, interface integration, patient-level reporting and live operational KPIs.

Illustrative user Task Proposed support
Booking administrator Book/amend appointment, verify scheduled date Booking-state validation and clear repair action
Reception / clinic administrator Check in and check out attendance Status consistency alert
Clinical team Document encounter and confirm follow-up plan Review prompt for documentation or unclear follow-up responsibility
Service manager / EPR analyst Investigate workflow exceptions Exception list, definition register and UAT evidence
Clinical safety lead (real implementation only) Review patient-safety implications Formal hazard assessment and governance

2 · Current-state vs proposed workflow

These are illustrative process models, not observations or measurements of a specific NHS department.

AS-IS (constructed example)

  1. Referral or clinic request is received.
  2. Administrator books or updates an appointment.
  3. Patient attendance is recorded.
  4. After consultation, different staff members may complete check-out, note review and follow-up coordination.
  5. Incomplete or contradictory fields may only be noticed when another team member reviews the record.

Illustrative failure point: Appointment status appears complete but the follow-up booking task has no nominated owner.