The Healthfirst New York ABA authorization policy October 2026 update is scheduled for October 7. The July 7 provider notice says the policy addresses coverage criteria, authorization requirements, documentation expectations, and related guidance. As of August 20, the effective date is still in the future. Providers should obtain the actual criteria through Provider Services, prepare a disabled configuration, and continue using current member, product, authorization, and service-date sources until the transition begins.

Keep the future policy disabled

The public notice supplies an effective date and a high-level scope, but it does not publish the detailed medical-necessity criteria. Record the notice, checked date, future effective date, affected plan or product as confirmed, owner, open questions, and next recheck. Avoid applying an October rule to August or September requests, schedules, clinical recommendations, or claims. Preserve the current source used for every live case.

Obtain the criteria through the named route

Healthfirst tells providers to call Provider Services for the updated criteria. Record the representative, date and time, reference number, product, document title, revision or effective date, delivery method, and any confidentiality or use restriction. Ask whether the criteria differ by line of business, initial versus concurrent review, code, age, setting, provider, or authorization period. A verbal summary alone is weak production evidence.

Assign one criteria custodian to receive, store, version, and distribute the official artifact through an access-controlled location. Record who may use it, when the source was rechecked, and what supersedes it. If Provider Services gives a verbal answer to an implementation question, request written confirmation and preserve the case reference. Do not translate an undocumented call into a global production rule.

Build a structured difference register

Compare the current and October sources field by field: coverage scope, eligible members, provider qualifications, assessment, treatment plan, goals, dosage, caregiver work, progress, coordination, documentation, codes, units, request timing, concurrent review, transition, exceptions, notice, appeal, and claim implications. Mark unchanged, changed, unknown, or product-specific. Do not infer a difference from the notice's topic list.

For every changed field, add the controlling source section, affected product, responsible role, system location, test, training need, effective event, rollback plan, and approval. Unknown fields remain disabled. Preserve current and future versions together until all older authorizations, appeals, corrections, and claims have reached final disposition.

Separate clinical recommendations from coverage criteria

The treating clinician owns assessment, case-specific recommendation, risk decisions, and plan authorship within scope. Healthfirst decides coverage and authorization under the applicable product. Operations may identify criteria evidence and route questions. It should not auto-rewrite goals, dosage, or clinical rationale. If a future configuration would reduce or block a recommendation, require qualified clinical review and preserve the payer notice and review path.

Protect in-flight requests during the transition

Ask Healthfirst which source applies to requests submitted before October 7, decisions issued after it, authorizations spanning the date, concurrent reviews, modifications, appeals, and corrected claims. Lock the answer by product and evidence. Keep current and future rules active in testing with mutually exclusive service-date and request-state gates. A calendar date alone may not resolve every in-flight case.

Create a transition cohort before activation. Include each member, product, current authorization, requested service, submission state, decision due date, next concurrent review, provider, and possible rule boundary. The cohort is for status review, not automatic clinical changes. Continue using the valid current authorization and actual provider capacity until a controlling decision changes the case.

Prepare member communication and appeal routing

When the updated policy affects a request, explain the payer decision, approved service and dates, open scheduling gates, and available review route in the person's preferred language and format. Preserve interpreter and AAC access, required consent and assent processes, and the person's priorities. A provider may explain its recommendation; it should not present the payer's criteria as a clinical conclusion.

Store the complete notice, receipt date, earliest deadline, records requested, submission, delivery receipt, case number, decision, and next option. Separate a member appeal, provider payment dispute, corrected claim, and clinical peer discussion. Each route has its own owner and evidence.

Run a controlled prelaunch test

Test initial, concurrent, spanning, modified, denied, appealed, and corrected scenarios for every confirmed product. Verify criteria access, forms, portal behavior, attachments, receipt, deadline calculation, decision mapping, notice delivery, and rollback. Use synthetic or properly authorized minimum-necessary data. A successful test does not establish coverage or payment for a real member, but it can expose configuration and access failures before October 7.

Test documentation without inventing requirements

The notice says the policy includes documentation expectations, but it does not list them publicly. Test only fields supported by the actual criteria or current product source. Retain authorship, service facts, signatures when required, data, progress, plan version, requested dates and units, and source references. A general completeness checklist cannot prove compliance with an unavailable or proprietary criterion.

A fictional future-policy register

Nadia locks 20 readiness controls across policy acquisition, product scope, request timing, clinical ownership, documentation, authorization, transition, notices, systems, and training. Fourteen have a source, owner, disabled rule, test case, and recheck date. Six remain unknown because the detailed criteria or transition answers have not been obtained. Readiness is 14 of 20, or 70.0%. The figure does not establish the October policy's final content or any member outcome.

Use a two-date release checklist

For current requests, verify the member, product, live policy, provider, service dates, authorization route, documentation, receipt, and decision. For October readiness, verify the actual updated criteria, product scope, effective date, request and service-date logic, transition, codes and units, form or portal changes, training, test cases, notices, appeals, and named approval. Recheck the Healthfirst announcement and Provider Services before activation.

Related resources

Sources