| Course | HIM 615 Health Care Information Systems and Technology |
|---|---|
| Topic | Topic 7 |
| Paper type | Post-implementation adoption review |
| Length | About 970 words, 3 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | MS in Health Informatics |
| Updated | September 2026 |
Free sample paper for HIM 615 Topic 7
Used Everywhere, Helping Unevenly: A Nine-Month Post-Implementation Review of Paloma Basin Medical Group's New EHR
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HIM-615: Health Care Information Systems and Technology
Topic 7 Assignment
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Used Everywhere, Helping Unevenly: A Nine-Month Post-Implementation Review of Paloma Basin Medical Group's New EHR
Measures Agreed Before Go-Live
Nine months after Paloma Basin Medical Group's twelve clinics went live on the new enterprise record, this review asks whether the system has helped. It uses only measures agreed before cutover, with baselines taken from the needs assessment and updated at cutover for the two problems the group fixed in its old system while waiting. Choosing measures after go-live would allow success to be found in almost anything, so none has been added.
The measures are organized by DeLone and McLean's (2003) model of information systems success, which separates system quality, information quality and service quality from use and user satisfaction, and all of these from net benefits. Used this way, the model stops high use from standing in for success. Clinicians must use the new record whether it helps them or not.
Results Against Baseline
Table 1
Agreed Measures, Baseline and Nine Months
| Dimension | Measure | Baseline | Nine months |
|---|---|---|---|
| Use | Orders entered electronically | 96% | 99% |
| Information quality | Outside laboratory results stored as discrete values | 22% | 81% |
| Net benefit | Referrals with consult report in record within 60 days | 63% at cutover | 78% |
| Net benefit | Transfers between clinics booked without a phone call | 0% | 88% |
| Net benefit | Median refill decision time | 1.4 business days at cutover | 1.1 business days |
| System quality | Physician time in record per visit | 14.8 minutes | 16.2 minutes |
| Net benefit | Time in record outside clinic hours per clinic day, physicians | 1.3 hours | 1.6 hours |
| Net benefit | Time in record outside clinic hours per clinic day, advanced practice clinicians | 1.2 hours | 1.1 hours |
| System quality | Inbox time per clinic day, physicians | 44 minutes | 52 minutes |
| User satisfaction | Clinicians satisfied or very satisfied | 41% | 58% |
What the Audit Logs Show, and What They Cannot
The structural gains are real. Discrete outside results, closed referral loops and cross-clinic scheduling were the three product limits the needs assessment identified, and all three improved substantially. These were the reasons for replacement, and on them the purchase has worked.
The documentation burden has not improved, and for physicians it is worse. Audit logs show physicians spending 1.4 more minutes in the record per visit and 18 more minutes a day outside clinic hours than before. Arndt et al. (2017) showed that event logs can measure this burden reliably when calibrated against direct observation, which the group did for two weeks at baseline. Averaged across all clinicians, the after-hours figure rose only slightly, which would have hidden the problem; broken out by role, it is concentrated among physicians, whose inbox volume grew when the new system began routing all outside results to the ordering physician rather than to a clinic pool.
Audit logs cannot see work done outside the system, which is why the review also walked the clinics.
The Workaround Inventory
Over two weeks, the review team observed each clinic for half a day and asked staff what they do outside the record. Seven workarounds were found. The most common was at eight of twelve clinics: nurses keeping paper lists of refill callbacks, because the refill protocol in the new system has no status for "patient called, waiting for pharmacy," so a refill disappears from the work queue once approved even if the patient has not been told. Others included a shared spreadsheet for tracking prior authorizations and sticky notes on monitors listing the order set names clinicians could not find by search.
Koppel et al. (2008) studied workarounds to bar-code medication administration and found that they arose from specific technology, task and organizational causes, and that they created their own risks. The review treats each workaround the same way, as evidence of a specific design or configuration gap, not as a violation. The paper refill list, for instance, points precisely to a missing status in the refill workflow, and it also carries a risk: a list on paper can be lost, and no one else can see it.
A Dimension Still Unmeasured
Mapping the agreed measures onto the model exposed one gap. Service quality, the support users receive, has no measure in Table 1. The group tracks help desk tickets, but a ticket count rises when users trust the help desk and falls when they give up on it, so it cannot be read either way. For the next review the group will measure the median time to resolve tickets affecting patient care and ask clinicians, in the same survey that measures satisfaction, whether their last request for a build change was answered. The model also treats net benefit as something that feeds back into use and satisfaction, and the physician burden found here is the kind of net loss that, left alone, tends to lower satisfaction within a year even while use stays near total.
Satisfaction, Read Last
Satisfaction rose from 41% with the old system to 58%. The figure is reported after the harder evidence because satisfaction in the first year partly reflects relief that go-live is over and that the old system's known frustrations are gone. It is encouraging but not a measure of net benefit.
Verdict
Adoption is achieved. Net benefit is mixed: the structural problems that justified replacement are largely solved, and the documentation burden for physicians is worse than before. Declaring success now would end the project at the point where the system still needs the most attention.
Optimization Targets
Table 2
Optimization Targets With Owners
| Target | Owner | Measure | Next check |
|---|---|---|---|
| Route outside results to clinic pools with physician review rules | Medical group chief medical information officer | Physician inbox time back to 44 minutes | Three months |
| Add a callback status to the refill workflow and retire paper lists | Ambulatory nursing director with informatics analyst | Paper lists found at zero clinics on repeat walk-through | Three months |
| Personalization sessions and note template review for physicians | Medical group chief medical officer | Physician after-hours time back to 1.3 hours | Six months |
References
Arndt, B. G., Beasley, J. W., Watkinson, M. D., Temte, J. L., Tuan, W.-J., Sinsky, C. A., & Gilchrist, V. J. (2017). Tethered to the EHR: Primary care physician workload assessment using EHR event log data and time-motion observations. Annals of Family Medicine, 15(5), 419-426. https://doi.org/10.1370/afm.2121
DeLone, W. H., & McLean, E. R. (2003). The DeLone and McLean model of information systems success: A ten-year update. Journal of Management Information Systems, 19(4), 9-30. https://doi.org/10.1080/07421222.2003.11045748
Koppel, R., Wetterneck, T., Telles, J. L., & Karsh, B.-T. (2008). Workarounds to barcode medication administration systems: Their occurrences, causes, and threats to patient safety. Journal of the American Medical Informatics Association, 15(4), 408-423. https://doi.org/10.1197/jamia.M2616
The HIM-615 Topic 7 assignment instructions
HIM-615 Topic 7 asks students to evaluate a system after implementation. Many papers report adoption rates or user satisfaction as proof of success. The assignment rewards reviews that use measures and baselines agreed before go-live, map them to a recognized success model, break audit log results down by role and look for work done outside the system. Students should treat workarounds as evidence of design gaps, read satisfaction with caution, separate adoption from net benefit in the verdict and close with optimization targets that each have an owner, a measure and a date.
How this HIM 615 Topic 7 example is built
The finished review examines a composite physician group some months after its new EHR went live, using measures fixed before cutover. DeLone and McLean's information systems success model organizes them into system quality, information quality, service quality, use, user satisfaction and net benefit, so that heavy use is never mistaken for success on its own. Audit-log measures show time in the record per visit, after-hours documentation and inbox time, each set against the baseline taken before selection. Function use is broken out by role. A workaround inventory, gathered by walking the clinics, finds nurses keeping paper lists for refill callbacks. The review concludes that use is high and net benefit mixed, and it assigns three optimization targets with owners and measures.
HIM 615 Topic 7 rubric: what Excellent looks like
GCU's rubric for the adoption review rewards separating use from benefit. Excellent reviews show that required use is near total and then test whether the system helped, measure by measure. Credit goes to role-level audit log results that reveal where burden grew and to a workaround inventory gathered by walking the clinics. The rubric values noting a dimension the measures do not yet cover. The highest level delivers a mixed verdict honestly and assigns optimization targets with owners and dates. Reviews that equate adoption with success, or that pick their measures after go-live, usually lose marks with graders.
Common HIM 615 Topic 7 mistakes, and how to avoid them
Reviews that equate adoption with success lose the most, since clinicians must use a new record whether it helps them or not. A review that picks its measures after go-live can find success in almost anything, and graders tend to check whether baselines existed. Audit-log figures averaged across all users hide the roles whose documentation burden grew, often the ones with least time to absorb it. Some drafts treat workarounds as violations to be stamped out, discarding the most specific evidence of where the build fails. Satisfaction surveys presented as the main finding measure a mood shaped by the relief of surviving go-live. A review ending in a declaration of success, without optimization targets and owners, closes the project at the point where most systems still need the most attention.
Get an HIM-615 Topic 7 example written to your instructions
Send the HIM-615 Topic 7 instructions, the rubric from your classroom and any baselines, usage data or scenario the assignment supplies. We write a custom example to those criteria, with measures fixed in advance, a success model applied, audit-log evidence read by role, workarounds treated as findings and optimization targets assigned, in 24 to 48 hours. The first one costs nothing.
More HIM 615 papers and MS in Health Informatics samples
- HIM 615 Topic 1: Baseline Needs Assessment
- HIM 615 Topic 2: Vendor Demonstration Script
- HIM 615 Topic 3: Total Cost of Ownership Model
- HIM 615 Topic 4: Interoperability Claim Test
- HIM 615 Topic 5: Vendor Contract Obligations Review
- HIM 615 Topic 6: Go-live Strategy Decision Paper
- HIM 615 Topic 8: Runner-up Selection Defense
- HIM 650 Topic 7: Quality Control Placement Audit
- HIM 515 Topic 7: Sociotechnical Root Cause Analysis
HIM 615 Topic 7 questions, answered
What is the DeLone and McLean success model?
A widely used model of information system success that groups outcomes into system quality, information quality, service quality, use or intention to use, user satisfaction and net benefits. Its value for a post-implementation review is that it treats use as one dimension among several. Where use is mandatory, as with a clinical record, high use says little about whether the system is helping.
What can EHR audit logs show and not show?
Audit logs record actions and timestamps, so they can estimate time spent in the record, after-hours activity and inbox work by user and role. They cannot show why someone spent the time, whether the work was clinically useful or what happened off-screen. The review uses them for patterns against baseline and pairs them with observation and workaround inventories to explain what the numbers mean.
When should a post-implementation review happen?
Your instructions or the organization's plan may set the timing. Many organizations review at more than one point, an early check once the immediate go-live period has passed and a fuller review later. The example reviews once, some months in, and schedules the next check as part of its targets, since adoption and optimization keep moving well after the project team disbands.
Where can I find a free HIM 615 Topic 7 sample paper?
This page contains the whole review: agreed measures, results against baseline, what audit logs show, the workaround inventory, an unmeasured dimension, satisfaction, the verdict and optimization targets. Send your go-live data for a free worked review.
Did the new EHR succeed in HIM 615 Topic 7?
Partly. Use is near total and the structural problems were solved, but physicians spend more time in the record after hours, so net benefit is mixed and optimization continues.