MISTAKE

Your body may soon get a patch Tuesday

A proposed update schedule for implanted medical devices would standardise when your hardware restarts. The working title of the document is said to be deliberately boring, for reasons its authors consider obvious.

SATIREBy 20406 min read
A patient sitting calmly in a bright clinic chair while a small bedside screen displays a four-minute progress bar.

A technical committee looking at implanted and wearable medical devices has begun discussing something the computing industry settled thirty years ago and the human body has not: a predictable day of the month on which software updates arrive. The proposal would align manufacturers on a single monthly window, so that a person carrying four devices would face one interruption rather than four.

The clinical argument is strong and slightly alarming. Implanted devices already receive firmware updates, sometimes for security reasons, and the current arrangement leaves each manufacturer to choose its own timing. A patient with a pump, a monitor and a stimulator can, in principle, be updated by three companies in the same week, none of which is required to tell the other two.

Under the draft, updates would be staged in advance and applied at a time chosen by the patient within a defined window. The device would confirm, in plain language, what is changing. The committee has spent what participants describe as a substantial amount of time on the wording of the sentence that appears while this is happening.

“The instruction would not say do not operate heavy machinery,” a spokesperson for the committee would note. “That is a different kind of warning. We are looking at something closer to: please remain seated, this will take four minutes, and your heart is not part of the update.”

The hard problem is rollback. Software that turns out to be wrong can normally be reverted, which is why the industry tolerates shipping it. A device that has already changed how it paces, doses or stimulates has, in a meaningful sense, already shipped its consequences, and the committee's own paper concedes that the word rollback carries less comfort here than elsewhere.

There would also be a question of consent fatigue. A patient asked once to accept an update will read it. A patient asked monthly for a decade will not, and the draft acknowledges that the most likely outcome of a well-designed consent flow is a well-designed habit of pressing the same button without looking.

None of this is scheduled. It is a committee, a draft and a long list of comments. But every element already exists, and the only genuinely new proposal is that the interruptions be synchronised — which is, on reflection, the most humane idea in the document and the one most likely to survive it.

This story is satire: it describes a hypothetical future, not a real event.

Editorial Policy

If you liked this…

Still laughing

We made it up. Then reality caught up.

View all
AI20212025

What we wrote

We wrote it in 2021

One day the junior developer's main skill could be describing the problem clearly enough for the machine to solve it.

What actually happened

Reality caught up in 2025

AI coding assistants are built into mainstream development tools, and producing code from a plain-language description is now a routine part of professional software work.

Vendor product documentation and developer surveys on assistant adoption.

The joke was the job description. The job description was updated.

How close we were88%

MISTAKE

TOMORROW, DELIVERED TODAY.

One email a week. The future, before it files a press release.

Worst case: you laugh. Best case: we predicted the future.