Work

Delivery model A clinical reference that does not depend on the ward network

Problem: Nurses need fast, trustworthy reference material at the point of care: not a prescribing calculator, and not something that dies without network.
Approach: Shipped an offline-first reference app with structured domain modules and a PWA/web surface alongside native.
Outcome: A clinical utility with typed domain modules and automated checks for lint, types, unit, and web end-to-end tests.

Read case study Demo

Product flow Clinical inputs become a plan patients can follow

Problem: Patients need a clear, timed prep plan. Generic PDF instructions create confusion, missed steps, and avoidable exam delays.
Approach: Built a bilingual (PT/EN) client-side wizard that personalizes diet, medication, and exam-day guidance from clinical inputs, with local persistence, deep links, and calendar export (.ics + VALARM).
Outcome: A responsive prep experience with testable core logic, end-to-end coverage, and CLS-conscious UI. Not in use yet: we plan to present it to CUF.

Read case study Demo

Curation loop Draft shortlists become human-reviewed digests

Problem: Patients, families, and clinicians need trustworthy, readable updates on cystic kidney disease: not raw paper feeds, and never advice disguised as curation.
Approach: Built an Eleventy publication with dual framing per item (summary plus clinical note), PubMed-assisted draft shortlists, and a strict human-publish gate with an explicit not-medical-advice boundary.
Outcome: A live digest with timeline, guides, glossary, and search, backed by content validation, unit and end-to-end tests, Lighthouse checks, and CI on every push.

Read case study Demo

Case studies