Modifier 25 and the Templated Review of Systems

Two separate questions must both be answered yes.

(1) Is there a significant, separately identifiable E/M above and beyond the procedure? The diabetes medication change (metformin increase in response to A1c 8.2) and the hypertension management are clinically distinct from the knee injection. On the substance of the work, yes.

(2) Is that work documented? Partially. The diabetes plan is documented, but there is no assessment entry for diabetes, no statement of the problem status, and no documentation of the BP value discussed. That is thin but not automatically disqualifying.

Level determination: Under current outpatient E/M rules, level is set by medical decision making or total time - history and exam are not required elements. Prescription drug management is a moderate-level MDM element, so 99214 could be supported on MDM alone if the record shows the provider made a decision about a chronic illness with exacerbation or progression. The metformin increase tied to an A1c of 8.2 approaches that, but the note never frames the diabetes as exacerbated or progressing.

Determination: Do not release 99214-25 on this note as written. Query the provider to confirm the status of the diabetes at this visit and whether the BP was addressed clinically. If confirmed, 99214-25 is defensible. If not confirmed, 99213-25 is the ceiling, or bill the procedure alone if the E/M is not separately identifiable.

The ROS is cloned documentation and must be disregarded.

• The same ROS paragraph appears in every note, including nurse visits where no provider performed a history. That is the definition of cloned/copy-paste documentation and is a standing target for payer audits and OIG scrutiny.
• It is also internally contradicted: the note documents a knee-only encounter yet reports 14 systems reviewed. An auditor reading two consecutive notes with identical ROS will question the entire record, including the parts that are accurate.
• Key point: the ROS cannot be used to support the level. Under current E/M rules it would not raise the level even if it were genuine, so it contributes zero coding value and 100% of the liability.

Effect on the analysis: ignore the ROS entirely. The E/M level must stand on the documented MDM (or time). This actually simplifies the decision - the only defensible basis for 99214-25 is the diabetes decision making, which is precisely the part that needs a query.

Recommendation to the practice: remove the auto-text from the template, or configure it to populate only when the provider actively selects systems. Consider a monthly clone-detection report (identical note bodies across more than N encounters).

To the provider (brief, case-specific):

• The knee injection is clean: 20610-RT, no global-day issue, no NCCI conflict with the E/M when modifier 25 is supported.
• The E/M is not billable at 99214 on this note. The diabetes management is real work, but the note does not say what the problem was, what the BP was, or why the metformin changed at this encounter.
• If you confirm at the time of the query that the diabetes was assessed and the BP addressed, we will bill 99214-25. Otherwise we will bill 99213-25 or the procedure alone.
• Your ROS template is auto-filled and does not reflect your encounter. It cannot help your level and it will hurt you in an audit.

To coding leadership:

1. Hold the claim pending query; do not release 99214-25 on assumption.
2. Return the 99214-25 modifier decision to the provider in writing with the specific missing elements.
3. Log the clone-detection finding and route it to the EHR build team.
4. Add a targeted education point: modifier 25 requires documentation that the E/M was separate and above the procedure - 'we also discussed' in the plan without an assessment rarely survives review.
5. Do not re-bill or re-level the claim upward after the fact without a properly documented, dated clarification.