Each patient services coordinator keeps this log for the team's two-week practicum, one row per held message, booking or request they decide. It records what the patient asked, whether any symptom or urgency was mentioned, what the AI agent proposed, how identity was checked, the coordinator's decision, a team lead's independent call, and any red line. Template below.
What is different about patient services?
Two things change the log. First, patients describe symptoms in admin messages. "Can I move my appointment, my chest has been tight since Sunday" is a booking request on its surface and an urgent clinical signal underneath. Second, health data is special-category data under GDPR, and in the United States HIPAA applies, so every disclosure decision carries weight.
The AI agent typically books and moves appointments within rules at depth 3, answers administrative questions, and drafts replies at depth 2. It is bounded away from clinical advice and holds anything that mentions symptoms for a person. Coordinators review those holds, along with records requests and third-party callers. The setup is covered in how to run a two-week practicum for patient services teams.
How should a coordinator fill in a row?
- Read the patient's own words, not only the agent's summary. Copy any symptom into the urgency column verbatim.
- Record the identity check used, and whether the requester is the patient or someone else.
- Record the decision and a short reason.
- Leave the team lead's column blank; they complete it without seeing yours.
The practicum log template
Header: coordinator; team lead with a current certificate; service (for example, outpatients or a GP practice); dates; bar of at least 95 correct in every 100 and no missed red line.
Red lines
- A reply giving clinical advice is approved, however mild it seems.
- A symptom suggesting urgency is not passed to a clinician during the same contact.
- Health information is shared with someone whose identity or authority was not verified.
| Column | Entry |
|---|---|
| Row and time | |
| Contact channel | Phone, message, portal, email |
| Request type | Book, move, cancel, question, records, third party |
| Symptoms or urgency mentioned | Verbatim, or "none" |
| AI agent's proposal and verdict | Including deciding bound |
| Identity check used | |
| Requester | Patient / named representative / unknown |
| Coordinator's decision | Approve, edit, route to clinician, refuse, escalate |
| Reason | |
| Team lead's decision | |
| Match | Yes / no / defensible |
| Red line | None / caught / missed |
A worked example
Take a sample community health clinic. Values are illustrative.
Row 63. Portal message: "Can I move Thursday's physio to next week? My knee's fine, just busy." Symptoms: none. AI agent: rebook to next Tuesday, allowed at depth 3, held only because the clinician's diary was full. Coordinator: approve next Wednesday instead. Team lead: same. Match: yes.
Row 64. Phone transcript: "I need to cancel tomorrow, I've been really dizzy and short of breath." Symptoms: "dizzy and short of breath". AI agent: holds the cancellation for a person. Coordinator: cancel and send the standard rebooking link. Team lead: transfer to the duty clinician now; then cancel. Match: no. Red line 2: missed.
Row 65. A caller says she is a patient's daughter and asks for test results. AI agent: refuses to discuss. Coordinator: uphold refusal; check the record for a named representative; none found; offer to ask the patient to call. Team lead: same. Red line 3: caught.
Row 66. Message asking whether to take a painkiller before a scan. AI agent drafts: "Paracetamol is usually fine before a scan." Coordinator: remove the advice; reply that a nurse will call. Team lead: same. Red line 1: caught.
Row 64 fails the bar. The coordinator dealt with the request in front of them and missed what the patient was telling them.
How does this log differ from student services and payments?
Student services teams face a similar hidden-signal problem, with wellbeing in place of symptoms; compare the practicum log for student services teams. Payments operations work is far less personal but shares the identity column; see the log for payments operations staff.
Where the Academy fits
Pryme Intelligence Academy's Operator track is for the people who run a live workspace every day, including reviewers and team leads. Certified Pryme Operator requires a written exam and a two-week practicum on real review decisions, at least 95 in every 100 correct and no missed red line. Module tests are set in the learner's own industry and role. More in AI literacy and certification for people who work with agents.
Questions people ask
Does every coordinator in the team need their own log?
Yes. The practicum assesses individuals, even if the whole team runs it in the same fortnight. A shared log hides who caught what.
What if the clinician disagrees with the team lead about urgency?
Record the clinician's view in the note. For assessment, the question is whether the coordinator routed the symptom, not whether it turned out to be serious.
Are coordinators responsible for what the AI agent tells patients?
For messages they approve, yes; the service answers for the deployment. See are patient services teams accountable for an AI agent's mistakes and do patient services teams need a certificate to approve AI agent actions.