Coverage Discovery
Coverage discovery answers a different question from eligibility verification. Verification asks whether known coverage is active. Discovery asks whether coverage exists that you have no record of.
Where the Missed Coverage Comes From
A patient presents without a card. An emergency encounter is registered with partial demographics. A member ID is transcribed wrong and re-entry does not fix it. A patient believes they are uninsured and is not. Each of these produces a self-pay determination that is often incorrect.
The write-off that follows looks like bad debt in the AR. It is frequently a data problem wearing a financial costume.
Discovery Versus Verification
Why a 270 Doesn't Answer It
An eligibility inquiry (the X12 270) requires you to know which payer to ask. Discovery is the case where you don't. That is why the two workflows are not interchangeable and why routing an unresolvable AAA 72 (the 271 response code for a subscriber or insured not found) back into eligibility retry logic produces nothing. Discovery searches across payers rather than querying one, and it uses demographics rather than a member identifier as the entry point.
Discovery Without Accumulation
Coverage discovery is a search across payer sources. Performing it does not require building a repository of the demographics searched or the results returned. PNT performs discovery in transit. Payer source coverage and match characteristics are maintained per engagement.
Frequently Asked Questions
What is coverage discovery?
Coverage discovery identifies active insurance coverage a provider has no record of, using demographics rather than a member identifier as the entry point. It applies after self-pay registration, emergency encounters with incomplete demographics, or an AAA 72 rejection that correction could not resolve.
How is coverage discovery different from eligibility verification?
Eligibility verification confirms whether coverage already on file is active, using a 270 directed at a known payer. Discovery finds coverage you don't know about, searching across payers rather than querying one. A 270 cannot perform discovery because it requires you to already know which payer to ask.
When should you run coverage discovery?
After a self-pay registration, after an emergency or incomplete registration, and after an AAA 72 that re-inquiry with corrected demographics did not resolve. Each of these commonly produces an incorrect self-pay determination that surfaces later as bad debt.
Transactions and Industries
270/271 Eligibility & Benefits Verification
Reading the response correctly, so inquiry failures don't become coverage determinations.
Providers
Fewer eligibility denials, faster prior authorization and clean claims that get paid sooner.
TPAs
Accurate claims, eligibility and remittance flows across every plan you administer.
Ready to talk through your use case?
Talk to a Post-n-Track specialist about your data challenges. A direct conversation, starting with what you need.