General Surgery Coding Alert - 2012 Issue 10
E/M Coding: Reasons Your Review of Systems Documentation Could Be Sabotaging Your Claims
Subscribe or sign in to view the full article.
Article Overview
This piece discusses Review of Systems documentation in evaluation and management coding, especially how common shorthand language may be viewed by auditors and payers. It covers CMS guidance, carrier and payer policy perspectives, and examples of documentation phrasing that may affect whether a ROS is treated as complete. The article is aimed at physicians, emergency department coders, auditors, and compliance staff who need to understand documentation expectations for E/M claims.
Why This Topic Matters
ROS documentation can influence whether an E/M service is supported on the claim and how it is reviewed during audits. Understanding payer and CMS expectations helps reduce documentation risk and improves compliance with medical necessity standards.
Article Sections
-
Overview of ROS documentation concerns
Introduces the documentation issue and explains why certain ROS language draws attention in claim review. It frames the topic in the context of E/M coding and audit risk.
-
Medical necessity and CMS guidance
Summarizes CMS-related guidance on documentation, payment, and the role of medical necessity in E/M services. It also notes how documentation volume and history conflicts can affect review.
-
Payer policy perspectives
Reviews how various payers and Medicare contractors have approached ROS language and documentation consistency. The section highlights differing interpretations and policy concerns.
-
Examples of problematic ROS phrasing
Describes categories of ambiguous or overly broad ROS statements that may not receive credit in review. It focuses on wording patterns rather than specific coding outcomes.
-
Documentation approach and example
Presents a general documentation approach intended to strengthen ROS completeness and includes a sample clinical note excerpt. The section illustrates how documentation may be structured in practice.
What You Will Learn
- How ROS documentation is evaluated in the context of E/M claims
- Why payer scrutiny can create compliance risk for routine documentation phrases
- How CMS guidance relates to medical necessity and documentation support
- What types of wording may be considered too vague in ROS documentation
- How documentation structure can affect whether a ROS is treated as complete
Who Should Read This
- Physicians
- Emergency department coders
- Medical coders
- Clinical documentation improvement specialists
- Compliance staff
- Auditors
- Practice managers
Codes Discussed
Subscribe or sign in to view the full article.


Quick, Current, Complete - www.findacode.com