End-to-end workflows
End-to-end workflows
Feature pages explain one screen. These pages explain a whole piece of work as it crosses applications - what creates the next record, which team owns each stage, and where a handoff is manual today.
Written for: Evaluators · Implementation teams · Operations and RCM leadership · New staff during onboarding
Why these pages exist
ArkCloud is several applications that share an account and a boundary. That design is good for permissions and poor for explanation: the sentence "a completed rehabilitation encounter becomes a billable charge that ArkCloud RCM claims against" belongs to neither product's documentation, and is the first thing an evaluator asks about.
Each workflow below lists its stages in order, names the application that owns each, and marks any stage that is not usable today with what it is waiting on.
The workflows
- The outpatient clinic day - one therapy patient from registration and referral through check-in, evaluation, SOAP documentation and signing to billing preparation: who does each step, which screen owns it, and what carries over automatically. Start here if you run or are evaluating an outpatient PT, OT or SLP clinic.
- Patient revenue cycle - encounter to charge to claim to remittance to patient responsibility to settlement. The core ArkCloud RCM workflow, with the payer-facing stages identified.
- Rehabilitation episode - referral to episode to treatment to documentation to charge to discharge, and where outcome scores sit.
- Patient financial journey - the same story from the patient's side: statement, portal, balance, payment or plan.
The ArkCloud RCM dashboard is where most of these workflows are picked up each morning: outstanding balances, work queues and the accounts that moved since yesterday.
/dashboard