| Course | NR 512 Fundamentals of Nursing Informatics |
|---|---|
| Week | 3 |
| Paper type | Terminology comparison |
| Length | About 1,260 words, 4 pages |
| Format | APA 7 student paper |
| School | Chamberlain University |
| Program | MSN, Nursing Informatics |
| Updated | September 2026 |
Free sample paper for NR 512 Week 3
Terminology Comparison: One Finding, a Saturation of 88% on Room Air That Rose to 94% on 2 Liters, Written in LOINC, SNOMED CT, ICD-10-CM and a Nursing Diagnosis, and What Each One Keeps and Drops
Student Name
College of Nursing, Chamberlain University
NR 512: Fundamentals of Nursing Informatics
Instructor Name
Month Day, Year
Terminology Comparison: One Finding, a Saturation of 88% on Room Air That Rose to 94% on 2 Liters, Written in LOINC, SNOMED CT, ICD-10-CM and a Nursing Diagnosis, and What Each One Keeps and Drops
The Finding
The finding comes from an admission on a medical unit. A 71-year-old man with community-acquired pneumonia had a pulse oximetry reading of 88% on room air at 1510. Oxygen was started at 2 L/min by nasal cannula, and at 1530 his reading was 94%. A nurse, a physician, a coder and a quality analyst will each need to say something about this, and each will reach for a different vocabulary. This paper compares four of them against that one finding, not against pneumonia in general and not against the patient's whole stay.
The Four Vocabularies Side by Side
Table 1 sets the four vocabularies against the same finding. The prose after it does what the table cannot.
Table 1
Four Vocabularies Applied to One Finding
| Vocabulary | What it offers for this finding | Detail kept | Built to serve | Maintained by |
|---|---|---|---|---|
| LOINC | Codes for the observations themselves: pulse oximetry (59408-5) and inhaled oxygen flow rate (3151-8), each with a value and unit | Both readings, both flows, times, units | Identifying what was measured so systems can exchange results | Regenstrief Institute |
| SNOMED CT | A clinical finding concept for hypoxemia, which can be refined by linking attributes such as severity or context | The clinical meaning: low oxygen in the blood, as a finding about this patient | Recording clinical meaning precisely in the record | SNOMED International |
| ICD-10-CM | R09.02, Hypoxemia; or, if the physician documents it, J96.01, acute respiratory failure with hypoxia | A category for the encounter | Classifying diagnoses for statistics and billing | National Center for Health Statistics, with CMS |
| NANDA-I nursing diagnosis | Impaired gas exchange, with defining characteristics and related factors | The nurse's judgment and its evidence | Naming nursing judgments to plan and evaluate care | NANDA International |
Note. The two LOINC codes shown are the ones the US Core profile for oximetry specifies (HL7 International, n.d.). The finding is a composite built for teaching.
Granularity: Who Keeps the Numbers
Only LOINC keeps the numbers. It does not say whether 88% is bad; it names the measurement so that 88 and 94, with their units and times, can be sent between systems and understood as the same kind of observation. McDonald et al. (2003) describe LOINC as a set of universal names and codes for observations, created because each laboratory and system had its own local names. The HL7 pulse oximetry profile then pairs the saturation code with the flow code, which is how the rise from 88 to 94 on oxygen stays interpretable after it leaves the unit (HL7 International, n.d.).
SNOMED CT keeps the meaning but not the numbers. A hypoxemia concept says what the clinician concluded, and it can be linked to other concepts to say more. Lee et al. (2014) reviewed 488 papers on SNOMED CT published from 2001 to 2012 and found most were theoretical or about design, with only 34 describing implementation in the later period; they concluded that most real implementations are not reported in the scientific literature. That is relevant here: the concept is precise, but a system still needs the LOINC observation to know how low the saturation was.
ICD-10-CM keeps a category. R09.02 tells a payer and a statistician that hypoxemia was part of the encounter. It cannot hold 88% or 2 L/min, and it was never meant to. The choice between R09.02 and J96.01 depends on what the physician documents, not on the numbers, which is why the same oximetry values can end up in two different categories.
The nursing diagnosis keeps the nurse's judgment and the evidence for it. Impaired gas exchange, with defining characteristics such as low saturation, says what the nurse will act on and evaluate. It keeps something none of the others do, the link to a care plan, but most hospital systems cannot exchange it with anyone outside the building.
Precoordination and Postcoordination
ICD-10-CM is precoordinated: a single code carries a fixed combination of meaning, and anything the code does not include is simply absent. J96.01 carries acute, respiratory failure and hypoxia together; it cannot be split to say chronic with an acute worsening unless a separate code exists for that combination. SNOMED CT allows postcoordination, in which a base concept is combined with others to express a meaning no single concept holds. That power costs something: two systems can express the same meaning in different combinations, and matching them later requires rules. LOINC sits apart from both, because it names observations rather than conclusions, and the value is stored beside the code instead of inside it.
What Happens When the Record Crosses a Boundary
Suppose the unit's system stores the finding in SNOMED CT and the hospital's billing system needs ICD-10-CM. Maps exist, and the National Library of Medicine's Unified Medical Language System integrated, in its 2004 description, some 900,000 concepts from more than 60 families of vocabularies, so that a term in one can be found in another (Bodenreider, 2004). But a map moves a concept, not the evidence behind it. Mapping the hypoxemia concept to R09.02 is straightforward. Nothing in the map carries the 88%, the 2 L/min or the fact that the patient improved on oxygen. If the quality analyst later wants to count patients who were hypoxemic on room air, the ICD-10-CM data cannot answer, and the SNOMED CT data can answer only if someone recorded the context. The LOINC observations can answer it directly, provided the flow value was recorded with each reading.
Which Vocabulary for Which Use
None of the four is better; each is better at its job. For deciding whether this patient is deteriorating, the nurse needs the LOINC-coded observations, since only they carry the trend. For summarizing the clinical picture in the problem list, SNOMED CT's hypoxemia concept is right. For billing and national statistics, ICD-10-CM is required and sufficient. For the nursing care plan, the nursing diagnosis carries what the others cannot: the nurse's reasoning and the interventions it leads to.
The practical lesson for a nurse is that the vocabulary is chosen by the question that will be asked of the data later. A nurse who records a saturation with its oxygen flow has made the finding answerable by all four. A nurse who writes only "hypoxic, placed on O2" in a free-text note has made it answerable by none, since none of the four can read the note until someone codes it by hand.
The comparison also shows why the terminology question cannot be left to coders at the end of a stay. By the time a coder sees the chart, the moment when the saturation was 88% on room air has already been recorded in one form or another. If it was recorded only as a sentence, the coder can choose R09.02 but cannot recover the numbers, and the quality analyst can count the code but cannot tell how severe the hypoxemia was or whether it responded to oxygen. The decision that matters most for all four vocabularies is made at the bedside, in the seconds it takes to key a value and its flow.
References
Bodenreider, O. (2004). The Unified Medical Language System (UMLS): Integrating biomedical terminology. Nucleic Acids Research, 32(Suppl. 1), D267-D270. https://doi.org/10.1093/nar/gkh061
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
Lee, D., de Keizer, N., Lau, F., & Cornet, R. (2014). Literature review of SNOMED CT use. Journal of the American Medical Informatics Association, 21(e1), e11-e19. https://doi.org/10.1136/amiajnl-2013-001636
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
What the NR 512 Week 3 assignment asks for
In Week 3 you set side by side the standardized terminologies or classification systems used in health care. Depending on the section, you may compare two systems in depth or survey several, but the stronger approach is to apply them to the same clinical finding so the comparison is concrete. Typical prompts ask for the purpose of each system, who maintains it, the level of detail it supports, and its role in nursing documentation, interoperability and reimbursement. You are expected to cite the developers or published reviews rather than general websites. Check whether your section requires a comparison table and a set number of systems, and keep any codes you quote accurate.
Inside the NR 512 Week 3 example
The example fixes one finding from a composite pneumonia admission and never leaves it. A table sets out what each vocabulary offers for that finding, the detail it keeps, the purpose it was built to serve and the body that maintains it. The prose then argues granularity: only LOINC keeps the values, SNOMED CT keeps the clinical meaning, ICD-10-CM keeps a category such as R09.02, and the nursing diagnosis keeps the judgment tied to a care plan. A section explains precoordination and postcoordination. Another uses the Unified Medical Language System to show that maps move concepts but not the evidence behind them. The paper ends by matching each vocabulary to a use and naming the bedside decision that serves all four.
Reading the NR 512 Week 3 grading rubric
Points in this assignment usually follow the depth of the comparison. The largest criterion rewards a real comparison, where systems are set against each other on the same features, rather than two summaries placed one after the other. Accuracy is graded closely, since wrong codes or maintainers are easy to spot. A criterion on relevance to nursing asks how each system affects documentation, data exchange or care planning. Support from published sources earns its own points, and the sample uses a LOINC update, a review of SNOMED CT use and a paper on the UMLS. As in earlier weeks, organization, APA 7 format and clear writing account for the remaining points on the rubric.
NR 512 Week 3 help from the desk
The biggest mistake is declaring one vocabulary better without saying better for what. A billing classification and a clinical terminology were built for different purposes, so a winner with no use named skips the analysis. Another is describing each system in turn and never comparing them. Students also claim that detail is lost in mapping without showing which detail; name the exact thing that disappears. Invented or outdated codes cost credibility quickly, so check every code you quote. Drifting from the chosen finding to a related one is another common problem. Keep one finding at the center of every paragraph, and if the table repeats the prose, cut one of them.
Get a NR 512 Week 3 example written to your instructions
Send the Week 3 prompt, the finding or the vocabularies your section named, and the rubric. We build the comparison table and the mapping argument around your own pairing, check every term against current published documentation, and it comes back inside 24-48h. The first example we write for you costs nothing at all.
More NR 512 papers and MSN samples
- NR 512 Week 1: Discussion Post on One Recorded Item
- NR 512 Week 2: Data Definition Brief, Oxygen Flow
- NR 512 Week 4: Concept Map
- NR 512 Week 5: Information Model Write-up
- NR 512 Week 6: Standards Appraisal
- NR 512 Week 7: Documentation Case Analysis
- NR 512 Week 8: Informatics Position Paper
NR 512 Week 3 questions, answered
Do I need access to a terminology browser?
Public browsers exist for the major vocabularies and using one keeps the codes accurate. Where access is limited, a comparison can be built from published documentation and course readings without quoting particular code values at all, so long as the paper is explicit that it compares structures and purposes rather than asserting specific codes it could not verify.
Can I compare a national standard with my hospital's local names?
That pairing is often the most interesting one available. Local names are an interface terminology in everything but title, built for speed at a keyboard rather than for comparison, and setting them against a reference terminology exposes the trade-off directly. The uncontrolled nature of the local set is itself part of the finding and belongs in the argument.
How much detail belongs in the table?
Enough that the table stands alone and no more. Four or five columns is typical, and each column should be one a reader could fill in for a third vocabulary tomorrow. Anything needing a sentence of explanation belongs in the prose instead. Tables asked to carry the argument tend to lose the reasoning marks entirely.
Where can I find a free NR 512 Week 3 sample paper?
This page holds a complete NR 512 Week 3 terminology comparison, with its table and references, free to read. For a comparison built on a finding from your own specialty, use the request form and a free custom version is written.
Which terminologies should I compare in NR 512 Week 3?
Common pairs are SNOMED CT and ICD-10-CM, or LOINC and a hospital's local lab names. The sample adds a nursing diagnosis because it keeps something the other systems cannot, the link to a care plan.