Community pharmacies are taking on more clinical services while carrying heavy admin — a context where AI can free pharmacist time, within patient-data rules. Here’s how in 2026. (dgm implements osFoundry as an independent partner; clinical responsibility stays with the pharmacy.)
Where AI helps
Practical use cases:
- routine patient query handling;
- communication drafting;
- stock and ordering support;
- information summarisation; and
- back-office admin.
With expanded clinical services in community pharmacy, cutting admin frees pharmacist time for patient-facing work — clinical decisions stay with the pharmacist.
The regulation
- GPhC — regulates pharmacy practice.
- UK GDPR — patient data is special-category.
- NHS Information Governance — for NHS-commissioned services.
- MHRA — AI for a clinical purpose is a regulated medical device.
So lawful basis, minimisation, security and human oversight apply.
Start with admin
Clinical decision-support AI brings medical-device obligations. Admin and communication AI doesn’t — the faster, lower-risk start. AI supports the pharmacist with information, not autonomous clinical advice.
Data control
The common risk is staff using consumer AI with patient data. A governed, approved platform that keeps data in your control prevents it.
Where osFoundry and dgm fit
dgm implements data-controlled AI on osFoundry: self-hosting or an EU region (it publishes US/EU/JP regions, not a UK one), bring-your-own-key, audit and human oversight, with usage pricing suited to smaller operators. Patient data stays in your environment.
dgm is an independent integration partner with zero integrations so far — no pharmacy case studies to claim. Clinical responsibility stays with the pharmacy. To scope a safe AI project, book a consultation with dgm. Not clinical or regulatory advice.