Incident-to billing is one of those rules that's perfectly legitimate when you follow it and quietly risky when you assume you are. It lets services delivered by certain non-physician providers be billed under a physician when specific conditions are met. The trouble is that the conditions are precise, and a busy practice can satisfy them most days and miss them on exactly the days that get reviewed.

The conditions are the whole game

Without turning this into a rulebook, incident-to generally depends on things like an established patient with an existing plan of care, the physician's involvement in that care, and the right level of physician presence in the practice when the service is provided. Each of those is a factual condition. If it isn't true on a given day, the billing should reflect that, and that's the part practices skip.

Where it goes wrong

  • A new problem gets handled as incident-to, when a new presentation often shouldn't be billed that way.
  • The supervising physician wasn't present in the way the rule requires that day, but the billing didn't change.
  • The documentation doesn't show the physician's involvement in the plan of care at all.
  • Nobody can reconstruct, after the fact, who was in the building and what their role was.
Billing and clinical staff reviewing documentation
Incident-to isn't risky because it's wrong. It's risky because the conditions are easy to assume.

Make the conditions provable

The fix isn't to avoid incident-to; it's to make its conditions visible in the record. Build prompts into your workflow that confirm the patient and plan-of-care status, capture physician involvement, and reflect who was present. When the conditions are documented as a matter of routine, a legitimate billing practice stays legitimate under scrutiny instead of depending on memory.