The Three Most Dangerous Words in an Operative Note: "Incidental Appendectomy Performed"

Last reviewed: June 2026

Every surgeon has seen it.

You are already in the abdomen.

The appendix is staring at you.

The patient is 42 years old.

You will probably never be back.

And suddenly a dangerous thought enters your brain:

"While I am here..."

Few phrases have caused more surgical debate than the incidental appendectomy.

Some surgeons love them.

Some surgeons hate them.

Some surgeons would rather debate politics at Thanksgiving than discuss whether they should remove a normal appendix.

But regardless of where you stand, there is an important coding and documentation lesson hiding underneath the controversy.

The Appendix That Did Nothing Wrong

Let us be honest.

The appendix has terrible public relations.

Most organs get to spend their lives quietly doing their jobs.

The appendix spends its entire existence being viewed as a future problem.

It is the surgical equivalent of the guy at work who has not done anything wrong but somehow everyone assumes he is eventually getting fired.

So when surgeons are already operating in the abdomen, the temptation is understandable.

The thought process sounds reasonable:

• The abdomen is open.
• The appendix is accessible.
• Future appendicitis is possible.
• Why not remove it?

Simple question.

Complicated answer.

Just Because You Can Does Not Mean You Should

The coding lesson begins here.

One of the most common mistakes in surgical documentation is assuming that every additional maneuver performed during an operation automatically represents a separately reportable procedure.

It does not.

Surgery is filled with activities that are necessary, reasonable, and appropriate, but not separately billable.

The challenge is understanding the difference.

The Operative Note Problem

Many surgeons document operations like they are writing text messages.

Example:

"Incidental appendectomy performed."

That is it.

No rationale.

No findings.

No explanation.

Nothing.

Imagine documenting a Whipple procedure with:

"Some plumbing was rearranged."

The operative note should explain why additional procedures were performed and how they related to the operation.

Not because you are trying to maximize reimbursement.

Because you are trying to accurately tell the story of the case.

The Real Value of Documentation

Good documentation does several things:

• Explains physician judgment
• Supports coding accuracy
• Helps future providers
• Improves audit defensibility
• Reflects operative complexity

Most importantly, it captures your thinking.

The operation is not just what your hands did.

It is what your brain decided.

The Residency Problem

Residents spend years learning anatomy.

Years learning physiology.

Years learning operative technique.

Then they graduate and discover that nobody ever taught them how to explain why they performed the operation.

As a result, many notes describe what happened but never explain why it happened.

And "why" is often the most important part.

What Surgeons Should Remember

The next time you are tempted to write:

"Incidental appendectomy performed."

Ask yourself:

Would another surgeon reading this note six months from now understand why I did it?

If the answer is no, the documentation probably needs work.

The Bottom Line

Most coding mistakes do not happen because surgeons are trying to bill too much.

They happen because surgeons document too little.

A great operative note does not simply list procedures.

It explains decisions.

Because surgery is more than technical skill.

Surgery is judgment.

And judgment deserves to be documented.