| Course | NURS 6451 Evaluation Methods for Health Information Technology |
|---|---|
| Week | Week 11 |
| Paper type | Reflection on evaluation practice |
| Length | About 760 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Master of Science in Nursing (MSN) |
| Updated | September 2026 |
Free sample paper for NURS 6451 Week 11
Three Things I Now Do Differently When a System Changes, and One I Still Do Poorly: A Reflection on Evaluating the Messaging App
Student Name
College of Nursing, Walden University
NURS 6451: Evaluation Methods for Health Information Technology
Instructor Name
Month Day, Year
Three Things I Now Do Differently When a System Changes, and One I Still Do Poorly: A Reflection on Evaluating the Messaging App
Three things have changed in how I approach a new system on a unit: I capture a baseline before anything changes, I read vendor reports as adoption data rather than evidence of effect, and I add the roles downstream of the user to every evaluation I touch. Each change can be traced to a place early in this course where I was about to do the opposite, and to later work that corrected it. One thing has not changed enough, and I name it at the end.
Capturing a Baseline Before Anything Changes
In my first-week post, I reported the dashboard's median time to read receipt, which was well under a minute, and wrote that the numbers "point in the right direction." I was already comparing it, in my head, with how slow pagers felt. I had no pager figure at all. By the time I wrote the measurement plan in Week 5, I had learned why: paging records show only that a page was sent, and the response came by phone and was recorded nowhere. Comparing a sent time with a read receipt would have manufactured an improvement. The plan rebuilt the baseline by watching requests on Units 3 and 4 while they still carried pagers.
What changed is not only that I know a baseline is needed but that I now think of it as perishable. Two of our four units had already gone live before anyone asked the question, and their pager period is gone for good. The next time any system is scheduled to change on a unit I work with, I will ask in the first planning meeting what we would need to measure before go-live, because after go-live it is too late.
Reading Vendor Reports as Adoption Data
In the same first post, I defended the dashboard's numbers as "real," "large" and pointing "in the right direction." I did go on to argue that it was not an evaluation, but my first instinct was to trust it. The CDC framework's standards helped me say why that instinct is risky: the dashboard fails the utility standard because no decision can be made from it, and it fails accuracy because read receipts measure opening, not answering (Centers for Disease Control and Prevention [CDC], 1999). By Week 8, I was writing about the vendor as a stakeholder with an interest in how results are reported. That shift, from treating vendor figures as evidence to treating them as one party's data, is the second change. I now ask of any vendor report what it counts, who chose what to count and what it would show if the system were not helping.
Adding the Roles Downstream of the User
My early evaluation questions were all about nurses and prescribers, the people who send and receive messages. The workflow analysis in Week 7 gave the medical record its own lane and found decisions agreed in threads that never reached the chart. Then, in Week 9, a pharmacist told me about clarification messages none of our measures would have caught. Research on clinical information systems has long warned that some of their most important side effects show up in how people coordinate work, not at the keyboard (Ash et al., 2004). The downstream prompt I proposed, a short question every two weeks to pharmacists, clerks and night coverage, is now part of the evaluation plan, and I intend to add something like it to any system change I am involved in.
What I Still Do Poorly
Stakeholder engagement is what I still do poorly. The stakeholder analysis in Week 8 was easy to write: a table of roles, what each controls and a planned step. The conversations the table implies are harder. When the night-shift hospitalists objected to being observed, my first response was to explain the design again rather than to ask what they were worried about. The table said to meet their group and offer an opt-out; in practice I put that meeting off for two weeks. Reporting guidance for health informatics evaluations expects the roles of everyone involved in a study to be described openly (Talmon et al., 2009), and doing that well depends on having talked to them. My commitment is concrete: for the next system change on my unit, I will hold the stakeholder conversations before I write the stakeholder table, and I will ask my manager to check at our next review whether I did.
References
Ash, J. S., Berg, M., & Coiera, E. (2004). Some unintended consequences of information technology in health care: The nature of patient care information system-related errors. Journal of the American Medical Informatics Association, 11(2), 104-112. https://doi.org/10.1197/jamia.M1471
Centers for Disease Control and Prevention. (1999). Framework for program evaluation in public health. MMWR Recommendations and Reports, 48(RR-11), 1-40.
Talmon, J., Ammenwerth, E., Brender, J., de Keizer, N., Nykänen, P., & Rigby, M. (2009). STARE-HI: Statement on reporting of evaluation studies in health informatics. International Journal of Medical Informatics, 78(1), 1-9. https://doi.org/10.1016/j.ijmedinf.2008.09.002
What the NURS 6451 Week 11 instructions ask for
The closing prompt generally has you look back at what you learned about health IT evaluation, identifying how your thinking or practice has changed, supported by examples from your coursework and by relevant literature. Many prompts ask for areas that still need development and a plan. Reflections are commonly two to four pages in first person. Choose a small number of specific changes, show each with evidence from earlier assignments, and be honest about what remains weak. End with a commitment that someone could check, tied to your actual practice setting. Some prompts ask you to connect your reflection to a professional standard; if so, cite it where it supports a claim.
How the NURS 6451 Week 11 example is put together
The opening paragraph names three changes in one sentence and promises a weakness. Each change has its own section pairing an early passage with later work: the dashboard comment with the observed baseline, the first instinct to trust vendor figures with the stakeholder analysis that treated the vendor as a party, and early questions limited to senders and receivers with the workflow analysis and the pharmacist's observation. Sources appear only for general claims, including the CDC framework and research on unintended consequences. The final section admits that stakeholder conversations were delayed and makes a checkable commitment. Every source supports a general claim rather than a personal one. Stakeholder work is the admitted gap.
NURS 6451 Week 11 rubric: what earns full marks
Reflection rubrics usually score depth of insight, use of specific evidence from coursework, connection to evaluation principles and literature, honesty about limitations, a forward plan and writing. Depth rewards changes in thinking explained with reasons, not a list of topics covered. Evidence is judged on whether earlier work is quoted or described precisely. Connection to literature should support general claims rather than decorate. Limitations earn credit when they are specific. The plan should be concrete and observable. Writing covers first person used with discipline and correct citations. Some rubrics also look for a link between the admitted weakness and the commitment, which the example provides. Honesty about weaknesses is valued.
NURS 6451 Week 11 help: mistakes that cost marks
The most common loss is a reflection that summarizes each week's assignment in turn. Another is claiming growth without showing an earlier passage that proves it. Some reflections list many small lessons and discuss none in depth. Others avoid naming any weakness, or end with a vague intention to keep learning. Pick three changes, show where each began and where it was corrected, name one thing you still do poorly and give a commitment tied to your next real opportunity. Also quote or describe earlier work precisely, since vague references to growth are hard to credit. Keep the commitment small enough to keep. Keep first person consistent.
Get a NURS 6451 Week 11 example written to your instructions
A passage or two from your earlier work anchors the reflection best, so attach them beside the Week 11 prompt and rubric and the pairs are drawn from that material. Your first request carries no charge and returns in 24-48h, with the closing commitment worded so you can adjust it.
More NURS 6451 papers and MSN samples
- NURS 6451 Week 1: Discussion post
- NURS 6451 Week 2: Evaluation question memo
- NURS 6451 Week 3: Literature matrix
- NURS 6451 Week 4: Evaluation design
- NURS 6451 Week 5: Measurement plan
- NURS 6451 Week 6: Usability analysis
- NURS 6451 Week 7: Workflow impact analysis
- NURS 6451 Week 8: Stakeholder analysis
- NURS 6451 Week 9: Discussion post
- NURS 6451 Week 10: Evaluation plan
- NURS 6501 Week 11: Multisystem cascade synthesis
- NURS 6441 Week 11: Lessons learned
- NURS 6512 Week 11: Full-system adult history and physical
- NURS 6421 Week 11: Change case
NURS 6451 Week 11 questions, answered
Which earlier assignments make the best evidence?
The ones where the author was most confident and later turned out to be wrong, because the contrast is sharpest. The sample draws on the Week 1 thread and an early dashboard sentence, both written before measurement and baseline problems had been met. Late work that simply extends early work shows growth less clearly than a correction does.
What if my evaluation was about a different system?
Then the three changes may differ, but the method holds: name specific changes, show each with earlier and later passages, admit what remains weak, and commit to something observable. A reflection built on a documentation module or a remote monitoring program would draw its pairs from that system's work, and the structure would not need to change.
Does the reflection need to mention practice outside informatics?
Only if your prompt asks. The sample stays with practice the author could influence, the next system change on a unit, because that keeps the commitment believable. Some sections ask how evaluation thinking applies to a clinical role more broadly, and a short added section can answer that without diluting the evaluation focus.
Where can I find a free NURS 6451 Week 11 sample paper?
The complete reflection, three changes, the admitted weakness and the commitment, is free to read here. A reflection built on your own term's assignments can be drafted on request.
Which assignments make the best evidence in a NURS 6451 reflection?
The ones where you were confident early and later corrected yourself, because the contrast shows real change. Early posts and first drafts often provide the clearest before picture.