How to set an approver rule for the patient services team

Coordinators approve the agent's non-routine bookings and patient letters. Removing a patient from a waiting list needs the patient services manager and the responsible clinician. Releasing records to anyone other than the patient goes to information governance. Clinical questions are not approved at all: the agent refuses them and routes to a clinician. Approval rights lapse with certificates.

What does a patient services approver rule cover, and who owns it?

Patient services teams in hospitals and clinics handle appointments, referrals, reminders, admin queries, records requests and patient feedback. Agents can take much of the routine load: booking, rescheduling, reminding, answering questions about parking or preparation instructions. Health information is special-category data, and in the US HIPAA governs it, so access and release need care. The approver rule names who releases each held action.

The patient services manager owns the rule, with information governance and a clinical lead signing it off. The agent owner configures it. Our guide to AI agent skills by role covers what coordinators need to know.

What are the steps?

1. Patient services manager: lists the agent's actions by depth. Depth 1: reads the appointment system, referral details and the patient's contact preferences. Depth 2: drafts patient letters and replies to feedback. Depth 3: books and reschedules within clinic rules, sends reminders, answers admin questions from approved content. Depth 4: cancels a procedure, removes a patient from a waiting list, releases records to a third party, changes contact details.
2. Patient services manager: assigns booking exceptions to coordinators: double appointments, out-of-hours slots, interpreter needs.
3. Patient services manager: assigns waiting list removals to themselves plus the responsible clinician, because removal can delay care.
4. Patient services manager: routes record releases to information governance.
5. Clinical lead: defines the clinical boundary. Any question about symptoms, medication or results is refused by the agent and passed to a clinician, with urgent symptoms given the approved emergency guidance.
6. Patient services manager: ties each role to a current certificate. Agent owner configures and files.

Why is the clinical boundary a refusal, not a hold?

If the agent drafted answers to clinical questions for a coordinator to approve, the coordinator would be approving clinical advice they are not qualified to give. That is worse than no agent at all. So clinical questions are outside the agent's bounds: it refuses, says plainly that a clinician will respond, and routes the message. For anything that sounds urgent, it gives the approved emergency guidance by template and flags the message.

The same logic sets who approves waiting list removals. A patient who has not responded to two letters might be removed under the clinic's rules, but the decision may affect their care. The patient services manager checks the process was followed; the clinician checks whether removal is clinically safe. The agent prepares the evidence.

Contact detail changes are held because appointment letters and results notifications follow them. A request to change a phone number by email is external until verified.

Records requests need the same care. A family member asking for a parent's letters, a solicitor asking for a client's file, an insurer asking for a report: each needs a lawful basis and the right consent or authority. The agent can collect the request, check it is complete and prepare the release pack. Information governance decides whether it goes, and nothing is released while a question about authority is open.

Which controls make the rule work, and what evidence do they leave?

Clinical boundary tested. Evidence: certification results on the refusal and scope gates, and refused verdicts in live use.

Two approvers on waiting list removal. Evidence: manager and clinician names on each removal, as set out in the approver authority matrix for the patient services team.

Records released by information governance. Evidence: the approver and the legal basis on each release.

Verification before contact changes. Evidence: the verification method on each change.

Rights lapse with certificates. Evidence: certificate status on each approval date.

What should you measure?

• Clinical questions answered by the agent. The target is none.
• Time from clinical question to clinician response.
• Waiting list removals reversed, which may show the rule is too loose.
• Missed appointments, before and after agent reminders.
• Coordinator coverage, using the competency matrix for the patient services team.

Where does it usually go wrong?

Admin content drifts into clinical content. Preparation instructions for a procedure are approved content; questions about whether to stop a medication are not. Keep the approved content library under clinical ownership.

Coordinators feel replaced. The agent takes the booking calls; coordinators handle exceptions, worried patients and complex cases. That is a more skilled job, as whether AI agents will replace patient services teams argues.

Cancellations are approved without the clinic. A coordinator approves the agent's held cancellation of a procedure because the patient asked, without checking whether the clinician needs to speak to them first. Some cancellations carry clinical risk; the rule should say which ones go to the clinic.

Rules are borrowed from other services. Compare the approver rule for the student services team and the approver rule for the payroll team: useful patterns, but neither carries clinical risk.