| Course | HIM 560 HIM Informatics and Technology Infrastructure |
|---|---|
| Module | Module 8 |
| Paper type | graduate reflective journal on technology acceptance and adoption |
| Length | About 380 words, 3 pages |
| Format | APA 7 student paper |
| School | Southern New Hampshire University |
| Program | MS Health Information Management |
| Updated | October 2026 |
Free sample paper for HIM 560 Module 8
Module Eight Journal
The Viewer Nobody Opens
Three years ago, Pelican Shoals Health bought a web viewer so hospital physicians could see clinic results without waiting for a fax. Last month I checked the access logs: eleven physicians had opened it in the past year, most of them once. In the same period, our coders adopted a new encoder so completely that no one remembers the old one. Both were decent products. I spent this week trying to understand why one took hold and the other did not.
Holden and Karsh (2010) looked back over two decades of health care studies using the technology acceptance model, and two beliefs, that a system is useful and that it is easy to use, kept predicting whether clinicians intended to use a system. The encoder was obviously useful to coders; it cut the time to code a chart and caught errors. The viewer's usefulness was real but invisible, because physicians did not know which patients had clinic results worth checking. It also failed on ease: a separate login, a patient search that required the clinic's record number and results three screens deep.
Venkatesh et al. (2003) added social influence and facilitating conditions to that picture. Coders learned the encoder together, from a supervisor who used it first, and had a vendor trainer on site for a week. The viewer was announced by email, with a tip sheet, and no respected physician ever used it in front of colleagues. In their review, Cresswell and Sheikh (2013) argued that adoption depends on the organization around a system, its leaders, its training and how well the tool fits the day's work, at least as much as on the software, and the viewer had none of that support.
This matters now, because we are asking every clinician to move to the regional system's record. I used to think adoption followed from buying the right product. I now think it follows from making usefulness obvious, removing steps, recruiting respected early users and supporting people in person. I will ask for a physician champion on each unit and trained helpers on the floors, beside users, through the opening fortnight. I will also check the logs again three months after go-live, because this week taught me that usage numbers tell the truth faster than surveys do.
References
Cresswell, K., & Sheikh, A. (2013). Organizational issues in the implementation and adoption of health information technology innovations: An interpretative review. International Journal of Medical Informatics, 82(5), e73-e86. https://doi.org/10.1016/j.ijmedinf.2012.10.007
Holden, R. J., & Karsh, B.-T. (2010). The technology acceptance model: Its past and its future in health care. Journal of Biomedical Informatics, 43(1), 159-172. https://doi.org/10.1016/j.jbi.2009.07.002
Venkatesh, V., Morris, M. G., Davis, G. B., & Davis, F. D. (2003). User acceptance of information technology: Toward a unified view. MIS Quarterly, 27(3), 425-478. https://doi.org/10.2307/30036540
What the HIM 560 Module 8 instructions ask for
The HIM 560 Module 8 journal asks you to reflect on how people come to accept or resist health information technology, using acceptance theory and your own observations. Keep it personal and about a page long, with a few sources in APA 7 that explain what you saw. Choose one or two systems from your experience, ideally one that was adopted and one that was not, and compare them. Use concepts such as perceived usefulness, ease of use, social influence and facilitating conditions to explain the difference. Reflect on what you believed about adoption before and what you believe now, and describe how you will apply the lesson to a change ahead.
How this HIM 560 Module 8 journal example is built
Pelican Shoals Health's director checks access logs and finds that eleven physicians opened a clinic results viewer in a year, while coders adopted a new encoder within weeks. Holden and Karsh's review of the technology acceptance model points to usefulness and ease, since the viewer required a separate login and clinic record numbers. Venkatesh and colleagues' social influence and facilitating conditions explain the encoder's supervisor-led, trainer-supported launch, and Cresswell and Sheikh's organizational factors complete the picture. The HIM 560 journal applies the lesson to the coming move onto a regional record with physician champions, on-floor helpers and a usage check three months after go-live.
Where the HIM 560 Module 8 rubric puts the points
Adoption journals in HIM 560 tend to be graded on a concrete comparison, accurate use of acceptance theory, honest reflection on the writer's earlier assumptions, attention to organizational as well as technical factors and a practical application to a real change, supported by sources in APA 7. Journals that stand out use evidence, such as access logs or usage counts, rather than impressions, and explain adoption as the result of several conditions working together. Graders reward entries in which theory changes the writer's plan for an upcoming implementation. Naming the specific steps that made one system easy to adopt is more convincing than general statements about training, and a follow-up measure shows commitment.
HIM 560 Module 8 help: the mistakes that cost points
HIM 560 journals fall short when they describe a system without comparing adoption, name a theory without applying its concepts, blame users for resistance or end without any change in practice. Some also cite acceptance models from other industries without connecting them to health care work. Should the prompt center on another angle, such as patient adoption of portals, telehealth or workarounds, pass it along with an example from your own setting, and the entry will examine that example just as candidly. Usage numbers help if you have them, even rough ones. HIM 560 journals we write compare real systems, apply acceptance theory and end with a plan for the next change.
Get HIM 560 Module 8 written to your instructions
Send the HIM 560 Module 8 journal prompt and one or two systems you have seen adopted or ignored at work. The entry will compare them honestly, explain the difference with acceptance theory and organizational research and describe how you will apply the lesson to an upcoming change, ready within 24 to 48 hours, free on a first request. 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 1 Discussion: What an HIM Department's Work Rests On
- HIM 560 Module 2 Interoperability Short Paper: Why Records Still Arrive by Fax
- HIM 560 Module 3 Final Project Milestone One: A Current-State Infrastructure Assessment
- HIM 560 Module 4 Discussion: Hosting the Record: On Site, Hosted or Cloud
- HIM 560 Module 5 Final Project Milestone Two: Requirements for Replacing Document Imaging and Unifying the Clinics
- HIM 560 Module 6 Downtime Short Paper: Downtime and Disaster Recovery on the Gulf Coast
- HIM 560 Module 7 Final Project Milestone Three: Evaluating Three Vendors
- HIM 560 Module 9 Final Project: The Technology Infrastructure Plan
- HIM 560 Module 10 Reflection: What Planning Infrastructure Taught the Writer
- HIM 540 Module 4 Coding and Compliance Short Paper: Governing Coded Data Across Four Hospitals
- HIM 550 Module 10 Reflection: What Managing Data Taught the Writer
- HIM 520 Module 5 Final Project Milestone Two: A Training and Development Plan
- HIM 530 Module 9 Final Project: The Information Protection Program
HIM 560 Module 8 questions, answered
Where can I find a free HIM 560 Module 8 Journal sample?
The complete HIM 560 Module 8 journal is on this page: why one system went unused while another was adopted in weeks, and lessons for a record change.
What is the technology acceptance model?
A theory that people's intention to use a technology depends mainly on how useful and how easy to use they perceive it to be.
What does UTAUT add to the technology acceptance model?
It adds social influence and facilitating conditions, such as training and support, to expectations about performance and effort.
Why do clinicians avoid some systems?
Extra logins, hidden information, unclear benefit, little support and colleagues who do not use them all discourage adoption.
How can adoption of a new record be encouraged?
By making usefulness obvious, reducing steps, recruiting respected early users and offering in-person support at go-live.