Leave-behind

Close the referral-to-reimbursement loop in home-health rehab.

Ritepath is an always-on agentic workbench that captures a referral, triages it, matches a therapist, books and confirms the visit, tracks functional outcomes, and hands a clean insurance packet to billing — without the spreadsheets and Slack pings you fall back on today.

Ritepath
One-pager

The problem

Home-health operations are a parallel-paths patchwork.

Where referrals fall through today
A new referral arrives by fax or portal; a coordinator hand-keys it; triage happens in someone's head; the matcher lives in a spreadsheet; visits get booked through a third-party scheduling tool and confirmed by phone; outcomes are logged on paper; and the claims packet is assembled by hand at the end of the month. Every step is a context switch — and every context switch is a place for a referral to drop.

What Ritepath does

One connected thread from referral to reimbursement.

Ritepath sits on top of your existing EHR, intake channels, scheduling tool, and billing system. Each agent reads from the same patient record and writes back the same record — so triage, match, book, confirm, track, and bill always agree on what happened.

Triage with auditable reasoning

AI-signed urgency + fit assessments; the model rationale is persisted alongside the referral so a coordinator never has to guess why a case was prioritized.

Explainable therapist matching

Top-three ranked fits for every referral, with per-axis reasoning across specialty, geography, language, and weekly availability.

Booking + visit confirmation

Schedule writes become confirmations; visit notes write back to the same patient record the matcher already read.

Outcomes + claims-ready packets

Functional scores (AM-PAC, ODI, generic) flow into a single visit narrative; the insurance packet is assembled at discharge, not assembled by hand.

How it works

Three agents, one patient record.

  1. Intake → triage → match

    A new referral triggers triage; the matcher reads the same patient record and returns ranked fits with the per-axis reasons a coordinator can defend.

  2. Schedule → visit notes → outcomes

    Confirmed visits write notes back to the patient record; the outcomes tracker sees the same visit data and surfaces functional scores as they land.

  3. Discharge → claims packet

    The Insurance assembler reads the visit narrative, the outcomes score, and the confirming provider data and emits a packet your billing system already accepts.

What you can expect

Fewer dropped referrals, faster matches, cleaner packets.

Ritepath replaces parallel tools with one connected thread. Coordinators spend less time chasing information and more time running exceptions; therapists see matched, prioritized caseloads; billing receives packets that already agree with the source visit data.

Email the team

Inside the leave-behind PDF

The download captures the same one-pager in a portable handout — title, subtitle, and the connective summary a clinical lead can forward to operations and finance.

Company

Ritepath

Prepared for

Founder / clinical lead

Sent by the Ritepath team · ritepath@polsia.app