Benefit Details Before the Visit, Not After the Denial

An eligibility check answers one question: is this plan active today. For a cardiology practice booking a stress echo or a cardiac CT, that answer is close to useless on its own. What decides whether the visit gets paid, and whether the patient shows up at all, lives one layer down in the benefit details.

The gap between active coverage and payable coverage is where cardiology revenue goes.

A plan can be active and still carry a deductible the patient has not touched, coinsurance on advanced imaging that turns a study into a four-figure bill, a requirement that the study be done at a facility the patient was not booked into, or a preauthorization requirement nobody checked because the appointment was made by phone in ninety seconds.

None of that appears in a yes-or-no eligibility response. It appears in the benefit detail response, which most practices either never pull or pull into a screen no one reads before the day of service.

By the time it surfaces, the study has happened. Now it is a denial, an appeal, or a balance the patient did not expect and will not pay quickly.

Denials cluster at the front end, where this work happens

The revenue cycle spends a lot of energy on the back end of a problem that is created at the front.

A Jan. 6, 2026, MGMA Stat poll of 288 applicable responses asked practices where the biggest revenue cycle leaks are today. Denials and appeals led at 48%, followed by front end issues at 23%, billing and collections at 14%, coding at 13%, and charge posting at 2%. Those first two categories are not independent. A large share of what gets counted as a denial problem was a registration and verification problem that nobody caught in time.

For cardiology the exposure is concentrated, because a small number of high-dollar studies carry most of the requirements.

Preauthorization denials are knowable before the appointment

KFF’s analysis of ACA marketplace claims puts a floor under how ordinary this failure is.

Across healthcare.gov insurers with complete data, nearly 17% of in-network claims were denied in 2021. Of those denials, about 14% were because the claim was for an excluded service and 8% for lack of preauthorization or referral.

Read the second number carefully. Preauthorization is a requirement you can discover before the appointment or discover after the claim, and the cost of those two moments is not comparable. The requirement itself is visible in the benefit detail response for the service category, which means the information needed to avoid that denial was available at booking.

For cardiology the exposure concentrates, because a small number of high-dollar studies carry most of the requirements. A practice does not need to verify everything with equal rigor. It needs to verify the studies that carry authorization rules, every time.

What a benefit detail response actually contains

It is worth being concrete about the difference, because the two checks get talked about as one thing.

An eligibility response confirms the patient is covered under a plan on a date. A benefit detail response describes the terms of that coverage for a service category: remaining deductible, coinsurance and copay amounts, out-of-pocket accumulation, network status for the place of service, and whether the category carries an authorization or referral requirement.

In athenaOne those live behind GET /patients/{patientid}/insurances/{insuranceid}/benefitdetails, with POST /patients/{patientid}/insurances/{insuranceid}/benefitdetails used to request a fresh response rather than reading a cached one. The distinction matters. A benefit response pulled at registration in January and read again in November describes a deductible year that has moved.

For a cardiology schedule the categories worth pulling are narrow and predictable: advanced imaging, cardiac testing, office visits, and durable medical equipment for patients going home with a monitor. You do not need the whole benefit file. You need four categories, refreshed close to the appointment date.

The complication: the data arrives and never reaches the field staff use

This is the failure practices report most often, and it is not a technology gap so much as a routing gap.

A revenue cycle lead at a multi-site vascular and cardiovascular group described it plainly. The payer’s real-time response comes back with the copay in it. Her staff were consistently not moving that number into the field the practice actually bills from, and they were not noticing when the plan named in the response differed from the plan on file in the chart. The information was arriving and dying in a window nobody had time to read during a phone call.

That is a records hygiene job rather than a phone job, which is why it never gets done by the front desk. The automation version is unglamorous: parse the response, write the copay and deductible values into the fields the practice bills from, and raise a flag when the plan in the response does not match the plan on the chart.

The mismatch flag is the highest-value output. Patients frequently do not know their insurance changed. The chart simply goes ineligible and nobody finds out until the claim comes back. Catching the discrepancy at verification turns a denial into a two-minute outbound call: text the patient a link, have them photograph both sides of the card, match it against the plans the practice is contracted with, and file the image in the chart before the appointment.

The handoff is the moment the answer is ambiguous. A plan name that partially matches two contracted products, a secondary payer that appears in the response but not the chart, or a response that returns an authorization requirement for a study the practice normally does without one goes to a verification specialist with the payer response attached, not to a guess.

Benefit details are what make the patient conversation possible

There is a patient-experience argument here that usually gets left out of the revenue discussion.

A patient scheduled for a cardiac study who is told the cost at the time of booking behaves differently from one who receives a bill six weeks later. They can plan for it, set up a payment arrangement, or ask whether a different site of service is covered. The practice collects more and argues less.

That conversation is only possible if the benefit detail pull happens before the call ends, or at minimum before the reminder call goes out. Pulling it the morning of the appointment is too late to change anything except whether the patient walks out.

This is also where phone time goes today. A March 10, 2026, MGMA Stat poll of 294 applicable responses asking practice leaders which phone tasks consume the most staff time put eligibility and prior authorization at 45%, ahead of scheduling at 31% and intake at 9%. Nearly half the phone burden sits on the two workflows that benefit detail data feeds directly.

Where to run the check, and how often

The timing rules matter more than the technology, and they are practice-specific.

Run the first pull at booking, against the appointment type rather than generically. A device check and a cardiac CT are different benefit categories with different exposure, and a single generic check answers neither well.

Run a second pull inside a short window before the appointment, because plan changes, deductible accumulation, and terminations all happen between booking and service. For a study booked six weeks out, the verification done at booking is a planning number, not a billing number.

Run an additional pull whenever the appointment moves. Rescheduling is the step where verification silently goes stale, and it is also the step where an authorization link commonly breaks. An appointment moved into a new plan year is a different financial event than the one that was verified.

Everything above is administrative. Which study a patient needs is decided by the cardiologist, and none of this touches that. The automation confirms what the plan requires and what it will pay, files the answer where staff and billing can see it, and escalates the cases it cannot resolve cleanly.

Key Takeaways

Eligibility confirms the plan is active. Benefit details tell you deductible, coinsurance, network status, and whether authorization is required. Only the second one prevents a denial.
Pull benefit details for four categories in cardiology rather than the whole file: advanced imaging, cardiac testing, office visits, and DME for take-home monitors.
Request a fresh response rather than reading a cached one. A benefit response pulled in January describes a deductible year that has already moved.
The common failure is not missing data, it is data that arrives and never reaches the billing fields. Write copay and deductible values into the fields the practice bills from automatically.
Flag every case where the plan in the payer response differs from the plan on the chart. Patients often do not know their coverage changed.
Verify against the appointment type, not generically. A device check and a cardiac CT carry different requirements and different patient exposure.
Re-verify whenever an appointment is rescheduled. That step is where verification goes stale and authorization links quietly break.
Route ambiguous plan matches, unexpected authorization requirements, and secondary payers that appear only in the response to a verification specialist with the payer response attached.

Cardiology carries an unusual amount of financial risk per appointment, and almost all of it is knowable before the patient arrives. The reason it usually is not known is that pulling benefit details, reading them, moving the numbers into the right fields, and noticing when the plan on file is wrong takes more minutes per patient than a front desk has during a phone call. An AI team working inside athenaOne can run the benefit detail pull at booking and again before the visit, write what comes back into the fields billing uses, flag the plan mismatches that would otherwise become denials, and hand the genuinely ambiguous cases to a verification specialist with the payer response already attached.

Sources