01
The data is the most sensitive there is
Health records carry obligations that shape architecture - access control, audit trails, encryption and retention are design inputs, not settings.
ThinkDebug
Practical deep dives on software architecture, AI systems, and scaling digital products - drawn from the work we ship.
Patient portals and clinical tools built to compliance.
We build patient-facing and clinical software: portals and appointment flows, records and care tooling, remote monitoring and wellness products, and the integrations that connect them to the systems a provider already runs.
Health software is judged on two things at once. Clinically it has to be correct and traceable - who recorded what, when, and on what basis. Commercially it has to be usable by patients who are anxious, unwell or unfamiliar with technology, which makes plain language and accessibility part of the clinical safety case rather than a design preference.
Almost every engagement involves an existing system: an EHR, a practice management suite, a lab or imaging provider. HL7 and FHIR make that possible but not simple, and the integration work is usually where the timeline actually goes.
The constraints that shape every build in this sector, and the ones teams usually meet too late.
Health records carry obligations that shape architecture - access control, audit trails, encryption and retention are design inputs, not settings.
Providers run systems that cannot be replaced, so almost every build is an integration through HL7 or FHIR with its own quirks and rate limits.
People using health software are often anxious, unwell or unfamiliar with apps. Clarity and accessibility are part of the safety case.
If a tool adds thirty seconds to a consultation, clinicians stop using it and go back to paper or the old system.
Who recorded what, when and on what basis has to survive, which rules out editing history in place.
Devices drop connections, batch late and disagree. The system has to reason about gaps rather than assume a clean stream.
Swipe to read all 6
Each one is a system we have built before, not a capability we are willing to try.
Booking, reminders, results and messaging in language patients can act on.
Connections to the clinical systems a provider already runs, including labs and imaging.
Workflows built around a consultation's real time budget rather than an idealised one.
Device and app data ingested with gaps, duplicates and late arrivals handled explicitly.
Granular consent, role-based access and an audit trail that answers who saw what.
Patient payments, insurer claims and subscription wellness products in one model.
Engagements across sectors - the same team, the same standards.
Partnering with Thinkdebug to develop the Forever 52 mobile app has been a game-changer for us. They were always open to feedback, and it was clear they were as invested in our success as we were. What really sets them apart, though, is the amazing support we've received since the app launched. They’ve made sure the app continues to run smoothly and are always ready to fix any issues that come up.DMDhruv MehtaBusiness Head, Forever 52
Chosen for fit and long-term maintainability, never for novelty.
Send us the scope and we come back with an itemised estimate - no discovery fee, no obligation.
What we design and document against, from the first commit rather than the week before an audit.
Certification itself belongs to your entity and its assessor. What we provide is software built and documented so the assessment is about evidence rather than remediation.
Most of our work comes from clients we already shipped for. These are the reasons they give.
Who can see a record, and who did see it, is modelled at the start - it cannot be added credibly once the data is already flowing.
The EHR stays. We build against FHIR and HL7 with their real limits in mind instead of designing as though the provider will migrate.
Plain language, large targets and accessible flows, because the person using a health product is rarely at their best.
Clinician tooling is measured against the seconds it adds to a consultation, which is what decides whether it gets used.
Clinical data is append-only with provenance, so a correction is a new fact rather than a lost one.
Gaps, duplicates and late batches are handled explicitly, so a missing reading is visible rather than silently interpolated.
Let's start with you.
Your information stays private. We reply within 24 hours.
Still have a question we have not answered?
Ask an engineerWhat we build for health & lifestyle, the work we have shipped, and what we have written about it.
