Navigating Imaging Auths and Oklahoma Attestations: A Contract Negotiator’s Playbook for Claims Teams

Executive Summary

As contract negotiators, we live at the intersection of dense policy language and the very practical reality of whether your claims get paid on first pass. Two current pressure points are driving avoidable denials and rework for many billing and claims shops:

• Radiology prior authorization for head CTs with UnitedHealthcare (UHC)

• Attestation and consent documentation for abortion‑related services under Oklahoma Medicaid managed care (Humana Healthy Horizons)

Understanding exactly how these rules work—and building them into your day‑to‑day workflows—is the difference between clean claims and chronic write‑offs.

This article walks through:

• How UHC structures prior authorization and CPT crosswalks for CT head codes like 70450, 70460, and 70470, and what that means for how you bill and correct claims[UHC-001] [UHC-CP-FAQ] [UHC-OX].

• Why Oklahoma Medicaid managed care now treats abortion, sterilization, hysterectomy, and initial hospice claims as documentation‑dependent, and how missing consent forms lead directly to denials[HUM-OK-1] [HUM-OK-2].

• Concrete workflow and contract‑language strategies you can use today to protect revenue and reduce back‑and‑forth with payers.

Think of this as a bridge document: translating policy clauses into the daily edits, attachments, and pre‑bill checks that keep your remittance advice clean.

The Revenue Impact of Getting Policy Nuance Wrong

Let’s start with a scenario you probably recognize.

A neurologist orders a non‑contrast head CT in the ED. Prior auth is obtained for 70450. On the table, the radiologist decides contrast is needed and performs a contrast study instead. Your team bills 70460. Weeks later, you’re staring at a denial for “no authorization on file for billed service.”

From a contract negotiator’s vantage point, this is a classic case where policy does protect you—if your team knows how to use it.

Similarly, in Oklahoma, a gynecological procedure is performed that meets Medicaid coverage criteria for abortion. The clinical work is flawless, coding is correct—but the claim denies because the required state or federal consent form wasn’t attached[HUM-OK-1]. The denial isn’t about medical necessity at all; it’s about documentation.

The through‑line: payer rules often anticipate these scenarios, but the protection only works if your billing workflows are aligned to the fine print.

UnitedHealthcare Radiology Prior Authorization: CT Head as a Case Study

Which CT Head Codes Need Prior Auth?

UnitedHealthcare’s Community Plan radiology prior authorization list identifies CT procedures, including head and neck series, as services that require prior authorization when performed in the outpatient setting[UHC-001].

For our purposes, the core head CT codes are:

• 70450 – CT head/brain; without contrast material[UHC-OX]

• 70460 – CT head/brain; with contrast material(s)[UHC-OX]

• 70470 – CT head/brain; without contrast material, followed by contrast material(s) and further sections[UHC-OX]

These codes fall under UHC’s outpatient radiology prior authorization program for both Community Plan and Medicare Advantage products[UHC-001] [UHC-CP-FAQ].

Operational takeaway: Treat all scheduled outpatient CT heads for UHC Community Plan and Medicare Advantage as prior auth required services.

The CPT Code Crosswalk: Your Safety Net for Code Changes

UHC’s radiology prior authorization FAQs and Oxford crosswalk tables explain how authorization obtained for one head CT code can be “translated” to closely related codes when the actual service differs from what was originally requested[UHC-CP-FAQ] [UHC-MA-FAQ] [UHC-OX].

How the Crosswalk Works

UHC describes the crosswalk as a left‑to‑right table:

• The left column lists the CPT code for which prior authorization (or precertification) was granted.

• The right column lists CPT codes that will be allowed when billed under that authorization[UHC-CP-FAQ] [UHC-MA-FAQ] [UHC-OX].

For example:

• Scenario 1

  • Prior auth is obtained for 70450 (CT head without contrast).

  • Claim is ultimately submitted with 70460 (CT head with contrast) or 70470 (CT head without then with contrast), or 76380 (limited or localized follow‑up CT).

  • UHC’s crosswalk specifies that if authorization exists for 70450, the claim submitted with these related codes will be allowed without requiring an updated authorization[UHC-CP-FAQ] [UHC-MA-FAQ] [UHC-OX].

• Scenario 2

  • Prior auth is obtained for 70460 (CT head with contrast).

  • Claim is submitted with 70450 or 70470 or 76380.

  • The crosswalk similarly treats billing these codes as valid uses of the original authorization[UHC-CP-FAQ] [UHC-OX].

UHC clarifies that when the ordering professional has obtained prior authorization for 70450 and the procedure changes to 70460 as listed in the crosswalk, no further action is required and the rendering provider does not need to update the prior authorization[UHC-CP-FAQ].

Crosswalk Highlights in Table Form

