Last October I stood at the end of a long day in Manchester, in front of a room of NHS scientists, point-of-care testing coordinators and commissioners, and gave the closing talk. It was called Building a POCT Service From the Ground Up. The event, Delivering POCT: Diagnostics in the Community, ran under one clear theme, the same shift the NHS keeps naming out loud: move testing out of the hospital and closer to where people actually live. Talk after talk circled the same tension. Everyone wants diagnostics in the community. Far fewer people want to talk about what it takes to run them safely once they are there.
That gap is where I have spent my working life, so that is what I spoke about. My argument was simple, and I will make it again here. A community point-of-care testing service is not a smaller version of a hospital service. It is the same discipline, delivered by different means. Three things travel with it wherever it goes: engagement, data and quality. Get those three right and the setting almost stops mattering. Get them wrong and no amount of clever hardware will save you.
You cannot govern what you cannot see
Every service I have built started in the same unglamorous place: a complete, accurate asset register. What devices do we have, where are they, and who is responsible for each one. It sounds trivial. It is not. Until you can see the whole estate on one page, you are guessing, and guessing is how meters go missing, controls lapse and a device quietly runs for months on nobody's authority.
The register also teaches the first real lesson of the job, which is that different devices carry completely different governance needs. In the hospital I support, the fleet runs from blood gas analysers and coagulation meters through urinalysis, HbA1c and infectious disease tests, all the way to more than a hundred glucose and ketone meters scattered across wards. A blood gas analyser and a ward glucose meter are both point-of-care devices, but the effort, the risk and the right level of oversight for each are worlds apart. Treat them the same and you will either smother the simple ones in bureaucracy or leave the complex ones dangerously light. The register is what lets you decide that on purpose rather than by accident.
When the technology works and the governance fails
The story I built the talk around was a respiratory testing change in the emergency department I support. A new acute respiratory infection algorithm made a rapid antigen point-of-care test the primary front-door test, in place of sending so much off for rapid PCR. On paper it was a connectivity and turnaround win, and the numbers were real. Over one five-month window, result turnaround fell from about 60 minutes to 13, rapid PCR use dropped by nearly 80 percent, and the department saved in the region of 200,000 pounds, with something like 1,650 hours of waiting handed back to clinical decisions. The results flowed straight into the laboratory system and the patient record, so every test was traceable.
But the honest part of the talk, the part that does not fit on a triumphant slide, was what happened when the governance around the test slipped. Stock management in the department faltered and the consumables ran out. Communication between teams broke down and the algorithm stopped being followed consistently. Patients were sent up to inpatient wards without being tested at all. Costs climbed straight back up. The device never failed. The assay never failed. The governance around them did, and that was enough to undo the gain.
The technology is almost never the hard part. The engagement and governance around it are the whole job, and they are the first things to quietly fall away.
Getting it back on track was not a technical fix. It meant sitting with the department, mapping who was actually responsible for what, understanding the handover documents and workflows they already used, attending the morning handovers to re-explain the algorithm, cascading training through super-users, and building the small, physical scaffolding that keeps a change alive: signage at the decision point, a triage tool, daily stock checks, a logbook redesigned to stop unnecessary repeat tests. None of that is exciting. All of it is the reason the service held the second time.
The unglamorous work is the work
The same pattern showed up in something as ordinary as glucose meters. In one year the hospital got through 73 replacement meters, against limited stock, which is the kind of number that looks like bad luck until you look properly. It was not bad luck. It was a lack of structure. The fix was mundane and it worked: standardised labelling of meters, control boxes and designated station areas, visual guides showing staff what good looks like, a troubleshooting log before a replacement could be requested, a clinical governance questionnaire to prompt local ownership, and incident reporting with monthly analysis so patterns surfaced instead of repeating. Data-informed procurement then put the right number of meters in the right places. Replacements fell because the system around the device changed, not the device.
Underneath all of this sits a method, and I am unapologetic about how plain it is. Lean Six Sigma, stripped of the jargon, just means fixing problems in a simple, repeatable way. Define one pain point. Measure a clean baseline from the middleware, the logbooks and the laboratory system. Analyse for patterns, expired training, stockouts, missing steps in the pathway. Improve with small, targeted changes, competency-gated device access, a one-page tool at the bedside, cascade training for super-users. Control it with a monthly dashboard of the metrics that matter, spot audits and short team huddles. Then you move to the next problem and run the same loop again. Fewer repeats, faster decisions, traceable results, one cycle at a time.
Stepping into the community
All of that was built inside hospital walls, with a hospital network, a laboratory next door and colleagues on the same site. The policy direction, restated across the whole Manchester day, is to take it somewhere with none of those comforts. The NHS 10-Year Plan sets out the shift from hospital to community and from analogue to digital. Neighbourhood teams built around populations of roughly 50,000 are meant to deliver joined-up local care. Virtual wards and hospital-at-home services keep expanding. The question every POCT service now faces is not whether to follow, but how to do it without leaving the discipline behind at the hospital door.
My answer is that the three pillars travel, but the delivery changes. Engagement in the community means finding the responsible leads and the existing structures in settings that were never built around a laboratory, supporting them to own their POCT processes, and paving the way toward a proper service-level agreement rather than an informal favour. Data and digital means connectivity you can actually deploy where there is no hospital network to lean on: a mobile data link on the device, a shared tracker as an honest bridge, and a plan to reach full integration rather than a shrug that leaves results stuck on a screen. Quality does not flex at all. Quality control, external quality assessment and operator competency are held to exactly the same standard whether the test runs in a resus bay or a community clinic, because the patient cannot tell the difference and neither should the result.
Laying that groundwork on site, before a single community test is run, is what tells you the things you cannot know from a distance: who the real responsible leads are and how reporting will flow, whether the case for a POCT structure is genuinely feasible, what a sensible community SLA should actually contain, and which key metrics will tell you early whether it is working. Do that homework and the community service starts on solid ground. Skip it, and you are back to running out of consumables and sending patients on untested, only now with no laboratory down the corridor to catch you.
What travels, and what changes
If there is one thing to take from a day spent talking about diagnostics in the community, it is that the hard-won lessons of hospital POCT do not expire at the boundary. Build from a clear asset register. Engage the people who own the pathway rather than imposing on them. Let the data show you where the risk really is. Hold quality at full standard no matter how small the setting. Fix one problem properly, then the next. The community will test whether we have actually learned those lessons or merely presented them on a slide. I would rather we arrived having learned them.