RevolutionEHR Insights ™

Release Notes have been moved to RevHelp

Doc/Coding tips

It All Starts with the Reason for Visit
Posted: June 5, 2018

It’s been said that the reason for visit (RFV) “drives the bus” for an encounter.  That is to say that doctors should carefully tailor their case history, physical exam, and medical decision making based on the reason the patient is being seen.  As an example, a patient presenting for an irritated right eye likely requires a different exam than one who complains of recent onset flashes and floaters.  In both instances, a case history, physical exam, and assessment and plan will take place.  But “how” the doctor proceeds through the visit will be quite different.  And it’s that “how” that should determine the final coding for the encounter.

Auditors know this, as well.  If the patient presenting for an irritated right eye has a comprehensive case history and physical exam performed, the doctor can expect some questions in an audit surrounding the necessity of that level of service given the reason for visit.  If the doctor can provide a valid rationale, great.  If they can’t, however, recovery of money by the 3rd party should be expected.

In the end, if the doctor provides exactly what’s necessary to evaluate and manage the reason the patient is being seen that day, no more and no less, then she’ll be in great shape.  This all starts with a clear and specific reason for visit so be sure that you’re including that documentation.





View Status Page
Updates Prior to 2018