Operational takeaway: If authorization exists for 70450, 70460, or 70470, and the actual billed code is a crosswalk‑linked code, the claim should be payable under the original authorization[UHC-CP-FAQ] [UHC-MA-FAQ] [UHC-OX].

What This Means for Your Billing Workflow

From a contract‑negotiation lens, we push for clear crosswalk language; from a claims‑operations lens, you need safeguards so your team can use it.

1. Pre‑Registration and Scheduling

• Flag 70450, 70460, 70470, and 76380 as auth‑required for UHC Community Plan and Medicare Advantage[UHC-001] [UHC-CP-FAQ].

• Build EHR or scheduling edits that won’t finalize the appointment until an auth number is documented.

2. Auth Capture on the Front End

• Capture the original CPT requested at the time of auth and store it as a discrete field.

• Train your teams to understand that for UHC, a prior auth obtained on any of the crosswalk‑linked codes should cover related codes as long as the crosswalk supports it[UHC-CP-FAQ] [UHC-MA-FAQ] [UHC-OX].

3. Coding and Charge Capture

• When the performed service differs, coders should select the clinically accurate code without trying to “match” the authorization. The crosswalk is designed to handle these changes[UHC-CP-FAQ].

• Educate coders and billers on the specific crosswalk pairs to reduce unnecessary auth updates.

4. Denial Management

• If UHC denies a CT head claim for “no authorization,” but your records show:

  • UHC auth for 70450, 70460, or 70470, and

  • The billed code is within the crosswalk set,

  then your appeal should explicitly cite UHC’s crosswalk policy[UHC-CP-FAQ] [UHC-MA-FAQ] [UHC-OX].

Negotiation Angle: Hard‑Wiring Crosswalk Protections into Contracts

In payer discussions, we leverage these published crosswalks to:

• Embed language affirming that authorization on one crosswalk code is valid for any listed reciprocal codes, and that denials for “no auth” in these situations will be reversed without penalty[UHC-CP-FAQ] [UHC-MA-FAQ] [UHC-OX].

• Require advance notice whenever UHC changes the crosswalks or auth lists, so your internal edits can be updated in time[UHC-001].

For your claims teams, this means fewer “gray areas” and more leverage when appealing denials that violate the contract.

Oklahoma Medicaid Attestations: Humana Healthy Horizons Requirements

Now let’s move from radiology to a very different—but equally unforgiving—area: documentation‑dependent coverage for sensitive services.

What Humana Healthy Horizons in Oklahoma Requires

Humana Healthy Horizons, operating under Oklahoma Medicaid (SoonerCare), specifies that certain claims must include completed consent forms or supporting documentation before payment will be made[HUM-OK-1] [HUM-OK-2].

The policy states that claim submissions for:

• Abortion procedures

• Sterilization procedures

• Hysterectomy procedures

• Initial hospice claims

must include the appropriately completed state or federal consent forms and/or other supporting documentation before payment can be made[HUM-OK-1] [HUM-OK-2].

Humana directs providers to obtain these required forms from the Oklahoma Health Care Authority (OHCA) Medicaid forms website[HUM-OK-1] [HUM-OK-2].

Operational takeaway: For these services, a correctly coded claim without the proper consent form attached is functionally incomplete and will not be paid[HUM-OK-1].

Why These Requirements Matter to Claims and Billing

From a billing perspective, these rules create a tight coupling between:

• Clinical documentation (consent/attestation forms), and

• Claims processing and payment.

The policy makes clear that payment is contingent on these documents being included with the claim[HUM-OK-1] [HUM-OK-2].

For many organizations, the weak link isn’t knowledge of the forms—it’s the handoff between:

• Clinic staff who obtain consent,

• HIM or records teams who index the forms, and

• Billing staff who submit the claim.

Without a deliberate workflow, the consent may live in the chart, but never make it into the claims attachment, leading to denials that are frustrating but entirely predictable.

Building an Attachment‑First Workflow

From a contract negotiator’s vantage point, I push to keep requirements predictable and clearly defined. Your job is to operationalize them.

1. Service Identification and Coding Flags

• Map all CPT/HCPCS codes used by your organization for:

  • Abortion

  • Sterilization

  • Hysterectomy

  • Initial hospice care

  and flag them in your billing system as “consent form required for OK Humana Medicaid” based on Humana’s manual[HUM-OK-1] [HUM-OK-2].

• Build edits that prevent claim submission for Humana Healthy Horizons members when these codes are present without a linked document ID.

2. Document Collection and Indexing

• Ensure clinic/OR workflows consistently:

  • Pull the current OHCA consent form from the OHCA Medicaid forms site[HUM-OK-1].

  • Complete all required fields (including any timing requirements, such as waiting periods, where applicable under state or federal rules).

