CAQH Checklist for ABA Providers and Practices

A CAQH checklist for ABA providers should begin with a verified clinician source file, secure account ownership, payer-access decisions, complete profile fields, current supporting documents, and clinician attestation. After the profile is complete, track the payer's credentialing decision, contract, enrollment, roster, locations, effective date, directory, and payment connections as separate work. Recheck the profile whenever information changes and before each required re-attestation.

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

CAQH now operates publicly as DataSpring, powered by CAQH. Its portal remains the CAQH Provider Data Portal. DataSpring explains that clinicians and group administrators can enter provider information and share it with authorized plans. Use the portal's current labels and requirements because fields, state questions, documents, and workflows can change.

This guide helps ABA practices organize the work. It does not replace the live portal, a payer application, state licensure rules, an executed agreement, or qualified credentialing advice.

Know what CAQH completion proves

Milestone	What it establishes	Evidence to save	What remains open
Profile data complete	Required portal fields have values	Portal status and dated review	Document, authorization, and attestation tasks
Documents complete	Required uploads meet current portal checks	Document status, version, and expiration	Accuracy of all data and provider attestation
Attested	The clinician completed the portal attestation for the submitted data	Attestation date and status	Payer retrieval, review, and decision
Organization authorized	The designated organization may access permitted profile data under portal terms	Authorization setting and date	Payer credentialing and participation decision
Payer credentialing approved	The named payer approved the stated clinician or entity step	Written payer decision	Contract, enrollment, roster, and effective date as applicable
Configuration active	Entity, clinician, product, service, and location relationships are loaded	Written effective status	Authorization and operating connections
Payment-ready	Claim, EFT, ERA, portal, and directory routes are validated	Test and reconciliation evidence	Ongoing maintenance

CMS states in its NPI fact sheet that an NPI does not establish licensure or credentialing, enroll a provider in a health plan, or guarantee payment. CAQH profile completion works the same way: it supplies organized provider data to authorized users, while the payer controls its own decision and implementation.

Assign roles before opening the profile

Use named accountability:

Role	Responsibility
Clinician and account owner	Reviews personal and professional data, controls personal account access, answers disclosures, approves organizations, and completes attestation
Credentialing coordinator	Collects source records, prepares data, uploads permitted materials, monitors tasks, follows payer applications, and logs evidence
Practice administrator	Maintains shared practice, location, insurance, and contact data through approved group tools where available
Clinical credential reviewer	Verifies license, BACB certification, role, scope, and practice details through primary sources
Privacy or security owner	Approves access, storage, identity verification, offboarding, and incident procedures
Operations leader	Owns payer configuration readiness and keeps scheduling behind the effective-status gate

Keep credentials individual. Use current portal administrator and group features rather than shared passwords. Remove access promptly when a worker's duties change or employment ends. Store sensitive identity data only in approved systems with role-based access.

Build one verified source file per clinician

Gather information before data entry. Mark every item with its source, verified date, reviewer, and expiration or refresh date.

Identity and identifiers

legal name and any professional names used
date and place of birth, citizenship or work-status fields when the portal requires them
home, mailing, professional, and credentialing-contact addresses in their correct fields
personal and professional contact information
Social Security number or other sensitive identifier through the portal's secure route
CAQH Provider ID, if already assigned
Type 1 NPI and taxonomy records from NPPES
provider type and specialties supported by current records

Compare name, address, and taxonomy values across the portal, NPPES, license, BACB record, malpractice policy, CV, W-9 or group record, and payer application. Document any intentional difference.

Education, training, and work history

schools, degrees, attendance and graduation dates
internships, supervised experience, residencies, or other portal-requested training
current employer, previous employment, and start and end dates
explanations for gaps when requested by the portal or payer
curriculum vitae matching the structured entries

Use complete month and year values when required. Avoid copying an old CV into several systems without reconciliation. A one-month mismatch can produce an information request.

Licensure, certification, and professional status

every active or historical state license requested by the portal
license number, type, state, issue date, expiration date, and status
BACB certification information relevant to the clinician's role
board actions, restrictions, or other disclosures answered by the clinician
controlled-substance or hospital fields only when they apply to the person and portal question

Verify BACB status through the BACB certification registry and state licenses through the issuing board. Preserve the result and date. A BACB credential and a state license are distinct records.

Professional liability and claims history

carrier, policy number, coverage type, limits, effective and expiration dates
named insured and covered professional relationship
certificate or declaration in the current portal-accepted format
claims history and explanations where requested

Check that the clinician, practice, and coverage period match the actual arrangement. Route policy interpretation to the broker, carrier, or counsel.

Practice locations and affiliations

each physical and service location
mailing, billing, credentialing, and primary-practice designations
phone, fax, hours, accessibility, languages, telehealth, and accepting-patient information when requested
group legal name, TIN, Type 2 NPI, and payer relationship where applicable
start date, provider availability, and location status
hospital or facility affiliations only when applicable

