NR 512 Week 7 Documentation Case Analysis Example

Documentation Case Analysis: A Blank Oxygen Row, an Early Warning Score Two Points Too Low, and the Hand-Off Where the Meaning of Nothing Changed

Student Name

College of Nursing, Chamberlain University

NR 512: Fundamentals of Nursing Informatics

Instructor Name

Month Day, Year

Documentation Case Analysis: A Blank Oxygen Row, an Early Warning Score Two Points Too Low, and the Hand-Off Where the Meaning of Nothing Changed

The Case

Everything in this case is invented for teaching purposes, including the unit and staff. At 2000, a man of 74 in hospital for a urinary tract infection was started on nasal cannula oxygen at two liters after his saturation dipped to 91% breathing unassisted. The evening nurse charted the device and flow in the flowsheet's O2 device and O2 flow rows. At 2400 and 0400, a second nurse charted his observations; at 0400 they were a saturation of 94%, heart rate 104, respiratory rate 20, systolic blood pressure 116, temperature 38.1 C, and alert. She left the oxygen rows blank at both times. The electronic record calculated a NEWS2 total of 3 at 0400 and did not display the prompt it shows at 5. At 0630, the patient was confused and his blood pressure had fallen; a rapid response was called and he was transferred to intermediate care with sepsis. He recovered. The case review asked why the 0400 score had not prompted an earlier call.

What the Field Permitted, What Was Meant, What Was Read

What the field permitted. The O2 device row was optional, had no default and accepted a blank. There was no written definition of what a blank meant. The unit's documentation policy said oxygen should be charted "with changes," which the second nurse had followed: nothing had changed.

What the recorder meant. To the second nurse, a blank meant no change since the last entry. She could see the 2000 entry two columns to the left, and the patient was plainly wearing a cannula.

What the scoring logic read. The early warning calculation looked only at the oxygen row in the same time column as the saturation. Finding it blank, it scored the air or oxygen parameter as air, 0 points, instead of 2 points for supplemental oxygen (Royal College of Physicians, 2017). With oxygen counted, the 0400 total would have been 5: one point each for the saturation of 94%, the heart rate and the temperature, and two for oxygen.

What the charge nurse read. The unit dashboard showed a score of 3, shaded yellow like every other low-risk score on the unit. She did not open the flowsheet, which is what a dashboard is for.

What the reviewer read at 0630. The physician looked at the trend and saw the rising heart rate and temperature, but also saw a score that had never reached 5.

Where the Divergence Began

The divergence began at a single hand-off: from the flowsheet to the scoring logic, at 2400. The nurse and the algorithm read the same blank cell and gave it different meanings, and both meanings were consistent with how the field was built. Nothing in the field told the nurse that a blank would be scored as air, and nothing told the algorithm that a blank might mean no change.

It is tempting to locate the failure with the nurse who left the row blank, and the first draft of the unit's own review did. That conclusion does not survive a look at the field. She followed the written policy, and her entry was correct under it. The HL7 pulse oximetry profile anticipates this situation and warns that when oxygen components are absent, a receiver cannot tell ambient air from an omission (HL7 International, n.d.). Its remedy is to enter ambient air as zero liters per minute, so that an empty cell is left with a single meaning: nothing was charted. The unit's build had never adopted that convention, so its blank carried two meanings and the algorithm chose one of them.

The later readers did not add new errors. The charge nurse trusted a score whose inputs she had no reason to doubt, and the physician gave weight to a number designed to summarize exactly what he was looking at. Each reading was reasonable given what the reader could see.

What Would Have Prevented This Case

Recommendations are judged by one test: would they have changed what happened at 0400 for this patient? More education about early warning scores fails that test, since both nurses understood the score; the problem was a field neither of them could see into.

A required companion field. Make the oxygen row required whenever a saturation is saved, with room air entered as 0, so a blank cannot be saved. This would have forced the 0400 entry of 2 L/min and a score of 5, which crosses the unit's prompt threshold.

No silent default in the calculation. Where the oxygen value is missing, the score should display as incomplete rather than be calculated as though the patient were on air. An incomplete score in gray is visible on a dashboard; a low score in yellow is not.

A written definition of the field. One sentence in the build documentation and the policy: the oxygen row records the oxygen flowing at the time of the paired saturation, and a blank means not recorded. In its informatics scope and standards, the American Nurses Association places the design of data and information structures that support nursing practice within the informatics nurse's role (American Nurses Association, 2022), and this definition is that kind of work.

Change the policy wording. Replace "chart with changes" with "chart with every saturation." The old wording was correct for a paper chart, where a nurse reads across columns, and wrong for a system that reads only the current column. A policy written for paper was never reviewed when the unit moved to a calculated score, and that review is the missing step behind all four recommendations: whenever a new reader, human or software, starts using an existing field, someone has to check that the field still means one thing.

What This Case Does Not Show

It does not show that an earlier call would have changed the outcome, which the case cannot answer. It does not show that the score is unreliable: with complete inputs, it reached the threshold two and a half hours before the rapid response. And it does not show that the second nurse was careless. It shows that a field built for one reader, a nurse scanning a row, was being read by a second reader, an algorithm reading a column, and nobody had written down what the field meant for both.

References

American Nurses Association. (2022). Nursing informatics: Scope and standards of practice (3rd ed.). American Nurses Association.

HL7 International. (n.d.). US Core pulse oximetry profile (US Core Implementation Guide, Version 9.0.0, STU 9). Retrieved September 30, 2026, from https://hl7.org/fhir/us/core/StructureDefinition-us-core-pulse-oximetry.html

Royal College of Physicians. (2017). National Early Warning Score (NEWS) 2: Standardising the assessment of acute-illness severity in the NHS. Updated report of a working party. https://www.rcp.ac.uk/improving-care/resources/national-early-warning-score-news-2/