Hospital Outpatient Proposal Would Widen Prior Authorization

Key Takeaways

The Health and Human Services Department has proposed expanding the prior authorization requirement to include additional Botulinum Toxin Injection services. This is a proposal at 91 FR 41734, not a requirement in force. Comments must be received by August 31, 2026 — the day the record closes, not a compliance date. It reaches hospital outpatient departments and ambulatory surgical centers. Federal Register

Nothing on this page describes work a provider would have to start doing. A proposed rule is the agency asking a question in public, and the only date attached to it is the date it stops listening.

The proposed changes this brief covers

The Federal Register document at 91 FR 41734 is a large outpatient payment omnibus. This page deliberately covers only the operational items below, each stated as what it actually is — a proposal or a request, never a requirement. Federal Register

Prior authorization would widen. The document proposes to expand the prior authorization requirement to include additional Botulinum Toxin Injection services. That is the whole of what the abstract says on the point: a named service category, added to an existing requirement, if the proposal is adopted in that form.

Accrediting organizations would check EMTALA administrative compliance. The document proposes that hospital accrediting organizations with deeming authority assess compliance with certain Emergency Medical Treatment and Labor Act administrative requirements during accreditation and reaccreditation surveys. The proposal is about who checks and when, during a survey a hospital already goes through.

Price transparency data is a question, not a rule. The document requests information on potential approaches to improve comparability and standardization — particularly for complex contracting methodologies — of hospital price transparency information reported in machine-readable files and consumer-friendly displays. A request for information is not proposed regulatory text. It carries no requirement, proposed or otherwise, and nothing a hospital publishes today changes because of it. The existing duty is a separate subject with its own brief on hospital price transparency requirements.

Expressly outside this page: payment rates and the amounts and factors used to set them, quality-reporting measure specifications, the Consolidated Appropriations Act off-campus outpatient department provisions, teaching-hospital slot notices, and the separate solicitation on inpatient payment for domestic procurement of personal protective equipment and essential medicines. Those subjects are in the document; they are not in this brief.

The last row is the one that matters most. A reader who files August 31, 2026 as a date by which something has to be ready has filed the wrong kind of date, and the consequence of that mistake runs in both directions — wasted readiness work, or a comment never written.

Hospital outpatient and ASC teams in scope

The named service category sits in outpatient and ambulatory surgical settings, so the operational weight falls on hospital outpatient departments and ambulatory surgical centers rather than on physician offices. Within those organizations, the functions that would absorb an expanded prior authorization requirement already exist: utilization management, clinical documentation, scheduling, revenue cycle, and denials or appeals.

Accreditation readiness is a separate internal audience. If accrediting organizations were asked to assess certain Emergency Medical Treatment and Labor Act administrative requirements during surveys, the people who prepare for a survey — quality, compliance, emergency department leadership, and whoever maintains the evidence binder — would be the ones affected, not the billing office.

Revenue-cycle management vendors sit across both. A vendor that runs authorization submission, documentation retrieval, or denial follow-up for a hospital would be the party configuring anything new, and it is often the party with the clearest view of where an authorization workflow currently breaks. That perspective is worth putting into the record while the record is open.

The document's own scope in the Code of Federal Regulations covers these parts of title 42, whose current text sits at eCFR title 42:

• 42 CFR Part 413 — Principles of Reasonable Cost Reimbursement; Payment for End-Stage Renal Disease Services; Prospectively Determined Payment Rates for Skilled Nursing Facilities; Payment for Acute Kidney Injury Dialysis

• 42 CFR Part 416 — Ambulatory Surgical Services

• 42 CFR Part 419 — Prospective Payment Systems for Hospital Outpatient Department Services (eCFR)

• 42 CFR Part 427 — Medicare Part B Drug Inflation Rebate Program

• 42 CFR Part 488 — Survey, Certification, and Enforcement Procedures

That list is the document's regulatory scope, not a map of which item lands where. The proposal's own text is the only place to read that, and the electronic Code of Federal Regulations was current to 2026-07-24 with title 42 last amended on 2026-07-20 when this brief was prepared. eCFR

The prior-authorization packet, end to end

A hospital that already submits prior authorization requests runs a packet workflow whether or not anyone calls it that. The proposal would not invent this workflow; it would point it at another service category. Describing it plainly is the most useful thing this page can do, because a team that can see its own handoffs can also see which of them would strain under more volume.

Order intake. A scheduled or ordered service is identified as one that needs an authorization before it proceeds. The failure mode here is silent: an order that should have been flagged and was not, discovered later by a denial rather than by a check.

