Product

One operational surface for the entire intake lifecycle.

Six surfaces, one continuous record. Built upstream of the EHR so the visit hits the schedule already provider-ready.

RLS-enforced tenant isolationGrounded AI with inline citations
Product architecture
One operating layer
Patient portal
Hashed token · autosave
Intake engine
Branching templates
Document OCR
Evidence + citations
Readiness engine
Aged blockers
Provider briefing
Grounded · cited
Analytics
7 / 30 / 90 days
data in: intake · docs · referrals · payerout: briefings · ops metrics
Architecture

Six tightly-integrated surfaces. One continuous record.

Each surface is useful on its own. Together, they replace the patchwork of intake forms, faxes, briefings, and routing tools specialty clinics have been duct-taping for years.

01
Adaptive intake
Branching templates per specialty. Versioned, auditable, customizable without engineering.
02
Patient portal
Hashed-token link. Mobile autosave. Resume across devices. Zero PHI in email envelopes.
03
Document intelligence
Rosiflow AI OCR on scanned PDFs + images. Evidence chunked, cited, and confidence-gated.
04
Readiness engine
Aged blocker queue. Per-role routing. Conservative scoring — flagged when uncertain.
05
Provider briefing
Sixty-second pre-visit summary. Inline citations. Patient evidence wins on conflict.
06
Operational analytics
Intake completion, blocker aging, briefing acknowledgement across 7d / 30d / 90d.
01 · Adaptive intake

Intake forms that reshape themselves to the visit.

Templates aren't a single linear form. The branching engine asks only what's relevant for the specialty, payer, and prior context — and skips the rest. Six clinic templates are wired out of the box; clinics customize their own without engineering.

  • Specialty templates: pain management, PT, behavioral health, chronic care, VA, telehealth
  • Per-question branches, conditional sections, and required-evidence gates
  • Versioned templates with safe rollback — patients in-flight don't break
  • Audit row on every template change
Explore the adaptive intake engine
/app/settings/intake-templates
Sample
Templates
6
Pain management18
Physical therapy12
Behavioral health22
Chronic care20
VA referrals16
Telehealth14
Pain management · branching
Live
Question 1
What's the primary reason for today's visit?
Pain follow-up → MRI history branchQ2–Q9
New injury → Symptom localization branchQ2–Q11
Imaging review → Document gating branchQ2–Q5
Branching enabled
02 · Patient portal

Patients finish where they started. The clinic doesn't re-key anything.

A hashed-token link arrives in the patient's email. They start on a phone in the waiting room, pause for lunch, finish on a tablet at home. Autosave runs every 700ms. The clinic sees a live progress bar in the roster the whole time.

  • Hashed portal tokens — raw token never re-enters the database
  • Mobile-first autosave with optimistic UI
  • Resume-from-where-you-left-off across devices
  • No identifiers in email envelopes — links only
How the patient portal works
/portal/•••
Sample
9:41rosiflow.com●●●
Pain mgmt intake
Maya Thompson
Q 14 / 18
Have you had imaging in the last 6 months?
YesNoNot sure
Progress82%
Autosaved 2s ago
03 · Document intelligence

Scanned referrals become cited evidence.

The intake packet that used to live in a fax queue now flows through document OCR with evidence extraction. Each snippet keeps a page number and a confidence score so the staff and the provider know exactly where each claim came from.

  • Rosiflow AI OCR runs against scanned PDFs + images
  • Evidence is chunked, retrieved, and cited in briefings
  • Original document is always one click away from the chip
  • Confidence threshold gates evidence quality before display
Inside document intelligence
/app/documents
Sample
Documents
Maya Thompson · 4 files
OCR ready
MRI referral packet.pdf
Rosiflow AI OCR
12-page scan · evidence extracted
Insurance card (front)
PDF text
BCBS · group 4421
PT referral letter
PDF text
Dr. R. Patel · 4 pages
Symptom log
Text
14 entries since Feb
Evidence (from MRI referral packet)
conf 0.94
"Mild medial meniscal degeneration without acute tear. Trace joint effusion. Recommend conservative management with PT × 6 weeks before considering surgical consult."
page 3·Rosiflow AI OCR
04 · Readiness engine

What's stopping the visit — before the visit.

Every patient gets a readiness score with explicit blockers — intake incomplete, imaging overdue, prior auth pending — and an age bucket. Staff see what to chase. Providers see what's resolved. Owners see operational health rolled up.

  • Aged blocker queue with role-based routing
  • Conservative scoring — flagged when uncertain, not optimistic
  • Configurable thresholds per specialty
  • Bulk actions for staff workflows
Workflow routing in detail
/app/patients/maya-thompson
Sample
Readiness
Maya Thompson
Needs review
Readiness score
68%
Intake 78%
Docs 90%
Auth 35%
Open blockers · aged
Referral authorization (BCBS imaging)12d
Symptom log incomplete (3 weeks)5d
Insurance card back not uploaded2d
05 · Provider briefing

Sixty-second pre-visit briefings, every claim cited.

