Quality
Inside our QA framework: how we audit our own clinical work.
The principle
Independence first.
By Emil — PCN Manager & Quality Assurance Lead, Bespoke Clinical Services · PCN management and clinical audit · Published 2 June 2026
The BCS quality assurance function does not report into operations. That single structural decision shapes everything else. The team that deploys and rosters pharmacists has no editorial control over the audit findings about those pharmacists, and no ability to adjust a monthly impact report before it reaches a PCN Clinical Director. QA signs the report; delivery does not.
This is deliberately inconvenient. It produces internal conversations that a more comfortable structure would avoid. It is also the only reason a Clinical Director can reasonably treat our numbers as evidence rather than as a sales document, and the only reason those numbers survive contact with an ICB assurance meeting.
Layer 1
Consultation sampling.
Every clinician has a rolling sample of their consultation records reviewed against a standardised audit tool. We look at documentation quality, whether the clinical reasoning is visible, whether the patient's own priorities were recorded, whether monitoring requirements were addressed, whether the coding matches what actually happened, and whether follow-up was arranged and closed.
New starters are sampled more heavily during their first three months, then settle to the standard cadence. Independent prescribers get an additional prescribing-specific review. The tool is the same for everyone, which means scores are comparable between clinicians, between hubs and over time — and that comparability is what lets us spot a developing problem before it becomes an incident.
Layer 2
Prescribing and high-risk drug audit.
Prescribing decisions are audited against NICE guidance, the BNF and the local Joint Formulary. Separately, we audit high-risk drug monitoring completeness — DMARDs, lithium, amiodarone, anticoagulants, methotrexate — because incomplete monitoring is the most common latent risk we find in a new PCN contract and one of the fastest to close.
Deprescribing decisions in frail and over-75 cohorts get particular attention. Stopping a medicine is a clinical act with the same weight as starting one, and the documentation standard we hold is identical: rationale, discussion with the patient, monitoring plan, and a review date.
Layer 3
Significant event analysis.
Any event with patient-safety implications triggers a structured significant event analysis: what happened, what should have happened, why the gap existed, what has changed as a result, who owns the change, by when, and when it will be re-audited. Re-audit is the step most SEA processes skip, and it is the only part that proves the corrective action worked.
SEAs are shared with the PCN Clinical Director where the event touches their patients. We do not treat that as reputational risk. A provider that never reports an event is not a safer provider; it is a provider with weaker detection.
Layer 4
Supervision, appraisal and CPD feedback loop.
Audit findings are worthless if they stop at a spreadsheet. Every finding is routed into the clinician's weekly supervision session with a senior pharmacist, and aggregated findings shape the training curriculum — if six pharmacists across two hubs are documenting monitoring plans inconsistently, that becomes a CPD session, a template change, or both.
At annual appraisal, the twelve-month audit record forms part of the discussion alongside personal development goals and scope of practice. Scope is widened only where competence has been evidenced, not on request.
Layer 5
The monthly impact report.
Each PCN receives a monthly report covering activity by cohort, prescribing interventions made, high-risk drug monitoring compliance, discharge reconciliations completed within seven days, movement in the long-term condition indicators we agreed at mobilisation, prescribing efficiency, and any audit or safety findings from the period. It is designed to be forwarded to an ICB without editing.
Reports are checked by QA against source data before release. If a number cannot be traced back to the clinical system, it does not go in. That rule costs us the occasional flattering statistic and has never once cost us a difficult conversation we could not defend.
None of this is exotic. It is ordinary clinical governance, applied consistently, by a function that has nothing to gain from a good-looking report. For a PCN Clinical Director accountable for ARRS spend, that independence is the point.
FAQs
Quality assurance at BCS
How does BCS quality-assure its pharmacists' clinical work?+
Every BCS pharmacist has their clinical work sampled on a rolling basis: consultation records are reviewed against a standardised audit tool, prescribing decisions are checked against NICE and local formulary, high-risk drug monitoring is audited for completeness, and findings feed into weekly supervision and the annual appraisal cycle.
Is BCS quality assurance independent of delivery?+
Yes. The QA function reports separately from the operations team that deploys pharmacists, so audit findings cannot be softened by the people responsible for delivery. Every monthly PCN impact report is signed off by QA before it is issued.
What happens when an audit finds a problem?+
Findings are graded. Low-level learning goes into supervision and CPD. Anything with patient-safety implications triggers a significant event analysis with a documented root cause, corrective action, timescale and a re-audit to confirm the fix held. Serious findings are shared with the PCN Clinical Director.
Related reading
Quality assurance at BCS
The QA function, in service terms.
PCN Management & QA service
How BCS manages performance across every PCN contract.
Supervision and governance
What ICBs audit and what CQC asks for.
Talk to our Service Development team
30-minute discovery call. We'll show you how BCS maps to your PCN's specific priorities.