The NHS respiratory pathway is a collection of services rather than one system. It includes GP-led primary care, community respiratory teams, secondary care outpatient services, and emergency pathways, each with its own commissioning arrangements and capacity pressures. Choosing the right digital intervention starts with identifying which part of the pathway, and which patients, you want to improve.
This article is for clinicians considering remote monitoring for COPD in practical terms. It is neither a framework nor a policy guide. Instead, it describes how services operate, where digital tools have gained traction in the NHS, and the practical barriers to adoption seen from within clinical settings.
Where COPD Care Takes Place
Most people with COPD in England are managed mainly in primary care. The annual review usually takes place at the GP practice with a practice nurse or nurse with a respiratory interest, rather than a specialist. Inhaler technique, spirometry, CAT score assessment, and medication review are primary care tasks. Secondary care supports more complex patients, diagnostic uncertainty, and assessment at GOLD stage 3 or above, when specialist input may alter management.
This arrangement means a digital tool intended to improve COPD outcomes must work in primary care, rather than only in a specialist respiratory clinic. Primary care teams have limited time, large patient lists, and little scope to take on new monitoring streams unless the workflow fits existing clinical administration instead of adding a parallel process.
Where present, the community respiratory team bridges primary and secondary care. Respiratory nurse specialists and physiotherapists deliver pulmonary rehabilitation, visit complex patients at home, and provide telephone support during recovery from exacerbations. This team may be the natural base for coordinating remote monitoring, although it is often among the most pressured teams in an integrated care system.
NHS Digital Policy Requirements for New Technology
Digital health tools entering NHS practice must meet requirements beyond clinical efficacy. Under UK GDPR, data storage must ensure patient data is not held on servers outside the UK or EEA without suitable safeguards. The tool should also meet NHS data security expectations described in the Data Security and Protection Toolkit (DSPT). Where a tool influences clinical decisions, it is necessary to consider whether it is a medical device under the UK Medical Devices Regulations 2002, as amended post-Brexit, and whether UKCA marking or MHRA registration is therefore required.
RespiroScreen is currently a decision-support tool in pilot phase. It offers no autonomous clinical recommendations, and a clinician reviews its outputs before action is taken. This is intentional, and means it does not currently occupy the same regulatory category as a product producing automated diagnostic conclusions. We are reviewing the MHRA's Software as a Medical Device guidance in relation to our development roadmap, and will keep clinicians informed as that assessment develops.
Clinicians assessing a digital tool should ask its supplier directly about regulatory status. For an early-stage product, "we are working on it" can be a valid response. By contrast, "we do not need to register" without a clear technical explanation should raise concern.
What Clinical System Integration Really Means
In health technology, "integration" can describe anything from a complete HL7 FHIR feed into an NHS clinical system to a simple PDF export. For respiratory monitoring, the practical issue is more specific: how does an alert reach the appropriate person at the appropriate time, and how is the resulting clinical response recorded?
Our pilot-site experience is that full EMIS or SystmOne integration, although desirable in the medium term, is not essential to making a pilot work. The essential workflow is simple and consistent: one named person receives alerts, contacts the patient, and records the outcome in the clinical record using the practice's existing method. This might be a task note, telephone encounter record, or clinical letter. We are working towards system integration, but do not require it for a useful initial deployment.
For Integrated Care Boards considering remote monitoring across a population, the situation is more involved. Care coordination tools, population health management platforms, and enhanced access services may all intersect with a COPD monitoring programme. Our recommendation is to begin with a defined cohort, named team, clear escalation pathway, and defined evaluation period. Once the workflow works at small scale, governance arrangements for wider deployment can follow.
Discussing Commissioning
NHS digital health tools are usually introduced through one of three routes: a national programme, such as an NHS England pathway or AHSN-supported rollout, a local ICB-commissioned service, or practice-level procurement funded through prescribing or QOF budgets. Each route brings different timescales, evidence requirements, and decision processes.
The NHS Long Term Plan supports COPD remote monitoring in principle, and the NHS IMPACT programme has piloted remote monitoring across various respiratory conditions. National endorsement, however, does not guarantee local commissioning. ICBs face substantial financial pressure, so new programmes need a clinical case as well as a financial one. For COPD remote monitoring, that case concerns avoided emergency admissions and readmissions. The monitored programme's marginal cost must be below the cost of the admissions it prevents. This can be calculated, but a local argument requires data on admission rates and NHS tariff costs.
From our work with pilot sites, the clearest cases come from clinicians who know which patients in their cohort have experienced two or more admissions in the past year. This group is generally a small part of the overall COPD list but uses a disproportionate amount of emergency resource. Beginning with a defined cohort makes the clinical and financial case easier to show.
Digital Maturity in Respiratory Teams
NHS England's Digital Maturity Assessment framework addresses many capability areas. For a primary care or community respiratory team considering remote monitoring, the immediate questions are simpler: is there a named digital lead, a process for handling clinical alerts from external systems, and capacity, even 20 to 30 minutes per clinical day, to review monitoring activity?
Digital maturity is not a prerequisite for a pilot. However, when these questions have no clear answers, monitoring programmes commonly stall after an enthusiastic launch. Technology is rarely the main constraint. Adoption depends more on workflow, staffing, and the organisation's willingness to review and respond to a new stream of data.