Symptom journal
Timestamped notes, severity, and body context give users a consistent way to capture what changed and when.
Back to Work
Personal product2025 · Solo buildHealth Tech
Cassandra
A private health-organisation workspace for documenting symptoms, keeping medical records together, tracking medications, and preparing a concise brief before an appointment.
Next.js 14TypeScriptTailwind CSSSupabaseReact-PDFStripe
Overview
The Challenge
Health information is often split between memory, phone notes, downloaded files, and different provider portals. When an appointment is short, reconstructing a useful timeline becomes another task for the patient.
Cassandra explores a patient-owned workspace for that preparation. Notes, symptoms, medications, providers, and files can be organised around a timeline and assembled into a deliberate pre-visit summary.
The product does not diagnose, interpret results, or replace clinical advice. Its job is narrower: help a person organise their own record, decide what to share, and arrive with the questions and context they do not want to forget.
Timeline
Ongoing Development
Role
Full-Stack Developer & Designer
Tech Stack
- • Next.js 14 + App Router
- • TypeScript
- • Tailwind CSS
- • Supabase (Auth, DB, Storage)
- • React-PDF
- • Stripe Integration
Classification
General Wellness Application (EU MDR Recital 19 & FDA compliant)
Brand Story
Why the name Cassandra
In Greek mythology, Cassandra was a Trojan priestess cursed by Apollo to always speak the truth, but never be believed. She warned Troy about the wooden horse. No one listened. The city fell.
The name became a prompt for the product question: how can software help a person communicate a long, messy history without pretending to decide what that history means?
Organise the record. Keep interpretation with the clinician.
Cassandra keeps notes, measurements, documents, and questions under the user's control. The output is a clearer brief for a conversation, not evidence of a diagnosis.
User-owned record
The person decides what to capture, retain, and share.
Deliberate sharing
A brief or document leaves the workspace only through an explicit action.
No diagnosis layer
The product organises information without making a clinical interpretation.
Care model
Turn a scattered health history into a usable record.
Cassandra is organized around the moments when personal context usually gets lost: noticing a change, preparing to explain it, finding the right document, and following a care routine over time.
Appointment brief
Relevant observations become a concise visit summary so the conversation can start with context instead of recall under pressure.
Document wallet
Prescriptions, results, insurance details, and provider records stay grouped around the person—not scattered by file type.
Care routine
Medication, condition, and measurement tracking supports continuity between appointments without presenting itself as diagnosis.
Health Journal
Document Your Journey
Visual body mapping, symptom tracking, and pattern recognition — all designed to help you spot connections your doctor might miss.
Appointment Prep Pack
Turn notes into a visit brief
Select the relevant dates, edit the questions and priorities, and export a concise document for the appointment or for deliberate pre-visit sharing.
01
Select Date Range
Choose which journal entries to include in your summary.
02
Review & Customize
Add questions, highlight priorities, edit what to share.
03
Generate PDF
Create a clean, professional document ready to share.
04
Share Pre-Visit
Email, fax, or create a shareable link for your doctor.
Document Management
Records grouped around the person
Store prescriptions, lab results, insurance cards, and medical records securely. Track medications and manage your healthcare providers.
Supporting context
Weather, patterns, and dashboard views
Environmental context and dashboard views help organise observations. They are presented as context, not as medical conclusions.
Product boundaries
Helpful organization without pretending to be a clinician.
The system separates private records, presentation logic, and educational content. Its role is to help users organize and communicate their own information—not interpret it or make medical decisions.
Authenticated workspace
Private journals and documents live behind account ownership rules rather than public or shared-by-default records.
Structured health records
Notes, measurements, providers, and files use separate models that can be assembled into a timeline when needed.
No diagnostic layer
The interface summarizes user-entered facts and trusted resources without generating diagnoses or treatment advice.
User-led sharing
Appointment briefs are created for deliberate sharing, keeping the user in control of what leaves the workspace.
Product boundaries
Useful without pretending to be a clinician
The product is designed around four promises that can be inspected in the interface rather than broad claims about health outcomes.
Private
Personal workspace
Explicit
Sharing actions
No diagnosis
Organisation only
Portable
Visit brief export
Engineering Challenges
Design choices behind the build
Document wallet for medical files
Solution · Encrypted upload + tag system (lab result, prescription, scan, insurance) with quick-access cards for upcoming appointments. Files live in Supabase storage with row-level security so each user only sees their own.
Outcome · Files remain grouped and searchable instead of depending on the original download location.
Appointment-prep notes
Solution · Pre-visit note template (current symptoms, questions, recent changes, medications taken) that the patient fills out and can show on-screen during the visit.
Outcome · The user can keep the questions and recent changes they want to discuss in one deliberate view.
Sharing controls without exposing everything
Solution · Per-document share links with expiry + access logs (who viewed, when). No "share my whole account" button — granularity by design.
Outcome · A user can share a specific item for a limited period without exposing the rest of the workspace.
Building a consumer health product?
I take on senior contract work for consumer products where sensitive data, sharing controls, and audit trails matter.