Home / Insights / Pharmacy

POCT quality and training for pharmacy chains: a head-office guide

PharmacyPublished 2026-11-1710 min readUnited Kingdom

How the head office of a pharmacy chain keeps point-of-care testing safe across many branches: QC and EQA per device, training that follows each person, lockouts, lot tracking, a branch dashboard and a rollout plan.

Written and reviewed by the Catenix team. How these guides are written and checked.

In brief

  • A pharmacy chain running point-of-care tests has the governance load of a small laboratory network, spread across branches that each hold one or two devices and are often staffed by locums.
  • Quality control and external quality assessment have to be scheduled and reviewed per device, per test and per branch, with a failed result taking that device out of use until someone signs it back in.
  • Operator training and competency should be recorded against the person, not the branch, so that a pharmacist or technician who moves between shops carries their sign-off with them and anyone without it is locked out.
  • Head office needs one view of every branch, rated red, amber or green on QC, EQA, competency, lot expiry and results awaiting onward reporting, rather than a phone round.
  • Roll out in phases: two or three pilot branches with different staffing patterns first, then waves, with the software, standard operating procedures and training records proven before scale.

Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).

Why a pharmacy chain needs central oversight of testing

A single independent pharmacy that runs point-of-care testing (POCT) can keep its records in one folder and one person's head. A chain cannot. The same services, HbA1c (glycated haemoglobin) and lipids for NHS Health Checks and private health checks, C-reactive protein (CRP) for respiratory consultations, INR (international normalised ratio) for anticoagulation monitoring under a local agreement, and urinalysis for private and local services, are delivered in many places at once by people who move between them.

Three features of pharmacy staffing make central oversight necessary rather than optional.

  • Rotating locums. The pharmacist on duty on a Saturday may not be the one who was trained on that branch's analyser. Unless competency is recorded centrally and checked at the device, nobody in the branch can easily tell whether today's pharmacist is cleared to test.
  • Staff turnover. Technicians and dispensers who run tests leave and join. Each departure can remove the only trained operator from a branch; each arrival needs training, assessment and sign-off before their first patient test.
  • Many small sites. Most branches hold one or two devices. A hospital POCT team supervises dozens of devices on one site with a laboratory behind it. A chain supervises the same number of devices across a region with no laboratory at all.

The Medicines and Healthcare products Regulatory Agency (MHRA) guidance Management and use of IVD point of care test devices expects a named person to be accountable for POCT, with trained operators, internal quality control (QC), external quality assessment (EQA) and a record of every result. In a chain that accountability usually sits with a clinical services lead or the superintendent pharmacist at head office. They cannot exercise it from a spreadsheet that branches update when they remember. For the single-pharmacy view, including which tests are realistic and how results reach the GP, see our guide to pharmacy point of care testing in the UK.

QC schedules and EQA for every branch

Quality control in a chain is the same science as in a laboratory, repeated on every device. The work for head office is to set one schedule per test, apply it to every device that runs the test, and see where it is not being followed.

Internal QC

Define the QC levels, frequency and lot-change checks for each test from the manufacturer's instructions for use (IFU) and write them into the standard operating procedure (SOP). A common pattern is two levels of control on a set schedule and whenever a new reagent or cartridge lot is opened, but the IFU and your own quality plan decide, not a general rule. Then make three things true in every branch:

  • QC results are captured from the analyser, not copied onto a paper log, so the chart is built as the work is done.
  • Results are plotted on a Levey-Jennings chart and checked against agreed rules. Our explainer on Westgard rules for POCT teams covers which rules suit a small device.
  • A failed QC takes the device out of patient use until the failure is investigated and a named person signs it back in.

With one device in a branch there is no second analyser to compare against, so QC is the only daily evidence the device is behaving. Control material also needs storage within its temperature range, which means a monitored fridge in each branch that keeps controls.

External quality assessment

EQA is where an independent scheme sends samples of unknown value and compares your result with other users of the same method. Each quantitative test on each device should be registered with a scheme accredited for that analyte. In a chain the practical problems are logistics: samples arriving at a branch where nobody knows what they are, returns missed because the trained operator was on leave, and poor performance reports sitting in an inbox. Head office should hold the EQA calendar for every device, see which returns are due this week, and record the review of each report. Our EQA management guide sets out the full cycle.

Operator training and sign-off that travels with the person

The most common gap in pharmacy POCT is not a faulty analyser. It is a test run by someone who was never assessed on that device, or whose assessment lapsed months ago. In a chain the fix is to record competency against the individual, across the whole organisation, rather than in a binder kept in each branch.

