Patient Experience
Before your appointment, you build your visit notes in your own words — no jargon required.
- Your most-logged symptoms are filled in from your daily check-ins before you start
- Add how long it's been going on, and any patterns or triggers
- Set your main goal for the visit — what you need to leave with
- Every field is optional; skip the lot and go straight to recording if you're already in the waiting room
- Already had the visit? Go straight to typing it up instead
Under the Hood
Input
Structured form captures symptoms, duration, patterns, and visit goal — every field optional. The draft is written to AsyncStorage as the patient types, so it survives closing the app, and it is flushed on the way out rather than lost to a half-finished keystroke.
Check-In Context
The daily symptom log lives on the device. Its ranked 30-day counts are pulled into the symptoms field automatically and travel with the summarization call, so the summary reflects how the patient has actually been between visits. The free-text note on a check-in is never sent.
Privacy
Intake notes are device-only until the patient continues to recording — the point at which the appointment record is created. Nothing is uploaded before it.
Notes stay on device until recording
Patient Experience
One tap starts the recording. You focus on your doctor. The app handles the rest — you don't have to take notes or try to remember everything that was said.
- Recording can't start until you tick both boxes: you told the room, and everyone agreed
- Your pre-appointment notes stay on screen to help you stay on track
- Audio captured locally while you have the conversation
- Pause and resume freely — the easy way to capture only the instructions at the end
- One tap to stop and trigger processing
Under the Hood
Audio Capture
On-device microphone via expo-audio, written to a single .m4a in app-private storage. Buffered locally, never streamed, no real-time transcription. Pause and resume write into the same file, so the paused stretches are simply not in it.
Resumable Pipeline
Transcribe → summarize → save runs inline; there is no background queue. Each finished step is checkpointed, so switching apps mid-flight resumes instead of losing the take, and an interruption — an incoming call seizing the microphone — surfaces as a recoverable state with the audio intact.
Text Fallback
If consent isn't given or the room isn't right for recording, the patient writes a free-text recap instead. It enters the same pipeline at the summarization step — no audio, no transcript, identical output.
Ephemeral Storage
The audio file is temporary by design: app-private storage, protected by the device's own disk encryption, uploaded once over TLS. It is deleted only after the summary is safely saved, so a failed step can always be retried from the file still on disk.
Audio deleted once the summary is saved
Patient Experience
Within minutes of leaving, you have a clean, readable summary of your appointment — what was said, what was decided, and what comes next.
- What you reported to your doctor, drawn from your notes and your daily check-ins
- What your doctor said and decided
- Any diagnoses, referrals, or explanations given
- Medications, tests, or follow-ups ordered
- Something off? Fix it yourself — the summary is yours to edit
- Text too small to read comfortably? One setting resizes every screen in the app
Rootwise doesn’t diagnose or treat. Summaries are AI-generated and can be incomplete, so confirm anything important with your care team.
Under the Hood
Transcription
Audio uploads to a Supabase Edge Function, which proxies it to OpenAI whisper-1 and returns the text. The API key is a server-side secret and never ships inside the app. No diarization — the transcript comes back as unlabeled speech.
Summarization
A second Edge Function calls Claude claude-sonnet-4-6 with the transcript plus the pre-visit context — the intake notes and the ranked 30-day check-in counts. One call returns structured JSON: what you reported, what your doctor said, diagnoses, and action items.
Patient Correction
Every generated section is editable. Patient edits overwrite the stored summary and are what the action-item extraction runs against — the human stays the final authority on the record.
Storage & Deletion
The transcript is never written to disk on either side — it exists in memory for the length of the pipeline. The audio is deleted once the summary saves. The summary itself is stored in the patient's own account, with row-level security scoping every row to their user id.
Audio and transcript are never retained
Patient Experience
Every action item from your appointment is extracted and color-coded by priority. Tap “Add to calendar” on any item to put it on the calendar you already use.
- Red — immediate (labs, urgent referrals)
- Yellow — schedule when ready
- Green — positive updates
- Blue — medications to start or change
- Lavender — other follow-ups
Under the Hood
Action Extraction
Action items come out of the same summarization call, not a second pass. Classified immediate, non-urgent, update, medication, or other, with whatever timeframe the clinician mentioned kept as free text.
Calendar Hand-Off
Tapping an item opens the OS event editor prefilled through expo-calendar, with a date parsed from that free-text timeframe. Nothing is written silently — so no calendar permission is ever requested, and an AI-guessed date can be corrected before it is saved. Android today; iOS pending its own EventKit pass.
Portability
Summary rendered to PDF and handed to the OS share sheet — save to Files, print, or email it. Once a copy leaves this way it is the patient's outright, and beyond anything Rootwise can recall or delete.
Final State
Appointments and summaries persist in the patient's account, encrypted at rest, until they delete them — deleting an appointment removes its summary too. The day-to-day check-in entries stay on the device; only the ranked counts travel, and only as context for a summary. Audio and transcripts are not retained anywhere.
Patient owns and controls all output data
