InterQual criteria support medical review—they do not define every payer policy

Clinical criteria and payer policy answer related but different questions

The direct operating boundary is that InterQual supplies clinical decision-support content, while an authorization decision can also depend on a payer's benefit design, plan document, medical policy, network rules, regulatory obligations, delegation arrangement, member facts, requested service, and effective date. A criterion can help a reviewer assess clinical appropriateness without becoming the complete coverage or payment rule.

The maintained record should name the criterion set and edition, care setting, clinical scenario, data elements, result, reviewer, payer policy, benefit, population, exception, and decision reason. If a local or custom policy adds, narrows, or supersedes a content path, the system should show that relationship explicitly rather than presenting one criteria result as the sole source of authority.

Content version belongs in the decision history

Optum describes an evidence-development process and regular releases for InterQual criteria. That makes content identity and effective dating essential. A reviewer should be able to reconstruct which edition, module, subset, update, and configured policy were available when the request was evaluated, including any local modification or exception path.

Buyers should test a request opened before a content update and completed afterward, a rule whose payer effective date differs from the vendor release date, and a reconsideration using additional clinical facts. The system should preserve the original review, subsequent evidence, changed content, reviewer action, reason, notice, and appeal or escalation path instead of recalculating history silently.

Review completion is not authorization completion

InterQual offerings support criteria access and medical-review workflow. Completing a criteria review can create an important clinical evidence record, but a prior-authorization workflow may still require eligibility and benefit confirmation, required documentation, delegated review, licensed-clinician escalation, plan-specific policy application, reason generation, notice, response transmission, and appeal rights.

A demonstration should include a case that meets the criterion but falls outside the benefit, a case that does not meet an initial path but requires qualified review, missing documentation, conflicting payer policy, and an expedited request. Operators should see where the content result ends, who owns the next judgment, which reason is communicated, and how the member and provider receive the decision.

The public source does not prove configured behavior or outcomes

Optum's page establishes current official positioning for InterQual content and related solutions. This review did not test a licensed criteria set, payer configuration, electronic health record integration, automation, medical-review output, response time, denial rate, clinical accuracy, or patient outcome. Product package, version, population, implementation, and customer responsibility require direct verification.

Payer, provider, utilization-management, clinical, pharmacy, interoperability, compliance, privacy, and legal owners should validate the exact workflow. InterQual content can support consistent review, but it should remain an attributable input inside a governed process rather than a label that obscures payer policy or qualified judgment.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Prior Auth Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.