E/M Coding: Miscoding ROS Level Could Cost You $91

Why This Topic Matters

Accurate ROS documentation can affect whether a visit supports a higher or lower E/M level, which in turn influences compliance and reimbursement. The article helps readers understand why payer expectations and complete history documentation matter in everyday coding workflows.

Article Sections

1. What Is ROS?

   Introduces review of systems as part of the history component of an E/M service and explains who may document it. The section also references general documentation guidance and the broad system categories used in ROS review.

2. Level 1: Single ROS

   Describes the first ROS category and its general relationship to lower-level E/M history support. An example scenario is used to illustrate the type of encounter discussed.

3. Level 2: Extended ROS

   Covers the mid-range ROS category and its general relationship to higher history levels. The section notes that other history elements must also be present and includes an example of the kind of visit discussed.

4. Level 3: Complete ROS

   Explains the broad criteria associated with a more comprehensive ROS review and discusses how payer policies may vary. The section also touches on documentation expectations and the need to align ROS with the overall visit record.

5. Documentation

   Summarizes payer variability in acceptable proof of ROS documentation and emphasizes the need to follow individual requirements. The section also reiterates the relationship between medical necessity, history, and overall E/M support.