Always-on · Outpatient home-health
Referral in. First visit booked. Claim out — automatically.
An operations assistant that manages every step from referral to reimbursement—so your staff can focus on patient care.
Why Ritepath is the right path
Fewer scheduling errors
Referrals land on the calendar matched by specialty, geography, and live panel load — no double-books, no empty slots parked on the wrong therapist.
Faster reimbursement
Progress notes and outcome measures flow into payer-format documentation in the same shift the visit closes, so the loop from visit to claim never sits in a Monday-morning queue.
Less administrative work
Intake, auth checks, and reminders run in the agent while your team is with a patient — your front desk stops being staffed around the backlog.
Referrals processed in under 5 minutes
From inbound fax or portal drop to a structured patient record ready for scheduling — a steady 5-minute turnaround, not a 5-hour overnight backlog.
Walk a real referral through the workbench — no signup, no email gate.
Who we serve
Built for outpatient home-health PT and OT.
Small and mid-sized agencies — typically 10 to 50 therapists — taking referrals from hospitals, physician offices, and payer care managers across multiple lines of business. The referrals keep coming; the night shift doesn’t. Denial rework is eating the margin your clinical team earned during the day.
- Faxes go unworked overnight and into Monday’s backlog
- Visits double-booked because no one owns the schedule
- Documentation is the last thing that gets done, so the claim goes out underbilled
The referral loop
The referral loop, in three steps.
Inbound fax, portal message, or phone call is parsed into a patient record. Insurance, geography, language, and clinical need land in a structured queue.
A therapist is matched on specialty, geography, language, and live panel status. The patient is confirmed; the visit goes on the calendar.
Progress notes, visit logs, and outcome measures are pulled into the payer-format documentation. Reviewed before submission, not after the denial.
Compliance you can audit
Built around the controls HIPAA expects.
Patient data was the first thing the architecture was asked to protect — not an afterthought bolted on at SOC 2 time. The controls below are the ones your privacy officer and security team will want to see in the review.
Every request between clinician and platform, and between platform and your EHR or payer endpoints, runs over TLS 1.3. HSTS is preload-listed and per-request CSP nonces are enforced at the edge so nothing unexpected renders in the patient chart.
PHI fields are stored encrypted in the platform database; keys are rotated through our managed KMS. Backups are encrypted with a separate key lineage so a backup credential alone cannot read a record.
Every signed-in user is scoped to their own agency and role. Clinicians see only the patients assigned to them; agency admins manage membership, not raw PHI; cross-agency queries are structurally impossible from the data layer up.
Short-lived JWTs with refresh rotation, idle-timeout, same-site strict cookies, and failed-login lockout keep sessions tight. Every read or write of a patient record produces an immutable, tamper-evident audit entry — actor, action, record, timestamp, source IP — exportable for OCR or regulator review.
Questions for our security team? ritepath@polsia.app — we route security questionnaires, BAA requests, and penetration-test summaries to the same inbox.
Try a real referral
Walk a referral through the workbench.
At /triageyou’ll submit a referral through the intake form, watch the agent pick a therapist from your panel, and see the loop close in the workbench — the same loop that runs for every patient your agency sees.
HIPAA-ready · on top of your EHR · no install required.