Cloned documentation on OIG radar screen in 2014May 23rd, 2014 - Scott Kraft
One of the areas where the OIG has its sights set in 2014 is on physician documentation. The OIG plans to review documentation of E/M services looking for what it describes as “documentation vulnerabilities.”
Put more specifically, the OIG reports that Medicare Administrative Contractors (MACs) have seen an increase in instances of “identical documentation across services,” noting that code selection for E/M encounters is based on the documentation for the services rendered.
If it sounds like they’re looking for cloned notes, it’s because they are looking for cloned notes. And with documentation generated by electronic health records (EHR) systems on the rise, and providers using EHR system tools that enable documentation to be carried forward to a new note, it’s likely that the OIG won’t have to look to far to see more cloning than they are comfortable with seeing.
There’s no doubt that the bells and whistles of EHR systems have changed the way that physicians document E/M encounters.
EHR systems make it easier to provide more robust documentation for each encounter and make it easier to port forward relevant documentation from previous encounters for the provider to review.
After all, there are only so many different ways to report on the fact that a patient is being seen for the same chronic condition when the patient returns to your office on a regular schedule. There are also only so many ways to describe the elements of a review of systems or an examination.
There are two problems, however, that the functionality of EHR is creating from a claims audit perspective. First, in too many instances the documentation for a single patient looks the same from encounter to encounter – across multiple encounters – because of the way in which the provider brings forward documentation.
Second, the provider is choosing to consistently review the exact same systems in the same way for the review of systems and examination across multiple encounters, regardless of the patient’s presenting problem.
Let’s look at the second problem first. Coders, billers and auditors are right to tread very carefully when it comes to second guessing the clinical judgment of the provider when it comes to deciding which systems are medically necessary to review and which exam elements are pertinent to the patient’s visit that day.
There could be a very good reason for what appears to a third-party review to be a review of a system seemingly unrelated to the patient’s presenting problem.
However, when a provider consistently reviews the same components of the same systems in the ROS across the patient population, without regard to the patient’s condition, it will appear suspicious to an auditor. It will look especially suspicious when the result is usage of high-level E/M codes that go beyond the typical practice pattern.
Practically speaking, it stands to reason that the ROS and exam elements would not always be the same across the patient population because patients will show up with different chief complaints at different levels of severity.
The same patient with multiple cloned notes raises a whole new set of problems, especially when documentation is being carried forward from note to note for a long period of time.
One problem is that it becomes harder to determine what the provider addressed during that visit because the note contains a laundry list of the patient’s chronic and acute conditions. The structural integrity of the note, which is intended to represent what happened during that specific visit, becomes compromised.
The problem is exacerbated when the same documentation appears in note after note. Sloppy mistakes begin to occur, including things like the patient’s age contradicting itself in the note because the HPI has been carried forward.
Providers note that patients are often seen for the same conditions over a period of time and, to our earlier point, there are only so many ways to describe that a patient has asthma or COPD or some other condition. When you do bring condition detail forward from the HPI, address that by having the provider add to the HPI details about how the patient is doing on that day. After all, it is the history of the present illness.
On contradictions, it is one of the biggest ways that cloned elements of notes are revealed. Because the information from previous notes is often brought forward by ancillary staff before the encounter, the provider will sometimes add contradictory information. An ROS that is negative for a headache is contradicted by an HPI of severe headaches.
In an era where demands for the provider’s time continue to go up, without payment following closely behind, it is hard to walk away from the time-saving advantages that EHR systems can potentially provide. Just do it very carefully, and know that the auditors are going to be looking closely to make sure there is variety in your notes that reflect the documentation needs of a specific encounter.
If you have questions or comments about this article please contact us. Comments that provide additional related information may be added here by our Editors.
Latest articles: (any category)Chronic Pain Coding Today & in the Future
July 19th, 2021 - Wyn Staheli, Director of Research
July 15th, 2021 - Aimee Wilcox, CPMA, CCS-P, CST, MA, MT, Director of Content
July 14th, 2021 - Aimee Wilcox, CPMA, CCS-P, CST, MA, MT, Director of Content
July 13th, 2021 - Aimee Wilcox, CPMA, CCS-P, CST, MA, MT, Director of Content
June 29th, 2021 - Christine Woolstenhulme, QCC, QMCS, CPC, CMRS
June 16th, 2021 - Aimee Wilcox CPMA, CCS-P, CST, MA, MT and Wyn Staheli, Director of Content Research
June 3rd, 2021 - Aimee Wilcox CPMA, CCS-P, CST, MA, MT and Wyn Staheli, Director of Content Research