270/271 eligibility transactions explained for clinics
A 270/271 eligibility transaction is the electronic way to ask a health plan whether a patient is covered. Your system sends a 270 inquiry, and the plan sends back a 271 response with the patient’s coverage status and some benefit details. If something is wrong with the request, you get an error instead. A 271 is a snapshot, not a promise that the plan will pay.
What are the 270 and 271?
They are a pair of X12 healthcare transactions. The 270 is the inquiry and the 271 is the answer. CMS lists the ASC X12N 270/271 version 5010 as the HIPAA standard for eligibility and benefit verification. CMS gives a standard compliance date of January 1, 2012, and an operating rules compliance date of January 1, 2013.
Most staff never see the raw file. Your practice management system or clearinghouse builds the 270 from the patient record and shows the 271 as a coverage screen. Knowing what is inside helps when a result looks wrong.
What does a 270 request need?
Each payer has its own rules, so use that payer’s companion guide. Medicare is a useful example because CMS publishes its rules. In the CMS HETS 270/271 companion guide (February 2022 revision), Medicare matches a patient using these fields:
- Medicare Beneficiary Identifier (MBI)
- Last name
- First name
- Date of birth
The guide accepts three combinations: all four fields, or the MBI and last name with either the first name or the date of birth. It also says not to send extra fields to try to force a match. It rejects requests that carry a middle name or initial, or a gender code, and it accepts only the MBI as the ID, not the older HICN.
Other payers will ask for other fields. The lesson holds for all of them: send exactly what the payer’s guide asks for, spelled the way the card spells it.
What comes back in a 271?
For Medicare, the guide says the response is not meant to show every benefit. It addresses whether eligibility is active or inactive and the patient’s financial responsibility for Part A and Part B. The basic response includes:
- Patient demographics
- Part A and Part B entitlement, including any inactive periods
- Status of the service types you asked about
- Medicare Secondary Payer, Medicare Advantage and Part D plan information, where it applies
- Plan-level financial information, such as deductibles
You can ask about specific services by sending service type codes in the 270. The guide notes that if you ask about a service it does not support, or about none, it answers as though you asked for the general code 30. Commercial plans vary a lot in how much detail they return, so test your top payers and compare the result with the portal.
A 271 is not a guarantee of payment. The CMS guide says a 271 should not be interpreted as a guarantee of payment. Payment remains subject to the plan’s terms, limits, conditions and exclusions and to the member’s eligibility when services are given. It also says the data is accurate only at the time of the transaction. For a longer walk-through of when to re-check, see our insurance verification checklist.
How fast should a response come back?
The CAQH CORE operating rules set speed targets. CORE 156 (version 1.1.0, March 2011) says a real-time 271, or a 999 error, must come back within 20 seconds. It counts the rule as met when 90 percent of responses meet that time over a calendar month. It also recommends 4 seconds or less per hop.
CMS lists the eligibility operating rules as federally mandated, with a compliance date of January 1, 2013. The measure is in aggregate, so any single check can still be slow. This is the March 2011 text, so check CAQH CORE for the current version if timing matters in a contract.
Medicare’s system has its own limit. The CMS guide says it returns an error code 42 if it cannot process a single transaction in under 60 seconds.
What do the error codes mean?
A transaction can fail at two levels. A 999 acknowledgment says the file was rejected because it broke the format or the payer’s implementation rules. An AAA segment inside a 271 says the file was read but the inquiry could not be answered. The CMS guide lists these examples:
| Code | Meaning in the CMS guide | What to do |
|---|---|---|
| AAA 72 | Invalid member ID (for example a HICN instead of an MBI) | Re-check the ID on the card |
| AAA 62 | Requested date is outside the allowed span | Use a date within four years back and four months ahead |
| AAA 42 | System unable to respond | Try again, then use a portal or phone |
| AAA 04 | More than one beneficiary on one request | Send one patient per request |
Other payers use their own code lists, so read their guides. A “not found” result can come from a typo, a swapped name or a wrong birth date, so confirm those first.
What should a front desk do with this?
- Keep the 271 or a screenshot with the visit record.
- Treat “not found” as a prompt to check the data, not as proof of no coverage.
- Re-run the check close to the visit date.
- Follow up by portal or phone for things the 271 did not answer, such as prior authorization.
Where Clinicrung fits
Clinicrung is being built to run routine eligibility checks, flag the ones that return errors or mismatches, and pass those to your staff to resolve. Join the waitlist.
This article is general information, not legal or billing advice. Payer rules differ, so check each payer’s current companion guide and your own compliance advisor.