A code is slated to disappear from a payer policy list. It is tempting to turn that into a rule for every spine claim. The November Surest and UMR bulletins make a narrower point: three codes are leaving their spinal-fusion applicable-code lists on December 1. Before anyone changes an edit, the plan and service date need a closer look.[1][2]
The change is specific
The November 1, 2026 medical-policy bulletins for Surest and UMR each list Spinal Fusion and Decompression as updated effective December 1, 2026. In the Applicable Codes entry, each says CPT 22850, 22855 and 63286 are removed. These are notices for named plan lines and a future policy date, not evidence that UnitedHealthcare has applied one new rule to every product or already denied any claim.[1][2]
The September 1 Surest version still lists the three codes. That older document also says its code list is for reference, may be incomplete, and does not itself decide coverage or guarantee payment. The meaningful comparison is therefore a dated policy-list change. It does not say the CPT codes were deleted, that they should never be billed, or that every service described by them is now noncovered.[3][1]
What the billing team should pin down
Start with the member’s actual plan line and the service date. Save the policy version that applies, not just a screenshot of the latest search result. Then have a qualified coder compare the proposed code with the operative note and the full code descriptor. If coverage or authorization is at issue, read the member-specific benefit terms and the payer’s actual response. A code-list edit, a documentation gap and a claim denial are different facts.[1][2][3]
- Plan and date. Record whether the case is Surest, UMR or another product, and which policy version applied on the service date.
- Code and note. Ask a human reviewer what procedure the note actually supports before changing a code or an edit.
- Payer outcome. If there is a response, preserve its exact reason and the relevant claim or authorization history instead of assuming the policy-list change caused it.
Where MedCode Pro fits
MedCode Pro’s near-term workflow is retrospective first. On de-identified historical spine cases, it can surface coding and documentation risk questions and link a reviewer back to source-note evidence. The reviewer can keep the applicable payer policy version beside that review. A qualified human still decides what the record supports. The product does not determine a member’s benefit, finalize codes, submit claims or prior authorizations, make payer-final decisions, or promise recovered revenue.
The useful test is modest: in a de-identified historical spine sample, see whether the team can separate a chart-to-code question from a policy-version check. Once the December 1 change takes effect, evaluate any actually affected cases using their plan and service dates. Neither exercise forecasts denials or payment.[1][2]
Sources
- UnitedHealthcare, November 1, 2026: Surest Medical Policy Update Bulletin, spinal fusion and decompression
- UnitedHealthcare, November 1, 2026: UMR Medical Policy Update Bulletin, spinal fusion and decompression
- UnitedHealthcare, September 1, 2026: Surest Spinal Fusion and Decompression policy, SRST2026T0639J
Reporting and analysis for revenue-cycle teams. Confirm payer requirements against current policy and your contracts.