Healthcare provider in NJ submitting a Medicare PA? See the WISeR Portal
A Healthcare Brain Academy By Genzeon Platforms
Learn/ Builders/ Step 2
TL;DR

Pre-payment edits (NCCI PTP and MUE) catch billing errors mechanically before payment. Coverage policies (NCDs nationally, LCDs locally) define what's medically necessary. Inpatient admissions are screened against InterQual or MCG criteria. Once a patient is admitted, the claim groups into a DRG that determines the lump-sum payment. For Medicare Advantage revenue, captured HCC diagnoses drive each member's RAF score and the plan's per-member payment from CMS. Every payer and provider AI product touches at least one of these systems.

Lesson 1: NCCI edits — the procedure-to-procedure rulebook

The National Correct Coding Initiative (NCCI) is a CMS program that publishes edits to prevent improper payments. There are two main edit types:

NCCI Procedure-to-Procedure (PTP) edits

PTP edits identify code pairs that should not be billed together on the same day for the same patient by the same provider. Each pair has a Column 1 code (the one that gets paid) and a Column 2 code (the one that gets denied as bundled).

Each pair carries a modifier indicator:

IndicatorMeaningBuilder implication
0No modifier allowed; never billable togetherIf both codes appear together, line 2 will deny regardless of modifiers. AI should flag.
1Modifier allowed under specific circumstancesA correct modifier (often -59, -XE, -XS, -XP, or -XU) can unbundle. Most flexible.
9Edit deleted / not in effectNo longer enforced. Models trained on old data need refresh.
▶ Worked PTP example

43239 (esophagogastroduodenoscopy with biopsy) and 43235 (EGD, diagnostic) are an NCCI PTP pair with indicator 1. 43239 is Column 1 (paid), 43235 is Column 2 (denied as included). The diagnostic EGD is considered part of the biopsy procedure. With a modifier -59 / -XS (separate structure) supported by documentation that the two procedures were truly distinct, the Column 2 can unbundle. Without it, line 2 denies. Your pre-bill AI should evaluate the PTP table and the documentation together.

NCCI Medically Unlikely Edits (MUE)

MUEs cap the number of units of a single code billable for the same patient on the same date of service. They're set per code, by setting (practitioner, outpatient hospital, DME). Each MUE has a MAI (MUE Adjudication Indicator):

MAIMeaningHow it adjudicates
1Line-edit MUEOnly units exceeding the MUE deny; the rest pay. Modifier -91 or appropriate anatomic modifiers can sometimes split units across multiple lines.
2Date-of-service edit, "absolute"Entire line denies if units exceed. Anatomic/clinical impossibility (e.g., billing 3 appendectomies — a person only has one appendix).
3Date-of-service edit, "per day"Entire line denies, but appealable with documentation of medical necessity.

MAI 2 is the unforgiving one. If your AI generates or suggests claims, it must enforce MAI-2 MUEs as hard constraints, not soft signals.

How to use NCCI in an AI pipeline

  1. Download the quarterly NCCI PTP file and the MUE file from CMS. They update every quarter.
  2. Load into a queryable store (Postgres, DuckDB, or a key-value store keyed on code pairs).
  3. Pre-bill: for every claim, check all line-pair combinations against PTP, and every line's units against MUE.
  4. Surface the specific edit code and the modifier indicator so a human (or your appeals model) knows whether unbundling is even possible.
Self-check
A claim bills 99214, 96365 (IV infusion, initial hour), and 96366 (IV infusion, each additional hour) with 96366 at 4 units. The MUE for 96366 in the practitioner setting is 8 with MAI=1. What happens at adjudication?

The 96366 line pays in full because 4 units is under the MUE limit of 8 and the MAI is 1 (line edit, only excess denies). No edit fires on units alone. Your model should not flag this. (You would still check PTP edits between 99214/96365 and modifier requirements separately.)

Why are NCCI updates considered a recurring data freshness problem for healthcare AI?

NCCI tables update quarterly — additions, deletions, and modifier-indicator changes. Models or rule engines that don't refresh against the latest table will start producing false positives (flagging edits that no longer exist) or false negatives (missing newly-added edits). This is one of the most common silent-decay failure modes in payment-integrity AI.

Lesson 2: LCDs and NCDs — what counts as medically necessary

Edits catch billing errors. Coverage policies determine whether a service is even covered for a given patient and condition. CMS publishes two kinds:

National Coverage Determinations (NCDs)

