Template Cloning, Modifier 25, and the Office Manager's Instructions
At a four-physician family practice, a newly hired coder reviews 20 charts and finds three things. First, every note in the EHR contains a 12-system review of systems and a detailed examination; the physicians say they usually ask only about the presenting problem, that the template fills the rest automatically, and that they sign without reading those sections. Second, the office manager instructs her to append modifier 25 to every E/M on days a nurse gives a scheduled vitamin B12 injection, and to 'use 99214 for anyone with diabetes.' Third, a coworker suggests changing a Medicaid patient's principal diagnosis to a better-paying one 'since the note supports either.' The practice bills Medicare and Medicaid.
1. Classify each of the three findings and state what the coder should do about each.
Read the worked answer
Finding 1 - documentation integrity problem, with downstream coding consequence. An auto-populated ROS and exam represent services not performed. If the code level was driven by those elements, the claim is inaccurate. Action: do not code from the templated sections; query the physician for the elements actually performed, and raise the template configuration to the compliance officer as a system fix - a template that fabricates clinical content is a recurring error generator, not a one-chart problem.
Finding 2 - coding directive that would produce false claims if followed. Modifier 25 is not a routine add-on for injection days, and 99214 has no relationship to a diabetes diagnosis. Action: do not follow the instruction; document the directive in writing and escalate through the compliance chain rather than arguing it out with the office manager.
Finding 3 - potential fraud, plainly. Selecting a diagnosis for payment rather than for clinical accuracy, when the record does not support it, is a false claim. 'The note supports either' is not a defense; the principal diagnosis must be the condition chiefly responsible for the encounter as documented.
Across all three: the coder is personally exposed. 'Knowingly' includes deliberate ignorance and conscious disregard - signing claims under a directive you know is wrong does not insulate you. Escalate, and expect self-disclosure and refund of identified overpayments within the applicable 60-day window.
2. When is modifier 25 actually supportable on a B12 injection day, and what documentation is required?
Read the worked answer
Modifier 25 signals that on the same day as a procedure or other service, the physician provided an evaluation and management service that was significant, separately identifiable, and above and beyond the usual pre-, intra-, and post-procedure work of that procedure.
Supportable: the patient presents for a problem (say, worsening fatigue and new paresthesias) that requires a history, examination, and medical decision making in its own right, and the physician documents that evaluation; the scheduled B12 injection is given at the same visit by the nurse. Report the E/M with modifier 25 and the injection administration separately.
Not supportable: the patient is in solely for the scheduled injection, the physician's note says only 'continue B12, no new complaints,' or the only documented content is the decision to give the injection that was already ordered. A nurse-administered injection alone does not generate a billable E/M at all, with or without modifier 25.
Documentation required: a separately identifiable history, exam, and medical decision making for the problem, recorded such that the work can be distinguished from the injection. If the same elements are being counted toward both the E/M and the injection service, the modifier is not supported. Blanket modifier 25 policies are a classic audit target and are indefensible chart by chart.
3. The coworker's diagnosis suggestion - what are the rules, and what is the practical risk?
Read the worked answer
Rule: code what the provider documented. The principal diagnosis is the condition established after study to be chiefly responsible for the encounter. Two diagnoses are not interchangeable just because a claim will pay under either; the record has to support whichever is reported, and the selection is a clinical determination, not a revenue determination.
Secondary rule: if the documentation genuinely supports either, that ambiguity is itself a query - ask the provider which condition was chiefly responsible, rather than choosing.
Practical risk:
- Altering a diagnosis to increase payment is a false claim whether or not the underlying care was rendered. The service being real is not a defense to a misdescribed claim.
- Medicaid and Medicare both run data analytics; a diagnosis pattern that shifts when a payer changes is a recognizable signature.
- Individual liability attaches to the person who made the entry, not only to the practice. 'My coworker told me to' has never been an effective defense.
- Once identified, the error must be corrected and any overpayment returned; letting it stand after discovery converts a mistake into a knowing violation.