What the competency record should hold

  • The person, their role and their General Pharmaceutical Council (GPhC) registration where they have one.
  • Each device model and test they are trained on, with the date of training, who assessed them and how (observed test, QC run, EQA sample or a written check).
  • A reassessment due date, set by your policy for each test.
  • Any restrictions, for example cleared for urinalysis but not yet for INR.

Because the record belongs to the person, a technician trained in one branch is cleared on the same analyser model in every branch. A locum who covers several shops is assessed once and their sign-off follows them. A person whose competency has expired is flagged everywhere at once, not only in the branch that happens to check.

Locking out untrained or lapsed staff

A record is only useful if it is enforced at the point of testing. The strongest control is an operator lockout: the analyser or the connected software asks who is testing and refuses a patient test from anyone who is not currently signed off for that device. Where the device cannot enforce it, the software should at least hold the result and flag it for review. The same principle applies to devices: a lockout after failed QC, an overdue maintenance check or an expired lot. Our resource on QC lockout and operator competency describes how these rules work together.

For locums, agree a simple rule with your agencies and branch managers: a locum is added to the competency list before the shift, or they do not run patient tests on that shift. Lockouts make that rule hold on a busy Saturday.

Lot and expiry tracking, and getting results to the record

Lots and expiry

Cartridges, test strips and controls are perishable and lot-specific. Each branch should record what it receives, the lot number and the expiry date, and every patient and QC result should carry the lot it was run on. Head office then gets two things it cannot get from paper. First, a forward view of stock that will expire before it is used, which can be moved between branches instead of written off. Second, if a manufacturer issues a field safety notice for a lot, a list of every branch holding it and every patient tested with it, within minutes rather than after a week of phone calls.

Results into the pharmacy record and onward to the GP

Every result should be recorded once, in the pharmacy, against a confirmed patient identity with the NHS number, operator, device, lot and time attached. From there it goes where it needs to: the pharmacy's clinical record, the service platform for a commissioned service, a letter or structured message to the patient's GP practice, and a copy for the patient. The routes available today, paper, NHSmail and GP Connect Update Record for some services, are described in the single-pharmacy guide linked above. The head-office question is whether each branch is sending results within the agreed period. A list of results awaiting onward reporting, by branch, answers it.

What an inspection or service audit will look for

The GPhC inspects registered pharmacies against its Standards for registered pharmacies, which are grouped under five principles: governance, staff, premises, services (including medicines management) and equipment and facilities. Commissioners of services such as NHS Health Checks, which are commissioned by local authorities, and NHS services commissioned through NHS England and integrated care boards (ICBs), may also audit delivery against the service specification. Neither is a POCT audit in the laboratory sense, but where a branch offers testing an inspector or auditor will reasonably ask to see evidence that it is done safely.

At a high level, expect questions like these:

  • Who is responsible for testing, and how do they know it is being done properly in this branch?
  • Is everyone who ran a test in the last month trained and assessed on that device? Show me the record.
  • Where is the QC record for this analyser, what happened the last time QC failed, and who signed the device back in?
  • Is the device registered for EQA, and what did the last report show?
  • Are the reagents and controls in date, stored correctly, and is there a temperature record?
  • Can you show where a given result went, and that the GP received it where the service requires that?
  • What is the procedure for a device fault or incident, including reporting to the MHRA?

A chain that can answer each of these for any branch, on the day, from one system, is in a far stronger position than one that has to ask the branch to find the binder. Service specifications and inspection approaches change, so confirm the current documents with the GPhC and your commissioners.

A head-office dashboard: red, amber and green branches

The point of central oversight is to see trouble before an inspector or a patient does. A simple red, amber and green (RAG) rating per branch, built from the records above, does that. The thresholds below are examples to adapt to your own SOPs, not a standard.

MeasureGreenAmberRed
Internal QCAll devices passed on scheduleQC due today and not yet runQC failed or overdue, device locked out
EQAReturns made, last report reviewedReturn due within 7 daysReturn missed or poor performance not investigated
Operator competencyAt least two current operators per deviceOne current operator, or a reassessment due within 30 daysNo current operator for a device in use
Lots and expiryAll stock in dateStock expiring within 30 daysExpired lot in use or on a recall notice
Results onwardAll sent within the agreed periodResults approaching the deadlineResults overdue to the GP
StorageFridge in rangeShort excursion recordedExcursion not investigated

Review the dashboard weekly with the area managers, and treat a branch that stays amber for several weeks as an early warning, usually of a staffing gap. Our guide to POCT governance for multi-site services covers the wider reporting structure.

A phased rollout plan

