The Note That Said Healing: Copy-Forward, Note Bloat, and the Unintended Consequences of Electronic Nursing Documentation
Student Name
Master of Science in Nursing Program, Aspen University
N537: Health Care Informatics
Instructor Name
Month Day, Year
The Note That Said Healing: Copy-Forward, Note Bloat, and the Unintended Consequences of Electronic Nursing Documentation
Electronic health records were expected to make documentation more complete, legible, and available, and they have. They have also introduced new kinds of errors that paper records rarely produced. This paper examines one of them, the copying forward of prior documentation, through a composite case on a medical-surgical unit, explains it using research on the unintended consequences of health information technology, and recommends changes in system design, organizational policy, and nursing practice.
The Case
Mr. R., 81, was admitted to a composite medical-surgical unit with pneumonia and a sacral pressure injury, stage 2 on admission. The admitting nurse documented the wound in detail. Over the next nine days, the wound assessment section of each shift's note was populated by a copy-forward feature that carried the previous entry into the new note, where nurses could edit it. The text continued to read "stage 2, 2 by 3 cm, pink wound bed, no drainage, healing." On day 10, a wound care nurse found a stage 3 injury with slough and odor. A review showed that several nurses had noticed changes and mentioned them in handoff, but the documented assessment had not been updated.
How Copy-Forward Creates Errors
Copy-forward and copy-and-paste save time, and clinicians use them widely. A systematic review of 51 publications found that 66 to 90 percent of clinicians routinely copy and paste, and that the practice can promote note bloat, internal inconsistencies, propagation of errors, and documentation in the wrong patient's chart (Tsou et al., 2017). In Mr. R.'s case, the copied text created the appearance of a current assessment while preserving an outdated one. The record did not lack information; it contained confident, well-formatted information that was no longer true.
Ash et al. (2004) described errors fostered by patient care information systems in two broad categories: errors in entering and retrieving information, and errors in the communication and coordination the system is supposed to support. Both appear here. The entry interface made it easier to accept prior text than to write a new assessment, and the coordination role of the record failed, since nurses communicated the change verbally at handoff while the chart, the source the physician and wound nurse consulted, said otherwise.
Documentation Burden as a Root Cause
Nurses do not copy forward because they are careless; they do it because documentation takes a large share of their time. A scoping review of how documentation burden is measured found that studies of nurses and physicians have used time spent in the EHR, the volume of documentation, and user-reported burden, and that there is not yet a standard measure, which makes the problem harder to manage (Moy et al., 2021). On Mr. R.'s unit, nurses complete assessments with dozens of fields each shift, many of which duplicate information recorded elsewhere. Copy-forward is a rational response to a design that asks for more documentation than a busy shift allows, and removing the feature without reducing the burden would simply move the workarounds elsewhere.
Why the Record Matters More Than the Handoff
It might seem that no harm resulted, since nurses discussed the change verbally. But the electronic record is the shared memory of the whole care team, and many of the people who act on it never attend a nursing handoff. The physician who reviewed the chart each morning saw a healing wound and did not examine it. The dietitian, who adjusts protein and calorie goals when wounds worsen, relied on the same entry. The wound care referral that should have been triggered by a change in stage was never sent, because the system's rule looked for a documented change that never appeared. And if the injury later became the subject of a complaint or claim, the record would show nine days of assessments that contradicted the wound nurse's findings, undermining every nurse who signed them.
The case also illustrates why informatics must attend to how systems shape behavior. The copy-forward feature was designed with good intentions, to spare nurses from retyping stable information. Its designers assumed that nurses would edit what had changed. Under time pressure, the default became the documentation. Defaults are powerful in any system, and in an electronic record they quietly determine what the chart will say when a nurse is too busy to override them.
Recommendations
System design: Copied assessment text should be visibly marked, for example in a different color with the date and author of the original entry, and critical assessments such as wounds, pain, and neurological status should require active confirmation or entry each shift rather than silent carry-forward. Wound documentation should prompt for measurement and attach photographs, which make change visible.
Organizational policy: Following the responsibilities outlined for authors, organizations, and developers in the systematic review (Tsou et al., 2017), the hospital should adopt a policy stating that the author of a note is responsible for everything in it, including copied text, and should audit a sample of notes for copied assessments that conflict with other data.
Nursing practice and burden: A documentation review committee led by nurses should identify and remove duplicate fields, so that the time saved goes into accurate assessments of what matters. Handoff should include checking that the chart reflects what is being reported verbally. Nurse educators can reinforce the habit by using de-identified examples of conflicting notes in annual competencies, so that nurses see how copied text reads to the next clinician.
Conclusion
Mr. R.'s record described a healing wound for nine days while the wound deteriorated. The copy-forward feature, created to reduce burden, produced an entry error and a coordination failure of the kind informatics researchers have described since the early years of electronic records. Preventing it requires better design, clear accountability for copied text, and a serious effort to reduce the documentation burden that makes shortcuts attractive. The goal of the electronic record is not more documentation but more accurate information at the moment it is needed.
References
Ash, J. S., Berg, M., & Coiera, E. (2004). Some unintended consequences of information technology in health care: The nature of patient care information system-related errors. Journal of the American Medical Informatics Association, 11(2), 104-112. https://doi.org/10.1197/jamia.M1471
Moy, A. J., Schwartz, J. M., Chen, R., Sadri, S., Lucas, E., Cato, K. D., & Rossetti, S. C. (2021). Measurement of clinical documentation burden among physicians and nurses using electronic health records: A scoping review. Journal of the American Medical Informatics Association, 28(5), 998-1008. https://doi.org/10.1093/jamia/ocaa325
Tsou, A. Y., Lehmann, C. U., Michel, J., Solomon, R., Possanza, L., & Gandhi, T. (2017). Safe practices for copy and paste in the EHR: Systematic review, recommendations, and novel model for health IT collaboration. Applied Clinical Informatics, 8(1), 12-34. https://doi.org/10.4338/ACI-2016-09-R-0150
How this N 537 Module 3 example is structured
N537's middle modules center on the electronic health record itself. Aspen does not publish module deliverables, so check your classroom for the exact prompt. This example analyzes one EHR problem through a case, explains it with research on unintended consequences, identifies the underlying cause and recommends changes at the design, organizational and practice levels.
N537 Module 3 questions, answered
What does N537 Module 3 usually ask for?
The module typically centers on the electronic health record, often asking you to analyze its benefits, problems or design in your own practice. Aspen does not publish module deliverables, so your classroom's instructions govern.
Why is copy-forward documentation risky?
It can carry outdated assessments into new notes, create internal inconsistencies, spread errors and bloat notes. A systematic review found that 66 to 90 percent of clinicians routinely copy and paste, and linked the practice to documented safety events.
What are unintended consequences of health IT?
Errors and problems the systems were not designed to create, such as errors in entering and retrieving information and failures in the communication and coordination the systems are meant to support.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official Aspen University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.