Digital telecare now has a procurement test. Can your specification prove the whole service?

What changed: procurement can now start from a common evidence structure

The three documents follow a consistent structure: digital telecare standards; connectivity and resilience; service management and service levels; cyber security and data protection; operational and performance data; and the obligations that remain with commissioners or service providers. They also distinguish the different components of the service. A personal alarm specification is not the same as a grouped living system, and neither is complete without an alarm receiving centre capable of supporting the relevant digital standards and service model.

That creates a practical procurement sequence. First define the people, settings, outcomes and current estate. Then map which requirements belong to the device, connectivity, receiving centre, maintenance organisation, commissioner and care-response service. Only after that mapping can buyers compare bids on a like-for-like basis. A lower equipment price may conceal commissioner-supplied broadband, wiring, power resilience, software, maintenance or integration; a bundled offer may include those elements but make switching or data access harder.

The guidance also gives procurement teams a better way to handle claims. For many requirements, it states what bidders should confirm and what evaluators should regard as a good answer. That can improve clarification questions and the audit trail behind an award. It does not remove the need for lawful procurement, proportionate evaluation or specialist advice, but it reduces the excuse for leaving safety-critical technical claims as untested marketing language.

The new test is not whether a supplier says the solution is digital. It is whether the commissioner can trace how the whole service remains secure, reachable, supportable and usable.

Interoperability has to survive the specification—and the real installation

DHSC identifies inconsistent implementation of digital standards as a source of configuration effort, installation risk and dependence on particular suppliers or receiving centres. For personal alarms, the guidance recommends full support for the documented Alarm IP communication protocol and says devices that use only SCAIP should be avoided because of known security vulnerabilities. For grouped living systems, it recommends full NOW-IP support. For alarm receiving centres, it recommends full support for both Alarm IP and NOW-IP.

The documents also acknowledge an important assurance gap: there is currently no independent body validating that equipment or receiving-centre solutions meet the relevant BSI standards. Commissioners may therefore be relying on bidder assurances. A strong evaluation asks the bidder to identify any manufacturer-specific variants, explain why they exist, state which combinations have been tested and demonstrate what happens if the commissioner changes device, connectivity or receiving-centre provider.

Interoperability should not become a paper-only pass. The housing guidance points organisations towards their own verification of the specific combination of equipment, receiving centre and connectivity. Acceptance should therefore include controlled end-to-end testing against the intended configuration, including connected peripherals and the information the responder receives. Where migration is phased, backwards compatibility may be necessary, but it should be treated as an explicit transitional dependency rather than proof that the long-term design is complete.

Resilience must be measured from the alarm to the receiving centre

The personal-alarm guidance favours a mix of modern mobile and fixed broadband connectivity. It asks bidders to explain 4G and Voice over LTE support, network and routing dependencies, coverage limitations and the resilient options available, including dual SIM, resilient SIM, eSIM and fixed broadband. It describes fixed plus mobile broadband as the best way to reduce single points of failure. The grouped-living guidance similarly recommends end-to-end internet connectivity, at least one second-connection option and appropriate battery backup for the alarm system and associated network equipment.

A headline uptime figure is useful only if its boundary is clear. Across the guidelines, DHSC suggests availability should not be below 99.9% annually for the relevant connectivity or alarm receiving centre service and should reflect the end-user route—not simply whether a supplier’s management portal is online. For alarm receiving centre solutions, it also suggests that service-affecting faults should be fixed within four hours. These are commissioning recommendations for a safety-critical service, not statutory guarantees that no interruption will occur.

The contract should define what counts as unavailable, where measurement starts and ends, which shared failures trigger the service level, what is excluded and who reports the evidence. Proactive fault notification should be specific to the provider and explain the effect on its service, rather than repeat a generic network message. A 24-hour service desk and regular service reporting are useful only if the named teams can see affected devices, communicate risk and support the commissioner’s contingency response.

Cyber assurance now belongs inside the telecare award decision

Digital telecare brings internet-connected equipment, cloud management platforms, call recordings and sensitive service-user information into the same supply chain. The guidance recommends a data protection impact assessment and asks for cyber certification covering the equipment and services in the bid, including relevant subcontracted elements. Depending on the component, bidders are directed towards ISO 27001, Cyber Essentials, Cyber Essentials Plus or an equivalent standard whose protections can be validated.

A certificate is not the end of the evaluation. Commissioners are encouraged to examine risk ownership, asset identification, incident detection and response, customer-notification timescales, vulnerability remediation, security-update periods and independent penetration testing. For personal and grouped-living equipment, the guidance also asks bidders to address the Product Security and Telecommunications Infrastructure Act where applicable and provide a statement of compliance or explain why it does not apply.

The commercial question is whether the promised controls cover the full solution and its expected life. A bidder may hold a relevant certificate while a connectivity partner, device management platform or subcontracted support function sits outside its scope. The evaluation record should identify that boundary and assign any residual responsibility. Contract review should then track certificate validity, significant vulnerabilities, remediation commitments and material supplier or software changes after go-live.

