Patient-specific detail stays behind verification
The agent must match surname, date of birth and postcode before returning prescription details. Failed verification returns no patient data.
Trust and compliance
Routine automation with patient-data boundaries that are visible.
PharmaLineAI is designed for the messy reality of pharmacy calls: it can answer routine questions, but it must verify identity before patient-specific detail and move clinical or sensitive queries to humans.
Clinical and sensitive queries stay with people
The public offer is routine call deflection, not clinical advice. Sensitive intents are routed to a human pharmacy team.
Audit trail by design
Significant access and mutations are recorded in an append-only trail, including patient IDs as plain columns so the trail survives record deletion.
UK/EU data-residency posture
The project is designed for UK/EU hosting and processor review before live pilots process real patient data.
Before live patient traffic
What remains before production pilot sign-off.
The current product workflows are implemented locally. A real deployment still needs external operational, legal and integration checks before processing live patient calls.
Telephony provider integration and call-recording policy
Processor/sub-processor review and privacy notice confirmation
DPIA, retention settings and pharmacy owner sign-off
Hosted deployment in a UK/EU data-residency region
Live fallback and escalation runbook for staff
Review the pilot scope with your governance lead.
We can walk through routine intents, identity checks, audit events, escalation boundaries and deployment assumptions before any live caller is routed through the agent.
Book a trust review