To reconcile ABA provider, NPI, location, and setting fields before submission, identify every role the request and payer route require. Map the billing entity, rendering professional, supervisor, ordering or referring professional when applicable, group, facility, service location, and submitter to the correct identifier and evidence. Verify licensure, competence, enrollment, contract, roster, effective dates, modality, and location separately.

Define Tomas's provider, NPI, location, and setting field reconciliation

Tomas starts from the actual proposed service configuration rather than copying the last request. He names the person or entity for each role and checks which fields the current payer form and portal expect. The provider-and-location crosswalk preserves sources, versions, decision authority, corrections, validation, and open work.

Build the fields Tomas needs

The record captures configuration ID, member and product, service and setting, modality, billing entity and Type 2 NPI, rendering professional and Type 1 NPI, supervisor, ordering or referring role when required, group, facility, physical and service address, taxonomy, licensure and scope, enrollment, contract, roster, effective dates, authorization field, claim-field mapping, source, conflict, owner, and validation. Structured fields support comparison and routing. Narrative retains clinical reasoning, context, client perspective, uncertainty, disagreement, corrections, and source limits.

Apply Tomas's workflow

Tomas compares the clinical plan, staff assignment, credentialing evidence, payer roster, form, portal, and expected claim configuration. He treats an NPI as identity, then checks every separate authority and participation state. A proposed provider change reopens the affected clinical, payer, schedule, and packet fields.

Identity never substitutes for authority

An issued NPI does not prove licensure, competence, enrollment, contracting, roster acceptance, authorization, or payment. A group address also may differ from the actual service location. Tomas preserves each state and its effective date rather than compressing them into a single provider-approved flag.

Separate related operational and payer states

Tomas tracks source collection, clinical authorship, administrative assembly, review, approval, release, transmission, receipt, request-for-information, payer decision, authorization, service, claim, adjudication, and payment separately. Each state has its own evidence, owner, timestamp, and reopening rule.

Protect urgent care and current information

Tomas routes imminent danger, medical emergencies, suspected pain, urgent clinical needs, suspected abuse or neglect, privacy incidents, and other time-sensitive duties through current authorized paths. Packet work never delays emergency, medical, protective, or mandated action. Material new information reopens the affected review.

Work through Tomas's fictional example

Tomas locks 32 fictional provider configurations. Twenty-five reconcile role, NPI, location, setting, modality, enrollment, roster, and effective dates. Two use a group NPI for an individual field, one lists an old clinic, one lacks a rendering roster date, one confuses telehealth with place of service, and two await payer confirmation. Five repair. Two remain held. This synthetic example tests workflow and denominator logic. It supplies no payer, clinical, privacy, legal, coverage, claim, or payment conclusion for a real person.

Calculate Tomas's measures honestly

Initial configuration readiness is 25 of 32, or 78.1%. Thirty configurations validate, or 93.8%. People, entities, identifiers, addresses, settings, authority states, and effective dates retain separate units.

Address the main provider, NPI, location, and setting field reconciliation risk

A correct-looking identifier can route a request to the wrong provider record or location while hiding missing licensure, enrollment, participation, or clinical fit.

Test Tomas's artifact against hard cases

Tomas tests new clinician, new group, moved clinic, home service, school service, telehealth, temporary location, individual NPI, group NPI, and roster lag. Every test records the starting state, expected safeguard, observed result, affected artifact, correction owner, retest, and final disposition.

Run Tomas's release test

Tomas asks a credentialing reviewer to trace one proposed encounter from clinician and service location through payer participation, authorization fields, and the expected claim roles. The reviewer must explain which evidence establishes identity, authority, and effective participation. A match on name or NPI alone fails. The same trace is repeated for every materially different location, modality, group, or provider configuration.

Close the packet state with open work visible

Tomas confirms the source set, qualified authorship, client access, validation evidence, released version, and unresolved work. The provider, NPI, location, and setting field reconciliation remains draft until every named reviewer finishes. Open items retain an owner, age, safeguard, deadline, and escalation route.

Keep clinical content with qualified authors

Tomas uses the CASP ABA Practice Guidelines Version 3.0 public summary for high-level autism-treatment context and the current BACB Ethics Code for covered behavior analysts' competence, client involvement, consent and assent when applicable, assessment, intervention, documentation, and billing duties. Neither source creates a payer rule or authorizes administrative staff or software to make clinical decisions.

Keep prior authorization separate from payment

The HealthCare.gov preauthorization glossary explains that preauthorization may be required and is not a promise that a plan will cover cost. Tomas keeps benefit, network, prior authorization, clinical recommendation, service release, clean-claim status, adjudication, and payment as separate states.

Use the CMS process rule within its scope

The CMS-0057-F fact sheet applies to named impacted payer classes and medical items and services excluding drugs. Its process rules and API requirements do not supply one national ABA packet, code map, source hierarchy, or medical-necessity standard. Tomas verifies the member's actual payer, product, contract, route, and effective date.

Use payer forms as scoped examples

The current Nevada Medicaid FA-11E form and instructions illustrate program-specific fields, evidence, timing, signatures, and attachments. The Texas Medicaid prior-authorization chapter says authorization is not a guarantee of payment and supplies its own field and claim relationships. Tomas never generalizes either program to another payer.

Separate codes and identifiers from authority

The CMS coding overview explains that a code's existence does not determine coverage or payment. The CMS NPI fact sheet says an NPI identifies a provider and does not validate licensure or credentialing, enroll the provider, or guarantee payment. Tomas verifies every separate clinical, legal, payer, and operational gate.

Control information by purpose

Tomas applies HHS treatment, payment, and healthcare-operations guidance and minimum-necessary guidance only after confirming entity, relationship, purpose, and applicable exception. Packet access, exports, reviews, test cases, and transmissions use authorized information and retain source attribution.

Preserve access and communication

The DOJ Title III overview addresses equal opportunity, effective communication, and reasonable modifications within its scope. The ASHA AAC Practice Portal says AAC users should always have access to their communication tools or devices. Tomas keeps communication and accessibility evidence intact without treating an access need as poor fit.

Use compliance guidance as orientation

Tomas uses the OIG General Compliance Program Guidance as voluntary, nonbinding orientation for risk assessment, auditing, reporting, incentives, and corrective action. Current payer, program, record, coding, privacy, contract, and professional sources govern the packet.

Related resources

Sources