How should a coder handle separate procedures vs bundled codes for the same encounter?

• A. Always unbundle procedures to maximize payment.
• B. Treat all procedures as bundled regardless of services.
• C. Use the lowest common denominator; ignore payer rules.
• D. Identify separately identifiable services that meet payer rules; avoid unbundling; apply appropriate modifiers when necessary.

Answer: (D)

The key idea is to code based on payer rules and the reality of what was actually performed, not on a desire to maximize payment. Some components of a procedure or encounter are bundled together because they’re considered part of a single service. Other times, parts of care are truly separate and separately billable, but only if the payer’s rules and the documentation support it.

Identify services that are truly separately identifiable and allowed to be billed apart from the bundled work. If the documentation shows a distinct service or component that stands on its own and the payer’s guidelines (like NCCI edits and modifier rules) permit separate payment, report those services separately. When you do bill separately, use the appropriate modifier to indicate that the second service was distinct from the first and thus may be paid separately, provided the payer accepts that modifier and the documentation supports it.

Avoid unbundling simply to increase payment. Unbundling without payer authorization risks audit findings and penalties because many services are bundled by design. Instead, rely on payer rules and thorough documentation to determine what can be billed separately, and apply modifiers only when they accurately reflect a distinct service.

In short: bill only what payer rules allow as separately identifiable services, support it with clear documentation, and use modifiers to show distinction when appropriate.