Documentation assembly. Clinical notes, prior conservative therapy, diagnosis coding, and any payer-specific form are gathered into one packet. Assembly is where most delay lives, because it depends on documents produced by people who are not watching the authorization queue.

Submission. The packet goes to the payer through whatever channel that payer accepts, and the submission itself becomes a record — what was sent, when, by whom, and to which destination.

Decision capture. An approval, a denial, or a request for more information comes back and has to land against the original case rather than in an inbox. A decision that is not captured against the case is functionally a decision that did not happen.

Appeal or resubmission. A denial routes to whoever can supply what was missing, with a clock and a named owner. This is the stage most likely to be run on memory and personal follow-up.

Evidence retention. The case, the packet, the submission record, the decision, and the approver are retained together so the sequence can be reconstructed later without reassembling it from scratch.

Nothing in that table is a legal determination, and nothing in it should be read as a description of what the proposal would require. It describes a control loop a provider can run today, which is precisely why it is the right thing to look at while a proposal to extend that loop is open for comment.

Operationalizing the workflow at volume

US Tech Automations can connect order intake, document retrieval, submission logging, and decision capture so that a case opens automatically when an in-scope order appears, missing documents queue to the person who owns them, the submission is recorded with its channel and timestamp, and a stalled case escalates instead of aging quietly. Clinical and compliance owners keep every judgment call.

The same orchestration covers the other two items without pretending to answer them. Machine-readable file production and its lineage can be tracked as a recordkeeping workflow, so that if standardization approaches ever change, the hospital knows which artifact it published and who approved it. Emergency Medical Treatment and Labor Act administrative evidence can be assembled and versioned the same way, so a survey request is answered from a maintained record rather than from a scramble.

The US Tech Automations agentic-workflow platform is built for that shape: connected intake, routed queues, recorded approvals, retained evidence, and monitoring that escalates to a person. It belongs around a hospital's governance model, never inside the clinical or legal judgment that model exists to protect.

Scope the first rollout to one service line and one authorization queue. Count how often a packet waits on a document, how often a decision has to be hunted for, and how often an appeal clock is tracked in someone's head. Those counts are the honest baseline against which any additional volume — proposed or otherwise — should be judged.

Frequently asked questions

Is the prior-authorization expansion in effect?

No. The document at 91 FR 41734 is a proposed rule, and the expansion of the prior authorization requirement to additional Botulinum Toxin Injection services is proposed, not adopted. It may be changed, withdrawn, or reproposed. Federal Register

When does the comment period close?

To be assured consideration, comments must be received by August 31, 2026. That is the date the rulemaking record closes. It is not a date by which any provider would have to have anything in place. Federal Register

Which services does the proposal name for prior authorization?

The abstract names additional Botulinum Toxin Injection services. This page does not extend that to any other service category, because the document's own text is the only source for what would and would not be covered. Federal Register

What does the price transparency request for information ask?

It requests information on potential approaches to improve comparability and standardization — particularly for complex contracting methodologies — of hospital price transparency information reported in machine-readable files and consumer-friendly displays. A request for information gathers input; it is not proposed regulatory text and imposes nothing. Federal Register

What would change for accreditation surveys under this proposal?

The document proposes that hospital accrediting organizations with deeming authority assess compliance with certain Emergency Medical Treatment and Labor Act administrative requirements during accreditation and reaccreditation surveys. Whether and in what form that happens depends on what the agency does after the record closes. Federal Register

Who should own a hospital's prior-authorization evidence trail?

That is an organizational decision, and it should be recorded rather than assumed. A common pattern gives utilization management the case, clinical documentation the packet contents, revenue cycle the decision record, and compliance or health information management the retained history — with one named approver for anything submitted externally.

Related guidance

• Hospital price transparency requirements

• Healthcare nondiscrimination compliance dates

• Medicare program oversight rule

Source: Federal Register / eCFR (91 FR 41734).

Last reviewed: July 28, 2026

Every date, citation, RIN, CFR reference, and figure in this post is copied verbatim from the Federal Register and eCFR as of the snapshot date. Nothing is estimated, modeled, or extrapolated. This is not legal or tax advice.

Disclaimer

This page is for informational purposes only. It is not legal or tax advice, creates no attorney-client relationship, and does not determine whether any hospital or ambulatory surgical center is affected by this proposal or how it should respond. Consult a qualified professional about the proposed rule, the parts of title 42 it names, and the organization's own facts. eCFR

US Tech Automations provides workflow orchestration rather than compliance determinations. See platform pricing when the team is ready to scope authorization intake, document routing, decision capture, and a retained evidence trail around accountable human owners.