NCDs apply to all Medicare beneficiaries nationwide. There are roughly 300 active NCDs covering specific services. Each NCD lists the conditions (ICD-10s), frequencies, settings, and other criteria under which a service is covered.

Example: NCD 220.6.17 (PET scan for oncology) lists the cancer types for which FDG-PET is covered, frequency limits, and clinical criteria.

Local Coverage Determinations (LCDs)

LCDs are issued by Medicare Administrative Contractors (MACs) for their geographic jurisdiction. Where no NCD exists, the local MAC's LCD applies. LCDs are more numerous (thousands) and more granular than NCDs.

Each LCD has a paired Local Coverage Article (LCA) that lists the specific CPT and ICD-10 codes that satisfy or fail the coverage criteria. This is the part your AI consumes.

▶ How an LCD maps to denial logic

An LCD for vitamin D testing (CPT 82306) typically lists covered ICD-10 indications (osteoporosis, chronic kidney disease, malabsorption syndromes, etc.) and notes that "screening" diagnoses are not covered. If a claim shows 82306 with only Z13.21 (encounter for screening for nutritional disorder) and no clinical indication, denial under CARC 50 + RARC referencing the LCD is the predictable outcome. Provider-side AI should flag this pre-bill; payer-side AI should auto-enforce it.

Where Medicare Advantage fits

Per the MA Final Rule (2024), MA plans must follow Traditional Medicare NCDs and LCDs as a floor. They cannot use proprietary criteria more restrictive than the applicable NCD/LCD. This was a major shift — many MA plans had to retire proprietary policies that were tighter than CMS standards.

Lesson 3: InterQual versus MCG — the criteria sets behind utilization management

For acute admissions and post-acute care, payers don't just check codes — they apply clinical criteria. Two products dominate the market:

InterQualMCG (formerly Milliman)
OwnerChange Healthcare / OptumMCG Health (part of Hearst)
StyleBranching, decision-tree logicGoal-oriented, evidence-summary style
Update cadenceAnnual major releaseAnnual major release
CoverageAcute, behavioral, post-acute, ambulatory, durable medical equipmentInpatient/Surgical Care, General Recovery, Behavioral Health, Recovery Facility
Typical fitCommon in MA plans; very granularCommon in commercial; emphasizes length of stay benchmarks

InterQual mechanics (simplified)

InterQual criteria are structured as decision trees. For an inpatient admission, you generally walk:

  1. Severity of Illness (SI) — does the patient's clinical picture meet thresholds (vitals, labs, imaging findings)?
  2. Intensity of Service (IS) — does the planned care require inpatient resources (telemetry, IV meds requiring monitoring, etc.)?
  3. If both pass — admission is supported. If only one passes — observation status is more appropriate. If neither — outpatient.

MCG mechanics (simplified)

MCG presents care guidelines: an admission criteria block, expected goal length of stay, and clinical indications for continued stay or discharge. Reviewers document met/not-met against the criteria language.

▶ Why this matters for AI

InterQual and MCG are licensed products. You cannot reproduce their criteria text in your model or in user-facing output. AI that helps reviewers apply criteria must operate against a licensed instance or output structured findings that the reviewer matches to their licensed criteria. Multiple vendors have been forced to redesign products around this.

What you can do: extract clinical findings from notes (vitals, labs, medications, history) and present them to the reviewer for criteria application. The criteria evaluation itself stays in the licensed tool. Several payers and vendors have built well-designed workflows around this split.

Self-check
A payer wants you to build a model that recommends inpatient versus observation status using InterQual. What's the legal and architectural constraint?

You cannot bake the licensed InterQual criteria text into your model or surface it as output. The right architecture is: (1) the payer licenses InterQual and provides the criteria reference in their environment; (2) your model extracts clinical evidence (vitals, labs, services, comorbidities) from the chart and presents it to a licensed reviewer; (3) the reviewer applies criteria within the InterQual tool. Confirm the licensing terms with the payer's compliance team before scoping the build.

Lesson 4: DRGs — how inpatient hospital reimbursement actually works

Inpatient hospital claims don't get paid per-procedure. Under Medicare's Inpatient Prospective Payment System (IPPS) and most commercial inpatient contracts, the hospital gets one lump-sum payment per admission determined by which DRG (Diagnosis-Related Group) the case falls into.

The current Medicare system is MS-DRG (Medicare Severity DRGs), with about 770 distinct DRGs. Each DRG has:

