3 timingsreview happens before (prospective), during (concurrent), and after (retrospective) care
InterQual + MCGthe two criteria sets payers and providers use for medical necessity
Clock-boundconcurrent review and authorizations run against tight payer deadlines

Utilization review decides whether care meets medical-necessity criteria, and it runs against a clock across inpatient and outpatient settings. The work is repetitive: pull the clinical record, check it against criteria, submit to the payer, and handle the back-and-forth. Flexbone supports the administrative side so the nurse reviewers spend time on judgment, not phones and portals.

What are prospective, concurrent, and retrospective review?

Utilization management runs at three points. Prospective review clears care before it happens, the prior authorization for an admission or procedure. Concurrent review happens during an inpatient stay, justifying continued stay and level of care against the clock so the payer keeps authorizing days. Retrospective review handles cases reviewed after care, often tied to a denial and appeal. Each involves the same loop of gathering documentation and working the payer, across both inpatient and outpatient settings. For Medicare patients, the Two-Midnight Rule also shapes whether a stay is billed as inpatient or outpatient observation.

Complimentary Flexbone audit

Get an outside read on your utilization review 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 medical necessity criteria apply: InterQual or MCG?

Payers and providers evaluate medical necessity against standardized criteria sets, most commonly InterQual and MCG. The reviewer matches the clinical picture, ICD-10 diagnoses, severity, treatment, and response, to the applicable criteria, then submits the request with the CPT codes for the planned care. Flexbone assembles the clinical record the criteria call for and submits the authorization or concurrent-review request through the payer portal, the X12 278 transaction where the payer supports it, or phone, then tracks it. When a case does not clearly meet criteria and the payer wants to discuss it, that routes to the peer-to-peer appeals workflow.

How does Flexbone run utilization review?

Flexbone runs the administrative loop of UM: gather the documentation, submit against criteria, hold the payer line, capture the decision and authorized days, and schedule the next concurrent-review touch. Inpatient continued-stay and outpatient authorization both run as tracked queues, with results written back so case managers and billers see current authorization status. Clinical judgment stays with your reviewers; Flexbone removes the phone and portal time. The work is scoped to your settings and payers.

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.