| Course | NR 361 RN Information Systems in Healthcare |
|---|---|
| Week | 7 |
| Paper type | Informatics project proposal |
| Length | About 1,100 words, 5 pages |
| Format | APA 7 student paper |
| School | Chamberlain University |
| Program | RN-to-BSN |
| Updated | October 2026 |
Free sample paper for NR 361 Week 7
Moving Pressure Injury Measurements Out of the Note and Into Coded Fields: An Informatics Project Proposal
Student Name
College of Nursing, Chamberlain University
NR 361: RN Information Systems in Healthcare
Instructor Name
Month Day, Year
Moving Pressure Injury Measurements Out of the Note and Into Coded Fields: An Informatics Project Proposal
The Problem, Stated as Data
On a composite 36-bed medical unit, nurses document pressure injury length, width and depth in a free-text wound note, usually as a phrase such as sacral wound 3 by 2.5 by 0.5, slightly smaller. The electronic record has structured wound fields in the Lines, Drains, Airways and Wounds section, including numeric fields for each dimension, but the unit's habit, carried over from paper documentation, is to type the measurements in the note. The problem is therefore data that is present but unstructured. Because the measurements sit in prose, the record cannot graph a wound over time, the wound care nurse cannot run a report of wounds that are not healing, and the unit's quality report cannot count how many pressure injuries were measured at least weekly as the unit's policy requires.
The size of the problem is known from one review. The wound care nurse reviewed the records of 20 patients with pressure injuries on the unit last quarter and found measurements in structured fields for 4 and in free text only for 13; 3 had no measurements at all for at least one week. International guidance recommends measuring pressure injuries regularly to monitor healing and to prompt reassessment of the treatment plan when a wound is not improving (European Pressure Ulcer Advisory Panel et al., 2019), and that monitoring depends on measurements being comparable over time.
The Change, in One Sentence
Every pressure injury measurement on the unit will be entered in the existing structured wound fields, and the free-text wound note will be shortened to a description of appearance and treatment with no measurements in it.
Why Structure Matters Here
Rosenbloom et al. (2011) describe a tension in clinical documentation between structured data, which computers can count, compare and report, and narrative text, which captures nuance and context but is hard to reuse. They argue that the right balance depends on how the information will be used. Wound measurements are a clear case for structure: they are numbers, they are compared over time, and their main uses are trend graphs and reports. Wound appearance, odor and the patient's pain are better suited to narrative. The proposal keeps each kind of information where it works best rather than moving all wound documentation into fields.
Stakeholders, With What They Will Do and What It Costs
Staff nurses: Will enter measurements in three numeric fields instead of typing them in the note. Cost: about 30 seconds more per wound at first, because the fields sit in a different part of the record from the note; after a few weeks, perhaps no difference.
Wound care nurse: Will build and run a monthly report of wounds whose area has not decreased in two weeks and review those patients. Gain: a list she currently cannot produce. Cost: about two hours a month.
Nurse manager: Will approve the change and include the percentage of wounds measured weekly in the unit quality report. Gain: a measure the unit is already expected to meet.
Clinical informatics analyst: Will add the wound measurement fields to the unit's shift assessment navigator so nurses see them next to the note, and build the report. Cost: about six hours.
Providers: Will see a trend graph of wound size in the record. Gain: faster recognition of wounds that are not healing.
Plan and Timeline
In weeks 1 and 2, the informatics analyst moves the wound measurement fields into the shift assessment navigator for the unit and the wound care nurse drafts the report. In week 3, the wound care nurse teaches the change at four huddles, five minutes each, using one example of a wound graph built from structured data. In week 4, the change goes live and the free-text wound note template is edited to prompt for appearance and treatment only. For the first month, the wound care nurse checks every new wound entry weekly and gives nurses same-day feedback. Carayon et al. (2006) describe how changes to documentation tools succeed when they are designed around how the work is actually done; placing the fields next to the note, where nurses already are, is the design choice that makes the change likely to hold.
How Success Will Be Measured
The primary measure is the percentage of pressure injuries with length, width and depth entered in structured fields at least weekly, calculated from a report of structured wound entries against the list of patients with pressure injuries, monthly. The baseline from the review is 4 of 20, or 20 percent; the target is 80 percent at three months. A secondary measure is whether the wound care nurse's monthly report identifies nonhealing wounds and leads to a change in treatment, recorded as the number of treatment changes following the report. The proposal does not promise faster wound healing, which depends on many factors and would take far longer to show.
Risks and Responses
Three risks could undermine the change. The first is duplication: nurses may enter measurements in the fields and keep typing them in the note out of habit, which doubles the work and leaves two versions that may disagree. The response is the edited note template, which no longer prompts for measurements, and the wound care nurse's feedback in the first month. The second risk is inconsistent measurement technique, which structured fields do not fix: a wound measured head to toe by one nurse and side to side by another will produce a misleading trend even when every number is in a field. The huddle teaching therefore includes the unit's measurement convention, length as the longest head-to-toe dimension and width perpendicular to it, and the fields will carry a short reminder of that convention. The third risk is that the report produces a list nobody acts on. The response is to assign the report to the wound care nurse by name, with the nurse manager reviewing the number of nonhealing wounds identified and acted on each month.
If the change works on this unit, the same fields and report could be offered to the other medical units without new build work, since the fields already exist hospital-wide. That makes the proposal inexpensive to extend, which is a point worth making to the nurse manager when approval is requested.
References
Carayon, P., Schoofs Hundt, A., Karsh, B.-T., Gurses, A. P., Alvarado, C. J., Smith, M., & Flatley Brennan, P. (2006). Work system design for patient safety: The SEIPS model. Quality and Safety in Health Care, 15(Suppl. 1), i50-i58. https://doi.org/10.1136/qshc.2005.015842
European Pressure Ulcer Advisory Panel, National Pressure Injury Advisory Panel, & Pan Pacific Pressure Injury Alliance. (2019). Prevention and treatment of pressure ulcers/injuries: Clinical practice guideline. The international guideline (E. Haesler, Ed.). EPUAP/NPIAP/PPPIA.
Rosenbloom, S. T., Denny, J. C., Xu, H., Lorenzi, N., Stead, W. W., & Johnson, K. B. (2011). Data from clinical notes: A perspective on the tension between structure and flexible documentation. Journal of the American Medical Informatics Association, 18(2), 181-186. https://doi.org/10.1136/jamia.2010.007237
What the NR 361 Week 7 assignment asks for
The Week 7 proposal asks you to design an informatics project that addresses a problem in your setting. Students are usually asked for a problem statement with data, the proposed change, a rationale from the literature, stakeholders and their roles, a timeline, an evaluation plan, risks and APA references. State the problem as a data failure before any solution. Size it with the numbers you can honestly support. Write the change in one sentence. Explain why structure matters, with a source. List stakeholders with a verb for what they will do and the cost to them. Measure success with a report that exists because of the change. Plan for the most likely ways it could fail.
How the NR 361 Week 7 example is put together
The problem section describes nurses typing wound size as a phrase in the note, which no report can read, and the wound nurse's review of 20 patients. The change section moves length, width and depth into existing structured fields and shortens the note to appearance and treatment. Rosenbloom and colleagues explain the tension between structured and narrative data. The stakeholder list gives staff nurses about 30 seconds more per wound at first, the wound nurse a monthly report of wounds not shrinking, the manager a quality measure, the analyst about six hours of work and providers a trend graph. The plan runs over several weeks. Evaluation tracks structured weekly measurement against the review baseline. Risks, including duplicate entry, close the proposal.
Reading the NR 361 Week 7 grading rubric
Proposal rubrics for NR 361 usually score the problem statement and data, the clarity of the proposed change, use of evidence, stakeholder analysis, implementation plan, evaluation and APA. The problem and evaluation rows decide the grade most, and the proposal meets them with a data problem sized from a review and a measure that exists only after the change. The change is credited for fitting in one sentence and using fields that already exist. Evidence scores through Rosenbloom and colleagues and the pressure injury guideline. Stakeholder analysis earns points because every group has an action and a cost or gain. The timeline and risk responses complete the implementation row. Declining to promise faster healing shows honest evaluation.
NR 361 Week 7 help from the desk
The most expensive proposal buys software, naming a product and describing what it can do without saying what anyone will do differently. Another loss is a problem stated so broadly, such as "poor documentation," that no change could address it. Students also list stakeholders by title with no actions, promise clinical outcomes the project cannot show, or skip the risks. Real workplace data is welcome but not required, and estimates should be labeled as such. Keep the project small enough for one unit. A change model can strengthen the plan if your course asks for one. If you have a documentation problem in mind, describe it and an NR 361 proposal can be built around a one-sentence change.
Get a NR 361 Week 7 example written to your instructions
Send the Week 7 assignment sheet or presentation requirements, plus the problem you want proposed against, and a custom example is written to those requirements and returned inside 24 to 48 hours. The first one is free. If slides are required rather than a paper, say so and the example arrives in that form.
More NR 361 papers and RN-to-BSN samples
- NR 361 Week 1: Downstream Data Entry Discussion
- NR 361 Week 2: Penicillin Allergy EHR Workflow
- NR 361 Week 3: Continuous Pulse Oximetry Evaluation
- NR 361 Week 4: Tele-ICU Literature Review Matrix
- NR 361 Week 5: Pediatric Telephone Triage Analysis
- NR 361 Week 6: Cycle Tracking Health App Review
- NR 361 Week 8: Reflection
- NR 393 Week 7: Nurse Leader Profile
- NR 360 Week 7: Fall-Risk Alert Informatics Project
- NR 394 Week 7: Health Promotion Plan
- NR 351 Week 7: Professional Development Plan
NR 361 Week 7 questions, answered
Does the proposal need real data from my workplace?
Rarely required and often not permitted. A published figure with the setting named does the same job, and a clearly labeled estimate does it well enough when nothing else exists. Anything from your employer stays yours to decide about, and if you leave it out the proposal still holds together, provided the before value is presented as an estimate rather than dressed as a measurement.
How big should the project be?
Small enough that you can name the unit, the owner and the month it starts. A single report scheduled to the right people, one free text field converted to a coded list, one alert retired: each of those is defensible in a course paper and each has a measure. Enterprise scale proposals read impressively and collapse the moment a grader asks who is doing the work.
Is a theory or change model expected?
Many sections ask for one and it earns its space only if the paper uses it. Naming a model and then writing a plan with no trace of it is worse than not naming one, because it advertises the gap. If your section requires a framework, let its stages set the implementation headings, so the reader can see the model doing something rather than sitting in the introduction.
Where can I find a free NR 361 Week 7 sample paper?
The full Week 7 proposal to move wound measurements into coded fields, with the problem sizing, the one-sentence change, stakeholders and costs, timeline, evaluation, risks and three references, is on this page.
How does the NR 361 Week 7 proposal measure success?
By the percentage of pressure injuries with length, width and depth entered in structured fields at least weekly, compared with the baseline from the wound care nurse's review.