Payer strategy · Aetna
An Aetna application is one step in a longer participation record.
The useful workflow separates the participation request, network-need review, credentialing, contracting, written effective-date evidence, demographic maintenance, and the billing configuration used by the practice.
Photo: Unsplash
Operational distinctions · reviewed 2026-08-09
What to separate in a Aetna workflow
Aetna's current provider documentation and the executed participation agreement control the process. Network need, provider type, state law, specialty, product, and location can change the available path.
Start with the right provider category
Medical, behavioral-health, facility, ancillary, dental, and pharmacy requests do not share one universal intake.
CAQH supports credentialing
A complete and authorized CAQH profile supports review; it does not itself establish an Aetna contract or effective date.
Credentialing and contracting differ
Credential review occurs before participation, while the agreement and written completion evidence define the actual network relationship.
Maintenance needs its own evidence
Locations, provider rosters, demographic details, and tax relationships should be stated precisely and retained with confirmation.
Evidence worth retaining
A durable record makes it possible to see which checkpoint is complete and which one still blocks payment.
Submission
The request type, submitted provider/entity, locations, product or specialty, confirmation, and submission date.
Developments
Requests for missing information, responses, CAQH authorization, and credentialing correspondence.
Participation
Executed agreement, written effective date, product and location scope, and any network limitations.
Billing readiness
Payer system loading, rendering/group relationships, EDI, ERA/EFT, and a controlled first-claim check.
Public guidance boundary
This page is not the payer's contract or an enrollment determination.
The payer's current documentation, written correspondence, executed agreement, and applicable law control. OneSource does not guarantee network need, acceptance, processing time, effective date, reimbursement, or continued availability of a workflow.
- Verify the source immediately before use
- Keep provider, entity, product, and location scope explicit
- Do not submit claims until the practice has the required participation and billing evidence
Review a Aetna workflow in practice context.
Include provider type, state, product, locations, current evidence, and the first unresolved transaction. Do not send PHI.