Warning: Import Text Properly
Ensure clinical documentation integrity in your electronic health records.
By Michael Stearns, MD, CPC, CFPC
There are advantages and disadvantages associated with the use of imported text in electronic healthcare records (EHRs). Let’s explore efficient documentation practices that support the integrity of the clinical record and prevent exposure to the potential risks of this technology.
Reasons to Be Concerned
The majority of EHRs allow medical providers to enter information into the record as blocks of pre-composed text. Common methods include copying and pasting information from another external source (such as another progress note), the reuse of prior clinical notes, and the use of templates. The Centers for Medicare & Medicaid Services (CMS), members of the federal government, the media, and the Office of Inspector General (OIG) have expressed concern that these practices may contribute to fraudulent behavior among medical professionals. The use of imported text in medical records continues to be an area of focus for the OIG, as noted in its 2014 Work Plan.
Resources: For more information regarding concerns about imported text, see “Letter from Secretary Sebelius and Attorney General Holder to Hospital Chief Executive Officers,” September 24, 2012 (www.modernhealthcare.com/Assets/pdf/CH82990924.PDF) and “Medicare Bills Rise as Records Turn Electronic,” New York Times, September 21, 2012. To view the OIG 2014 Work Plan, go to http://oig.hhs.gov/reports-and-publications/archives/workplan/2014/Work-Plan-2014.pdf.
Benefits of Imported Text in
Patient Care and Provider Efficiency
Imported text in any form can have significant value in medical care, when used properly. Providers have stated that this type of information can provide reminders and serve as a guide toward thorough and complete documentation. It serves as a “checklist” that may encourage clinicians to ask additional relevant questions, perform more detailed examinations, and consider additional diagnoses and management options.
Pulling information forward from a prior visit compels the provider to thoroughly review the prior encounter note while updating it to reflect findings from the current encounter. It’s not uncommon for hurried providers to overlook details from prior documents that may have clinical relevance (see examples in the accompanying sidebar, Modify Text to Warn Users of Inaccurate Information). The pull-forward process has the potential to remind the provider of prior issues or concerns that otherwise could have been missed.
Templates have significant value as tools for patient safety and quality of care. They have the ability to instantiate clinical knowledge specific for the type of patient encounter. For example, a well-designed template for a disease process (e.g., multiple sclerosis) provides a road map for providers that can guide the history, examination, diagnosis, and management process. Clinical guidelines may be incorporated into the workflow of templates, giving them the potential to foster improvements in the overall quality of care.
The intelligent and professional use of imported text potentially can benefit patient care. A primary value of importing text within EHRs is increased efficiency of documentation over dictation and keyboard entry. Providers can create multi-page documents with a single mouse click. These large bodies of text also assist providers with meeting documentation requirements for reimbursement — a process that can actually improve the accuracy of coding, if used properly.
Human Factors and Imported Text
Human factors associated with using imported text in EHRs have led to a relatively high frequency of documentation errors. Providers are often pressured to evaluate and manage complicated patients in short time intervals, reducing the time they have to validate accompanying documentation.
Documentation tied to reimbursement for evaluation and management (E/M) services often requires fairly extensive detail, and EHRs facilitate this process through the use of imported text. Many EHRs are specifically designed to assist providers in meeting evaluation and coding requirements and facilitate adding large volumes of free text into patient records. This has a tendency to make the documentation review process even more laborious. Given the time pressures on physicians, a tendency to accept imported text as “good enough” may arise. Unfortunately, this is a primary source of documentation inaccuracies associated with EHR use.
Preformatted text that’s imported into a document, never reviewed, and used to justify an E/M level is considered fraudulent activity by CMS. Nearly every coding professional has encountered documentation errors associated with using imported text. Some striking examples include documentation of amputated extremities that subsequently have “grown back,” vanishing scars, symptoms in the history of present illness that conflict with the review of systems and/or assessment, and potentially dangerous medication errors.
Identify Identical Text Blocks
For over 10 years, reviewers have been employing plagiarism detection software to identify identical blocks of text in medical documentation, and its use is increasing among auditors, as well. Audit logs provide another method for identifying imported text in medical records. Although EHR vendor products vary in their audit capabilities, some are able to track user actions, including when the user imports text into a medical record and whether the text was subsequently modified. The OIG has increased its focus on EHR audit logs to detect inappropriate documentation, and the OIG 2014 Work Plan describes reviewing multiple documents from the same provider to identify identical documentation.
Imported Text Strategies and Vendor Help
Representatives from six of the top 10 EHR vendors in the United States were interviewed confidentially in February 2014, in preparation for this article. They were asked if their current systems included features to alert providers when text has been imported during documentation review, prior to signature. None of the vendors said their EHR has this feature in place; although, one did describe having audit logs that track when text is imported.
Strategies to help providers identify imported text are relatively straightforward, and include font changes for imported documents (e.g., color changes, italics, underlining, shading, etc.), changes to the background of that portion of the document, and alerts and reminders. In this setting, providers have the ability to validate that the text accurately represents the encounter, after they have made necessary modifications. As of the writing of this article, few (if any) vendors have implemented such features.
Recommendations to Help Integrity
Text imported into medical records from other sources via copy and paste, pull forward, macros, or templates has the potential to benefit patient care and the efficiency of medical documentation. When used inappropriately, however, their use can adversely affect the integrity of the medical record and lead to claims denials or, in some cases, accusations of fraud.
Resource: The Legal Health Record Copy and Paste Functionality, AHIMA Seminar, September 9, 2009 (http://campus.ahima.org/audio/2009/RB111709.pdf)
Healthcare organizations using EHRs need to be aware of the potential pitfalls of using imported text, and of the need for clinicians to thoroughly review documentation before signature. They should institute policies that address the use of imported text, and test the review auditing features of their EHRs to see how the use of imported text may be recorded.
When possible, the patient record should show when imported text is used in medical documentation. In the near future, EHR vendors may offer additional features to alert providers when imported text has not been reviewed or when it may represent inaccurate information. At this time, however, providers are encouraged to increase their level of diligence when using imported text.
Modify Text to Warn Users of Inaccurate Information
Example 1a: The patient is a 47-year-old white male who presents with a three-day history of cough. The symptoms have been progressively worsening and are currently severe. The patient reports a low-grade fever. The cough is nonproductive. The patient also describes having general malaise. He denies headache.
This example shows imported text from a prior visit or template without warning enhancements. This information may or may not be relevant for the current visit; the default text is added to speed up the documentation process by anticipating what the patient “might” say. It could easily be mistaken as “real” information entered for that patient on that same day. EHRs vary considerably regarding their approach to allowing users to modify blocks of text; however, most do not provide warnings when imported text has not been modified or reviewed.
Example 1b: The patient is a 47-year-old white male who presents with a five-day history of cough, chest congestion, and headache. The symptoms have been progressively worsening and are currently moderate to severe. The patient denies fever. The cough is productive, with thick yellow sputum but no blood. The patient also describes having general malaise. He denies shortness of breath or lightheadedness.
This example shows how the text in Example 1a would be altered once the provider obtains the actual history.
Example 2: The patient is a 47-year-old white male who presents with a three-day history of cough. The symptoms have been progressively worsening and are currently severe. The patient reports a low-grade fever. The cough is nonproductive. The patient also describes having general malaise. He denies headache.
This example shows imported text that highlights the areas requiring modification and review. In this example, the user would click on each highlighted word or phrase and add the correct information via free text or drop-down menus.
This is an example of imported text with the entire text field highlighted and a warning alert. The user would click on the text and make changes via free text or drop-down menus.
Michael Stearns, MD, CPC, CFPC, works as a healthcare compliance and health information technology consultant. He has over 12 years of experience designing and implementing EHRs, and has created requirements for computer-assisted coding software applications for three major health information technology companies, including two leading EHRs. Stearns is a member of the Austin, Texas local chapter. He can be reached at email@example.com.
Latest posts by Renee Dustman (see all)
- Avoiding Physician Self-Referral Violations Starts with a Code List - January 15, 2019
- Ignore New MIPS Requirements at Your Own Risk - January 14, 2019
- Non-coverage Denials: Cause and Cure - January 8, 2019