Skip to content
PixelformBuy the $500 audit

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

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
Production components and a documented system

Three surfaces, and the constraint each is under

The three surfaces a healthtech interface needs, and their constraintsConsent capture: Granular, Revocable, Timestamped. Record view: PHI visible only on intent, No data in URLs. Referral handoff: Chain of custody, Read receipts.Consent captureGranularRevocableTimestampedRecord viewPHI visible only on intentNo data in URLsReferral handoffChain of custodyRead receipts
Three surfaces, and the constraint each one is under.

What the studio is not

Not your compliance advisor. The studio builds the interface that makes your policy visible and enforceable; a lawyer or a compliance officer decides what the policy is. It doesn't write your controls, and it won't tell you what your regulator will accept.

What there is to show

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.

Start by finding out what’s wrong.

$500, five business days, a recorded walkthrough, a written action plan and a competitor table, and it comes off the project if you book one.