The briefing grounds on patient evidence and clinic SOPs separately. Patient evidence wins on conflict — no fabrications, no synthesized confidence. Inline citations link back to the original document. The model name never leaks into the UI.

  • Inline citations to [intake], [referral], [note] sources
  • Patient evidence prioritized over clinic protocol on conflict
  • Provider must acknowledge before the visit (audit row)
  • Brand-only labels — 'Rosiflow AI', never upstream model names
See the provider workspace
/app/workspace
Sample
Briefing
Pre-visit · Maya Thompson
Draft · review before clinical use
Summary
54-year-old presenting for knee-MRI follow-up. Imaging shows mild medial meniscal degeneration without acute tear [referral]. PT × 6 weeks already attempted [intake]. BCBS prior auth pending for surgical consult [referral].
Red flags
· Authorization aged 12 days
Patient evidence
  • [intake] symptom log
  • [referral] MRI report
  • [note] PT discharge
Clinic knowledge
  • AI retrievalPre-visit imaging protocol
  • PCP referral required
06 · Operational analytics

What got stuck, who's chasing it, how long it took.

Real metrics, not aspirational case studies. Intake completion, blocker aging, briefings acknowledged, staff time saved — across 7-day, 30-day, and 90-day windows. The same dashboard owners watch is the dashboard the workflow ends on.

  • Intake completion rate (avg 78% across activated clinics)
  • Blocker aging buckets — staff sees what's old, not just what's open
  • Briefing acknowledgement rate as a provider-engagement signal
  • Filterable by provider, specialty, and date window
Explore clinic analytics
/app/analytics
Sample
Analytics
Operational overview
7d30d90d
Intake completion
78%+4%
Blocked visits recovered
12this week
Staff time saved
4.2hper provider
Briefings acknowledged
94%+8%
Completion rate · last 30 days
▲ 4 pts
Continuity intelligence layer

The connective tissue across the six surfaces.

Surfaces capture work. The continuity intelligence layer keeps that work coherent across visits, sources, and clinicians — without ever displacing the EHR.

Source-aware records
Every document carries its origin — VA, community care, external specialist, lab, patient — so its weight in the briefing is honest.
Recurring concern detection
When the same symptom or unresolved item recurs across visits, it surfaces as a continuity flag instead of a fresh note.
Operational readiness states
Ready, Needs Review, Missing Records, Pending Coordination, Provider Escalation — states the clinic actually operates on.
Coordination as a typed lane
Referrals, authorizations, and records requests route by category and role with SLAs — never personal inbox work.
Briefings that admit gaps
If a record source is missing or stale, the provider briefing names it. The layer does not synthesize confidence.
Audit-grade across handoffs
Every continuity decision, routing call, and document touch is logged with the inputs that produced it.
Trust posture

The boring infrastructure your compliance team is going to ask about.

100%
tenant isolation via RLS
DB-layer enforcement
6
named roles, gated at the DB
owner / admin / provider / nurse / intake / front-desk
0
deletable rows in the audit log
append-only, no admin bypass
30 min
support impersonation TTL
read-only · matrix-blocked writes
Read the full posture:Security overview·HIPAA posture
Common questions

The questions specialty-clinic operators actually ask.

Does Rosiflow replace our EHR?
No. Rosiflow runs the operational layer between booking and visit — intake, documents, readiness, briefing, analytics. Your EHR remains the clinical system of record.
What does pilot setup actually involve?
A single working session loads your templates, referral sources, and document flow against your clinic's data. We onboard two providers + one front-desk staffer the same day. Pilot data lives behind a signed BAA + RLS isolation from day one.
How does Rosiflow handle PHI?
PHI lives behind authenticated sessions and Supabase RLS. Email envelopes carry portal links, never patient identifiers. The audit log records every state-changing operation with the actor and entity. Read the HIPAA posture page for the full conservative framing.
Is the AI grounded?
Yes. Briefings ground on patient evidence and clinic SOPs separately. Every claim is cited inline. Patient evidence wins on conflict — the briefing names gaps instead of synthesizing confidence. The customer UI shows brand-only labels; upstream model names never leak.
What integrations are available?
Available today: secure portal links via email, document uploads, audit-ready workflow history, and provider briefings. On the enterprise roadmap: structured EHR exports (CSV / FHIR) and outbound notification channels. New integrations are announced once they are live for customers.
Where can I see the product?
Pilot setup is the canonical way to see it against your own workflow. The product surfaces shown on this page are the real product — the same code your pilot will run on.
Rosiflow ships HIPAA-conscious safeguards by default — tenant isolation, append-only audit history, evidence-backed AI outputs, and operator-controlled support access. Infrastructure providers underpinning Rosiflow maintain SOC 2 Type II; Rosiflow's own attestations sit on the enterprise readiness roadmap.

Wire Rosiflow to your clinic in one working session.

Pilot setup loads your templates, referral sources, and document flow against your clinic's data. Two providers + one front-desk staffer onboarded the same day.