Clinical questions are never approved by patient services staff; they go to a clinician. Around that rule, a patient services approver authority matrix sets which actions an AI agent may complete, such as routine bookings, and who approves fee waivers, refunds, record releases, referrals and complaint responses, with limits for each.
What should a patient services matrix protect?
Patients' care and their privacy. Patient services teams handle bookings, payments, records and messages, and almost every request carries health information. Under the GDPR health data is special-category data; in the US, HIPAA governs it. An agent that sends the right appointment to the wrong person, or releases records without checking who is asking, causes harm that cannot be undone.
The matrix rests on three rules. Administrative actions within clinic rules may run at depth 3. Anything that releases information, moves money or responds to a complaint is held for a person. Anything clinical, such as a question about symptoms or medication, is refused by the agent and routed to a clinician, and no coordinator may approve an answer to it.
How do you fill it in?
- List the patient services actions the agent touches.
- Set the agent's depth for each.
- Name the approver and their limit or scope.
- Note the identity check required before the action.
- Note the clinical escalation, if any.
- Record the certificate approvers must hold, if your organisation ties approval rights to certification.
The template
| Patient services action | Agent depth | Approver | Limit or scope | Identity check | Clinical escalation | Certificate |
|---|---|---|---|---|---|---|
| Book or move appointment | ||||||
| Cancel appointment | ||||||
| Waive missed-appointment fee | ||||||
| Refund a patient payment | ||||||
| Send copy of records to the patient | ||||||
| Release records to a third party | ||||||
| Send referral letter | ||||||
| Respond to a complaint | ||||||
| Answer a clinical question |
A worked example
A hypothetical private outpatient clinic: eight coordinators, a patient services lead and a medical director. Values are illustrative.
| Action | Agent depth | Approver | Limit or scope | Identity check | Clinical escalation | Certificate |
|---|---|---|---|---|---|---|
| Book or move | 3 | None within clinic rules | Standard slots | Patient portal login | Patient mentions new symptoms | n/a |
| Cancel | 3 | None | 48 hours' notice | Portal login | Cancelling follow-up after abnormal result | n/a |
| Fee waiver | 2 | Coordinator | One per year | n/a | None | Operator |
| Refund | 4, held | Patient services lead | 500 | Original payment method only | None | Operator |
| Records to patient | 2 | Coordinator | Patient's own records | Verified in person or portal | Clinician reviews for harmful content | Operator |
| Records to third party | 2 | Patient services lead | Signed consent on file | Consent verified | Medical director if consent unclear | Operator |
| Referral letter | 2 | Referring clinician | All | n/a | Clinician signs | Foundations |
| Complaint response | 2 | Patient services lead | Service complaints | n/a | Complaints about care to medical director | Operator |
| Clinical question | Refused and routed | Clinician | All | n/a | Always | n/a |
Cancelling a follow-up after an abnormal result is always held, even though the agent normally cancels at depth 3. The agent may not know the significance of the appointment; the clinic does. That condition is written into the agent's bounds and reviewed by the medical director.
Refunds go back only to the original payment method. A patient emailing new bank details for a refund is external data, and the agent refuses to act on it.
Records to a third party need signed consent on file, checked by the lead. An insurer or solicitor's request letter is signed by them, but it is not the patient's consent.
Student-facing teams face similar privacy questions; compare the approver authority matrix for the student services team. Clinic-wide approvals, such as supplier payments, are in the approver authority matrix for the practice team. Thresholds belong in the approver rule for the patient services team. Market rules differ, as the brief on training patient services teams in healthcare in Japan shows.
Where the Academy fits
Pryme Intelligence Academy's Operator track trains coordinators and leads to decide held actions, with module tests set in healthcare for their own role. Its practicum requires no missed red line, which matters in a queue where releasing the wrong record is the error to avoid. The admin view shows each approver's certificate and expiry.
Questions people ask
Can a coordinator approve an answer to a clinical question?
No. Clinical questions are refused by the agent and answered by a clinician. Coordinators route them and may reassure the patient that a clinician will reply. The skills each role needs are in AI agent skills by role.
Why check records before giving them to the patient?
In some circumstances, a clinician may need to review records for content that could cause serious harm before release. Your organisation's procedure decides when.
What if the booking agent's certificate lapses?
Bookings become held drafts for coordinators until it is recertified. Plan extra cover for the lapse date, especially on clinic days with high demand.