Coverage Requirements Discovery: What Changes for You?

Key Takeaways

• Coverage Requirements Discovery is a live check built into Epic's patient chart that instantly tells clinical and billing staff whether an insurer requires prior approval for a treatment, replacing phone calls, faxes, and manual portal lookups.

• According to Yahoo News, the tool went live first at four health systems — Ochsner Health, Froedtert ThedaCare Health, Denver Health, and Summit Health — working with UnitedHealthcare, Aetna, and Network Health, with 16 more insurers testing it.

• According to HIT Consultant, the rollout arrives ahead of a federal mandate requiring most Medicaid, Medicare Advantage, and ACA marketplace insurers to support prior-authorization APIs by January 1, 2027.

• For a small medical or dental practice, the near-term relevance is practical: this is a preview of the same prior-authorization API standard every insurer covering Medicaid, Medicare Advantage, and ACA marketplace plans will be required to support within months — whether or not that practice runs Epic.

The answer in plain English

Coverage Requirements Discovery is a tool built into Epic's electronic health record that shows clinicians and billing staff, at the moment they're placing an order, whether the patient's insurer requires prior approval before that treatment happens. It launched publicly in mid-August 2026. As of August 18, 2026, four health systems were live with it, and the tool runs on an industry-standard interface called FHIR, built by the standards group Health Level Seven International, so it can talk to multiple insurers' systems the same way instead of needing a custom connection for each one.

A solo-run clinic or a 5-person dental practice doesn't run Epic and isn't one of the four launch health systems — but the underlying shift matters anyway, and it's worth understanding now rather than when a vendor's compliance deadline forces the issue. This same prior-authorization check standard is becoming a federal requirement, not just an Epic feature. According to HIT Consultant's reporting, most Medicaid, Medicare Advantage, and ACA marketplace insurers must support a prior-authorization API by January 1, 2027 — meaning practice-management and EHR vendors serving small practices are very likely building the same kind of check into their own products on a similar timeline, even if a given small practice never sees the word "Epic."

Who should use this page

This page is for a practice administrator, billing manager, or clinician trying to understand what Coverage Requirements Discovery actually does, whether it applies outside of Epic-run health systems, and what's coming as the federal prior-authorization API deadline approaches — and how much lead time realistically remains.

Red flags: a practice-management vendor claiming "AI prior authorization" without naming the actual API standard (FHIR, and specifically the Da Vinci Coverage Requirements Discovery specification) is likely describing a proprietary workaround, not the interoperable standard insurers are being required to support — worth asking directly which standard the vendor's tool implements. A vendor that can't answer that question in plain terms probably hasn't built the interoperable version yet.

The rollout, by the numbers

The table below lays out exactly who is live, who is testing, and how much runway exists before the federal deadline makes this kind of check mandatory industry-wide. Four health systems are live with three insurers; 16 more are testing. According to TechTarget, Epic already moves more than 9 billion health records a year across its platform — the scale of infrastructure this prior-authorization check now plugs into.

Sources: Yahoo News; TechTarget.

What it replaces

The tool is built to replace four specific manual steps that eat billing-staff time today, a shift documented by Healthcare Dive alongside HIT Consultant's reporting. Per HIT Consultant's reporting, the automation replaces manual payer-portal lookups, phone inquiries, faxed requests, and outdated internal spreadsheet matrices that staff previously used to track which insurer required prior approval for which service.

Ochsner Health's assistant vice president of revenue cycle and financial clearance, Melissa Woods, put the goal directly. According to Yahoo News's reporting, she said the tool "will reduce administrative burden, improve efficiency, and minimize delays in patient care."

USTA analysis: how much runway the launch health systems had

Working from two sourced dates — Epic's August 18, 2026 public launch and the federal January 1, 2027 compliance deadline HIT Consultant reported — the four launch health systems went live 136 days ahead of the January 1, 2027 federal deadline. That is every Medicaid, Medicare Advantage, and ACA marketplace insurer's deadline to support this same kind of check. It's not a vendor-quoted number; it's a straightforward date subtraction between the two cited dates, and it puts a specific number on what HIT Consultant's coverage more loosely called an early move: under five months of lead time before the standard becomes a floor, not an early adopter's edge, for every other insurer and health system still watching from outside the launch group.

The infrastructure this plugs into

Coverage Requirements Discovery didn't launch in isolation — it rides on interoperability infrastructure Epic has been building for years, which is part of why a same-day chart-side check was technically possible at all. Epic exchanged more than 9 billion health records in 2025 alone, according to TechTarget's reporting on the company's broader data-sharing footprint.

