NUR4083 Module 2 standardized terminology paper example

Reviewed by Junia Fairbank, MSN, RN · American College of Education · True APA form, annotated

This page holds a complete NUR 4083 Module 2 example in true APA form: a standardized terminology paper for American College of Education's Nursing Informatics course. Two composite hospitals have merged and want one fall prevention dashboard, but one records fall risk with the Morse Fall Scale and the other with the Hendrich II model, and both call their top category high risk. The paper shows why that shared word hides two different meanings and how standard terminologies fix it.

1

Two Hospitals, One Word, Two Meanings: Why High Fall Risk Needs a Standard Terminology Before a Merged Dashboard Can Be Trusted

Student Name

American College of Education

NUR4083: Nursing Informatics

Module 2 Assignment

Instructor Name

January 18, 2027

What this page is doingThe title states the problem in six words, one word with two meanings, and names the practical stake, a dashboard that cannot be trusted. That frames terminology as a patient safety and data quality issue rather than a technical detail. The APA 7 title page carries the course line and module assignment as listed.
2

The Problem

Two community hospitals in the same region merged last year and are consolidating their quality reporting. Both hospitals, and every number that follows, are invented for this assignment. The chief nursing officer has asked for a single dashboard showing the percentage of high fall risk patients on each medical-surgical unit who have a bed alarm, a scheduled toileting plan and a documented fall prevention care plan. The first draft of the dashboard showed that 41 percent of medical-surgical patients at Hospital A were high fall risk, compared with 18 percent at Hospital B. Leaders began asking why Hospital A's patients were so much sicker.

They were not. Hospital A records fall risk with the Morse Fall Scale and flags patients as high risk at a score of 45 or more. Hospital B uses the Hendrich II Fall Risk Model and flags patients as high risk at a score of 5 or more. Both electronic records store the result in a field labeled fall risk level, with the value high. The dashboard compared two different measurements because they had been given the same name, and the name was all the reporting system could see.

What this page is doingThe problem is presented through a concrete, believable error: a dashboard that produced a large difference between hospitals from a labeling problem rather than a real one. The highlighted sentence identifies the root cause, which the rest of the paper addresses.
3

Two Tools, Two Meanings

The Morse Fall Scale was developed from a study of hospitalized patients and scores six items: history of falling, a secondary diagnosis, use of an ambulatory aid, an intravenous line or saline lock, gait and mental status (Morse et al., 1989). Its total ranges from 0 to 125, and the threshold for high risk is set locally, commonly at 45. The Hendrich II Fall Risk Model was validated in a large case-control study of hospitalized patients and scores different factors: confusion or disorientation, depression, altered elimination, dizziness or vertigo, male sex, certain antiepileptic drugs and benzodiazepines, and performance on a get-up-and-go test (Hendrich et al., 2003). A score of 5 or more indicates high risk.

The two tools share a purpose and some overlapping ideas, such as mental status and mobility, but they do not measure the same thing in the same way. A patient with an intravenous line and a walker scores points on the Morse scale for both, and neither counts on the Hendrich II model. A patient taking a benzodiazepine for anxiety scores on the Hendrich II model and not on the Morse scale. The proportion of patients labeled high risk will therefore differ between the hospitals even if their patients are identical, simply because the tools and thresholds differ. The word high carries meaning only in relation to the tool and cutoff that produced it.

What this page is doingEach tool is described from its original validation study with its actual items and thresholds, which shows exactly why the two categories are not equivalent. The concrete patient examples make the abstract point about meaning visible, which is the core of this module.
4

What Standard Terminologies Provide

Standard terminologies exist to solve exactly this problem: making sure that when two systems exchange or combine data, a term means one thing. Rutherford (2008) describes standardized nursing language as a common vocabulary that allows nursing data to be communicated across settings, compared across populations and used to demonstrate nursing's contribution to outcomes. Westra et al. (2008) describe how several recognized terminologies serve different purposes in the electronic record, some describing nursing diagnoses, interventions and outcomes, and others coding the assessments and observations nurses record.

Two standards matter most in this case. Logical Observation Identifiers Names and Codes, known as LOINC, was created to give each laboratory test and clinical observation a unique code that identifies exactly what was measured and how (McDonald et al., 2003). Under LOINC, a Morse Fall Scale total and a Hendrich II total are different observations with different codes, so a system that receives them cannot mistake one for the other. SNOMED CT, a clinical terminology used for findings, diagnoses and procedures, can represent the clinical finding that a patient is at risk for falls, and it can also represent the specific assessment tool that established the finding. Used together, the two standards separate what was measured from what was concluded.

What this page is doingThe terminologies are introduced with sources and explained by the job each one does in this specific case, rather than listed in general. The key point, that LOINC distinguishes the two tools as different observations, is exactly what would have prevented the dashboard error.
5

Applying the Standards to the Merged System

With the tools coded correctly, the dashboard can be rebuilt in one of two ways. The first is to report each hospital's high-risk proportion separately and label each with its tool, so that leaders see Morse high risk at Hospital A and Hendrich II high risk at Hospital B and do not compare them directly. That approach is honest but does not produce a single system measure. The second is for the merged system to adopt one tool at both hospitals, so that future data are comparable. Either way, the dashboard's underlying query should select observations by their LOINC codes rather than by the free-text label high, so that a future change of tool or threshold cannot silently alter the numbers.

