The lapsed attestation: how payers see a stale profile

What "expired" status actually shows a payer

When your CAQH attestation window closes without action, your profile's status changes to expired inside CAQH's system, and that's the exact status every payer pulling your data sees — not a private flag visible only to you 1Ref 1CAQH (2026).CAQH.That CAQH ProView's self-reported profile carries an attestation status every payer pulling it sees identically.. The underlying information in your profile doesn't disappear; what changes is that CAQH is no longer certifying it as current, which is the whole point of periodic attestation.

That distinction matters for how you think about the problem: nothing about your license, your work history, or your malpractice disclosures is being questioned by an expired status. It's a procedural flag, not a substantive one — the data is unverified-as-current, not disputed or wrong.

Still, payers treat that flag seriously precisely because their own credentialing and recredentialing obligations depend on working from current information. A payer's system generally won't advance a decision built on a profile CAQH itself won't vouch for, regardless of how accurate the underlying content actually is.

What freezes, and what doesn't

A lapsed attestation does not remove you from a network you're already actively participating in — you don't lose in-network status the moment your profile expires. What it freezes is anything still moving through a decision process: a new credentialing application in review, a recredentialing cycle underway, or a new payer's initial evaluation of your profile.

That said, your specific payer's own contract and policy control what a prolonged lapse eventually triggers for your network status, and that's worth checking directly rather than assuming CAQH's flag alone determines it. Aetna, for example, publishes its own provider policies on its portal 2Ref 2Aetna (2026).Aetna Clinical Policy Bulletins.Named as an example of a payer's own provider portal where a solo practice checks that specific payer's policy on network status, rather than assuming a lapse is treated identically everywhere. — the kind of thing worth reading for your specific plans rather than assuming every payer treats an expired profile identically at every stage.

The practical read: a lapse measured in days is a paperwork problem. A lapse measured in months, left unaddressed through multiple missed attestation cycles, starts to look like something a payer's contract language may actually address.

Recovering: what re-attesting actually fixes

Clearing an expired status takes exactly one action: log back into your CAQH profile 3Ref 3CAQH (2026).CAQH Provider Data Portal Sign In.Where a provider logs back in to review the profile and re-attest, clearing the expired status., review every section for accuracy, and re-attest. There's no separate reinstatement request, no fee, and no waiting period imposed by CAQH itself — the expired flag clears the moment you complete that review and certification.

Any credentialing or recredentialing decision that was frozen while your profile sat expired resumes automatically once the status clears — nothing about the underlying application needs to be resubmitted. The one thing that doesn't reverse is time: whatever delay accumulated while the profile was expired is added to your overall timeline regardless of how promptly you fix it afterward.

If your attestation lapsed because something genuinely changed — a new malpractice disclosure, a new practice location, an updated license — use the re-attestation as the moment to update that content too, rather than re-certifying stale information just to clear the flag.

Why the fix isn't instant everywhere

Re-attesting clears the expired status inside CAQH immediately, but each payer that pulls your profile does so on its own refresh schedule, not in real time. A payer that last synced your data the week before you re-attested may not reflect the current status again until its next scheduled pull, which can leave you technically current in CAQH while a specific payer's system still shows the old, expired snapshot.

If a specific application or recredentialing decision is genuinely time-sensitive, the reliable move is contacting that payer directly to confirm they've registered the re-attestation, rather than assuming the sync happened the moment you logged out of ProView. UnitedHealthcare, for instance, publishes its own provider policies directly on its portal 4Ref 4UnitedHealthcare (2026).UnitedHealthcare Policies and Protocols.Named as an example of a payer's own published policy portal to check directly when a re-attestation update needs confirming with that specific payer. — the kind of primary source worth checking for exactly how a specific payer's systems handle an update, rather than assuming every payer behaves identically. Most delays here are measured in days, not weeks, but a deadline riding on an exact date is not the moment to discover which end of that range you landed on.

Directory and network-status ripple effects

Data flowing from ProView to the provider directory a payer publishes runs on its own pipeline and schedule, separate from the attestation flag itself, so a directory listing built from a profile that was expired for a stretch can carry outdated information even after you've fixed the underlying CAQH record. A patient searching that directory during the gap sees whatever the directory last pulled, not your current, corrected status.

Check your directory listing with any payer where accuracy matters most to your referral volume once you've re-attested — don't assume the correction propagated on its own. This is also a good moment to confirm your authorization settings are current for every payer you're contracted with, since caqh authorization determines who's even pulling your corrected data in the first place.

Preventing the next lapse

A single lapse is a recoverable, unremarkable event, not a pattern — but a habit of running attestation to the very edge of the deadline, or past it, is worth fixing structurally rather than repeatedly firefighting. The 120-day attestation clock resets on your own attestation date, not a shared calendar, which is exactly why a personal reminder system beats relying on memory.

Set your own reminder ahead of the required date rather than relying solely on CAQH's automated emails, and treat attestation integrity as an ongoing habit rather than a once-a-cycle scramble — the discipline that prevents the next lapse is exactly the same discipline this whole process is checking for in the first place.

A calendar entry set the day you attest, dated well before the next deadline, costs a few minutes and outlasts any inbox filter or forwarding rule that might otherwise swallow a reminder email unnoticed.