Healthy Blue North Carolina Medicaid RB-BHT Coverage: A Family Guide

Distinguish Healthy Blue from Care Together

The Healthy Blue provider home identifies both the Standard Plan and Healthy Blue Care Together, North Carolina's Children and Families Specialty Plan. Confirm the member's exact card, product, member-services number, eligibility dates, and service period. This page addresses the Standard Plan. A Care Together case needs that product's own manual, contacts, and authorization route.

Apply the statewide RB-BHT framework

Use NC Medicaid's live Policy 8F page for RB-BHT clinical coverage and provider requirements. Healthy Blue administers the Standard Plan request, while the qualified clinician remains responsible for the individual recommendation. Store the state policy, plan requirement, and member-specific decision as three separate evidence layers.

Date every 2026 policy change

The August 5, 2026 state update replaces a July notice and points to the amended policy. It separates certification grace periods, enrollment timing, and shorter authorization duration at reauthorization. Record the specific rule, affected provider or episode, effective date, and transition evidence. Do not apply one August date to every field.

Give each Healthy Blue state an owner

Track Standard Plan enrollment, provider NC Medicaid status, Healthy Blue participation or approved out-of-network route, clinical recommendation, Availity intake, authorization, communication access, real staffing, calendar release, delivered care, claim acceptance, adjudication, and family cost separately. A lookup result can inform one state without completing any of the others.

Build Luca's product-specific record

Luca's evidence index contains the Healthy Blue product, service dates, order, assessment, diagnosis support, priorities, bilingual communication, AAC access, treatment plan, model, settings, service lines, units, provider entity, rendering staff, submission, receipt, correspondence, and result. Keep any Care Together document out of the Standard Plan packet unless Healthy Blue confirms its relevance.

Preserve the right decision-maker

Luca and the family explain goals, preferences, language, access, health, and schedule. The qualified clinician authors clinical findings and recommendations. Healthy Blue decides its coverage and authorization. The provider verifies enrollment, participation, staff qualifications, supervision, documentation, and schedule. Availity and administrative staff transmit evidence; they do not make the clinical recommendation.

Use the current Healthy Blue lookup carefully

The plan's prior-authorization lookup tool requires North Carolina and the Medicaid line of business. It warns that the result does not show all noncovered services or establish the member's benefit coverage. Save the selected market, product, code, result date, provider and site, then verify eligibility and benefits before using the result.

Submit through the named Availity workflow

Healthy Blue's prior-authorization page directs providers to the Interactive Care Reviewer through Availity for requests and status checks. Record the service line, request type, provider, setting, attachments, transaction ID, submission time, receipt, case number, and every plan message. A portal draft or inquiry is not proof that a request was received.

Resolve a lookup and case-status conflict

Suppose Healthy Blue's public lookup shows authorization while Availity has no matching case. Preserve the exact lookup inputs, result date, member and provider identifiers, site, service dates, screenshot, transaction log, and call reference. Ask which requirement and receipt control. Send a focused supplement or resubmission only after the plan explains how the original date will be treated.

Use current member materials

Healthy Blue's member-materials page links the current handbook and member resources. Pair that handbook with the member's actual notice. A general benefit description cannot reveal Luca's approved services, amount, setting, provider, dates, limitations, or appeal clock. Keep the plan document version with the decision it informed.

Match authorization details to the schedule

Check every planned Healthy Blue visit against member, product, provider group, rendering professional, location, modality, code, modifier, units, frequency, authorization dates, and conditions. Maintain separate queues for approved, pending, partially approved, and adverse lines. Release a visit only when the matching decision, qualified staff, supervision, access supports, and safe setting are present.

Turn directory failures into an access request

For each Healthy Blue provider, record the Standard Plan product, geography, setting, age and clinical scope, Spanish-language and AAC support, contact date, intake status, wait, and barrier. When no network provider can supply a necessary covered service, 42 CFR 438.206 requires the MCO to arrange timely out-of-network coverage. Ask Healthy Blue to identify the route in writing.

Keep bilingual communication and AAC available

Luca communicates in Spanish and English and uses a speech-generating device. ASHA's AAC guidance says users should always have access to their tools or devices. Confirm interpretation, translated materials, device positioning, charging, backup mode, wait time, assent, dissent, and how the plan fits school, health care, rest, transport, and a science club.

Use Healthy Blue's current appeal instructions

The plan's grievances and appeals page describes a 60-day member appeal period, standard and expedited review, Fair Hearing, and continuation steps. These are different from a complaint or provider claim dispute. 42 CFR 438.402 supplies the federal managed-care framework. Follow the issued notice and prove filing.

Act quickly when existing care may stop

Healthy Blue's member instructions describe a shorter request period to keep previously authorized care during an appeal. 42 CFR 438.420 governs the federal conditions and possible repayment. Ask whether an appeal and continuation request require distinct actions, which service lines may continue, and what receipt proves timeliness.

Follow Luca's fictional request

