Insurance and Front-Desk Billing

Real-Time Eligibility Checks (270/271) Explained

What an electronic 270/271 eligibility response tells your front desk, the reject codes to know, and the gaps that still need a portal or payer call.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. What a 270/271 exchange is
  2. What the 271 response contains
  3. Service type codes decide which benefit you see
  4. Where real-time checks fall short
  5. Reading the free-text messages
  6. Reject codes and how to fix them
  7. How much to automate
  8. Worked Example: checking tomorrow's schedule
  9. Measuring whether the setup works
  10. Setup questions for your vendor
  11. Frequently asked questions
  12. References
Insurance and Front-Desk Billing: Real-Time Eligibility Checks (270/271) ExplainedArticle coverINSURANCE AND FRONT-DESK BILLINGReal-Time EligibilityChecks (270/271)ExplainedAva Medical IntakeInsightsInsurance and Front-Desk Billing: Real-Time Eligibility Checks (270/271) ExplainedArticle coverINSURANCE AND FRONT-DESK BILLINGReal-Time EligibilityChecks (270/271)ExplainedAva Medical Intake

Key takeaways

  • The 270 inquiry and 271 response are the HIPAA standard way for a practice to ask a health plan about a patient's coverage.
  • A 271 reliably shows active coverage and core cost sharing; it is weaker on specialist benefits, carve-outs, visit limits and authorization rules.
  • Most rejections come from mismatched member ID, name or date of birth, and are fixed at the front desk, not by the payer.
  • Map each visit type to the right service type code, and route every incomplete response to a short exceptions queue.

What a 270/271 exchange is

When your practice management system shows a green "eligible" flag, it has usually sent a 270 eligibility inquiry and received a 271 response. Under HIPAA, the adopted standard for this transaction between providers and health plans is the ASC X12 270/271, version 5010[1]. Every covered payer must accept it, which is why most systems can check many payers from one screen.

For traditional Medicare, the equivalent service is the HIPAA Eligibility Transaction System. CMS describes it as letting users submit 270 requests over a secure connection and receive 271 responses in real time; it does not accept batch transactions and is typically available around the clock[2]. Commercial payers and clearinghouses offer both one-at-a-time and batch checks.

Behind the screen, the path is short. Your system builds the inquiry from the registration fields, sends it to a clearinghouse or straight to the payer, and the payer's system matches the member and returns a 271. If any step fails, you get a rejection, a timeout or a response with less detail than you asked for. Knowing which of the three happened tells you whether to fix the data, try again later or check the portal.

What the 271 response contains

A 271 is a structured file, not a sentence. Your system turns its segments into a benefits screen. Knowing what sits behind that screen helps staff judge how much to trust it.

Parts of a 271 response and where each one tends to fall short
Part of the responseWhat it tells youTypical gap
Subscriber and patientNames, member ID, date of birth and relationship as the plan holds themDependents sometimes listed under the subscriber only
Plan and coverage datesPlan or group name, eligibility start and end datesProduct name may be generic, hiding a narrow network
Eligibility or benefit linesActive coverage, copay, coinsurance, deductible, out-of-pocket amounts by service typeOnly a general coverage line returned for some payers
Network indicatorWhether a benefit applies in network, out of network or bothNot tied to your specific clinician
AccumulatorsDeductible and out-of-pocket amounts met to dateLag behind claims still in process
MessagesFree-text notes, such as referral needed or benefits managed by another companyInconsistent wording; easy to miss
Other payerA second plan or Medicare the payer knows aboutOften absent even when the patient has one
RejectionA reject reason when the request cannot be matched or answeredStaff may read it as "no coverage"

Service type codes decide which benefit you see

