Luxailux.ca

Articles · Health & Care

The reading that travelled alone

Care at home runs on readings that cross a home network, a phone, and a vendor cloud before anyone sees them. HomeWard proves which device sent each one.

By Lucian · Lux Automations

The problem

Care has moved into the home, and the readings have moved with it. Remote monitoring grew from 55,000 Medicare patients in 2019 to 570,000 in 2022, and 133 hospital-at-home programs had been approved by April 2024. Cuffs, monitors, and patches in people’s homes now send readings to platforms and care teams as a matter of routine.

Each of those readings travels. It crosses a home network, a phone, and a vendor cloud before it reaches the platform that asked for it. Along that road, a simple question is surprisingly hard to answer with proof: which device sent this reading, and did anything touch it on the way. The number arrives, and its provenance is taken on trust. For a platform whose work depends on trustworthy device data, and for the health systems behind it, trust without proof is a thin place to stand.

The technology

HomeWard starts at enrolment, where every device is given an issued identity. Every cuff, monitor, and patch is known by its own key, so a reading can be tied to the device that sent it rather than to an account or an address it passed through.

Requests are mandate-checked in the other direction. A platform may request only what its mandate allows it to ask for, no more. And every batch of readings crosses with a signed receipt: which device, when, and to whom, with the crossing proven and the record kept. The reading itself never touches our layer. Receipts record the crossing, never the content. That boundary is the design, not a detail. HomeWard proves which device sent a reading, never that the reading is right. It makes no medical promises; it keeps the record honest, and it sits beside the clinical path, on identity, access, and evidence, never inside it.

What it changes

For monitoring platforms and the health systems running hospital-at-home programs, provenance stops being an assumption. A batch of readings arrives with its source device named and its crossing receipted, and a platform’s requests are bounded by what it was actually allowed to ask. When the record is reviewed later, the question of where a reading came from has an answer written at the time it crossed.

For the person at home, the change is mostly invisible, and that is as it should be. Their devices are enrolled and known, the platforms that receive from them are checked, and the content of their readings does not pass through our hands at all. We sell the check, never custody. HomeWard’s whole job is the honest record around the reading, so the people doing the care can stand on where it came from.

See it

Care at home runs on readings, and HomeWard proves which device sent each one. HomeWard — the product page · All the house articles · Lux Automations — ailux.ca