Source: TechTarget.

That scale is why a practice outside Epic's four launch health systems should still pay attention: the same data-sharing rails carrying billions of records a year are what a federally mandated prior-authorization API will eventually ride on too, regardless of which EHR vendor builds it.

Signal vs Speculation

Demonstrated signal: as of August 2026, Coverage Requirements Discovery is live at four named health systems, connected to three named insurers with 16 more testing, running on the FHIR Da Vinci standard — confirmed independently across Yahoo News, TechTarget, HIT Consultant, and Healthcare Dive's reporting.

Our read: over the next 6-12 months, expect the practice-management and EHR vendors serving small clinics and specialty practices to announce their own versions of this same check, timed to land before the January 1, 2027 federal deadline — a small practice that hears "prior-authorization API" from its own software vendor in the coming months is very likely hearing about compliance with the same underlying standard Epic just launched, not a separate proprietary feature.

Our read: over a 24-36 month horizon, if the pattern from other interoperability mandates holds — TechTarget's reporting notes Epic already moved over 9 billion records in 2025 across more than 100,000 sites through the related TEFCA data-sharing framework — a live prior-authorization check will likely become as unremarkable a baseline feature as electronic eligibility verification is today, with the real competitive differentiation moving to how fast a practice can act on the flag once it appears, not whether the flag exists.

What this does not establish

Coverage Requirements Discovery does not establish that prior-authorization denials will drop — the sourced coverage describes a faster, more visible check, not a change to insurers' underlying approval criteria. It also doesn't establish that every EHR or practice-management vendor will roll out an identical feature on the same timeline as Epic, only that most relevant insurers face the same January 1, 2027 deadline to support the standard. For a small practice weighing what to do next, the practical parallel is workflow readiness rather than any single tool: a clinic already using prescription prior-authorization tracking can treat this rollout as a preview of what its own workflow may need to plug into as insurers publish their APIs. A practice handling medication refill request triage is managing the same category of insurer back-and-forth that Coverage Requirements Discovery is designed to shortcut. And a billing team that already routes prior-authorization status updates between systems is positioned to add a live coverage-requirement check as a step in that same pipeline once its own vendor ships one — that's the kind of workflow-level readiness question a team using US Tech Automations to route those status updates today would ask of a new API the moment its vendor announces one, rather than rebuilding the pipeline from scratch. A clinic already leaning on US Tech Automations to keep prior-authorization paperwork moving between systems can treat a future insurer API the same way: as a data source to plug into an existing routing step, not a reason to replace the step itself.

A practice's evaluation sequence

Frequently asked questions

What is Coverage Requirements Discovery?

It's a tool built into Epic's electronic health record that instantly shows clinical and billing staff whether a patient's insurer requires prior authorization for a treatment, without a phone call or fax.

When did Coverage Requirements Discovery launch?

It went live publicly in mid-August 2026, with four health systems as the first adopters.

Which health systems were first to use it?

Ochsner Health, Froedtert ThedaCare Health, Denver Health, and Summit Health.

Which insurers work with it today?

UnitedHealthcare, Aetna, and Network Health are live, per Yahoo News's coverage, with 16 more insurers currently testing the connection.

Do I need to run Epic to be affected by this?

Not directly, but insurers face a January 1, 2027 deadline to support a prior-authorization API regardless of which EHR a practice uses — a timeline HIT Consultant's coverage confirms — so a similar check is likely coming to other systems too.

What manual steps does this tool replace?

Payer-portal lookups, phone calls to insurers, faxed prior-authorization requests, and internal spreadsheet trackers, per HIT Consultant's reporting.

Does this tool change whether a prior authorization gets approved?

No — the sourced coverage describes a faster way to see whether prior authorization is required, not a change to an insurer's approval or denial criteria.

What standard does Coverage Requirements Discovery run on?

The FHIR standard built by Health Level Seven International, specifically its Da Vinci Project's Coverage Requirements Discovery specification, which is designed to work the same way across different insurers' systems.

Will this eliminate prior authorization entirely?

No. The sourced coverage describes a faster way to find out whether prior authorization is required and to see the requirement at the point of care — it doesn't remove the underlying prior-authorization requirement itself, which is still set by each insurer's own coverage policy.

If your practice already routes prior-authorization paperwork or insurer status checks through automated workflows, see how US Tech Automations connects those steps so a new insurer API becomes one more data source, not a rebuild.