Loading
Loading
Case study · Studio study
A care-adjacent portal with privacy as a layout problem.
Studio study with a working title. Not a named-client claim.
Overview
Pulse is a patient-adjacent portal study: appointments, documents, and messages. We do not claim clinical or regulatory certification. The study is about consent, least privilege, and calm UX under stress.
The challenge
People use these products when they are tired and worried. Dense hospital software is a known failure. Consumer-cute is another. The work is clarity, audit, and not mixing records.
Objectives
Session and role discipline
Documents with access logs
Language a non-clinician can parse
No dark patterns on scheduling
Strategy
Every view names why you are allowed to see it. Messaging is not a chat toy; it is a thread with an audit. Scheduling shows what is actually available.
Discovery
We wrote anxious-user scenarios first. If a screen required a legend, it was redesigned.
UX
Home is 'next' and 'needs you'. Records are a timeline. Download is explicit. Logout is easy.
Design
High contrast, large type, maroon reserved for alerts that are truly alerts. No ambient animation in clinical-adjacent views.
Engineering
Short sessions, strict CORS, downloads logged, encryption in transit as a baseline. We document what this study is not (not a certified medical device, not a HIPAA attestation by itself).
Architecture
Auth
Short-lived sessions.
Technology
Frontend
Backend
Storage
Implementation
Result
Session policy
Documented
Audit
Sensitive reads
Claims
No certification implied
Replace with measured results after a client engagement.
Voice
“Replace with a product owner in care operations — after legal has cleared the quote.”
Start
Tell us what you are trying to ship. We will come back with questions, a shape, and whether we are the right studio for it.