Software for healthcare that has to hold up under scrutiny
Care staff spend the last hour of a shift re-entering the same information into a roster, a client file, and a billing export. We build the systems that capture it once and keep it where the people delivering care can actually reach it.
What we see in healthcare
The same data entered three times
A shift is planned in one system, reported in the client file, and then rekeyed for billing. Every extra entry is an hour not spent on care and another place the record can drift.
Client information moving through channels nobody controls
Practitioners fall back on WhatsApp and personal email for hand-overs because the official system is slower. Special category data ends up outside the systems you can account for.
Software shaped around a billing code, not a shift
Off-the-shelf care software models the reimbursement, not the way your teams actually work across locations, hand-overs, and irregular hours.
What we build for it
One entry point for care administration
Roster, client record, and reporting joined so information is entered once and flows to everything downstream, including the exports finance needs.
Hand-over and communication inside your own system
Structured hand-overs and messaging with role-based access and logging, so the fast route is also the compliant one.
AI that drafts, a professional who signs
Summarising and reporting assistance that shortens the administrative tail of a shift, with the practitioner responsible for what is finally recorded.
What an inspector can ask to see
Care records are among the most tightly governed data in the country, and two of the rules dictate architecture rather than policy. That is why they belong on this page instead of in a compliance annex.
- NEN 7513
Access to a client record has to be logged well enough to show a client who opened their file. It sits alongside NEN 7510, the sector's security standard.
Reads are logged, not only writes. That carries a real cost in storage and in design, and it has to be decided before the record store exists rather than added to it later.
- Special category data
Health data carries a higher bar to process lawfully and a heavier consequence when it leaks.
Least-privilege access throughout, no production data on a developer's machine, and hand-overs kept inside systems you can account for rather than in a messaging app.
- Wgbo retention
Medical records kept for twenty years from the last entry, and destroyed once that period ends.
A twenty-year window is a schema decision, not a setting. It is designed in alongside deletion that runs on schedule and leaves a record that it ran.
This is how we design against these obligations. It is not legal advice: your compliance officer owns the interpretation, and we make sure the software can answer them.
Compliance and data
Client records are special category data under the GDPR, and the people who need them work across locations, shifts, and devices. Access control is a design decision here, not a setting someone flips afterwards.
Related case
We cannot yet publish a care client. This one is the closest work we own: a legal claims team was chasing medical documents by hand. Sensitive records, deadlines that slip and communication scattered across inboxes are the same problems care administration has.
Let’s build your next solution
Bring your industry challenges and we’ll pair them with the right mix of AI, engineering, and design to launch fast without sacrificing quality.