Healthcare / telehealth
A platform where a bad release is a safety problem
A telehealth platform where the software sits in a safety-critical path: getting a release wrong has consequences for a patient, not just for a metric.
Anonymous, a telehealth business
The challenge
Identity data needed real isolation rather than a column flag, and nothing client-facing could be allowed to ship on an automated pipeline alone. The usual startup defaults, one database and deploy on merge, were the wrong defaults here.
The old process
The requirement was not "move faster". It was to make the dangerous actions impossible to take by accident, without making ordinary development miserable.
The system we built
- Identity data held in a physically separate database with its own isolated credentials
- A human approval gate in the release state machine, so nothing client-facing ships unreviewed
- A crisis check that runs before payment is taken, not after
- An end-to-end integration test suite covering the paths that matter
The technology
- NestJS
- Next.js
- PostgreSQL
- Prisma
The result
Built, proven end to end by the integration suite, and running. Included here because it shows the same instinct as the automation work: find the failure that nobody would notice until it was expensive, and design so it cannot happen quietly.