The 270 asks about a category of service. If your system sends only the general code, the payer may return only a general answer. Ask your vendor which codes you send for each visit type, and request the specific ones.

  • 30, Health Benefit Plan Coverage: the general check. Confirms the plan is active; benefits returned vary widely by payer.
  • 98, Professional (Physician) Visit, Office: the line most primary care and specialist offices need for copay and deductible.
  • 35, Dental Care: for dental practices and medical plans that include a dental benefit.
  • MH, Mental Health, and UC, Urgent Care: worth sending for behavioral health and walk-in visits, which often carry different cost sharing.

Map each visit type in your scheduler to one or two codes once, and the right inquiry goes out automatically for every booking.

Example mapping for a fictional family practice: new-patient and follow-up visits send codes 30 and 98; behavioral health visits send 30 and MH; walk-in sick visits send 30 and UC. The practice reviews the map once a year and whenever it adds a new visit type.

Where real-time checks fall short

  1. Carved-out benefits: behavioral health, imaging or physical therapy may be managed by another company, and the 271 may show only a message pointing elsewhere.
  2. Clinician-level network status: the response says whether a benefit applies in network, not whether your new associate is credentialed for that product.
  3. Visit limits and used counts: therapy and chiropractic limits are often missing or out of date.
  4. Authorization rules: few responses say reliably that a specific service needs prior approval.
  5. Accumulators: deductible met reflects processed claims only, so it can be weeks behind.
  6. Coordination of benefits: the plan may not know about a spouse's plan or new Medicare entitlement.

Treat a complete 271 as enough for a routine office visit with a known payer. Treat anything with a carve-out message, a procedure, a limit-based service or a new product as needing a portal check or a call.

Reading the free-text messages

The most useful line in a 271 is often a message rather than a field. Payers use messages to say that another company manages a benefit, that a referral is required, or that a primary care physician must be on file. Many benefit screens show these in small type at the bottom, or behind a separate tab.

  • Train staff to read every message before marking a visit verified.
  • Ask your vendor to flag any response with a message so it lands in the exceptions queue.
  • Keep a short list of the phrases your top payers use for carve-outs and referrals, with what each means for your visit types.
  • When a message names another company, record its name and phone number in the verification record.

Reject codes and how to fix them

A rejected inquiry is not a denial of coverage. It means the payer could not match or answer the request. The reject reason tells you what to fix.

Common 271 reject reasons and the usual fix
Reject reasonLikely causeFront-desk fix
72: Invalid or missing member IDTypo, old card, or prefix left offRe-key from the card image, including any alpha prefix
73: Invalid or missing subscriber nameNickname or hyphenated name entered differentlyUse the name exactly as printed on the card
58: Invalid or missing date of birthSubscriber's date used for a dependent, or the reverseConfirm whose date of birth the plan holds
75: Subscriber not foundWrong payer selected or coverage endedCheck the payer ID; ask the patient for a new card
42: Unable to respond at current timePayer system down or slowRetry later; do not mark as ineligible

How much to automate

Eligibility is already where front-desk phone time goes: 45% of practice leaders in an MGMA poll named eligibility and prior authorization as the most time-consuming phone task for staff[3]. Among practices using AI and automation to improve access, 23% pointed to registration and eligibility, after scheduling and calls[4].

Where practices using AI and automation for access are focusingMGMA Stat poll, February 2026, 177 responses
Where practices using AI and automation for access are focusingBar chart. Scheduling: 31%; Calls: 27%; Registration and eligibility: 23%; Prior authorization: 16%.SchedulingScheduling: 31%31%CallsCalls: 27%27%Registration and eligibilityRegistration and eligibility: 23%23%Prior authorizationPrior authorization: 16%16%Where practices using AI and automation for access are focusingBar chart. Scheduling: 31%; Calls: 27%; Registration and eligibility: 23%; Prior authorization: 16%.SchedulingScheduling: 31%31%CallsCalls: 27%27%Registration and eligibilityRegistration and eligibility: 23%23%Prior authorizationPrior authorization: 16%16%

Source: Medical Group Management Association (MGMA), 2026[4]

Show the data
ItemValue
Scheduling31%
Calls27%
Registration and eligibility23%
Prior authorization16%

