Medicare Compliance & Reimbursement - 2001 Issue 4
Solve ROS Documentation Mystery Watch for Language Clues And Win the Reimbursement Prize
Subscribe or sign in to view the full article.
Article Overview
This article covers review of systems (ROS) documentation in emergency department evaluation and management coding, with emphasis on distinguishing ROS from history and exam content. It discusses how documentation language, source attribution, completeness of system review, and exception language can affect whether a chart supports a higher or lower ED E/M level. The piece is aimed at coders and billing professionals who review emergency department records and want to understand general ROS documentation pitfalls and guideline-based considerations.
Why This Topic Matters
ROS documentation is a common source of coding discrepancies in emergency department charts. Understanding how the documentation is organized and interpreted helps coders assess whether the record supports the reported E/M level.
Article Sections
-
ROS, HPI, and exam overlap
Introduces the documentation challenge of separating review of systems content from history and physical exam material in emergency department encounters. Focuses on how chart language can create ambiguity for coders.
-
Language clues and documentation source
Explains the kinds of wording that may indicate a patient-reported ROS versus information that appears more consistent with exam findings or other history elements. Also addresses where ROS information may originate in the record.
-
Blanket ROS statements
Discusses broad negative statements and template-style documentation, with attention to how completeness of the review is reflected in the chart. Highlights the importance of specific system documentation in ROS narratives.
-
Level-five caveat and documentation exceptions
Reviews circumstances in which a complete ROS may not be feasible and the documentation considerations tied to that exception. Covers the need for clarity about patient condition and the source of historical information.
-
ROS significance in E/M level selection
Summarizes the relationship between ROS extent and emergency department E/M leveling. Notes the general documentation expectations associated with different levels and the impact of incomplete ROS documentation.
-
Body systems recognized for ROS
Lists the body systems identified in the source note as recognized for ROS under the referenced CPT guidelines.
What You Will Learn
- How ROS documentation is distinguished from HPI and exam content in emergency department records
- Why wording and source attribution matter when charting ROS information
- How broad negative statements and template language affect ROS review
- What general documentation considerations apply when an ROS exception is claimed
- How ROS completeness relates to emergency department E/M level selection
- Which body systems are recognized for ROS in the referenced guidance
Who Should Read This
- Medical coders
- Emergency department billing staff
- Compliance reviewers
- Physician documentation specialists
Codes Discussed
Code Ranges Discussed
Subscribe or sign in to view the full article.


Quick, Current, Complete - www.findacode.com