All guides

Insurance eligibility verification software: a buyer checklist

Good eligibility verification software sends a standard 270 inquiry to the right payer, shows the 271 answer in plain words, flags problems for a person, and has a signed HIPAA business associate agreement with you. Beyond that, the right pick depends on your payers and your volume. This checklist gives you the questions to ask on a demo call, and why each one matters.

What does eligibility verification software actually do?

It sends the question “is this patient covered, and for what?” to a health plan and returns the answer. Under HIPAA, the adopted standard for this is the X12 270/271 version 5010 (standard effective January 1, 2012, with operating rules effective January 1, 2013, per CMS). Our guide to 270/271 transactions covers the format.

So the tools mostly differ in what they put around that exchange: which payers they reach, how they show results, and what they do when an answer is bad. Those are the things to compare.

Which payers does it reach?

This is the first question, because a tool that misses your top payers saves little time.

  • Ask for a list of payers supported for real-time checks, and which need batch or a portal.
  • Ask for your five biggest payers by name, and get the answer in writing.
  • Ask how Medicare and Medicaid checks work. Medicare data comes through CMS’s HETS system. See our guides to verifying Medicare eligibility and Medicaid verification.

How fast is it, and does it do batch and real-time?

The CAQH CORE Eligibility & Benefits Infrastructure Rule (vEB.2.0, April 2022) sets a 20-second maximum for a real-time response. It also says a batch sent by 9:00 pm Eastern on a business day must be returned by 7:00 am Eastern the next business day. Conformance means 90 percent of required responses meet those limits, measured over a calendar month.

Maximum real-time response time under the CAQH CORE rule
20secondsfrom sending the 270 to receiving a 271 or an error

Conformance is 90 percent of required responses within a calendar month.

Source caqh.org

Those limits apply to plans and clearinghouses that follow the rule, so treat them as the outer limit, not a promise from every vendor. Ask what the typical time is per payer, not the maximum. Ask whether the tool can do both modes, and read our guide to batch vs real-time checks to decide which you need.

What happens when a check fails or coverage changes?

Every system gets rejections. What matters is what your staff sees. A raw error code is not useful at the front desk. Ask to see a real rejection on screen, and check three things:

  1. Is the reason shown in plain words, such as “member ID not found”? Our guide to 271 AAA error codes lists the common ones.
  2. Can staff fix the member ID or date of birth and rerun in one step?
  3. Does the failed check go onto a work list, or does it disappear?

Then ask about re-checks. A check is a snapshot. CMS’s HETS guide says the data in a 271 response is “true and accurate only at the particular time of the transaction” and is not a guarantee of payment. So ask whether the tool can re-run checks on the day before a visit, and whether it flags a change from the last result. Our open enrollment checklist shows why this matters in January.

Does the vendor sign a business associate agreement?

HIPAA defines a business associate as a person who, on behalf of a covered entity, creates, receives, maintains or transmits protected health information for a regulated function. The definition names billing, claims processing and practice management among them. A verification vendor handling patient names, dates of birth and member IDs for you may fit that.

The rule on business associate contracts says the contract must, among other things:

  • set the permitted uses and disclosures of the information,
  • require appropriate safeguards,
  • require the vendor to report uses or disclosures the contract does not allow, including breaches of unsecured information,
  • bind any subcontractors to the same restrictions,
  • require return or destruction of the information at termination, if feasible, and
  • let you terminate if the vendor violates a material term.

Ask for the agreement before the trial, not after. A signed agreement does not make a clinic compliant by itself, so ask your compliance advisor or counsel what else you need. Our HIPAA guide for front desk staff covers the daily habits.

What will it cost, and does it fit your staff?

Prices vary widely, so get quotes in writing rather than trust a review site. Ask:

  • Is the price per check, per provider, per month, or a mix?
  • Are there setup, integration or payer enrollment fees?
  • Do batch and real-time checks cost the same?
  • What is the contract length, and what happens to your data if you leave?

To judge the savings side honestly, count your own minutes per check first. Our guide on what manual verification costs shows how to do that with the published industry averages.

Software that does not fit the workflow also gets skipped. Ask:

  • Does it connect to your practice management system or EHR, or do staff retype data?
  • Where do results land, in the patient record or in a separate screen?
  • Who owns the exceptions list each morning?
  • Can you try it with one week of real appointments before you commit?
A simple way to score a vendor
  1. 1List your top five payers
  2. 2Ask each vendor for a written yes or no
  3. 3Watch a real rejection on screen
  4. 4Get the business associate agreement
  5. 5Run one week of appointments as a trial

Illustrative scoring routine, not a standard.

Where Clinicrung fits

Clinicrung is being built to run routine eligibility checks ahead of visits and pass the rejected or inactive ones to a person for follow-up. It is not built yet, and early access is delivered in small groups, partly by hand, so ask us the same questions above. Start your free trial.

This post is general information, not legal, billing or compliance advice. Rules and software vary, so check with a qualified professional about your clinic’s obligations.