Batch checks for the next day's schedule remove most routine work. The value is in what happens to the exceptions, so design that queue first.

Worked Example: checking tomorrow's schedule

Example: A fictional four-clinician practice runs a batch check at 6 p.m. for the next day's 96 appointments. The system returns 81 complete responses, 9 with carve-out or referral messages, 4 rejections and 2 with no response.

Example: The morning coordinator ignores the 81 complete responses and works the 15 exceptions. The 4 rejections are fixed from card images in ten minutes. The 9 messages need two portal checks and one call to a behavioral health manager. The 2 non-responses are retried at 7 a.m. and both return. By 8 a.m. every patient has a status, and check-in staff know which 3 patients to ask for a new card.

Example: The two non-responses and four rejections would have looked like coverage problems if staff had read them as "not eligible". Treating rejections as data errors and non-responses as retries kept all six patients on the schedule without a single call to the payer.

Measuring whether the setup works

Track a handful of measures for the first three months after any change, then monthly.

  • Share of appointments with a complete response by the evening before the visit.
  • Rejections per hundred checks, split by reason, to see whether registration errors are falling.
  • Exceptions per hundred checks, split by payer, to see which payers need a portal-first rule.
  • Eligibility-related denials as a share of claims, which shows whether the checks are catching real problems.

If rejections stay high, the fix is at registration: card images, name rules and date of birth checks. If exceptions stay high for one payer, change that payer's route rather than the whole setup.

Setup questions for your vendor

Eligibility features differ a lot by system, and small practices often run different systems from large ones. In 2024, 32% of solo physicians used an EHR from one of the five market-leading developers, against 90% in practices of more than 50 physicians[5]. Ask these questions whatever system you use.

  1. Confirm payer coverage

    Get the list of payers your system or clearinghouse reaches in real time and in batch, and how Medicare checks are routed.

  2. Agree the service type map

    Send specific codes for office, specialist, behavioral health and urgent visits rather than the general code alone.

  3. Choose what displays

    Show copay, coinsurance, deductible met and any payer messages on one screen, with the response date.

  4. Build the exceptions queue

    Route rejections, carve-out messages and missing benefit lines to one work list with an owner.

  5. Set re-check triggers

    Re-run checks automatically for visits booked across a month end, for the first weeks of January and when demographics change.

Once the setup is right, use the verification steps for the exceptions and record results with the verification record template.

Frequently asked questions

What is the difference between a 270 and a 271?

The 270 is the inquiry your system sends to the health plan, naming the patient and the type of service. The 271 is the plan's response, with coverage status and benefit details, or a reason it could not answer.

Is a real-time eligibility response legally binding on the payer?

No. It reflects what the plan holds on the date of the check and is not a guarantee of payment. Save it with the date, because it is still strong evidence of what you were told.

Why does the response say active but show no copay?

Your system may have sent only the general coverage code, or the payer may not return detail for that service. Ask your vendor to send a specific service type code, or check the payer portal.

Can we run eligibility checks in batch overnight?

For most commercial payers and clearinghouses, yes. For traditional Medicare, CMS's eligibility system takes real-time requests only, so vendors usually send them one at a time on your behalf.

References

  1. Legal Information Institute, Cornell Law School (current). 45 CFR ยง 162.1202 - Standards for eligibility for a health plan transaction (opens in a new tab) โ†‘

  2. Centers for Medicare & Medicaid Services (CMS) (current). HIPAA Eligibility Transaction System (HETS) (opens in a new tab) โ†‘

  3. Medical Group Management Association (MGMA) (2026). Phones are still a bottleneck costing medical practices time they can't afford (opens in a new tab) โ†‘

  4. Medical Group Management Association (MGMA) (2026). Automatic for the people: AI moves for medical practices to boost the front office and access (opens in a new tab) โ†‘

  5. Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) โ†‘

Book a demo

See Ava handle your calls.

Book a short demo. Weโ€™ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo