For healthtech
the hard part is what the screen is allowed to show.
Consent is not a checkbox. It is granular, revocable and timestamped, and every screen after it has to know what it is allowed to render. PHI in a page title, in a URL, or in a screenshot somebody pastes into a chat is the same failure three times.
what ships — 5 rows
What ships
- Consent
- granular, revocable, timestamped — and readable back
- Record views
- PHI on intent, never in a URL or a page title
- Referrals
- chain of custody, read receipts, no dead ends
- Audit trail
- who saw what, and when
- Shipped as
- Figma variables and production components
What ships
- Consent
- granular, revocable, timestamped — and readable back
- Record views
- PHI on intent, never in a URL or a page title
- Referrals
- chain of custody, read receipts, no dead ends
- Audit trail
- who saw what, and when
- Shipped as
- Figma variables and production components
what I’m not.
I am not your compliance advisor. I build the interface that makes your policy visible and enforceable; a lawyer or a compliance officer decides what the policy is. I don't write your controls and I won't tell you what your regulator will accept.
what I can show you.
No published healthtech work yet. The nearest real thing is DEVSFORFUN — the identity layer seven products run on, where consent is logged against the record rather than assumed from a ticked box.
what it costs.
every line item, priced →Launch
$5,800$5,300
you save $500
brand core + website + social kit
Product
$11,300$10,500
you save $800
brand core + website + design system, standard tier
Everything
$16,400$14,900
you save $1,500
Product + the build at the system-owner rate
start by finding out what’s wrong.
$500, five days, a recorded walkthrough and a written action plan — and it comes off the project if you book one.