Written by Jessica Miller · Published 8 November 2026 · Last reviewed 8 November 2026
UnitedHealthcare says it will remove nearly two-thirds of prior authorization requirements for select services for patients under age 18 beginning December 1, 2026. Code removals vary by state and plan. RCM teams should verify member-specific requirements before changing authorization queues, because several plan categories remain excluded.
| Policy detail | Announced scope | Operational action |
|---|---|---|
| Effective date | December 1, 2026 | Separate current requirements from future rules |
| Patient age | Under 18 | Retain age-sensitive checks |
| Announced reduction | Nearly two-thirds for select services | Do not apply this fraction to your entire workload |
| Code-list update | November 6, 2026 | Use the revised payer material |
UnitedHealthcare's announcement , published November 1 and updated November 6, supplies these details. Its scope is narrower than "pediatric prior authorization is ending."
What is changing in UHC pediatric prior authorization?
Prior authorization is a payer's advance review requirement for a service. Removing that requirement changes the authorization step for an eligible service. Your team should continue to check the member's coverage and the documentation supporting the eventual claim.
For a billing company serving several physician groups, the practical problem is deciding which work can leave the authorization queue. Removing the check from all pediatric accounts would apply a limited policy to patients and services outside its scope. Leaving the old queue untouched would send staff after approvals the payer no longer requires for affected services.
Build the change around the member, service, plan and state. Keep the authorization decision separate from the coding decision. Our guide to payer-specific coding requirements across RCM clients explains why a payer name alone is too broad for a usable rule.
Which UnitedHealthcare plans are included and excluded?
UnitedHealthcare lists commercial plans, Individual Exchange Plans and Community Plans as included. It also says removals vary by state and UnitedHealthcare plan. Inclusion in one of those categories starts the review; it does not establish that a particular procedure qualifies.
The payer lists these exclusions:
- UMR plans not following the UMR prior authorization list.
- Health Plan of Nevada Medicaid.
- Dual Eligible Special Needs Plans.
- UnitedHealthcare Medicare Advantage plans.
Preserve the qualifier on UMR. Rewriting the exclusion as "all UMR plans" would change the payer's statement. Preserve the Nevada Medicaid exception when you configure Community Plan rules, rather than treating Community Plans as a uniform national category.
Hospitals and health systems should check which billing entities use the rule before distributing it across departments. Physician groups should check their scheduling and referral instructions. An ASC business office should verify the planned service and member rather than assuming pediatric surgery falls within the removals. An outsourced RCM team should document the decision for each client configuration.
How should RCM teams verify a service before removing a hold?
UnitedHealthcare directs practices to the Prior Authorization and Notification tool on its Provider Portal to verify whether a service is included. Use that member-specific check alongside the applicable procedure-code details linked from the payer announcement. This article does not establish that any particular CPT or HCPCS code is on the removal list.
Use the following operational sequence as a local control, rather than treating it as an additional payer mandate:
- Confirm the member's plan and state, and identify any listed exclusion.
- Record the intended service date and the patient's age relevant to that service.
- Check the applicable procedure-code details and the member-specific portal result.
- Save the result with the date of verification and the staff member responsible.
- Remove only the authorization hold that the verified policy change resolves.
Keep unresolved records in an exception queue with a named owner. "UHC pediatric update" is not enough evidence to close a hold. The record should show which service the team checked and why the result applies to that member.
For a separate source of claim risk, review why correctly coded claims still get denied . Authorization relief does not settle every question involved in claim readiness.
What does a worked example look like?
Consider an illustrative scheduling review, not an actual patient case or a statement about a named procedure code. A physician group has a patient under age 18 scheduled for a service on December 1. The member has a commercial plan included in the announcement. Staff check the revised procedure details and the member-specific portal, which confirm that this service no longer requires prior authorization.
The authorization specialist records the verification and removes that authorization hold. The coder still reviews the clinical documentation for the performed service. The billing team retains its coverage and claim checks. Staff have resolved one administrative requirement without making assumptions about the remaining work.
Now change the plan in the example to Health Plan of Nevada Medicaid. That plan is an explicit exclusion in the payer announcement . Staff cannot use this initiative as the reason to remove the hold. They must verify the applicable requirements for that member and service.
Change the patient's age to 18 instead. The announcement says "under age 18," so this initiative does not establish relief for that patient. These variations show why copying a payer-level rule into every pediatric account would produce unreliable decisions.
What should leaders change before December 1?
Assign an authorization operations owner to maintain the implementation record. Have that owner approve the plan and state mapping, while a separate reviewer tests the rule against included and excluded examples. Keep the previous configuration available so the team can investigate a disputed result.
Update work instructions where staff encounter them. A policy memo in a shared folder will not correct an outdated scheduling checklist. Review referral intake, authorization holds, outsourced team instructions and escalation templates. Use the same scope language in each place so different departments do not interpret the announcement differently.
For multi-client RCM firms, avoid a single change across all client accounts. Identify the clients with relevant pediatric volume, review their plan mix and apply the verified change within those accounts. Track unresolved services without guessing whether a code qualifies. Ask the payer for clarification through the established support channel when the available materials do not resolve a case.
Measure the work your team can observe: eligible holds removed, exceptions still open and records missing verification. Do not forecast a nearly two-thirds reduction in staff workload. The payer's announced fraction describes authorization requirements for select services, not your organization's service mix, labor hours or collections.
What remains unchanged for coding and documentation?
Code the service the documentation supports. An authorization removal supplies no clinical evidence and does not expand the performed procedure. Keep documentation queries and coding exceptions separate from authorization exceptions so one resolved task does not close an unrelated hold.
Our guide to handling incomplete client documentation covers that handoff. A scheduler may have enough information to verify an authorization requirement while a coder still needs a completed note. Record both states rather than assigning the entire encounter a single "cleared" label.
MediCodio AI's role in this workflow is AI medical coding , not issuing a payer's authorization decision. Complete charts flow through AutoPilot for fully autonomous coding. Charts where the documentation is thin or contradictory stay in CoPilot, where certified coders review and finalize the output. The coding record stays separate from the authorization record. For teams evaluating RCM medical coding , compare coding output against source documentation while retaining the payer's member-specific authorization check as its own control. Do not present a coding demonstration as proof that a particular service qualifies for this UHC initiative.
Frequently asked questions
Does UHC remove prior authorization for every pediatric service?
No. UnitedHealthcare describes removals for select services for patients under age 18, beginning December 1, 2026. The payer says code removals vary by state and plan. Verify the procedure details and member-specific portal result before removing a hold; the announcement does not establish relief for every pediatric service.
Are all UnitedHealthcare plans included?
No. The announcement includes commercial, Individual Exchange and Community plans, with state and plan variation. It excludes UMR plans not following the UMR prior authorization list, Health Plan of Nevada Medicaid, Dual Eligible Special Needs Plans and UnitedHealthcare Medicare Advantage plans. Retain those distinctions in your implementation instructions.
Can we stop checking authorization before December 1?
The announced removals begin December 1, 2026. Do not use that future effective date to remove requirements from earlier services. Verify the applicable requirement for the intended service and member, and keep current and future configurations separate until your operations owner approves the effective-date change.
Does an authorization removal mean the claim will be paid?
An authorization removal addresses the advance-review requirement for an eligible service. It does not establish that your claim meets all other coverage, documentation and billing requirements. Keep those checks in place, code the documented service and preserve the verification record supporting your decision to remove the authorization hold.
Should an RCM company expect nearly two-thirds less authorization work?
UnitedHealthcare's announced reduction concerns requirements for select services, not an RCM company's workload. Your result depends on client plan mix, states, patient ages and services. Measure the holds your team can remove after verification, and review unresolved exceptions before making staffing or financial assumptions from the payer's announcement.
Book a Demo to review coding accuracy on your own charts using de-identified samples or an agreed secure process. Keep member-specific prior authorization verification with your payer workflow.
Sources
