Infrastructure for care that happens out of sight.

Why we built it

The record was the hard part.

Moving an infusion out of a hospital chair and into somebody's front room is good for almost everyone involved. It is cheaper, it is kinder, and for a patient on a long course of therapy it is the difference between a treatment plan and a life.

What does not travel well is the evidence. In a clinic, the documentation is a by-product of the building — badge readers, a chart that stays put, colleagues who witnessed it. In a home, all of that has to be deliberate. Most of the industry solved it with paper, photographs, and trust, and then discovered how those hold up under audit.

So the platform is built the other way around: the record is the product, and the scheduling is what makes the record possible. A nurse cannot accept a visit their licence does not cover, because the eligibility test runs before the visit is visible. A patient's address is not in the network's field of view, because masking is the default rather than a preference. Every hand-off writes to a log that cannot be edited afterwards, because a log that can be edited is not evidence.

How we work

VeinFusion ships a web portal per role and native apps for the three roles that work away from a desk. The isolation rules live in one API, so a new client cannot introduce a new way around them. And staff access to patient data is logged the same way anyone else's is — including the act of reading the log.

If you want the mechanics rather than the intent, the security overview is the honest version, including what we do not yet claim.