01
The EHR cannot be replaced
Epic, Cerner or a regional system is already in place. Every build is an integration, and its interfaces and rate limits shape what is possible.
ThinkDebug
Practical deep dives on software architecture, AI systems, and scaling digital products - drawn from the work we ship.
Patient portals and clinical tooling built to compliance requirements from the first commit.
We build provider-side healthcare software: clinical tooling and EHR integration, referral and care-coordination flows, claims and revenue cycle systems, and the interoperability layer that lets any of it exchange data with the rest of the health system.
Institutional healthcare has a different centre of gravity from consumer health. The user is a clinician with no spare seconds, the data is a legal record, and the system it must talk to was chosen a decade ago and cannot be replaced. Most of the engineering effort goes into that last part.
The constraint that shapes the architecture is traceability. A clinical record is evidence: who wrote it, when, on what basis, and what it said before it was corrected. That rules out editing history in place and makes an append-only model the starting point rather than an optimisation.
The constraints that shape every build in this sector, and the ones teams usually meet too late.
Epic, Cerner or a regional system is already in place. Every build is an integration, and its interfaces and rate limits shape what is possible.
A tool that adds thirty seconds to a consultation is abandoned. Adoption is decided by time saved, not by features shipped.
Clinical data must show who wrote what, when and on what basis, which rules out overwriting history.
It is not enough to restrict who can see a record. You must be able to show who did, months later, on demand.
Referrals, labs and specialists sit in different systems and different organisations, and the handoffs are where information is lost.
Coding, eligibility, denials and resubmission form a workflow as complex as the clinical one, and it is where the revenue actually is.
Swipe to read all 6
Each one is a system we have built before, not a capability we are willing to try.
Integration with the clinical systems a provider already runs, including labs, imaging and health information exchanges.
Order entry, documentation and care coordination built around a consultation's real time budget.
Cross-organisation referral flows that keep context rather than losing it at each handoff.
Eligibility, coding, submission and denial management wired to the clinical record.
Role and purpose-based access with an audit trail that answers who saw what and why.
Quality measures, utilisation and regulatory reporting derived from the source record rather than re-keyed.
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.
The EHR interface is the part most likely to move a timeline, so we prove it early rather than discovering its limits in month four.
Append-only with provenance, so a correction is a new fact and the original is still answerable months later.
Every read and write of a clinical record is logged with purpose, because restricting access is only half of what an auditor asks for.
Tooling is judged on the time it adds to a consultation, which is what actually decides whether it is used or bypassed.
Referrals and cross-organisation flows carry their context, because that is exactly where information is normally lost.
Coding and eligibility draw on the clinical source rather than re-keyed data, which is where most denials originate.
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 healthcare, the work we have shipped, and what we have written about it.