The practice council recommended the second approach. The council chose the Hendrich II model for both hospitals, partly because it includes medication factors the council considered important and partly because it is shorter to complete, and it set a transition date after which Hospital A would stop recording Morse scores. For the six months of overlap, the dashboard would show both tools separately. The informatics team mapped each tool's items and totals to the appropriate LOINC codes and configured the fall risk finding in SNOMED CT so that downstream care plan rules would read the finding rather than the label. A standard terminology does not choose the better tool; it makes sure that whichever tool is used, every system knows which one it was.

What this page is doingThe application offers two options with their trade-offs and then reports the decision and its reasons, including a transition period. The technical step of querying by code rather than label is explained in plain words, which shows how terminology prevents the original error from recurring.
6

What Bedside Nurses Need to Know

Terminology standards are configured by informatics teams, but they depend on bedside nurses in two ways. First, the codes only work if nurses complete the structured fields rather than typing risk levels into free-text notes, where no code can be attached and no report can find them. During the transition, Hospital A's nurses were asked to stop writing high fall risk in their shift notes and to complete the Hendrich II flowsheet instead, because the note would carry the word without the code. Second, nurses are often the first to notice when a report does not match what they see on the unit. The dashboard error in this case was first questioned by a Hospital B charge nurse who knew her unit was not less frail than Hospital A's. Teaching nurses that a surprising number may be a terminology problem, and giving them a way to report it to the informatics team, makes them part of the data quality system rather than only its source.

7

Conclusion

The merged hospitals' first dashboard suggested that one hospital's patients were more than twice as likely to be at high risk of falling, when the real difference was in the tools and thresholds hidden behind a shared word. Standard terminologies address that problem by giving each observation a code that identifies what was measured and how, and by separating the measurement from the clinical conclusion drawn from it. For nurses, the lesson reaches beyond fall risk: any time nursing data are combined across units, hospitals or systems, the words on the screen must be backed by codes that mean one thing, or the comparisons built on them will mislead the people who act on them.

8

References

Hendrich, A. L., Bender, P. S., & Nyhuis, A. (2003). Validation of the Hendrich II Fall Risk Model: A large concurrent case/control study of hospitalized patients. Applied Nursing Research, 16(1), 9-21. https://doi.org/10.1053/apnr.2003.YAPNR2

McDonald, C. J., Huff, S. M., Suico, J. G., Hill, G., Leavelle, D., Aller, R., Forrey, A., Mercer, K., DeMoor, G., Hook, J., Williams, W., Case, J., & Maloney, P. (2003). LOINC, a universal standard for identifying laboratory observations: A 5-year update. Clinical Chemistry, 49(4), 624-633. https://doi.org/10.1373/49.4.624

Morse, J. M., Morse, R. M., & Tylko, S. J. (1989). Development of a scale to identify the fall-prone patient. Canadian Journal on Aging, 8(4), 366-377. https://doi.org/10.1017/S0714980800008576

Rutherford, M. A. (2008). Standardized nursing language: What does it mean for nursing practice? OJIN: The Online Journal of Issues in Nursing, 13(1). https://doi.org/10.3912/OJIN.Vol13No01PPT05

Westra, B. L., Delaney, C. W., Konicek, D., & Keenan, G. (2008). Nursing standards to support the electronic health record. Nursing Outlook, 56(5), 258-266. https://doi.org/10.1016/j.outlook.2008.06.005

How this NUR 4083 Module 2 example is structured

NUR 4083 Module 2 typically covers standard terminologies and why two systems must mean one thing by a term; your classroom's instructions decide the example and which terminologies to cover. This example starts with a concrete problem, a merged dashboard that would compare two different measurements as if they were one, then explains what each tool actually measures. It introduces the terminology standards that address the problem, shows how each would be used in this case and ends with the decision the merged system should make. Anchoring the discussion in one term keeps the paper from becoming a list of acronyms.

NUR4083 Module 2 questions, answered

What does NUR4083 Module 2 usually ask for?

NUR4083 Module 2 typically covers standardized terminologies in nursing informatics and why systems need a shared meaning for each term. Many sections ask students to explain one or more terminologies, such as SNOMED CT, LOINC or a nursing classification, and apply them to a practice example. Your classroom's instructions decide the example and which terminologies to discuss.

What is the difference between LOINC and SNOMED CT?

LOINC gives codes to observations and measurements, identifying what was measured and how, such as a specific fall risk scale total. SNOMED CT represents clinical concepts such as findings, diagnoses and procedures, such as being at risk for falls. They are often used together: LOINC for the question asked and SNOMED CT for the clinical answer or conclusion.

Why do nursing data need standard terminologies?

Without them, the same word can mean different things in different systems, and combined reports can compare measurements that are not equivalent. Standard terminologies allow nursing data to be exchanged, compared across settings and used to show nursing's effect on outcomes. They also protect reports from silent errors when tools or thresholds change.

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 American College of Education 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.