Denials, Appeals and Continuity of Care requires a disciplined response to a payer action while the treating team protects the client's safety and access. The practice should identify the exact denied request, reason, authority, notice date, deadline, review level, and continuation rules; preserve the clinician's recommendation; build an evidence-linked response; communicate options clearly; and make a qualified care plan for any funding gap. Every payer, product, program, and jurisdiction can differ.

Capture the payer action before interpreting it

Obtain the complete notice and related request record. Record the member, payer, product, request, service, units, dates, decision, reason, clinical criteria or source cited, notice date, receipt date, appeal route, deadline, continuation terms, reviewer type, reference number, and available external review.

Separate an authorization denial from a claim rejection, adjudicated claim denial, network issue, benefit exclusion, missing-information request, credentialing problem, and payment delay. Each follows a different route. A portal label may be operational evidence rather than the complete notice.

HealthCare.gov's internal appeal guidance provides general marketplace orientation. The actual levels, filing window, expedited criteria, forms, representative rules, and external review depend on the plan and governing source. Use the notice and current plan materials for the case.

Classify the reason using source evidence

Build a denial analysis with four columns: payer statement, source cited, packet evidence, and unresolved issue. Common categories include missing or late information, eligibility, network or provider status, authorization dates, service or code mismatch, medical-necessity disagreement, treatment-plan inconsistency, noncovered service, and duplicate or wrong route.

Do not accept a short denial label as the full rationale. Request the applicable criteria and record whether they were included. Compare the exact request that the payer reviewed with the practice's final submitted packet. A transmission or version error can create a different dispute from a clinical disagreement.

The treating clinician decides whether the recommendation remains appropriate after reviewing current evidence. A payer's coverage action does not rewrite the clinical record. If the clinician changes a recommendation, document the new evidence and clinical reasoning rather than editing the plan solely to match the denial.

Preserve every deadline and continuity question

Create a deadline ledger as soon as the notice arrives. Include internal appeal, peer review, external review, continuation request, records submission, representative appointment, hearing, and any plan-specific step. Record the source, event that starts the clock, calendar or business-day rule, due time, owner, submission route, and confirmation.

Medicaid managed-care rules illustrate why scope matters. 42 CFR 438.400 defines terms and applicability for Subpart F. Section 438.402 addresses grievance and appeal systems, section 438.404 addresses adverse-benefit-determination notices, and section 438.408 addresses resolution and notice. Apply these only to covered programs and entities, with state implementation and the member's actual notice verified.

Continuing services during an appeal can require a timely request and other conditions. Never infer continuation from a prior authorization or a verbal call. Confirm the exact rule in writing and tell the family which fact remains uncertain.

Build the appeal around the disputed point

The ABA authorization appeal packet guide organizes the cover request, notice, authorization history, relevant plan criteria, treating-clinician rationale, current assessment and plan, goal data, service record, risk and transition information, and supporting documents.

Create an issue-to-evidence map. For each denial reason, state:

  1. the payer's claim or criterion
  2. the practice's relevant evidence and exact location
  3. current clinical interpretation by the qualified author
  4. source-based response
  5. requested remedy

Keep the packet concise enough to review. Include complete supporting records when required, while using an index and descriptive labels. Explain conflicts rather than hiding them. If evidence is missing, state the gap and the plan to resolve it.

Use attributable, current data. Report raw counts, mature denominators, observation periods, treatment integrity, generalization, maintenance, adverse effects, client experience, and barriers. A graph without definitions or plan version may add pages without answering the denial.

Prepare peer-to-peer review as a clinical exchange

The peer-to-peer review guide starts with route verification. Confirm whether the discussion is an informal reconsideration, appeal step, medical-director review, or another process; who may participate; what it can change; deadlines; records available; and whether a written decision follows.

The treating or reviewing clinician should know the referral question, current functional impact, assessment basis, requested services, intensity rationale, progress, barriers, risks, alternatives, transition plan, and exact points in dispute. Bring a short evidence map and the current source documents.

Record participants, roles, date, time, questions, evidence discussed, representations made, additional information requested, deadline, decision if given, and follow-up. A call note is operational evidence. Seek the formal written action and preserve the appeal route.

Plan continuity through a qualified care review

Coverage loss may reduce funded access, while the clinical recommendation remains a separate record. A qualified clinician should review current safety, health, communication, active goals, likely effects of interruption, alternatives, available resources, and the client's and family's priorities.

Possible actions can include seeking continuation through the verified appeal route, correcting and resubmitting when allowed, using another covered provider or service, modifying schedule based on a new clinical decision, arranging transition, using available private-pay options with clear financial consent, or pausing safely. The correct option depends on authority, resources, evidence, and family choice.

The current BACB Ethics Code addresses service interruptions, discontinuation, transition, communication, documentation, and client involvement for covered behavior analysts. Plan dates, responsible parties, referrals, record transfer, emergency information, and follow-up. Funding pressure does not permit abandonment or a misleading promise that care can continue unchanged.

Communicate without promising the outcome

Give the client or representative an accessible explanation of what was requested, what the payer decided, what the notice says, deadlines, options, who is responsible, expected next contact, and immediate care plan. Distinguish confirmed facts from interpretation. Provide translated, large-print, AAC-compatible, or other effective communication as needed.

Avoid saying that an appeal “will overturn” a decision or that authorization guarantees payment. State what the team can control: accurate evidence, timely filing, clinical review, follow-up, and transparent continuity planning.

A short family-facing timeline can reduce confusion. List the notice date, filing deadline, expected payer step, current service status, continuity decision, next update, and contact person. Update the timeline after every formal action and provide it through the family's usable communication channel. When a deadline or service state remains unverified, label it as pending and show who is obtaining written confirmation.

Measure the process with mature cohorts

Track notices received and classified by deadline, appeals filed on time divided by appeals due, payer requests answered by deadline, decisions by appeal level, days in each state, continuation questions resolved, and continuity tasks completed. Keep open cases visible by age and next action.

Review recurring denial reasons by payer, product, service, source version, template, and workflow. Correct the source process that created preventable errors while preserving the right to challenge disputed criteria.

Try Finni AI Prior Auths. Confirm current supported payers, source coverage, privacy terms, human review, and validation evidence during diligence.

Related resources

Sources