NR 512 Week 8 Informatics Position Paper Example

Position Paper: No Field a Nurse Records Should Feed a Score or a Report Until a Nurse Has Written Down What It Means, Including What It Means When It Is Empty

Student Name

College of Nursing, Chamberlain University

NR 512: Fundamentals of Nursing Informatics

Instructor Name

Month Day, Year

Position Paper: No Field a Nurse Records Should Feed a Score or a Report Until a Nurse Has Written Down What It Means, Including What It Means When It Is Empty

The Position

Defining a documentation field is a clinical decision, not a technical one, and the people who record the data should make it. The position of this paper is narrow and testable: before any nurse-recorded field is used to calculate a score, trigger an alert or populate a report, a nurse must write a definition of that field, including what an empty entry means, and the definition must be kept where both the nurses recording and the people building the calculation can read it. A field that lacks a definition should not be used downstream, however useful its data seem.

This is not a claim that documentation matters, which nobody would dispute. It is a claim about who owns meaning and when that ownership has to be exercised. It has costs, and the paper accepts them.

The Evidence From One Element

The strongest evidence comes from a single element followed through this course: the oxygen a patient is receiving when a saturation is recorded. A saturation of 93% means something different on room air than on 4 liters of oxygen. Early warning scores recognize this; in NEWS2, being on supplemental oxygen scores 2 points on its own (Royal College of Physicians, 2017). Yet on many flowsheets, oxygen is an optional row, recorded when it changes, and its blank has no written meaning.

The course case analysis showed what follows. A nurse left the oxygen row blank because nothing had changed, which was correct under her unit's policy. The scoring logic read the blank as air and scored the patient 2 points too low, below the threshold that would have prompted a call. Nobody misread a word. The field meant one thing to the person who filled it in and another to the software that used it, and nobody had written down which meaning was right.

National standards do not close this gap. The HL7 pulse oximetry profile names the ambiguity exactly, pointing out that a receiver cannot distinguish ambient air from a skipped entry when oxygen data are missing, and it advises coding ambient air as a zero flow (HL7 International, n.d.). But it recommends; it does not require. A hospital can conform to the profile and still send readings whose oxygen context is empty. The standard carries meaning well once a meaning has been recorded. It cannot supply the meaning at the bedside.

Why This Belongs to Nurses

Only the person who records a value knows what the recording practice is. The builder of a scoring rule knows what the calculation needs; the nurse knows whether a blank means no change, not assessed, room air or forgot. Writing that down is a clinical judgment about practice on a particular unit. The American Nurses Association's scope and standards of practice for nursing informatics treat designing the data structures nursing relies on as part of what informatics nurses do (American Nurses Association, 2022). The position here extends that responsibility from specialists to the unit: the nurses who record a field should approve its definition.

There is also a larger reason. Westra et al. (2015) argue that nursing's contribution to large-scale data science depends on nursing data being captured in standardized, comparable forms. Data that are standardized in format but ambiguous in meaning are worse than useless for that purpose, because they look reliable. A report that counts patients on oxygen from a field whose blank means two things will produce a number, and nobody reading the report will know it is wrong.

The Opposing View, Stated Fairly

The strongest objection comes from informatics analysts and system builders, and it deserves a fair statement. Definitions, they argue, need to be consistent across units, hospitals and systems. If every unit's nurses write their own definitions, the same field will mean different things on different floors, which is the very problem the position aims to solve. Consistency is better achieved centrally, by people trained in data modeling and standards, working from national specifications. Nurses on busy units also lack the time to review field definitions, and asking them to do so will either delay useful tools or produce hurried approvals that add nothing.

This objection is right about consistency and right about time. It is wrong about where meaning comes from. A central team can write a definition, but it cannot know what nurses actually mean when they leave a row blank unless nurses tell it. The case in this course did not fail because the definition was inconsistent across units; it failed because there was no definition, and the build team assumed one. The answer is not for every unit to invent its own meaning. It is for a central definition to be written with and approved by the nurses who record the field, and for recording practice to be changed where it disagrees.

What the Position Does Not Cover

A definition cannot fix measurement. Sjoding et al. (2020) showed oximeters overlooking low arterial oxygen roughly three times more frequently for Black patients than for White patients. A perfectly defined saturation field will faithfully record a reading that is wrong for the patient in front of the nurse. The position is about the meaning of recorded values, not their accuracy, and it should not be sold as a solution to both.

What Follows If the Position Is Accepted

Three things follow, and each has a cost. First, every calculated score and every report that uses nurse-recorded data needs an inventory of its input fields, with a written definition for each. For a single early warning score, that may be a dozen fields. Second, nurses on the units that record those fields need protected time to review definitions, perhaps an hour a quarter for a small group of staff nurses. Third, and most uncomfortable, nurses must accept that approving a definition makes them accountable for recording to it. A nurse who approves "a blank means not recorded" can no longer leave a row blank to mean no change.

The alternative is the current state, in which fields are defined by default, by whoever builds the calculation, and nurses discover the definition only after a case review. That costs more, and it is paid by patients.

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/

Sjoding, M. W., Dickson, R. P., Iwashyna, T. J., Gay, S. E., & Valley, T. S. (2020). Racial bias in pulse oximetry measurement. New England Journal of Medicine, 383(25), 2477-2478. https://doi.org/10.1056/NEJMc2029240

Westra, B. L., Clancy, T. R., Sensmeier, J., Warren, J. J., Weaver, C., & Delaney, C. W. (2015). Nursing knowledge: Big data science. Implications for nurse leaders. Nursing Administration Quarterly, 39(4), 304-310. https://doi.org/10.1097/NAQ.0000000000000130