Good Faith Estimates in 2026: A Complete Guide for Healthcare Practices

Federal price transparency expectations and No Surprises Act (NSA) enforcement have made the good faith estimate one of the most visible parts of No Surprises Act compliance for front-line teams. Under the NSA GFE requirements, convening providers and convening facilities that are not enrolled in Medicare or Medicaid must furnish an estimate to uninsured and self-pay patients when items or services are scheduled, and when those patients request one. The obligation is not only about sending a PDF on time. It is about whether the numbers reflect the care plan you expect to deliver.

Auditors and patients experience good faith estimate healthcare obligations differently. An auditor asks whether a document went out inside the delivery window. A patient asks whether the number on the page matched the number on the statement. When those two experiences diverge, the practice still spent staff time on paperwork, yet it did not buy the trust or collections stability that motivated the rule in the first place.

This good faith estimate healthcare guide covers who needs NSA GFE documents, what they must contain, how timing rules change with the scheduling window, and why CPT-level verification is the operational difference between a compliant file and a patient cost estimate patients can rely on. For the broader federal picture, including balance billing and facility-based protections, start with our No Surprises Act compliance hub.

Schedule a demo to see how Fuse turns payer-specific benefits into structured documentation your team can use before the visit.

Most GFE Failures Are Accuracy Problems, Not Paperwork Problems

Most practices understand that a good faith estimate must exist for qualifying patients. The harder problem is that many GFE requirements are satisfied on paper with figures that do not survive contact with the claim. Teams pull a benefit tier from a portal, drop it into a template, and move on. When the claim posts, the patient sees a different copay, an unmet deductible segment, or a denied add-on code. If the final bill is at least $400 above what the NSA GFE showed for the same episode, the patient can pursue patient-provider dispute resolution through HHS. That is why accuracy matters as much as timestamps.

The gap is not usually neglect. It is structural. Standard workflows answer, “Is this member active on this plan?” Good faith estimate healthcare workflows must answer, “What will this member owe for these procedure codes on this date of service at this place of care?” Those are different questions. Closing the gap is what separates a symbolic estimate from a dependable patient cost estimate.

Practices that already collect deposits or card-on-file authorizations feel this tension first. A patient cost estimate that was rounded from a brochure copay creates downstream refunds, payment plan rework, and phone volume your team cannot schedule away. Treating the NSA GFE as a revenue-cycle artifact rather than a patient communication tool is how teams end up compliant on delivery timestamps and exposed on dollar variance.

Generic Eligibility Checks Do Not Return the Data GFEs Require

Front desk teams are trained to run eligibility checks early. Those checks are necessary, but they are rarely sufficient for GFE requirements. A typical payer portal or 270/271 eligibility transaction confirms identifiers, plan selection, and that coverage appears active. It may summarize deductibles and out-of-pocket maximums at a plan level. It generally does not tell you the member’s cost share for the exact CPT or HCPCS codes on the schedule, whether those codes require prior authorization, or whether a carve-out applies to the rendering provider.

For a scheduled knee injection, for example, the plan may show a primary care copay online while the specialist office visit applies under a different benefit. Imaging bundled with surgery may process under another rule set entirely. No Surprises Act compliance for NSA GFE documents expects an itemized expected charge picture tied to the items and services reasonably expected to be furnished. Plan-level snapshots rarely reach that depth without an extra verification pass.

Think of it as a checklist your schedulers can use when judging whether an eligibility screen is “good enough” for a good faith estimate:

• What standard checks usually confirm: Member identity, plan name, effective dates, and sometimes aggregate deductible or out-of-pocket totals.

• What GFE-accurate checks still need: How the listed CPT or HCPCS codes map to benefit categories for that plan, what cost sharing applies after deductible credit order is applied, whether authorization is in place for those codes, and whether any provider- or site-specific limitations change the allowed amount.

If your team cannot point to where each line item on the NSA GFE came from in the payer’s own materials, you are still in the first column.

CPT-Level Verification Gives You the Benefits Detail Every GFE Depends On

CPT-level verification means confirming benefits in the payer’s system against the same procedure codes you expect to bill, not only against the member ID card. Done well, it surfaces procedure-specific cost sharing, remaining deductible balances that will apply to the claim, coinsurance percentages that attach to the service category, prior authorization requirements, and coverage limitations that portals omit. When payer portals stop short, direct payer calls fill in the blanks and create an auditable trail.

That is the workflow Fuse automates. Fuse runs CPT-level verification and direct payer calls, then writes structured notes back into the EHR so schedulers and financial counselors see payer-confirmed details where they already work. The output aligns with what GFE requirements ask you to document: expected items and services described with enough specificity that a patient can compare the estimate to the bill.

Because the note lands in the chart, medical records staff, billing, and the clinician share one version of what was verified. That matters when a patient later says the good faith estimate did not mention an ancillary code. Structured documentation makes it easier to show what was known at scheduling time versus what changed when the plan processed the claim.

Who Must Provide a Good Faith Estimate?