Home and community services can still require an administrative or service-area record. Follow the portal and payer's current definitions instead of inventing a location.

Complete disclosures with the clinician

Disclosure questions may cover professional actions, criminal history, sanctions, malpractice matters, health-related limitations, loss of privileges, or other state and payer topics. The clinician should read and answer every question accurately. Obtain qualified legal guidance when a question, event, sealing rule, or explanation creates uncertainty.

Use an explanation log:

Field	Record
Question and version	Exact current portal question or reference
Clinician response	Answer selected by the clinician
Event details	Date, jurisdiction, matter, outcome, and present status
Supporting record	Board order, court record, carrier letter, or other evidence
Reviewer	Clinician plus counsel or credentialing reviewer when appropriate
Submitted version	Final explanation and submission date

The HHS OIG maintains the List of Excluded Individuals and Entities. Build exclusion screening around applicable federal, state, payer, and organizational requirements, and retain the search inputs and results.

Upload documents by requirement, version, and expiration

The live portal should decide the required file and format. Common preparation categories include:

professional liability insurance evidence
state license evidence where requested
curriculum vitae or work-history support
state-specific authorization, release, or disclosure forms
certification, training, or specialty support where applicable
explanation documents tied to a disclosure

Create a document register with owner, portal slot, filename, document date, signature date, expiration, upload date, acceptance status, and rejection reason. Use readable source files. Check all pages, signatures, names, dates, and policy numbers before upload.

DataSpring's current Provider Data Portal resources direct clinicians to complete the profile, upload documents, attest, and authorize organizations. The portal identifies missing or expired items. A coordinator should review the live task list after every upload rather than rely on an old checklist.

Authorize the correct organizations

The provider decides which participating organizations may access the profile under the portal's current authorization options. Match each choice to the payer and application route. Record:

payer or organization name as shown in the portal
product, state, and application reference in the internal tracker
authorization choice and date
clinician approval
payer confirmation that it can retrieve the profile when available

The current CAQH Provider Data Portal terms describe transmission of user-submitted data to designated recipients and recurring attestation. Review the current terms and privacy information before authorizing access. Removing an organization later cannot retract data it already received.

Review and attest

Run a two-person review before clinician attestation:

The coordinator compares structured fields with the controlled source file.
The clinician reviews identity, history, disclosures, authorization choices, and uploaded records.
Both resolve portal errors and warnings.
The clinician reads the current attestation language and completes the required action.
The coordinator saves the status, date, and evidence without storing prohibited sensitive material outside approved systems.

DataSpring says clinicians generally confirm their profile on a recurring cycle and currently identifies a 120-day attestation period, with a different period for Illinois providers in its resource FAQ. Portal tasks, state rules, and payer requests can create earlier work. Update the profile when information changes instead of waiting for the next cycle.

Use group tools without erasing clinician ownership

DataSpring's current groups credentialing page describes centralized management of group and provider information. Group features and permissions may vary by product and payer relationship.

For each shared value, identify:

the authoritative practice source
which clinicians and states receive it
which user entered or exported it
whether the clinician reviewed or accepted it
the date it reached the individual profile
whether a later clinician edit created a discrepancy

Shared locations, insurance, and credentialing contacts can save time. They can also spread one wrong address or expired policy across many profiles. Run a post-distribution audit on a sample and reconcile the full roster when the source changes.

Follow the payer after CAQH is complete

Track one row per payer-product, entity, clinician, location, and service configuration:

Payer requested or accepted the CAQH route.
Correct organization is authorized.
Payer retrieved or acknowledged the profile.
Information requests are resolved.
Credentialing decision is written.
Contract is executed when required.
Group, clinician, product, service, and location records are loaded.
Written effective date is confirmed.
Directory, portal, authorization, EDI, EFT, and ERA connections are ready.
First eligible claim and remittance receive accountable review.

Aetna's joining-the-network FAQ illustrates that credentialing and contracting can be separate payer steps. Apply that example only to the named payer and route. Each ABA payer may use different terminology and sequence.

CMS's Prior Authorization API FAQ covers specified interoperability requirements for impacted payers. Those requirements do not convert a completed CAQH profile into provider participation or a member authorization.

Synthetic example: one address change, three systems

Willow Path ABA is fictional. A BCBA moves from Location A to Location B. The practice updates its controlled provider record and verifies the effective date. The credentialing coordinator changes the appropriate CAQH practice-location entry. The clinician reviews the profile and re-attests. The coordinator then follows each payer's separate location and roster process.

Payer R acknowledges the CAQH update but still shows Location A in its directory. Payer S requires a location-add form outside CAQH. Payer T confirms Location B for the commercial product while its managed Medicaid product remains pending. Willow Path releases scheduling by active configuration and keeps all three payer records open until written status, directory, authorization, and claim routes agree.

The example shows why one portal update belongs inside a wider change-control process.