Healthtech
A growth chart plotted against the wrong standard does damage before anyone catches it.
Patient- and parent-facing products where the guidance on screen has to match the clinical standard it cites, and every record is personal data before it is a row.
What the domain demands
Health data is treated as sensitive by default, not hardened later. Guidance shown to a parent or a clinician is checked against the standard it claims to follow, and the version of that standard is recorded alongside the reading, because the curve is published by someone else and can change. Access to any record is scoped to the person who actually needs it.
What changes about how we build
We store the least personal data that does the job, encrypt it at rest and in transit as a default rather than a hardening pass, and keep an audit trail on who read a record, not only who created it. Identifying data stays out of logs, traces, and error reports entirely, which is a decision made at the instrumentation layer rather than scrubbed afterwards.
- Built against
- Data privacy by default / Role-scoped access / Accuracy against clinical standards / Audit logging / Consent tracking
Other domains
Different pressure, the same way of building.
Building in Healthtech?
Tell us the constraints. We will come back with how we would build against them.