How a case groups into a DRG

  1. Principal diagnosis — the condition determined after study to be the reason for admission. ICD-10-CM.
  2. Major Diagnostic Category (MDC) — mapped from the principal diagnosis (e.g., MDC 4 = diseases & disorders of the respiratory system).
  3. Surgical vs. medical partition — if a relevant OR procedure was performed, the case goes to a surgical DRG; otherwise medical.
  4. Severity adjustment — secondary diagnoses are checked for CC (Complication or Comorbidity) or MCC (Major Complication or Comorbidity) status. Many DRG triplets exist as "with MCC / with CC / without CC/MCC."
▶ DRG triplet example — heart failure

A patient admitted with acute systolic heart failure (I50.21) will group into one of three DRGs:

  • DRG 291 — Heart Failure & Shock with MCC (relative weight ~1.42)
  • DRG 292 — Heart Failure & Shock with CC (relative weight ~0.96)
  • DRG 293 — Heart Failure & Shock without CC/MCC (relative weight ~0.68)

If the patient has acute kidney injury (N17.9, an MCC) documented and coded, the case groups to DRG 291. If only documented as "renal insufficiency" (no MCC), it may group to DRG 292 or 293 — paying potentially tens of thousands less. This is why Clinical Documentation Improvement (CDI) is a massive enterprise and a major AI use case: capturing every legitimate CC/MCC in the documentation.

DRG validation: where audits happen

Payers conduct DRG validation audits (pre-pay or post-pay) to verify the principal diagnosis, secondary diagnoses, and procedures coded support the DRG billed. The most common DRG-shift findings:

AI for DRG validation reads the discharge summary and full chart, identifies what diagnoses are supported by documentation per ICD-10-CM Official Guidelines, and compares to what was actually coded. The legal framework is significant: improperly upcoded DRGs can trigger False Claims Act exposure.

Lesson 5: HCC coding and risk adjustment — how MA plans get paid

Medicare Advantage plans receive a per-member, per-month (PMPM) capitation payment from CMS. That payment is risk-adjusted: sicker members generate higher payments. The mechanism is HCC (Hierarchical Condition Category) coding and the RAF (Risk Adjustment Factor) score.

How HCCs work

CMS maintains a mapping from ICD-10-CM diagnosis codes to HCC categories. The current CMS-HCC v28 model has about 115 HCCs. Each HCC has a coefficient (its relative weight). For each member, the plan sums:

The sum is the member's RAF score, normalized so a typical FFS Medicare beneficiary equals 1.0. A member with a RAF of 1.7 generates 70% more PMPM revenue than one at 1.0.

HCCDescriptionExample ICD-10 maps
HCC 17Diabetes with Acute ComplicationsE11.10, E11.11
HCC 18Diabetes with Chronic ComplicationsE11.21, E11.22, E11.40, E11.51
HCC 19Diabetes without ComplicationE11.9
HCC 85Congestive Heart FailureI50.21, I50.22, I50.23
HCC 108Vascular DiseaseI70.x, I73.9

Hierarchy

HCCs hierarchical — if a member has both HCC 17 (Diabetes with Acute) and HCC 19 (Diabetes without), only HCC 17 counts. The more severe code in the same hierarchy trumps the less severe.

Why this matters for AI

Risk adjustment is one of the largest dollar levers in MA. Major use cases:

▶ The enforcement reality

Improper HCC coding is a major DOJ and OIG focus. Several MA plans have settled False Claims Act cases for hundreds of millions of dollars over HCCs that were coded without documentation support. AI that surfaces "suspects" must also surface the evidence supporting them, must enforce MEAT criteria, and must log who reviewed and accepted each code. Any vendor selling suspect-identification AI without these controls is selling legal exposure.

Self-check
A member had I50.9 (heart failure, unspecified) documented in a 2023 progress note with no current-year encounter. The plan wants to know if it can be submitted for the 2024 risk adjustment payment year. What's the answer?

No. Risk adjustment diagnoses must be from a face-to-face encounter in the data collection year, by an acceptable provider type, documented and supported (MEAT). A diagnosis from a prior year alone does not establish current-year status. Models must enforce date-of-service eligibility, not just "did this code ever appear for this member."

Why is E11.9 (Diabetes without complications) less valuable from a RAF perspective than E11.22 (Diabetes with diabetic chronic kidney disease)?

