Testing patient access with reception colleagues
GP reception patient access testing is most useful when colleagues can observe a complete task and explain what would happen next. Use a small structured walkthrough before relying on a feature demonstration or a general staff reaction. The purpose is to expose unclear steps while they are still easy to discuss.
Keep the exercise separate from live service performance measurement. A fictional task in a demonstration environment can show how a configuration behaves. It cannot establish production accuracy, real patient experience or an average time saving.
Give the walkthrough a narrow question
Choose one operational question, such as whether staff can understand and act on a routine appointment request after it arrives. Identify the configuration being shown and the people responsible for receiving the work.
Agree the environment and test method with the authorised owner. Use fictional information and avoid placing a real patient enquiry into a live queue merely to see what happens. If a live-system test is needed, it requires an approved plan and clear handling of any resulting records or notifications.
Assign observation roles
One colleague follows the caller’s experience. Another follows the request at the receiving end. A facilitator records what was actually shown, questions raised and decisions made.
These roles help prevent a polished conversation from distracting everyone from the staff workflow. The caller observer may hear a clear promise while the receiving observer finds that the next action is still ambiguous. Both observations belong in the record.
Include a colleague who may cover the task occasionally. A process that works only for the person who designed it can be difficult to maintain when shifts change.
Use a small set of administrative tasks
- A routine request within the agreed configuration.
- A correction to an administrative detail during that request.
- Two separate administrative requests in one conversation.
- A request for human help, including the agreed behaviour when the intended person is unavailable.
Adapt these suggested administrative tasks to the question being explored. Keep the expected observation clear before running the example so that success is not redefined afterwards.
For each task, record the caller’s understood next step, the result visible to staff and any work left unresolved. Mark a feature as explained rather than demonstrated if it cannot be shown in the agreed environment.
Turn feedback into a correction record
Replace “that was confusing” with a specific observation: which phrase, screen or handover caused uncertainty, for which role, and what consequence might follow? Then assign the question to someone able to resolve it.
A useful record contains the observation, proposed change, responsible owner and evidence needed for recheck. After a material change, repeat the affected task rather than treating the existence of a revised document as proof that the problem is fixed.
Keep positive observations too. They show which parts of the workflow colleagues found clear and should preserve. Avoid combining every response into an invented quality score.
Apply the exercise to EMMA
EMMA supports patient requests and routine appointment booking and cancellation during surgery hours. The options available depend on the service agreed with each practice. EMMA does not provide medical advice or clinical triage. Current product information
The two-requests guide offers a focused question for staff discussion. Request an EMMA demonstration to explore a workflow with the colleagues who will receive and act on the requests.