Using a code hub page to cross-check a claim before it goes out
Most claim errors are visible before submission if someone looks at each code in one place, with its rules attached, instead of looking at codes in a chargemaster where they appear as bare numbers with prices. That is what a code hub page on this site is for. Every code has a page at /code/ followed by the code itself, gathering the information a reviewer needs for that single code: its official description and place in its code family, and for procedure codes, the payment and edit context that decides whether a line built on it will survive. This guide turns that page into a repeatable pre-submission routine.
Start with identity: is this the right code at all
Read the description on the hub page against the documentation, word by word. Confirm the code is active and billable for the date of service: diagnosis hub pages sit inside families that list billable codes only for FY2027, and HCPCS pages list active codes from the October 2026 quarterly file, so a code you cannot reach on a hub page is a warning in itself. Confirm the family context by following the category or group links from the hub page. Sibling codes are the most common correct answers to a wrong first choice, and the hub page puts them one click away instead of one search away.
Procedure-to-procedure counts: know a code's bundling footprint
For procedure codes, the hub page summarizes NCCI procedure-to-procedure edit involvement: how many active edits list this code as Column 1, how many as Column 2, in the current quarterly edit data used by the site. A code with a large Column 2 count is bundled into other services frequently, so any claim pairing it with a comprehensive code deserves a pair check. A code with a large Column 1 count absorbs many components, so review the claim for separate lines that its edits already include. The counts do not decide any specific pair; they tell you where to look. Decide the pair itself in the NCCI checker, which returns the exact edit, the column order, and the modifier indicator for the two codes and date in question.
MUE: check units before the payer counts them for you
The hub page shows the medically unlikely edit value for the code where CMS publishes one: the maximum units generally plausible for one patient on one date. Compare your line units to that number as a hard review trigger. Units at or under the limit pass this gate, though documentation must still support them. Units above it need immediate explanation: a unit definition misread is the usual cause, especially for drug codes where units follow the dosage amount in the description, and for time or mileage based codes where rounding habits inflate totals. Correct the calculation from the documented amount administered, supplied, or traveled. Do not split lines or add modifiers to evade a unit limit without a payer rule that supports the approach for the documented facts.
Fees: price the line while you can still fix it
Where a code is priced under the Medicare Physician Fee Schedule, the hub page connects the code to its fee schedule context: relative value components and locality based amounts through the site's calculators. For a full calculation with a chosen locality, setting, and date of service, continue into the Medicare fee lookup, which applies the CY2026 or CY2027 figures by date as described in the fee schedule guide. Pricing at review stage catches a class of errors that coding checks miss: facility versus non-facility setting mismatches, wrong year pricing on January boundary claims, and expected payment variances that reveal a wrong code more clearly than the description did.
Status indicators: some codes do not pay separately at all
Fee schedule and outpatient status indicators on or linked from the hub page flag codes that are bundled into other services, not valid for the payer or setting, restricted, or contractor priced rather than schedule priced. Treat a status warning as a stop sign, not fine print. If a code is shown as bundled or not separately payable in the setting on your claim, the fix is structural: report the payable service correctly and keep the bundled item off the paid lines as the applicable rules require, rather than appending modifiers in search of an exception the status does not offer.
The full routine, claim by claim
- For each diagnosis: open its hub page, confirm billable status, specificity, and family fit, and confirm the diagnosis supports the lines it will be pointed to.
- For each procedure and supply code: open its hub page, read the PTP counts, MUE value, fee context, and status indicators.
- For each procedure pair the counts flag: run the exact pair in the NCCI checker and act on the indicator, removing the bundled code for indicator 0 or documenting true distinctness for indicator 1.
- For the claim as a whole: enter all codes in the batch checker so pairs and problems you did not suspect surface in one pass.
- Reconcile units, laterality, modifiers, and diagnosis pointers against the documentation one final time, using the modifiers list for any modifier wording you have not re-read this session.
Worked example
A claim carries a comprehensive procedure, a second procedure from the same family, a drug code with high units, and three diagnoses. Hub review shows the second procedure has a large Column 2 footprint; the pair check confirms an active edit with indicator 0, so the second procedure comes off the claim instead of denying after submission. The drug hub page shows an MUE below the billed units; recalculation from the documented dose and the unit definition in the description brings units under the limit. The fee lookup prices the main procedure in the non-facility setting and matches the expected contract amount, confirming setting and year. One diagnosis hub page reveals a more specific sibling that matches the documented laterality, and the pointers are rebuilt so the drug line points to the condition it treats.
Search from the homepage, verify on the hub page, test pairs and units, price the result, then batch check the whole claim. Five minutes inside that loop, before the claim goes out, is the cheapest denial management a practice can buy.