All projectsIndependent product Health-Organization Tool
Cassandra
A clearer record for the next appointment.
My role
Product design & full-stack development
Built as
Independent product
Engagement
2025
Location
Solo build
Inside the productCassandra
The context
What needed to work.
Health context often lives in memory, phone notes, downloaded files, and separate provider portals. Reconstructing a useful timeline during a short appointment adds another burden.
Cassandra explores a patient-owned workspace for symptoms, documents, medications, and appointment preparation. The product organises information and helps users choose what to share; it does not diagnose or interpret clinical results.
My contribution
I designed and built the private workspace, structured health records, document wallet, and appointment-preparation flows using Next.js and Supabase.
Inside Cassandra
Explore the product.
The key workflows, up close.
01Personal observations
Capture what changed while it is still clear.
A health journal gives observations a date, severity, and body context. The aim is to help a person retain the details they want to discuss later.
CassandraPersonal observations
The thinking behind it
User-entered observations remain records, not automated medical conclusions.
02Appointment preparation
Choose the useful context before the visit.
The appointment brief starts with a date range, relevant observations, questions, and recent changes. Users review and edit what they want to communicate before exporting a concise document.
CassandraAppointment preparation
The thinking behind it
The output supports a conversation with a clinician while keeping interpretation and clinical decisions outside the application.
03Between appointments
Keep records and routines together.
Medication and condition records provide continuity between visits. Documents and provider information stay grouped around the person instead of depending on the original download location.
CassandraBetween appointments
The thinking behind it
Supabase authentication, storage, and record ownership rules support a private workspace with deliberate sharing.
04A useful overview
Bring the timeline back into view.
Dashboard and supporting context views help users review what they have recorded and decide what belongs in the next conversation.
CassandraA useful overview
The thinking behind it
Sharing is specific and user-led. A document or brief can leave the workspace without exposing the whole account.
Behind the interface
The decisions underneath.
Next.js
Supabase
Tailwind CSS
PostgreSQL
Organisation, not diagnosis
The product boundary is explicit: retain and communicate user-entered information without generating diagnoses or treatment instructions.
Granular sharing
Per-document sharing, expiry, and access context allow deliberate disclosure of one item instead of a broad account-sharing action.