Digital continuity: can the care service depend on its systems?

1. Start with the care task the system supports

A digital programme becomes easier to govern when it begins with a task people recognise. Describe the information needed, the person retrieving it, the timing and the consequences of incomplete access. That makes it possible to assess a proposed change against the service rather than against a feature list.

An illustrative handover may need a current account, a conversation and access to supporting information. A successful login establishes only one part of that process. Ask staff to explain the points where information is checked, clarified or corrected, including who can resolve a disagreement between records.

Keep the person receiving support in that description. A record can be complete in its fields while losing a preference, a reason or uncertainty about what occurred. The right test depends on the care task and should be agreed with the relevant professional and information-governance leads.

Home-care continuity provides a concrete test for digital records. NICE’s home-care guidance is an established England reference for service delivery, not a digital product specification. It helps identify the care task that an implementation should support: staff need an appropriate understanding of the person and the agreed support, while the person needs confidence about the visit. A successful login does not establish either outcome.

Care Circle’s interpretation is that an outage exercise should follow a realistic handover, not end with the IT recovery time. Could the worker obtain the current plan, recognise a recent change and reach the appropriate service contact? Could a temporary colleague understand what mattered to this person? The answers depend on the service’s arrangements and should be recorded as exercise observations, not assumed because the supplier offers an offline mode.

The exercise also needs to examine reconciliation. Information captured during an interruption may later meet an updated electronic record. The provider should decide how conflicting entries are reviewed, who can resolve them and how the audit trail is preserved. This is a governance question about the quality of the final account; recovering the application is only one part of the response.

A credible future case study would describe the service context, dependencies, safe exercise conditions, observed difficulties, action taken and a later retest. Screenshots of an available system or a supplier’s performance claim would not, by themselves, show care continuity. This edition provides the questions and linked guidance; it does not claim that Care Circle has tested a provider’s technology or interviewed a service about an outage.

Evidence: NICE [7]

2. Read adoption and assurance on their own terms

The published adoption statistics describe penetration across the sector. They cannot establish the way an individual service uses its system. Preserve the location and people denominators, and retain the reporting period when quoting a figure. A June observation is not a verified October operating position.

DHSC’s selection guidance describes the assured-solutions list and the requirements it addresses. The provider still needs to examine its infrastructure, implementation and staff support. Record the supplier’s relevant assurance evidence without using it as a substitute for a local account of practice.

Care Circle’s synthesis is to keep three evidence files connected but distinct: the product or solution assurance, the provider’s operating arrangements and the exercise or incident evidence about continuity. The files answer different questions. Combining them into a single green status can hide a weakness in one part of the service.

Evidence: DHSC [1] · DHSC [2]

3. Map the dependencies behind access

Follow an essential function through device, local connection, external service and the person who can provide support. Include power and the means of contacting the responsible organisation when the usual system is unavailable. The resulting map should help the service understand a failure, not become an elaborate diagram nobody maintains.

DHSC’s digital-record guidance identifies infrastructure and support as part of implementation. Leaders should ask how those requirements appear in the agreed specification and daily arrangements. Separate the assurance of a software service from the reliability of the connection or equipment on which local use depends.

Where organisations share responsibility, name the boundaries. A landlord may control equipment or a building connection while a care provider controls staff practice. A supplier might support only one part of the system. The service needs an agreed escalation route for an issue that falls between those responsibilities.

Evidence: DHSC [2]

4. Test AI at the point where a draft becomes a record

DHSC’s AI guidance supports scrutiny of generated care-planning material and identifies limits in the evidence. A provider considering a tool needs a bounded use case, a responsible reviewer and a clear account of the material being compared. Checking spelling is a narrower task than checking meaning.

An illustrative draft could compress an account of a person declining an activity and omit the reason they gave. A fluent summary might then change the interpretation of the event. The reviewer needs access to the underlying account and authority to reject or correct the result.

Measure the whole task. Include drafting, checking, correction, training and supervision when examining a proposed time saving. Identify material errors and agree an escalation or stopping rule before the pilot begins. This report makes no claim that a product has produced a net saving or improved a provider’s records.

Evidence: Department of Health and Social Care [3]

5. Follow telecare through to the response

The housing-provider guidance published on 8 October belongs to its stated audience. Care services sharing responsibility for a building, alarm or response arrangement nevertheless need to understand the wider phone migration. Obtain the actual migration position from the relevant communications provider rather than treat the national timetable as every site’s appointment.

Follow the function from the device to the receiving service and the person expected to act. Identify who owns compatibility checks, the arrangements during loss of power or connectivity and the appropriate end-to-end test. Use the competent suppliers and responsible leads rather than invent a generic technical fix.

A project status of line migrated needs a separate service account. Has the agreed pathway been tested and documented, and what remains unresolved? A provider should not assume that an upgrade to one component demonstrates the reliability of every connected alarm or device.

Evidence: UK Government [4]

6. Exercise an outage without putting care at risk

The purpose of an exercise is to discover whether the plan can be used. Choose a proportionate scenario with the responsible service and technical leads. A tabletop exercise may be appropriate before any more involved test. Do not interrupt live care or security controls merely to create a dramatic demonstration.

Ask how essential information would be obtained, who would decide the temporary process and how the resulting records would be brought back into the normal system. Include the people on duty outside ordinary office hours. If the answer depends on a contact, verify how that contact can be reached when the usual channel is unavailable.

Keep an action trail for the gaps discovered. A successful discussion about one scenario does not validate every possible outage. State what was examined, what remains untested and which actions need technical or professional advice. Follow those actions into appropriate verification rather than close them because the meeting ended.

Evidence: NHS England [6]

7. Govern the ending of a supplier relationship

DHSC’s September supplier guidance includes transition and the removal of old access. The provider should understand the systems, accounts and documentation within the handover and agree how completion will be confirmed. Distinguish access intentionally retained from access that should have ended.

Before entering the next contract, ask about export, support boundaries, changes to the service and the practical route out. Relevant data-processing terms need appropriate advice. A supplier’s standard assurance statement should be examined against the actual service the provider is purchasing.

The same questions support the next editorial investigation. A documented provider handover or outage exercise could show where responsibility became clear and where gaps remained. We invite those accounts with dates and evidence; this first edition contains no provider interviews or independent system tests.

Evidence: DHSC [5]