They map to different HCCs. E11.9 maps to HCC 19 (Diabetes without Complication), a lower-coefficient category. E11.22 maps to HCC 18 (Diabetes with Chronic Complications), a higher-coefficient category. If both are clinically true and documented, the more specific code captures the higher HCC. This is also why "coding to highest specificity supported by documentation" is the operative legal standard — not "coding to whatever pays most."

Certifications to layer in during Step 2

At least one engineer or clinical informaticist per pod should pursue these. They translate the lessons above into operational fluency:

CredentialIssuerFocusEffort
CPC — Certified Professional CoderAAPCOutpatient and physician-side coding. The single most useful credential for AI builders working with claims data.~80–120 hrs study; 4-hour exam
CCS — Certified Coding SpecialistAHIMAInpatient + outpatient, includes ICD-10-PCS and DRG. Required reading for anyone building DRG validation AI.~120–180 hrs; harder exam
CPMA — Certified Professional Medical AuditorAAPCAudit methodology, sampling, payer policy. Best fit for payment integrity teams.~80 hrs; requires CPC or equivalent
CRC — Certified Risk Adjustment CoderAAPCHCC coding, risk adjustment audits, RADV. Essential for MA-focused builds.~80–100 hrs

Order of priority depends on use case: CPC first if you're broad, CCS first if you're inpatient-heavy, CRC first if you're MA risk adjustment, CPMA first if you're payment integrity.

Step 2 Glossary

NCCI PTP
National Correct Coding Initiative Procedure-to-Procedure edits. Code pairs that should not normally be billed together.
MUE
Medically Unlikely Edit. Cap on units of a single code billable on one date of service.
MAI
MUE Adjudication Indicator (1, 2, or 3). Determines how strictly an MUE is enforced.
NCD
National Coverage Determination. National Medicare coverage policy.
LCD
Local Coverage Determination. MAC-specific coverage policy. Often paired with an LCA listing covered codes.
MAC
Medicare Administrative Contractor. Regional CMS contractors that process Medicare claims and issue LCDs.
InterQual / MCG
The two dominant licensed clinical-criteria products used by payers for UM.
DRG / MS-DRG
Diagnosis-Related Group / Medicare Severity DRG. Inpatient payment classification system.
CC / MCC
Complication or Comorbidity / Major CC. Secondary diagnoses that shift the DRG to a higher-paying tier.
HCC
Hierarchical Condition Category. CMS-defined diagnosis grouping used in risk adjustment.
RAF score
Risk Adjustment Factor. Per-member multiplier on the base PMPM payment.
MEAT
Monitoring, Evaluating, Assessing, Treating. The documentation standard for valid HCC capture.
RADV
Risk Adjustment Data Validation. CMS audit of MA plan HCC coding.
CDI
Clinical Documentation Improvement. Practice of improving documentation completeness for accurate coding and reimbursement.

Frequently asked questions

Can I use NCCI tables commercially in a vendor product?

NCCI files are published by CMS and free to use. You can build them into your product. InterQual and MCG criteria are licensed and you cannot. Always confirm the licensing of any criteria, code set, or grouper you embed.

Are DRG groupers free or licensed?

CMS publishes the MS-DRG grouper logic and code; you can implement it from the specifications. Most vendors use a commercial grouper (3M APR-DRG is licensed, for example) for clinical and operational reasons — but the MS-DRG version is reproducible from public CMS materials.

How fresh does my edit data need to be?

Quarterly for NCCI PTP and MUE. Annual for MS-DRG and HCC models (CMS publishes annual updates). InterQual and MCG annual. Build a dependency-update calendar; "stale codes" is a common silent failure mode.

What about commercial plans — do they use NCCI?

Many do, often with their own additional edits layered on. Some use proprietary edit engines like ClaimsXten (now Lyric) or Optum's policy library. Your pre-bill AI should know which payer applies which edit set — payer-specific edit profiles are a real feature.

Is HCC coding still as important under the v28 model?

Yes — but the economics shifted. CMS-HCC v28 dropped several codes from the model entirely (around 2,000 fewer ICD-10s map to HCCs), changed coefficients, and increased the constraint that diagnoses be sufficiently specific. Suspect-identification models trained on v24 logic will surface codes that no longer pay. Refresh your mapping tables for each payment year.

Self-check · End of Step 2

Did you absorb Step 2?

Questions grounded in real curriculum material. No certificate at this stage — the certificate is earned at the end of the track via the final exam. Honor system. Unlimited retakes. Wrong answers come with explanations.

← Previous
Step 1: Foundation