ESRD monthly capitation payment billing: 90951-90970 explained.

The ESRD monthly capitation payment (MCP) is a bundled monthly fee, not a fee-per-visit code, and the code you select is decided by two variables at once: the patient's age band and the number of face-to-face physician visits furnished during the month. Get either variable wrong — miscount the visits, misjudge whether a month was full or partial — and the claim either pays at a lower tier than the care actually delivered supports, or denies as a duplicate against another physician's claim for the same period. This guide walks the full code matrix, the From/To date mechanics for partial months, the one-per-patient-per-month rule, and the single documentation error that costs nephrology practices the most MCP revenue.

Why the MCP isn't billed like a normal E/M

Once a patient is established on outpatient maintenance dialysis, the physician work of managing that dialysis — reviewing labs, adjusting the prescription, managing anemia and mineral-bone complications, coordinating the vascular access, seeing the patient face-to-face — is paid as a single bundled monthly service rather than as a series of separately billed encounters. That's the entire logic of the MCP code family, 90951–90970: one code represents a month (or a partial month) of related dialysis management, selected by the patient's age and, for in-facility care, how many face-to-face visits actually happened. There's no add-on for a fifth visit in a 4-or-more month, and there's no partial credit for a visit that happened but isn't documented as a distinct, dated, signed encounter.

Full-month in-facility codes: 90951–90962

Twelve codes cover a full calendar month of in-facility (non-home) maintenance dialysis management, organized as four age bands crossed with three visit-count tiers. A fourth visit scenario — zero face-to-face visits in the month — doesn't have its own code in this range; it's handled through the less-than-full-month mechanism below, or through whatever documentation and medical-necessity standard your MAC's coverage policy attaches to a zero-visit month, which is worth confirming directly with your contractor rather than assuming a default treatment.

Read the table by row first, then column: age band decides which row applies, and it doesn't change mid-month even if a birthday falls inside the billing period — use the age band that applied for the majority of the month, and if your practice has a different convention documented with your MAC, follow that instead. Visit count decides which column applies, and it's counted against the calendar month being billed, not a rolling 30-day window.

Full-month home dialysis codes: 90963–90966

Home dialysis — peritoneal dialysis or home hemodialysis — uses a separate, simpler four-code set for a full month of management. There's one code per age band, and critically, no visit-count tiering at all:

This is a real structural difference from in-facility billing, not a simplification for convenience: a home dialysis patient managed with two physician contacts in a month and one managed with six both bill the identical code, because the monthly management model for home dialysis doesn't tie payment to visit frequency the way in-facility care does. A coder trained on the in-facility matrix who tries to apply visit-count logic to a 90966 claim is solving a problem that code family doesn't have — the error runs in the other direction from the usual one, but it still produces an incorrect code selection. Home dialysis training codes, the virtual-supervision allowance for training, and the unresolved telehealth-modifier question specific to 90966 are covered in our home dialysis billing: peritoneal dialysis and home hemodialysis codes guide.

Less-than-full-month codes: 90967–90970 and the From/To date mechanics

The remaining four codes cover ESRD-related service that doesn't span a full calendar month under a given physician's management, billed per day rather than as a flat monthly unit.

Four scenarios trigger this family, and each one has a specific date-span rule:

• 1Dialysis starts mid-month. The From date is the date maintenance dialysis actually began under this physician's management (or the date the patient came under the physician's care, if dialysis was already established), and the To date is the last day of the calendar month. Units are billed for each day within that span.
• 2Mid-month transplant. The To date is the day before the transplant, since post-transplant management shifts to a different billing model entirely — don't extend the MCP span through the transplant date.
• 3Mid-month transfer between facilities or physicians. Each physician bills a partial-month code for only the days they actually managed the patient, and the two spans have to be coordinated so they don't overlap — see the one-MCP-per-month rule below.
• 4Death during the month. The To date is the date of death; the span runs from the first of the month (or the start of this physician's management, if later) through that date.

Get the date span wrong in either direction and the per-day unit count won't reconcile: too few units for the days actually managed, and the claim underpays for care that was delivered; a From date that predates the physician's actual involvement, or a To date that runs past a transfer or death, overstates the span and invites a payer request for records that the documentation won't support. Pull the exact From and To dates from the chart at the time of the transition — the day of transfer, the date of death on the death certificate, the transplant date from the operative note — rather than approximating from the billing calendar after the fact.

The one-MCP-per-month rule

Only one MCP service is payable per patient per calendar month, full stop, regardless of how many physicians were actually involved in that patient's care during the month. This rule sits above the entire code matrix above it and is the source of a disproportionate share of MCP-related denials, because it's a coordination problem between two billing parties, not a coding decision either one makes alone.

The scenario that trips this up most often is a mid-month coverage handoff: patient transfers from Physician A's panel to Physician B's, or a group restructures on-call coverage mid-month and two different providers end up documenting MCP-qualifying visits in the same calendar month. If Physician A bills a full-month code (90951–90966 range) covering the whole month, and Physician B also bills a partial-month code (90967–90970) for the days after the transfer, one of the two claims is going to deny as a duplicate — the payer's system doesn't reconcile the split for you. The fix has to happen before either claim is submitted: both physicians' billing offices need to agree on the exact transfer date, Physician A bills a less-than-full-month code ending the day before transfer, and Physician B bills a less-than-full-month code starting the day of transfer. Waiting until one claim denies to sort this out turns a five-minute coordination call into a multi-week reconciliation with two different billing departments.

The documentation short-by-one-visit error

This is the single most expensive recurring error in the MCP code family, and it doesn't behave like a normal billing mistake, because it never generates a denial. The MCP is banded by face-to-face visit count within the month — four-or-more, two-to-three, or one — and each band pays at a different rate. If the physician actually saw the patient four times during the month but only three of those visits are documented as a distinct, dated, signed face-to-face encounter, the claim has to be coded and paid at the 2–3 visit tier even though the fourth visit genuinely happened. There's no code for "we saw the patient four times but can only prove three" — the documentation gap is the billing outcome.

What counts as a visit for this purpose is specific: a face-to-face encounter between the patient and the billing physician (or, under your practice's normal incident-to and supervision arrangement, a qualifying non-physician practitioner), independently dated and signed as its own note. A chart addendum mentioning "spoke with patient today" without a distinct visit note doesn't establish a countable visit on audit. A rounding note written for four patients in a batch, where one patient's individual encounter isn't separately documented, has the same problem. The clinical work may have been done correctly and completely — the billing failure is purely in whether the record can independently prove the visit count the claim is asserting.

Because this error never denies, it also never surfaces in a denials work queue the way a rejected claim does. A practice can run this way for months, paid consistently at the 2–3 visit tier for patients actually seen four times, and nothing in the standard AR workflow flags it, because every one of those claims paid. The only way to catch it is to audit visit-count documentation against actual physician schedules and note logs before the claim goes out — a monthly reconciliation, not a claims-level QA step, since the claims themselves look clean.

Frequently asked questions

Related resources

• Nephrology billing and coding guide
• Prior authorization for ESAs and dialysis services in nephrology
• Dialysis vascular access billing: fistula, graft, and angioplasty CPT
• Denial management