HIM 560 Module 10 Reflection Example

Reviewed by Delia Ravenscroft, MSN, RN

This HIM 560 Module 10 Reflection sample looks back on a graduate course in informatics and technology infrastructure and asks what the writer now does differently. It was written for SNHU HIM 560 (HIM-560), whose final module invites MS Health Information Management students to weigh how the term changed their planning habits. The composite health information director at a 220-bed hospital on the Texas Gulf Coast confesses to starting the course with a list of products to buy. The entry explains three shifts: inventorying what exists before proposing anything, judging a system by the people, workflow and rules around it rather than its features, and stating recovery targets in hours and minutes. It closes with an uncomfortable lesson about a failed viewer and one concrete habit the director will keep.

CourseHIM 560 HIM Informatics and Technology Infrastructure
ModuleModule 10
Paper typegraduate reflection on learning to plan health IT infrastructure
LengthAbout 420 words, 3 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramMS Health Information Management
UpdatedOctober 2026

Free sample paper for HIM 560 Module 10

1

Module Ten Reflection

From a Shopping List to a Map

I started this course with a list of things I wanted Pelican Shoals Health to buy: a cloud archive, a new interface engine, a patient portal for the clinics. Looking at that list now, I can see that I had never written down what we already ran. Ten modules later I have a map of forty interfaces, two record systems, one basement and a fax line, and the shopping list looks very different.

What this page is doingThe reflection opens with an honest starting point.
2

The first change is order. I now describe the current state before proposing anything. Writing the assessment in Module Three forced me to learn that six of our interfaces carried no owner at all, and that discovery shaped every later choice more than any product brochure did.

The second change is what I count as the system. Sittig and Singh (2010) treated health IT as eight dimensions that act on one another, among them the machines and code, the clinical content, the people using it, how work flows, internal policy and outside regulation, and argued that problems usually appear where those dimensions meet. Greenhalgh et al. (2017) made a similar point about why technology projects are abandoned: complexity in the condition, the users, the organization and the wider system adds up. The unused clinic viewer from my journal entry fits both. Ash et al. (2004) warned that patient care information systems fail in ways that come from the fit between a system and real clinical work, not only from bugs, and that matched what I saw. Nothing was wrong with the software. It failed at the login, at the workflow and at the absence of a physician who used it in public. I now ask about those dimensions before I ask about features.

The third change is that recovery has a number. I used to say our backups were fine. After the downtime paper I can say the record must be running again inside four hours and lose at most a quarter hour of entries, and I can test whether a plan meets that, which is far more useful in a contract meeting than reassurance.

What this page is doingThree shifts are tied to course moments and two frameworks.
3

The hardest part was admitting that the viewer, which I had championed three years ago, was my own failure of planning. I still want the clinics on one record, but I will keep the systems map current every quarter, review it with our two analysts and treat any new purchase as a change to that map, not an item on a list.

What this page is doingThe writer owns a past mistake and names one lasting habit.
4

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

Greenhalgh, T., Wherton, J., Papoutsi, C., Lynch, J., Hughes, G., A'Court, C., Hinder, S., Fahy, N., Procter, R., & Shaw, S. (2017). Beyond adoption: A new framework for theorizing and evaluating nonadoption, abandonment, and challenges to the scale-up, spread, and sustainability of health and care technologies. Journal of Medical Internet Research, 19(11), Article e367. https://doi.org/10.2196/jmir.8775

Sittig, D. F., & Singh, H. (2010). A new sociotechnical model for studying health information technology in complex adaptive healthcare systems. Quality and Safety in Health Care, 19(Suppl. 3), i68-i74. https://doi.org/10.1136/qshc.2010.042085

What the HIM 560 Module 10 instructions ask for

The tenth HIM 560 module closes the course by asking how planning informatics and infrastructure changed the way you think and work. Expect a personal entry of roughly a page, citing a source or two in APA 7 when a reading helped cause a shift you actually made. Skip the tour of each module. Choose two or three changes in how you approach systems, link each one to a specific assignment or discovery from the term and say what it means for your job. Graders also look for something you got wrong, a decision you would now make differently or a limit in your own knowledge. Finish with a habit or step you will continue once the course is over, tied to your role.

How this HIM 560 Module 10 reflection example is built

Pelican Shoals Health's director opens by admitting the course began with a list of products to buy and no record of what the hospital already ran. Three shifts follow. Inventory comes first, prompted by finding six interfaces with no owner during the Module Three assessment. A system now means its people, workflow and rules as well as its software, explained with Sittig and Singh's eight dimensions and the nonadoption framework of Greenhalgh and colleagues, and illustrated by the clinic viewer that eleven physicians opened in a year. Recovery is stated as four hours and fifteen minutes rather than a feeling. The entry ends by owning the viewer as the writer's own planning failure and committing to a quarterly systems map.

Where the HIM 560 Module 10 rubric puts the points

Reflection rubrics in HIM 560 tend to reward specific changes in thinking rather than summaries of content, a link between each change and a real moment from the course, sources used to explain rather than decorate and an honest look at the writer's own limits or past decisions. Strong entries show that the student can now see infrastructure as a sociotechnical whole and can speak about targets, owners and dependencies in concrete terms. Graders give credit when a reflection admits a mistake plainly, because that makes the claimed growth believable. Clear organization, a professional tone and correct APA 7 for any cited work also count. A closing step that names a routine, a schedule and the people involved scores better than a loose pledge to stay curious.

HIM 560 Module 10 help: the mistakes that cost points

HIM 560 reflections often lose marks by retelling the syllabus, praising the course, citing a framework without connecting it to anything the writer did or ending with a vague wish to stay current with technology. Others stay so positive that nothing seems to have changed. If your prompt focuses instead on a program outcome, your leadership style or a career goal in informatics, send it with a short note on your final project and your current job, and the entry will be built from that material. A detail or two about a system you have seen succeed or fail helps a great deal. Our HIM 560 reflections name real shifts, own a misstep and end with a routine you can keep.

Get HIM 560 Module 10 written to your instructions

Share the HIM 560 Module 10 prompt along with a note on your final project and what you do at work. We will write a reflection that traces two or three real changes to moments in your course, owns a decision you would revisit and ends with a habit you can keep. Turnaround is one to two days, and the first one costs nothing. The paper above is an original model document written by our desk, not a submitted student paper and not an official Southern New Hampshire University document.

More HIM 560 papers and related MS Health Information Management samples

HIM 560 Module 10 questions, answered

Where can I find a free HIM 560 Module 10 Reflection sample?

This page carries the complete HIM 560 Module 10 reflection, in which a hospital HIM director moves from a product wish list to a systems inventory, sociotechnical thinking and recovery targets written as numbers.

What should an HIM 560 reflection cover?

Two or three specific changes in how you plan systems, each tied to an assignment or discovery from the term, a mistake or limit you recognized and a routine you plan to carry into your job.

Which frameworks fit an informatics infrastructure reflection?

Sociotechnical models such as Sittig and Singh's eight dimensions, or the NASSS framework on nonadoption, work well because they explain why technology succeeds or fails beyond its features.

Do I need citations in a reflection post?

Cite one or two readings in APA 7 when they helped change how you plan systems. A reflection built entirely on citations reads like a literature review rather than a personal entry.

How long is the HIM 560 Module 10 reflection?

Most versions run about a page, roughly 350 to 500 words, though your instructor's prompt and rubric set the actual expectation for your section of the course.