• In your document management or EHR system, standardize a naming convention such as OK_HUMANA_<ServiceType>_CONSENT_<Date>, and index the form to the encounter that will generate the claim.

3. Claim Submission Mechanics

• For electronic claims:

  • Use your clearinghouse or payer portal’s attachment functionality to send the consent form with the initial submission, not as a follow‑up.

• For paper claims (if applicable to your operation):

  • Physically attach the form to the CMS‑1500 or UB‑04 and clearly indicate in a remark field that consent documentation is included, consistent with Humana’s manual requirement to submit consent before payment[HUM-OK-1].

4. Denial Prevention and Audit

• Implement a monthly audit of a random sample of abortion, sterilization, hysterectomy, and initial hospice claims for OK Humana Medicaid to confirm that consent forms were attached at submission[HUM-OK-1].

• Track denials explicitly related to “missing consent/attestation” and use this data to refine your pre‑bill checks.

Negotiation Angle: Making Documentation Rules Workable

In payer negotiations, we use this manual language to:

• Confirm that only these categories—abortion, sterilization, hysterectomy, and initial hospice—are subject to mandatory consent form submission prior to payment, preventing scope creep[HUM-OK-1].

• Clarify that if the consent is on file and appropriately completed, payment will not be withheld for purely technical issues (e.g., if a resubmission is needed due to a non‑clinical claim edit), provided the form is re‑attached.

• Establish remediation expectations: if Humana denies a claim despite a properly attached consent, the contract should support quick reprocessing once evidence is provided.

For your teams, this means fewer arbitrary denials and more predictable revenue when procedures meet coverage criteria and documentation is in order.

Comparing the Two Payers: Different Tools, Same Goal

On the surface, UHC’s prior auth crosswalks and Humana’s Oklahoma consent requirements couldn’t be more different. One deals with code substitution and medical imaging; the other governs sensitive procedures and regulatory consents.

But for your claims and billing operations, they share key themes:

• Front‑loaded requirements

  • UHC requires prior authorization before services like CT heads are performed[UHC-001].

  • Humana requires documentation attached to the claim before payment for specific procedures[HUM-OK-1].

• Policy as protection—if used correctly

  • UHC’s crosswalk is designed to protect you when clinical realities shift from the original planned imaging[UHC-CP-FAQ] [UHC-MA-FAQ] [UHC-OX].

  • Humana’s consent requirement is straightforward: meet it, and payment is permitted; miss it, and payment is blocked[HUM-OK-1].

• Workflow‑driven success

  • Clean claims in both programs come from aligning your scheduling, coding, and billing workflows with the policy details—a core area where contract negotiators and revenue cycle leaders must partner.

Practical Checklist for Claims and Billing Teams

Here’s a concise checklist you can use as a starting point.

For UnitedHealthcare CT Head Claims

• Confirm 70450, 70460, 70470, and related CT codes are flagged as auth‑required for UHC Community Plan and Medicare Advantage[UHC-001].

• Ensure the original authorized CPT code is stored and easily visible to coders.

• Educate coding and billing staff on UHC’s CT head crosswalk pairs (auth vs. allowed claim codes)[UHC-CP-FAQ] [UHC-MA-FAQ] [UHC-OX].

• Build denial appeal templates that explicitly cite UHC’s crosswalk rules when an authorized CT head is denied for “no authorization.”

For Humana Healthy Horizons in Oklahoma

• Maintain an updated list of abortion, sterilization, hysterectomy, and initial hospice codes used in your organization.

• Configure claim edits that block submission of these codes for OK Humana Medicaid without a linked consent/attestation document[HUM-OK-1] [HUM-OK-2].

• Standardize how consent forms from the OHCA Medicaid forms website are collected, indexed, and attached to claims[HUM-OK-1].

• Audit a sample of these claims monthly for attachment compliance and track related denials.

Key Takeaways and Call to Action

• Prior authorization and documentation requirements are now central revenue drivers, not side‑notes. UHC’s CT head crosswalks and Humana’s Oklahoma consent rules are prime examples[UHC-001] [UHC-CP-FAQ] [HUM-OK-1].

• Contracts can and should enshrine operational protections—but it’s your internal workflows that ultimately determine whether those protections prevent denials.

• Claims and billing teams sit at the fulcrum: you see firsthand where policy friction turns into lost revenue. Your feedback is indispensable in shaping negotiation priorities.

As a next step, consider convening a short working session between your revenue cycle, HIM, and contracting teams with two goals:

1. Map your current CT head and Oklahoma consent workflows against the policies cited here.

2. Identify one or two high‑impact edits or process changes you can implement this quarter.

The policies are written; the leverage exists. The real question is whether your workflows—and your payer contracts—are built to make those rules work for you instead of against you.