Teach a new way to scour op notes to capture all codes

Why This Topic Matters

Operative notes can contain the information needed to support complete coding, but it may be difficult to recognize when notes are reviewed in a traditional format. This article is relevant to organizations that want a more systematic way to analyze surgical documentation and reduce missed or incorrectly reported services.

Article Sections

1. Plain-English review approach for operative notes

   Introduces a workflow for breaking operative documentation into basic elements that are easier to review for coding purposes. The section emphasizes a structured way to scan notes for relevant information.

2. Identifying procedures, locations, and diagnoses

   Discusses how documentation can be organized to connect what was done with where it was done and why. The section describes a simple mapping approach used during code review.

3. Validating code choices and applying edit checks

   Covers the need to compare code selection against official references, payer guidance, and edit tools before final claim submission. The section also addresses review of services that should not be reported separately.

4. Correction

   Provides a follow-up notice that clarifies a printing error and explains that certain items referenced in the article were not intended to be treated as separately reportable.