How integrations surface
Illustrates ingest points without vendor lock-in language. Local-primary; auth boundary; no PHI in public.
Labs PDF ingest
Surface
Drop a lab PDF → structured panel JSON (demo shows resulting
blood-work.json trends).Privacy
Parsed artifacts stay in private/demo storage; public site stays case-agnostic.
Imaging pack
Surface
Report text + optional viewer assets. This LITE demo uses labeled placeholders only.
Privacy
Clinical pixels never belong on public routes; demo PNGs are watermarked fiction.
Wearables stub
Surface
OAuth / export drop zone stub — sleep and recovery scores for context, not diagnosis.
Privacy
Tokens and exports stay behind auth; revoke and local delete are first-class.
Calendar / email stubs
Surface
Upcoming consult holds and “records to attach” reminders — no automated clinical messaging in demo.
Auth boundary
Public education ≠ private hub. Demo under
/demo is readable for sales walkthroughs with a persistent FICTION banner.
Education only — not medical advice.
This demo shows how a private Stage 0 workspace can organize labs, imaging descriptions,
care-team contacts, and multiple critical-thinking paths. Clinicians advise; people decide.
All names, IDs, dates of service, and values here are invented for demonstration.