Convening providers and convening facilities that are not federal health program participants in Medicare or Medicaid must provide NSA GFE documents to uninsured and self-pay patients when they schedule a primary item or service, or upon request. Uninsured patients lack applicable coverage for the visit. Self-pay patients are those who choose not to have a claim submitted to their plan for that encounter. Emergency services sit outside the standard advance estimate pathway, and other exclusions can apply depending on how the patient is classified and how care is delivered.

The “who” question also has a practical corollary for operations: someone on your team must own the convening role for each episode. In independent practices, that is often the scheduling site where the patient first books. In facility-based care, the hospital or ASC registration desk may convene while professional charges still require coordination. Map that ownership explicitly so GFE requirements do not fall between departments.

State laws can layer on additional estimate duties, as they do in several jurisdictions. For the federal baseline and how it interacts with facility-based care, keep the No Surprises Act compliance hub handy when you train staff.

What Must a Compliant GFE Include?

A compliant estimate is more than a single dollar total. Federal GFE requirements call for patient identifiers, provider identifiers such as NPI and TIN, an itemized list of expected charges, applicable diagnosis and service codes such as ICD and CPT or HCPCS, expected dates of service and service locations, and co-provider or co-facility details when others are expected to bill separately. Patients must also receive information about their rights if billed substantially above the estimate, including the patient-provider dispute resolution pathway.

Itemization is where CPT-level verification pays off twice: first when you build the estimate, and again when the patient compares the statement line by line. A lump-sum total without code-level backing is difficult to defend if a single add-on code posts differently than expected. Listing each anticipated charge with its code also helps patients understand facility fees, supply charges, and professional components that otherwise read as duplicate billing.

When care is recurring, a single good faith estimate can cover repeated items or services for up to twelve months if the expected scope stays consistent. That is useful for therapy series or infusion schedules, but it still assumes the underlying clinical plan and codes remain stable.

GFE Requirements for Multi-Provider and Surgical Cases

Surgical episodes and imaging bundles are where NSA GFE coordination becomes operationally heavy. The convening provider—the entity that receives the scheduling request for the primary service—must request expected charge information from co-providers and co-facilities within one business day of scheduling (or of the estimate request). Co-providers and co-facilities are expected to respond quickly enough for the convening provider to assemble a consolidated estimate. When everyone returns data on time, good faith reliance protections limit how much liability falls on the convening provider for another party’s late or incomplete numbers. When responses lag, the convening provider still faces clock pressure. That is why surgical and multi-specialty cases benefit from automated benefit pulls and documented payer contacts rather than ad hoc email chains alone.

GFE Timing Rules: How Long You Have Based on When the Visit Is Scheduled

Timing is measured in business days from the day the service is scheduled or requested, not calendar days from the clinical event. Missing the window is an easy-to-audit failure mode, which is why scheduling software flags and EHR tasks matter as much as template content.

How the Scheduling Window Determines Your Deadline

Use a simple grid with scheduling staff:

Days between scheduling and expected date of service	GFE delivery requirement
At least 10 business days	Provide the GFE within 3 business days of scheduling
Between 3 and 9 business days	Provide the GFE within 1 business day of scheduling
Fewer than 3 business days	No advance GFE is required before the service under the standard scheduling rule
Patient requests an estimate without scheduling	Provide the GFE within 3 business days of the request

If the date of service or scope of care shifts materially, treat it as a trigger to refresh documentation. An outdated good faith estimate undermines trust and reopens PPDR exposure if the bill diverges from what the patient was told.

The $400 Variance That Triggers a Patient-Provider Dispute

When actual billed charges exceed the total expected amount on the NSA GFE by $400 or more, the patient may initiate patient-provider dispute resolution with HHS within 120 calendar days of receiving the bill. The process is designed to be patient-navigable, which means your practice may receive a formal dispute even when clinical care was appropriate. Staff time spent assembling records, revisiting eligibility, and reconciling ledgers is unbillable overhead, and payment timelines can stretch while the dispute runs.

The preventive strategy is not to lowball estimates. It is to build estimates from CPT-level verification and documented payer responses so the expected total matches how the claim will actually process. Fewer surprises mean fewer disputes and cleaner patient cost estimates at the point of collection. For a deeper walkthrough of the dispute mechanics, read the PPDR discussion in our No Surprises Act compliance hub.

Learn How Fuse Builds Accurate GFEs Into Your Existing Verification Workflow

Fuse sits on the intake and verification steps you already perform. It ingests the appointment context from the schedule, runs CPT-level verification, escalates to direct payer calls when portals stall, and writes structured results back into the patient chart. Teams do not learn a new platform for No Surprises Act compliance; they read Fuse’s note inside the EHR alongside the rest of the record. That is how practices close the gap between “active coverage” and the procedure-level numbers GFE requirements expect.

There is no parallel IT project because Fuse operates with the same credentials and permissions you would give a new billing teammate: schedule visibility to know what is coming, and note writeback to document what was verified. For groups juggling multiple payers, that consistency matters more than any single feature list. Every appointment inherits the same verification depth whether the patient is commercial, exchange, or self-pay for that date of service.

Book a demo to see the workflow on your EMR. Practices that move forward can also take advantage of Fuse’s benchmarking analysis offer described on the Fuse homepage, which compares negotiated payer rates to market data for your specialty and region so you understand not only patient responsibility, but also how your contracts sit relative to peers.