The Line Between Preventive and Problem Visits That You Cannot Ignore

Preventive visits and problem visits seem straightforward on the surface, but this is one of those areas where I still see consistent confusion in documentation and coding. It is not that the rules are unclear. It is that they are often overlooked in day to day practice. If you are an auditor or are educating providers, this is a topic that deserves regular attention.

Let us start with the key rule. A preventive visit is not the same as a problem visit, even if both happen on the same day.

A preventive service is focused on wellness. It is about age-appropriate screening, risk assessment, and preventive counseling. The patient is presenting with no problem to be addressed, rather the aim of the visit is how to we minimize future disease, injury, or illness for this patient. The goal is prevention and early detection.

A problem-oriented visit, on the other hand, is driven by a specific concern.

It requires evaluation, assessment, and medical decision making related to that issue. This is where E/M guidelines come into play and where the level of service must be supported by documentation.

Here is where things tend to get blurred. A patient comes in for a preventive visit, and during that encounter, additional concerns are addressed. This happens all the time. The question becomes, can both services be reported?

The answer is yes, but only when the key rule is met. The problem-oriented service must be significant and separately identifiable from the preventive service.

This is not about simply mentioning a condition. It is about doing additional work that goes beyond the scope of the preventive visit. If a provider evaluates a new issue, adjusts treatment for a chronic condition, or performs additional assessment that requires medical decision making, that may support a separate problem visit.

However, the documentation must clearly reflect that distinction. If it is not documented, it is not supported from an auditing perspective.



This is where education becomes critical. Providers need to understand that one note is acceptable, but blending everything together can make it difficult to support both services. Instead, the documentation should clearly outline what was addressed as part of the preventive service and what was addressed as a separate problem.

Another important point is medical necessity. Just because a problem is addressed does not automatically mean it qualifies for separate reporting. The work performed must rise to the level of a problem-oriented service.

From an auditor perspective, this is an area that is reviewed closely. If the distinction is not clear, the additional service may not be supported. That can lead to denials or repayment.

When you are teaching this concept, keep it simple and practical. Encourage providers to pause and ask themselves one question. Did I go beyond the preventive service in a way that required separate evaluation and management?

If the answer is yes, then the documentation should reflect that clearly. If the answer is no, then it should remain a preventive service.

At the end of the day, this is not about making documentation more complicated. It is about making it more accurate. Clear separation, supported work, and thoughtful documentation will go a long way in reducing risk and improving compliance.