Data access is both an oversight control and an exit condition

The three guidelines repeatedly ask for provider access to operational and performance data through open, editable exports and, where applicable, secure published application programming interfaces. For personal alarms and grouped living systems, that includes build, configuration, peripheral and connectivity information. For alarm receiving centre solutions, the expected data can include service-user records, call history, responses, background messages, failed connections and call recordings.

This matters before award because digital telecare can create several separate management platforms. A provider using equipment from more than one manufacturer may otherwise have to monitor multiple portals without a reliable end-to-end view. Procurement should define which data is required for daily assurance, incident investigation, contract management, integration and eventual migration—and whether staff can export it without asking the incumbent supplier to do the work.

An API promise scheduled for a future roadmap is not the same as a live, documented interface. Where a capability is not yet available, the bid should contain a committed delivery date, acceptance criteria and a contractual consequence if it is missed. Exit planning should cover format, completeness, secure transfer, retention, deletion and the continued availability of evidence needed for complaints, safeguarding, investigations or legal obligations.

Grouped living turns telecare procurement into an estates and fire-safety decision

DHSC estimates that around half a million people—approximately a quarter of UK telecare users—use grouped living or warden-call alarms. One analogue master unit can serve up to 40 flats, and the wider system may be linked with fire detection, lifts or door entry. Replacing a grouped system is therefore not simply a swap of alarm hardware. It can alter wiring, building connectivity, resident interfaces, response arrangements and the safety strategy for a whole scheme.

The housing guidance says providers should identify installed equipment and connected systems, assess the effect on the fire strategy and fire risk assessment, involve the responsible person and consider whether building-regulations action is needed. A bidder should identify which existing elements can be reused, which are incompatible and which infrastructure the commissioner, another supplier or the service user must provide. That is the basis for understanding whole-life cost and disruption, not an optional technical appendix.

Resident involvement also belongs before the design is fixed. A building-wide replacement and a move to personal digital alarms can have different implications for people, communal coverage and connected safety functions. Co-design should examine accessibility, confidence, privacy, response arrangements and what happens during installation or an outage. The purchasing decision is stronger when resident experience, estates constraints and care-response reality shape the specification rather than being managed after contract award.

Put the whole decision-making group in the room before bids are scored

The core group is likely to include the commissioning lead, telecare or technology-enabled-care lead, procurement, adult social care operations, housing or estates, information governance, cyber security, legal or contract management and the people responsible for receiving and responding to alerts. Grouped schemes may also require the fire-safety responsible person and building specialists. People who use telecare and their representatives should influence needs, accessibility and acceptance—not only receive a notice after selection.

Each member should own a defined part of the evaluation. Technical specialists can challenge standards, connectivity and security; operational teams can test alert handling, escalation and support; estates can validate power, wiring and building dependencies; procurement and legal teams can make service levels, data access, change control and exit obligations enforceable. The commissioner remains responsible for balancing those views against need, affordability and the lawful procurement route.

Supplier demonstrations should follow scenarios chosen by the commissioner. Useful tests include loss of the primary connection, loss of mains power, an alarm software update, a receiving-centre fault, a failed connection, a service-user move and the export of a complete data set. Demonstration is not acceptance, but it reveals where answers depend on an unrepresented subcontractor, an unbuilt integration or an assumption about infrastructure at the setting.

A 30-day procurement-readiness programme

Days 1 to 7: establish the buying boundary. Separate personal alarms, grouped living systems and alarm receiving centre requirements. Map the current equipment, standards, connectivity, building systems, contracts, renewal dates, users and responsible organisations. Identify lines or broadband connections that support telecare and confirm the relevant data-sharing and migration position. Record unknowns rather than treating them as future implementation details.

Days 8 to 15: run a structured gap review against the three guidelines. Classify each provision as essential for the local service, desirable, not applicable or requiring specialist advice. Define the evidence bidders must provide and the people who will evaluate it. Complete or begin the DPIA, cyber review, fire-safety assessment and resident involvement needed to shape the specification. Use early market engagement to test deliverability without designing the competition around one supplier’s architecture.

Days 16 to 23: write the service, evaluation and contract controls together. Connect outcomes and user needs to technical standards, availability boundaries, fault handling, planned maintenance, security updates, reporting, data access, change control, subcontractors, acceptance and exit. Price the commissioner-side infrastructure and resources as well as the supplier charge. Define how a phased migration will be governed and when transitional compatibility will end.

Days 24 to 30: challenge the draft through failure scenarios and an independent red-team review. Ask whether a bidder could score well while leaving a material dependency unowned. Confirm the procurement timetable allows site work, resident communication, implementation, testing and remediation before vulnerable users depend on the new arrangement. The output is not a promise that procurement will finish in 30 days; it is a decision-ready evidence pack for the next governance gate.