CMS’s CPT Coding RFI: What It Means for Compliance Teams

·

For the first time in decades, the federal government is formally asking whether the American Medical Association should keep sole control over the CPT code set. Buried inside the CY2027 Medicare Physician Fee Schedule proposed rule, released in draft form in July 2026, CMS included a request for information (RFI) that questions the AMA’s six-decade role writing and pricing CPT codes — an arrangement that has stood essentially unchanged since CPT became the mandated code set under HIPAA in 1996, as Medical Economics reported on August 31, 2026. For coding and compliance teams, this is not a code-set update to file away. It is an open question about who gets to define the codes at all.

What CMS Is Actually Asking

The RFI is embedded in the broader CY2027 physician fee schedule proposal that CMS issued in July 2026, with a public comment period running through September 14, 2026, according to a detailed summary from Holland & Knight’s July 2026 analysis of the rule. Alongside conversion-factor changes and a proposed overhaul of add-on code G2211, the same rule solicits public input on alternatives to the current CPT framework — including how codes get created, how the AMA’s Relative Value Update Committee (RUC) assigns physician work values, and what it costs practices and vendors to license a code set they are legally required to use.

Why Now

The timing is not accidental. Coverage of the RFI has noted that HHS leadership has been weighing alternatives to the AMA’s role for roughly two years before this proposal surfaced, framing the question explicitly around whether the arrangement functions as a monopoly that constrains competition in how medical services are described and valued. CMS has not proposed replacing CPT outright — the RFI seeks input, not a final decision — but the fact that the question was asked at all, in a binding rulemaking document rather than a speech or white paper, is itself the story for anyone who works inside the current system every day.

A Lawsuit Adds Pressure From a Different Angle

Weeks after the RFI became public, the pressure on CPT’s governance model widened beyond CMS. On August 13, 2026, the advocacy group PatientRightsAdvocate.org filed a declaratory judgment lawsuit against the AMA in federal court in Chicago, seeking the right to freely publish the CPT Professional Edition, as detailed in reporting on the filing from August 15, 2026. The suit rests on three separate legal theories: that CPT’s government-mandated use invokes the government edicts doctrine and voids the AMA’s copyright claim; that free publication of legally required code text is fair use regardless of copyright validity; and that a 1983 licensing arrangement between the AMA and the federal government, though later renounced, still limits how the AMA can enforce that copyright today.

None of the three theories has been tested to a verdict, and the AMA has not issued a public response to the suit. But the case and the RFI are pulling on the same thread from different directions — one questioning who should set CPT’s content and pricing, the other questioning who should be allowed to distribute it.

What This Means for Coding and Compliance Teams Right Now

Nothing about how you code claims changes today. CPT remains the mandated code set, the RUC process continues to run on its normal calendar, and the CY2027 fee schedule rule — RFI included — is still in the comment phase. But a few practical points are worth tracking as this plays out over the coming months:

  • The comment window closes September 14, 2026. Specialty societies, health systems, and RCM vendors that want a say in how CMS frames any future coding-governance changes have a narrow window to weigh in.
  • This is separate from the annual CPT update cycle. The RFI is about who controls the process long-term, not about specific 2027 code additions or deletions, which continue on their normal AMA editorial schedule.
  • A ruling in the copyright case could move faster than any CMS policy change. Federal litigation on a declaratory judgment claim can resolve well before a rulemaking process concludes, so the copyright question may reach a decision point independently of what CMS ultimately proposes.
  • Licensing costs are explicitly part of the RFI’s scope. Any organization that pays to license CPT content for internal tools, EHR integrations, or coding software has a direct stake in how this question is resolved.

How to Prepare While the Outcome Is Still Open

The honest answer is that there is no coding action to take yet — CPT is not going away in the near term, and no alternative framework has been proposed, let alone adopted. What compliance leaders can do now is make sure someone on the team is actually reading CMS’s RFI responses and any docket activity in the copyright case, rather than relying on the annual code-set refresh as the only trigger for policy review. Coding operations that depend heavily on rigid, single-source code mappings are also worth stress-testing: if code governance does shift in the next few years, the organizations least disrupted will be the ones whose coding logic and audit trails are not brittle to a change in who defines the underlying code set.

That is the same reasoning behind why more RCM and coding organizations are moving toward platforms that can adapt to code-set and policy changes without a manual rebuild each time. Medikode’s automated medical coding platform is built around exactly that kind of adaptability, so if the CPT landscape does shift, the coding infrastructure underneath it does not have to be rebuilt from scratch.