Luca is six and communicates in Spanish and English with a speech-generating device. The family locks 13 gates for clinic services and a neighborhood science club: active Medicaid eligibility, Healthy Blue member record, state benefit, current Policy 8F version, provider-group configuration, qualified clinical packet, primary communication access, request-submission proof, family schedule fit, exact Standard Plan product confirmation, science-club setting, bilingual backup staff, and Availity receipt. Nine are complete. The Standard Plan confirmation, science-club setting, bilingual backup staff, and Availity receipt remain open. Readiness is 9 of 13, or 69.2%. Each remaining gate answers a different operational question.

Prepare a focused Healthy Blue call

Ask which Healthy Blue product is active, which Policy 8F version and code result apply, whether Availity received each attachment, what the decision covers, which provider can meet the access needs, and what appeal or continuation deadline is next. If a representative mentions Care Together, verify the product before allowing that answer into the record.

Ask the Ombudsman for unresolved access help

The NC Medicaid Ombudsman supports members who cannot resolve a health-plan or provider issue. Bring the Healthy Blue product evidence, Availity transaction, access log, notice, contact history, requested remedy, and due date. Ombudsman involvement does not pause an appeal deadline, so preserve both tracks.

Prove Healthy Blue Standard Plan before opening Availity

Healthy Blue now administers both a Standard Plan and Healthy Blue Care Together, the Children and Families Specialty Plan. Use Luca's card, eligibility response, member-services number, county, and service dates to establish the exact product. Keep the product name in every lookup, provider search, request, receipt, and notice. A provider contracted with one Healthy Blue product is not automatically confirmed for the other, and a Care Together transition rule should not enter this Standard Plan record.

Create separate rows for Standard Plan enrollment, NC Medicaid provider status, Healthy Blue participation or approved out-of-network route, Policy 8F clinical recommendation, Availity intake, line-level authorization, clinic and science-club settings, Spanish and English access, AAC, actual capacity, delivery, claims, and payment. Luca's 9-of-13 readiness record remains open for exact product confirmation, the community setting, bilingual backup staff, and the Availity receipt.

Build a product-specific Healthy Blue packet

Index Luca's member and Standard Plan data, diagnosis evidence, assessment, priorities, Spanish and English communication, speech-generating device, provider and rendering staff, treatment model, goals and baselines, service lines, weekly total, dates, clinic and science-club settings, supervision, coordination, transition plan, signatures, Policy 8F version, and lookup result. For a request above 16 total weekly RB-BHT hours, record the three-month reauthorization rule at the next review while preserving the existing authorization duration already issued.

The Healthy Blue prior-authorization page directs requests and status checks through Interactive Care Reviewer in Availity. Save the selected product, request type, provider, locations, lines, attachment inventory, transaction ID, submission time, receipt, case number, and messages. If the lookup and Availity case status conflict, freeze both results and ask which requirement and receipt govern before sending a duplicate packet.

Translate Healthy Blue's decision into bilingual access

Put each requested line in a table with its service, quantity, frequency, dates, provider, rendering arrangement, location, modality, conditions, and written outcome. Mark partial approval, denial, and pending items precisely. A lookup answer and authorization cannot establish current eligibility, network capacity, an appointment, language access, delivery, claim acceptance, or payment.

For Luca, verify clinic and science-club care independently. Confirm community-site permission, qualified bilingual staff or an appropriate language-access plan, a charged device and backup mode, safe transport, and a schedule compatible with school, sleep, health care, family life, and Luca's preferences. At day 10, reconcile authorized, scheduled, and delivered care and record interpreter, AAC, staffing, or setting failures. At day 30, review Luca's experience, outcomes, family effort, claims, and approaching reauthorization tasks.

Keep Healthy Blue access and member remedies product-specific

Log every Standard Plan provider contacted, site, age and clinical fit, Spanish-language and AAC support, requested setting, date, intake result, wait, and barrier. When no participating option can deliver a necessary covered service, send the evidence to Healthy Blue and ask for a named provider or written out-of-network arrangement. If the response references Care Together, return to the product evidence and request the Standard Plan owner.

For a delay, reduction, partial approval, or denial, preserve the full Standard Plan notice and identify disputed lines, reason, effective date, evidence route, appeal method, expedited review, and remedy. Prove receipt and keep grievances or provider payment disputes separate. When current services may decrease or stop, act on any shorter continued-benefit instruction while preparing the clinical and access evidence. Ombudsman help can proceed in parallel.

Limits and next Healthy Blue Standard Plan actions

This guide cannot determine Luca's product, eligibility, clinical need, network status, authorization, payment, or appeal result. Healthy Blue may change portals, provider records, lookup content, and product instructions. The current Standard Plan record and member-specific determination control this case.

Next, verify the exact Healthy Blue product, confirm provider and science-club setting, reconcile Policy 8F and the line-specific lookup, submit through Availity, and save the receipt. Compare the result with all 13 gates, assign the four open states, and schedule day-10, day-30, product-change, and reauthorization reviews.