Web-based EMRKanTime spans home health, hospice, palliative, pediatric, and private duty lines
Auth-gated episodesMedicare Advantage and Medicaid managed care episodes depend on timely authorization
Long-episode checksFlexbone rechecks coverage on a cadence so a mid-episode change is caught early

Flexbone works alongside KanTime by operating in the same web interface your staff use, not through a native or certified integration. KanTime is a web-based EMR for home health, hospice, palliative, pediatric, and private duty agencies, carrying intake, scheduling, documentation, and billing in one platform. Flexbone browser agents verify whether a patient holds Original Medicare, a Medicare Advantage plan, or Medicaid, submit and track episode authorizations and reauthorizations, and recheck coverage across long episodes so a payer change surfaces before it becomes a denial. Voice agents answer referral calls from discharge planners and physician offices and place the visit confirmation calls a schedule depends on.

Which teams use KanTime?

KanTime is a web-based enterprise EMR for home-based care. Agencies run home health, hospice, palliative, pediatric, and private duty lines on it, from intake and scheduling through clinical documentation and billing, and it connects to the electronic visit verification systems many state Medicaid programs require. The administrative pressure differs by line but rhymes: referrals arrive from hospitals and physicians and need fast turnaround, Medicare Advantage and Medicaid managed care plans authorize a set span of visits that has to be renewed, pediatric and private duty cases run for months or years while coverage shifts underneath them, and the schedule only bills when visits are confirmed and staffed. Flexbone works alongside KanTime by operating in the same web interface your intake, authorization, and billing teams already use, with no native or certified integration; the browser agents drive the screens a person would.

Complimentary Flexbone audit

Get an outside read on your KanTime 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.

Book an audit →

Which front and back office workflows does Flexbone run?

Voice agents answer referral calls from discharge planners, case managers, and physician offices, collect the patient, payer, and order detail, and write the intake into KanTime. Browser agents verify coverage with a 270/271 check at referral and before the start of care, then recheck it on a cadence through long episodes, because a Medicaid lapse or a switch to a Medicare Advantage plan changes what the episode needs. They submit the initial authorization, track it to a decision, and submit reauthorization before approved visits run out, and voice agents confirm upcoming visits with patients so the schedule holds. Denials route by CARC and RARC code from the 835. The detail lives on the eligibility verification, prior authorization, and denials management pages, and the EHR integrations page covers the browser-agent mechanism.

How does Flexbone work alongside KanTime?

Flexbone is forward-deployed. We build the agents around your KanTime configuration, care lines, referral sources, and payer mix, validate them against your real intake and authorization patterns, and keep refining them. Because the agents operate in the KanTime web interface rather than through an integration, a processed referral, a verified benefit, or a tracked authorization lands in the record your team already works, and anything outside the agent scope is handed to a person with context. For most agencies the rollout starts with referral intake and eligibility monitoring, since those protect admissions and catch coverage changes early, then adds authorization tracking and denial follow-up. We operate under HIPAA with a business associate agreement.

How Does a Flexbone Deployment Work?

Every deployment starts from the work as your team does it today, not from a product demo. The steps below are the same whether the first agent answers phones, checks eligibility, or files incoming documents.

  1. Audit first, then automate. We listen to a sample of your calls and read the work queues, then agree with your team on which work to automate first. The audit is complimentary.
  2. Forward-deployed engineers map your SOPs. An engineer sits with the staff who do the work and turns your written and unwritten rules into agent logic.
  3. Agents act on your rules, and exceptions go to a person. Each step follows logic built from your SOPs. A case outside those rules, or one the agent is not confident about, goes to your team with the context attached.
  4. Every action leaves a record. A check in a web application saves a screenshot, a call saves a transcript, and results are written back where your team already looks.
  5. Start with one or two agents on the systems you already run. The agents work in your EHR, practice management system, phone system, and the web applications your staff use, as they are configured today, so nothing is migrated or rebuilt.
  6. The same team stays after go-live. We monitor results, tune the agents as payers and workflows change, and add agents as new work is found.

The engagement model is described in more detail in forward-deployed engineering for healthcare contact centers.