Part B Insider - 2010 Issue 6
Reader Questions: Count Systems, Not Symptoms, On ROS Levels
Subscribe or sign in to view the full article.
Article Overview
This article addresses a reader question about review-of-systems documentation in an emergency department scenario and the general approach to symptom-based diagnosis coding when no definitive diagnosis is documented. It is aimed at coders, billers, and clinical documentation staff who need to understand how encounter documentation is evaluated for E/M history elements and how broad symptom reporting is reflected in diagnosis selection. The discussion includes ROS level concepts, emergency department E/M context, and the use of ICD diagnosis codes for presenting symptoms.
Why This Topic Matters
Understanding how ROS documentation is interpreted affects evaluation and management coding accuracy and supports consistent handling of encounters where only symptoms are documented. The article is relevant for those reviewing ED notes, history elements, and symptom-based diagnosis coding.
What You Will Learn
- How review-of-systems documentation is characterized in an emergency department encounter
- How symptom-based diagnosis coding is addressed when no definitive diagnosis is documented
- How ROS-level concepts relate broadly to E/M history documentation
- Which types of presenting symptoms may be reflected in diagnosis coding
Who Should Read This
- Medical coders
- Medical billers
- Emergency department coding staff
- Clinical documentation improvement staff
- Revenue cycle professionals
Codes Discussed
Subscribe or sign in to view the full article.


Quick, Current, Complete - www.findacode.com