Fictional demonstration. Not for patient use.

Intake file SB-2041

One missing item.
Draft request ready for review.

A parent finished the intake on a phone. The AI drafted the file one claim at a time, each with its source, checked by the code. The reviewer checks the source, corrects what needs it, and approves. Nothing is sent before that.

Requested items1 received of 2

Insurance card (front and back)

Not received. Required for the file.

Not received

Rule 1 · request prepared, not sent

Hi Jordan, One item is still missing: Insurance card, front and back.

Prepared by rule · awaiting reviewReview the request

Workflow rules

Three rules, run for real.

Each one fires on the sample file. You can watch it happen in the reviewer view, and read what it did in the journal.

A required item is missing

A request to the family is prepared, in the parent's language. It is not sent.

Insurance card: not received

Two sources disagree

The file waits for a reviewer. Nothing is chosen for the family.

Form: Thursday. Extracted from the recording: not Thursdays.

The reviewer approves the current version

The file moves to the next administrative step. The journal keeps the approved version.

Version 1 approved by the reviewer

About this sample

What is real here, and what is not.

What runs for real

  • Transcription (a Google model) and extraction (an Anthropic model), on request, on the sample media only.
  • Quotes, values and dates are checked on the page; audio segments against the recording. Days, hours and places are shown as extracted, next to their quote, and compared field by field with the form: to confirm, or sources disagree as extracted. The code reads no polarity from words and never writes that two sources agree.
  • The review shown first was recorded on September 20, 2026. It can be run again under a daily cap; past the cap, the recorded review stays and says so.

What stays on your device

  • The camera and microphone check records on your device and sends nothing.
  • Form progress and the reviewer's actions stay on your device, not on a server. Saving the form sends nothing.

What this sample does not do

  • No upload of your own files: the server processes only the sample media the page provides.
  • No cross-device resume, no messages sent, no accounts or roles, no multi-tenant setup.
  • No clinical assessment of any kind. The checks are administrative: received, readable, to confirm, sources disagree.

Before any patient data

  • Signed agreements with every processor, including the model providers. Storage with signed URLs and an access log. Encryption at rest and in transit. Role-based access and retention rules.
  • None of that is claimed here. This page proves the processing of one sample and a local capture.

This sample demonstrates one workflow. Your existing prototypes would inform the production scope.