What this page covers
Flexbone deploys AI voice and browser agents inside Homecare Homebase for referral intake, eligibility checks, episode authorization, and scheduling calls. HCHB structures agency work as tasks and workflows, so the agents pick up the same queues your intake, authorization, and billing teams work, and write results back to the patient record.
Homecare Homebase and the agencies it serves
Homecare Homebase, often shortened to HCHB, is a cloud platform for home health and hospice agencies and part of the Hearst Health network. Field clinicians document visits in its PointCare mobile app, while intake, scheduling, authorization, and billing teams work queues in the back office. Many of the largest home-based care agencies in the United States run on it. Flexbone operates in that same HCHB web interface. A processed referral, a verified benefit, or a tracked authorization is written to the record your team already works.
Get an outside read on your homecare homebase workflow
In 30 minutes we map your current volume, the payers and systems involved, where staff time goes, and the highest-ROI calls and follow-ups Flexbone can take off your team first, scoped to the work you actually run.
Front and back office workflows Flexbone runs
Flexbone answers referral calls, confirms demographics, insurance, and orders, and writes the referral into HCHB. It verifies eligibility and benefits, submits and tracks episode authorizations, follows unsigned physician orders, and places patient scheduling and confirmation calls. It also works denials and claim status. The referral management and post-acute prior authorization pages cover the workflow detail.
Can AI process referral intake calls for an HCHB agency?
Yes. Voice agents answer referral calls from hospital discharge planners, case managers, and physician offices at any hour. They collect the patient, payer, and order detail intake needs, and write it into the HCHB intake workflow. Browser agents monitor referral portals where hospital systems use them. A complete referral processed quickly shortens the time from referral to start of care, which referral sources weigh when they choose an agency.
Can AI verify eligibility and benefits inside Homecare Homebase?
Yes. Flexbone verifies coverage at referral and again before the start of care. The agents identify whether the patient holds Original Medicare, a Medicare Advantage plan, or Medicaid, because that decides whether an authorization gates the episode. They read payer responses and portals, call the plan when benefit detail is missing, and write the verified result to HCHB. A coverage change mid-episode is caught by the recheck rather than by a denied claim.
How does AI handle authorization and reauthorization in HCHB?
Original Medicare does not require prior authorization for home health, outside the Review Choice Demonstration states. Many Medicare Advantage and Medicaid managed care plans do. Flexbone submits the initial authorization with the order and assessment detail from HCHB, tracks it to a decision, and submits reauthorization before the approved visits run out. Authorization numbers and spans are written back to HCHB. The agents also track unsigned physician orders and place the follow-up calls, because Medicare home health claims need signed orders before billing. The post-acute EHR authorization page has the per-system detail.
Have Flexbone run your homecare homebase for a week
A live pilot on real cases with a shared dashboard showing which calls Flexbone placed and resolved, which results were written back to your system, and the hours your team got back.
How Flexbone deploys inside Homecare Homebase
Flexbone is forward-deployed: we build the agents around your HCHB configuration, referral sources, and payer mix, then validate them against your real intake and authorization patterns. The agents work in the HCHB web interface the way staff do, and use interfaces where the vendor offers them. Flexbone is not a certified Homecare Homebase integration and not an HCHB partner. Results write back to HCHB, and exceptions go to staff with context. We scope the rollout to the workflows that protect the most billable episodes first.