HELIOSum needs separate states for authorization, appeal, and grievance

Keep the cases connected but distinct

The direct answer is that an authorization, an appeal of an adverse determination, and a grievance should have separate case identities even when they concern the same member and episode. The authorization record answers a scoped request under the benefit, policy, clinical evidence, and authority in effect for that review. An appeal examines a prior determination under the applicable review level and procedure. A grievance can concern service, access, communication, conduct, or another complaint that may not change the authorization decision at all.

The shared link should preserve member and episode identity, requested service, provider, line of business, product, governing contract or delegation, related decisions, notices, and evidence lineage. Each case still needs its own received time, issue, scope, governing procedure, urgency, clock, owner, reviewer qualifications, evidence cutoff, communications, disposition, reason, approval, and closure basis. A single mutable status risks closing one obligation when only another one is complete.

Freeze the determination under review

An appeal should point to the exact determination version being challenged, including requested and authorized scope, clinical facts, criteria and policy versions, reviewer, decision time, reason, and notice. Later chart information, a corrected code, a changed policy, or a subsequent authorization should not rewrite the record that triggered the appeal. The workflow can present current context while retaining what the member, provider, and reviewer received at each stage.

New information also needs an explicit disposition. The applicable procedure may require it to supplement the appeal, return the request for a new determination, create a reconsideration path, or affect a separate concurrent review. Technology can route the material and highlight differences; it should not decide which procedural effect applies without the plan's configured rules and accountable qualified judgment.

Use separate clocks and notices

Authorization, expedited review, retrospective review, appeal levels, external review, and grievance handling can operate under different clocks and notice requirements. The record should name the clock type, start event, paused or tolled periods where applicable, information requests, extensions, due time, completion event, and source of the rule. A platform-wide turnaround metric should not merge those populations unless definitions and denominators remain visible.

Communications should identify which case and decision they concern. An acknowledgement, information request, adverse-determination notice, appeal resolution, grievance response, or provider message can share facts but serve a different purpose. Delivery attempt and receipt evidence, accessible format, language, recipient, version, and correction history should remain connected to the correct case. A sent notice does not itself establish that the underlying determination or appeal was substantively correct.

Test a mixed case with a changed fact

A representative evaluation should create an authorization, issue a partial adverse determination, open an expedited appeal, record a separate service grievance, add new clinical evidence, correct one request field, and later begin concurrent review. Reviewers should see distinct owners and clocks, reproduce the original and revised evidence sets, prevent one closure from closing the others, and show exactly which notice and decision changed downstream work.

VirtualHealth's official page supports the described care-management, utilization-management, prior-authorization, routing, tracking, medical-necessity-review, grievance, appeal, and automation positioning. It does not establish a payer's benefit, policy, delegation, procedure, configured clock, reviewer authority, case decision, notice sufficiency, regulatory compliance, or outcome. Payers, delegated entities, providers, clinicians, utilization-management leaders, compliance teams, regulators, and counsel retain their respective responsibilities.

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.