Temporary solutions have a real virtue: they make a response possible when time, evidence or capacity to build something better is missing. They also conceal a risk. Once the emergency has passed, the application, data collection, validation pathway or organisational exception may remain, even though nobody again justifies its necessity. In health, that inertia matters especially because it affects privacy, access, safety and trust. More precise medicine should not merely produce a better estimate; it should remember why each tool was adopted, when it will be reviewed and who can withdraw it without abandoning people who already depend on it.
This analysis provides neither diagnoses nor instructions for individual cases. It examines clinical and technological governance: how an organisation distinguishes a temporary response from permanent infrastructure, how it measures benefits and harms over time, and how it preserves a human route to care. Anyone concerned about symptoms, treatment or a change in health should seek advice from qualified healthcare professionals, or contact emergency services when the situation is immediate.
Temporary measures need deliberate design#
A temporary measure is not a rule-free zone. It needs a limited purpose, a defined population, an accountable owner, a review date and explicit closure criteria. Without those elements, urgency becomes an indefinite authorisation. The problem rarely looks like a single momentous decision. It more often arrives through small renewals: a licence paid for another year, a form that continues to request information, an alert nobody feels authorised to disable, or an access exception that quietly becomes the ordinary route.
A temporary measure is not a rule-free zone. It needs a limited purpose, a defined population, an accountable owner, a review date and explicit closure criteria.
Continuation may be reasonable. Video consultations introduced during a crisis may prove that they prevent unnecessary travel. A reminder service may reduce missed appointments. A monitoring dashboard may improve coordination. Yet observed value does not remove the duty to decide again. The mature question is not whether a measure began as an exception, but whether it now retains proportionate benefit, sufficient evidence, acceptable safety and accessible alternatives. Renewal should be a documented decision, not the automatic consequence of failing to schedule an ending.
Time also changes context. Guidelines, teams, suppliers and security threats evolve; so do the needs of patients and professionals. A tool evaluated in one population may later be used in another. Accumulated data may acquire uses that did not exist at the outset. An initial authorisation therefore cannot cover the system's entire life. Responsible precision requires surveillance, learning and the institutional ability to recognise that a solution useful yesterday may need different limits today.
Expiry, renewal and accountability#
A sunset clause makes the decision visible. It does not mean switching off a service abruptly; it sets the point at which reasons must be presented for continuing it. A review should compare the original objective with clinical and operational outcomes, incidents, complaints, workload, differences between groups and people's experience. It should also ask what is no longer being measured. A favourable average can conceal withdrawals, language barriers or extra tasks absorbed by relatives and healthcare staff.
Accountability needs a name and real authority. If everyone can flag a problem but nobody can pause the system, oversight is ornamental. The accountable person or committee needs access to intelligible records, must listen to people providing and receiving care, and must be able to require supplier corrections or order a safe reduction or withdrawal. This role should not become a way to blame an individual professional for a structural failure. Its purpose is to coordinate evidence, protection and repair.
Continuity of care must also be separated from continuity of technology. Withdrawing an application does not mean withdrawing care. Before closing or changing a service, an organisation should identify people who depend on it, offer an equivalent route, communicate deadlines in plain language and preserve clinically necessary information. A planned exit prevents technological caution from landing on patients as one more barrier.
Case 1: digital triage that outlived the emergency#
A primary care centre introduced a digital questionnaire during an emergency to sort incoming requests. The measure reduced overloaded phone lines and enabled faster responses to some reasons for contact. Two years later, the form was still the preferred entry point. The organisation no longer recorded how many people abandoned it, needed help to complete it or described their situation poorly because the closed options did not fit. Early success had turned into an assumption of permanent success.
The review revealed three distinct layers. The questionnaire was useful for predictable administrative tasks, less reliable for ambiguous narratives, and exclusionary for some people because of language, digital literacy or disability. The team did not conclude that all digital classification was harmful. It narrowed the tool's role, added telephone and face-to-face access without penalty, reviewed its wording with patients and introduced quarterly audits of withdrawals, waiting times and referrals. Warning signs remained the responsibility of trained professionals working with current protocols.
The case demonstrates that an operational metric is not the same as clinical safety. Fewer calls may indicate better organisation, or it may mean that certain people stopped trying. Responsible decisions combine quantitative data with testimony, examine outcomes across groups and allow a concern to be escalated. No questionnaire should be treated as a personal diagnosis. A person with worrying symptoms or deterioration should contact healthcare professionals or emergency services, according to the seriousness of the situation.
Case 2: remote monitoring that began to create noise#
A hospital loaned connected devices to people living with a chronic condition so that follow-up could continue remotely. At first, the programme provided reassurance and detected changes that warranted clinical contact. Over time, alerts increased, but the team's capacity to review them did not. Some alerts came from poorly positioned sensors, unstable connections or thresholds developed for a different population. Professionals and patients began living with frequent notifications whose relevance was not always clear.
The response was not to recommend that each patient change medication or behaviour in response to a screen. The hospital treated measurements as supporting information, not commands. It reviewed device quality, redesigned escalation with clinical oversight, explained what the system could and could not infer, and offered channels for reporting symptoms even when sensors showed no change. It also limited data retention, renewed consent for secondary uses and allowed people to leave the programme without losing care.
Precision emerged from reducing noise, not accumulating more numbers. An isolated measurement lacks the context provided by clinical history, symptoms, preferences and professional judgement. An alarm may also generate anxiety or false reassurance. When an individual has doubts about a reading or personal health, guidance should come from the responsible healthcare team. The technology programme should make that conversation easier, never replace it or present a prediction as certainty.
Case 3: a temporary database that became a permanent archive#
During an exceptional campaign, a public authority created a register to coordinate appointments and resources. Consent materials and public information described a specific purpose, but after the campaign ended the data remained available for analysis and new projects. Nobody had explicitly decided what to retain, for how long or on which basis. The infrastructure made storage easy and deletion difficult. The technical emergency was over, but the information exception remained alive.
The review brought together care leaders, data protection and security specialists, patient representatives and research staff. It classified information according to clinical need, legal obligation and scientific value; removed duplicates and obsolete access; documented retention periods; and subjected new uses to independent assessment. Where renewed information or consent was required, clear language was used. People received a channel for exercising rights and asking questions without having to understand the system's architecture.
The central lesson was that health data do not become insensitive as time passes. Even pseudonymised datasets may reveal habits or vulnerabilities when combined with other sources. Protection requires minimisation, access control, traceability and incident response, as well as a valid justification. Not all retention is illegitimate, and not all deletion is prudent. The decision should rest on clear purposes, applicable rules and proportionate analysis, with professional legal and data-protection advice where appropriate.
What a periodic review should measure#
A useful review covers at least five dimensions. The first is benefit: whether the measure improves meaningful outcomes rather than merely increasing activity. The second is safety: failures, delays, false alerts and unintended consequences. The third is equity: who obtains access, who withdraws and who needs extra help. The fourth is burden: time contributed by patients, carers and professionals, including the invisible work of correcting data. The fifth is trust: understanding, consent, complaints and the ability to obtain a human explanation.
Indicators need a comparator and a timetable. Counting incidents without knowing the volume of use misleads; measuring satisfaction only among people who completed a pathway erases those excluded from it. Outcomes can be disaggregated respectfully, without creating new categories of surveillance, and figures should be combined with interviews or listening forums. The World Health Organization has stressed that digital health should uphold rights, transparency, inclusion and accountability. Patient-safety practice adds another rule: learn from incidents and near misses before harm is repeated.
The review should also test adverse scenarios. What happens if connectivity fails, the supplier changes, an identification error occurs or staff are unavailable? Can someone continue care and reconstruct the decision? Is there a manual process that has been practised rather than merely documented? A resilient system does not promise a total absence of failure. It detects limits, contains the spread of error and makes it possible to recover control promptly and with dignity.
A safe exit is part of care#
Ending a measure may require more work than starting it. Information must be migrated, people warned in good time, teams trained, alternatives secured and checks made that nobody is trapped between systems. An exit plan should exist from procurement onward: exportable formats, supplier responsibilities, verifiable deletion, continuity if the company closes and a transition budget. Without those conditions, technological dependence can make every renewal feel compulsory.
Communication deserves the same rigour. An organisation should explain what is changing, why, when and whom to contact. It should neither promise that a new tool will solve every problem nor frame withdrawal as failure. Correction is part of a learning institution. If someone is harmed, there should be investigation, explanation, support and proportionate repair. Dignity is protected when the person affected is not required to reconstruct the whole chain of failure alone.
Precise medicine that keeps listening retains review dates, identifiable responsibility and exit routes. It asks whether an exception still answers a real need, whether benefits reach diverse groups and whether the human cost remains acceptable. Above all, it distinguishes sustaining care from sustaining a tool. Time turns a temporary solution into something else; attentive governance decides whether that new thing deserves to become infrastructure, needs redesign or has already fulfilled its purpose.
