An edit pair in a spreadsheet can look like a simple yes-or-no answer. It is not useful until someone can say which file, which setting and which date the answer came from.

What CMS has announced

A September 17, 2026 CMS transmittal announces National Correct Coding Initiative procedure-to-procedure (NCCI PTP) version 33.0, effective January 1, 2027, with a January 4 implementation date for contractors. It says test files will be available through CMS’s Hybrid Cloud Data Center on or about November 2, and final files on or about November 17. Those are target availability dates in a contractor transmittal, not proof that a practice can download a final public file today.[1]

As checked November 4, the CMS public PTP download page still displays 2026 fourth-quarter files, effective October 1, 2026. It lists separate hospital-outpatient and practitioner files. We did not verify access to the contractor test files and are not naming a new or deleted 2027 edit pair before CMS publishes the final files.[2]

The question for an older claim

CMS explains that a PTP edit has a Column One and Column Two code. When an edit pair is reported for the same beneficiary and service date, the Column Two code is generally denied unless a clinically appropriate associated modifier is reported. CMS also publishes quarterly additions, deletions and modifier-indicator changes. That makes the applicable quarter and setting part of the evidence, not a footnote.[2]

For a retrospective review, start with the date of service and the claim setting. Then identify the practitioner or hospital-outpatient file that applied on that date, preserve the exact file version, and ask a qualified coder to examine the pair and modifier question against the documented work. A future version should not be projected backward onto a 2026 service just because it is the newest one in a download folder.[2]

  1. Date and setting. Record service date and whether the claim used the practitioner or hospital-outpatient edit set.
  2. Version and source. Keep the CMS file name, quarter and effective date beside the review.
  3. Human decision. Show the note passage and the reviewer’s reasoning about the pair and any modifier; do not treat an automated flag as a final coding answer.

Where MedCode Pro fits

MedCode Pro’s near-term workflow is retrospective and human-reviewed. With de-identified historical cases, it can surface coding and documentation questions and link a reviewer back to source-note evidence. The relevant NCCI version and setting still need to be verified for the service date. The product does not finalize codes, submit claims, decide payer coverage or guarantee payment.

When CMS publishes the final 2027 files, the useful question will be which actual edit and modifier-indicator changes affect a practice’s case mix. Until then, the announcement is a prompt to tighten version control, not a claim that a specific 2027 pair has changed.[1][2]

Sources

  1. CMS Transmittal 13946 / Change Request 14611, September 17, 2026
  2. CMS Medicare NCCI Procedure-to-Procedure Edits, public download page

Reporting and analysis for revenue-cycle teams. Confirm payer requirements against current policy and your contracts.