Switching a whole chain to a new way of running testing in one go is how SOPs get skipped and staff lose confidence. A phased plan works better.

  1. Baseline. List every device in every branch, its serial number, the tests it runs, its EQA registration and the staff who use it. This register is often the first time head office sees the full picture.
  2. Standardise. Agree one SOP, one QC schedule and one competency assessment per test across the chain, signed off by the clinical services lead.
  3. Pilot. Choose two or three branches with different patterns: one with a stable team, one that relies on locums, one with high test volumes. Connect their devices, load their staff and run for four to eight weeks.
  4. Review. Check that QC and results are captured without retyping, lockouts behave as intended, locums can be added quickly, and results reach the GP. Fix the SOPs and settings before going wider.
  5. Waves. Roll out by region or area manager in groups of branches, with training for each group before go-live and a named contact at head office.
  6. Steady state. Run the weekly dashboard review, a quarterly audit of a sample of branches and an annual review of the whole programme.

What to ask a software vendor

Software that manages POCT quality and training for a pharmacy chain has to do the job a laboratory's middleware does in a hospital, without the laboratory, across many small sites. Useful questions:

  • Which of our analysers can you connect, and how: over standard protocols such as HL7 v2 (Health Level Seven), POCT1-A2 or ASTM, through a gateway in the branch, or by manual entry?
  • What happens when a branch loses its network connection during a test?
  • Is competency held against the person across all branches, and does it enforce a lockout at the device?
  • Does QC capture happen automatically, with Westgard rules and a lockout on failure?
  • Can you track lots and expiry per branch and produce a recall impact list?
  • How do results reach our pharmacy record and the GP, and which standards does that use?
  • Is there one dashboard for head office with a view per branch and per area?
  • Where is data hosted, what is the pricing model, and do costs rise with test volume?

Catenix is built for this kind of distributed testing. It connects analysers over HL7 v2, POCT1-A2, ASTM, FHIR and REST, with a branch gateway that stores and forwards if the network drops. It captures QC with Westgard multi-rule and lockouts, records operator competency against the person who ran each test, tracks inventory by lot and expiry, and gives head office one view across every site, with UK hosting available and a subscription per site with no per-test fees. The Catenix pharmacy page describes how it fits a chain. Whichever product you choose, use the questions above as the specification.

Questions people ask

Which software manages point-of-care testing quality control and operator training for a pharmacy chain?

Look for POCT management software, sometimes called POCT middleware, that connects to your analysers, captures QC automatically, applies Westgard rules, records operator competency against each person across all branches and locks out untrained staff or failed devices. It should also track lots and expiry, send results onward and give head office one dashboard. Catenix is one platform designed for this; compare several against the same checklist before choosing.

How do we stop locums running point-of-care tests they are not trained for?

Record competency against the individual centrally, not in each branch, and enforce it at the device with an operator lockout so a patient test cannot be run by anyone not currently signed off for that analyser. Agree with agencies and branch managers that a locum is added to the competency list before the shift, or does not test on that shift.

How often should each pharmacy branch run QC on its point-of-care analysers?

Follow the manufacturer's instructions for use and your own documented quality plan for each test. Two levels of control on a set schedule and whenever a new reagent lot is opened is a common pattern. Apply the same schedule to every device across the chain, capture the results automatically, and take any device out of patient use after a failure until it is investigated and signed back in.

Does every branch need its own EQA registration?

Each device that runs a quantitative patient test should take part in EQA, because the scheme checks that device and its operators, not the chain in general. In practice head office manages the registrations, holds the calendar of returns for every device, and records the review of each report, while the branch runs the sample. Discuss multi-site arrangements with your EQA provider.

What will a GPhC inspector look for if our pharmacies offer testing?

The GPhC inspects against its Standards for registered pharmacies, covering governance, staff, premises, services and equipment. For testing, expect to show who is responsible, that each operator is trained and assessed, QC and EQA records with action on failures, in-date stored reagents, where results went, and how device incidents are handled. Confirm current expectations with the GPhC.

How should a pharmacy chain roll out new POCT software?

Start with a register of every device and operator, standardise SOPs and QC schedules across the chain, then pilot in two or three branches with different staffing patterns for a few weeks. Review captures, lockouts and results reaching the GP, fix what is wrong, then roll out in regional waves with training before each go-live and a weekly dashboard review afterwards.

Sources and further reading

Take it with you

The buyer's guide, in your inbox.

Nine pages on what POCT connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier.

Get the POCT connectivity buyer's guide

Nine pages, vendor-neutral: what connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier. The PDF also opens directly from the downloads page; leave an email only if you want it in your inbox.

We use your email only to send the guide and, if you ask, to follow up once. No newsletter unless you tick the box. See our privacy notice.

Thank you. The guide is on its way. You can also open it now.
That did not send. Open the guide directly or email contact@catenix.com.

See it done in software.

A 30-minute walkthrough on a live tenant, with your analysers and your allowable-error limits.