| Course | HIM 370 Health Care Information Systems |
|---|---|
| Topic | Topic 8 |
| Paper type | Installed system evaluation |
| Length | About 960 words, 3 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | BS in Health Information Management |
| Updated | September 2026 |
Free sample paper for HIM 370 Topic 8
Two Years After Go-Live: An Installed System Evaluation of Bajada's EHR Against Needs That Did Not Exist at Selection
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HIM-370: Health Care Information Systems
Topic 8 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.
Two Years After Go-Live: An Installed System Evaluation of Bajada's EHR Against Needs That Did Not Exist at Selection
The Question
Two years after Bajada Community Hospital's new EHR went live, the executive team asked whether it still fits the hospital. The question is not whether the selection was right; the requirements matrix answered that at the time. It is whether the installed system meets needs the hospital has now, three of which did not exist at selection: an outpatient surgery center opened last year in a separate building, a state stroke registry reporting obligation added after the hospital became a certified stroke center, and clinicians who now document across the main campus and a new satellite emergency department. This evaluation gathers evidence first and then judges the system against each need, using a recognized model of information system success to organize the judgment.
The Framework and the Evidence
DeLone and McLean (2003) offered a model in which success has several connected parts: technical soundness, the usefulness of the data, the help users get, actual use, user contentment and, finally, the benefits the organization gains. The model is useful here because it keeps the evaluation from collapsing into user satisfaction alone, which reflects how people feel about a system but not whether it produces the information the hospital needs.
Four kinds of evidence were gathered over eight weeks: eighteen months of help desk tickets, categorized by module and theme; an inventory of workarounds, collected by asking each department what it does outside the system to get its work done; a list of report requests the analytics team could not fill; and a survey of 214 clinicians and staff, with a 58% response rate. Each finding below cites the evidence behind it.
Need 1: The Outpatient Surgery Center
The surgery center uses the EHR's inpatient surgical module, configured for the main operating rooms. Help desk tickets from the center, 142 in a year, concern scheduling blocks that assume inpatient staffing, preference cards that cannot be separated by location and a discharge workflow that requires inpatient documents a same-day patient does not need. The workaround inventory found that center staff keep a paper checklist for same-day discharge because the electronic version cannot be completed until an inpatient field is filled. The vendor offers an ambulatory surgery module that Bajada did not license at selection, when no surgery center existed. On system quality and use, the installed configuration fails this need; the product can meet it with additional licensing and build.
Need 2: Stroke Registry Reporting
The stroke registry requires about 60 data elements per case, including when the patient was last seen without symptoms, door-to-needle time and reasons for not giving thrombolytics. The analytics team's list of unfilled requests shows that 23 of those elements are captured only in free-text notes, and the stroke coordinator abstracts them by hand, about 50 minutes per case for roughly 320 cases a year. This is an information quality failure: the data exist but not in usable form. The fix lies in configuration, adding discrete fields to the stroke documentation templates, and it does not require a new product.
Need 3: Documentation Across Two Campuses
Clinicians who work at both the main campus and the satellite emergency department reported in the survey that the system works identically at both, and help desk tickets show no location-specific problems except printer routing. The satellite department's workaround inventory was empty. On this need the system succeeds.
Service quality, the support the information technology department and the vendor provide, drew mixed survey results: 71% of respondents rated the help desk satisfactory, but tickets requiring vendor involvement took a median of 19 days to resolve.
What the Evaluation Could Not Show
The evidence has limits, and the judgment depends on stating them. Help desk tickets record problems people chose to report; a department that has given up reporting a problem, or never expected the system to solve it, leaves no tickets. That is why the workaround inventory mattered: it found the surgery center's paper checklist, which appeared in no ticket because staff had stopped asking. The survey measured satisfaction among those who answered, and the 42% who did not may be less satisfied or simply busier. None of the evidence measured net benefits directly, such as whether documentation time or medication errors changed after go-live, because the hospital did not collect those measures before the new system arrived.
The evaluation therefore judges fit, not return on investment. It can say that the system meets one need, can meet a second through configuration and a third through purchase. It cannot say whether the system has improved care, and it recommends that the hospital begin measuring two outcomes now, documentation time per encounter and time from stroke arrival to treatment decision, so that the next evaluation can.
The Judgment
The installed EHR does not need replacing. It meets the cross-campus need well, can meet the registry need through configuration and can meet the surgery center need through an added module. The evaluation recommends licensing the ambulatory surgery module, with a build completed within nine months; adding discrete stroke fields to templates within three months, with the stroke coordinator's abstraction time as the measure of success; and negotiating faster vendor response in the next contract year. Sittig and Singh (2010) emphasized that health information technology must be evaluated as part of a sociotechnical system that includes workflow and organizational change, and two of the three findings here arose not from the software but from the hospital changing around it. Kim et al. (2017) found that problems with health information technology can affect care delivery, which makes the surgery center's paper checklist, a workaround outside the record, the finding to fix first.
References
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
Kim, M. O., Coiera, E., & Magrabi, F. (2017). Problems with health information technology and their effects on care delivery and patient outcomes: A systematic review. Journal of the American Medical Informatics Association, 24(2), 246-250. https://doi.org/10.1093/jamia/ocw154
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
The HIM-370 Topic 8 assignment instructions
The final topic of HIM-370 asks students to evaluate an information system already in use. Many evaluations rely on user satisfaction or repeat the original selection criteria. The assignment rewards evaluations that set the system against the organization's current needs, including needs that arose after selection, gather several kinds of evidence first and organize the judgment with a recognized model of information system success. Students should cite the evidence behind each finding, distinguish problems solvable by configuration from those needing purchase, state the limits of the evidence and reach a clear recommendation.
Inside the HIM 370 Topic 8 example
The finished evaluation reads as a structured judgment with the evidence gathered first. It sets out the composite hospital's current needs in workflow terms: a new outpatient surgery center that did not exist at selection, a registry reporting obligation added since go-live, clinicians documenting across two campuses. Each need then meets the installed EHR, with evidence drawn from help desk tickets, workaround inventories, report requests that could not be filled and observed documentation time. Interfaces are counted and rated by stability. A cost of leaving section describes the work of a replacement in categories rather than invented figures: data migration, retraining, interface rebuilding and contract exit terms. The verdict is one of three options, keep, optimize or replace, and the evaluation states which evidence would reverse it.
Where the marks sit in the HIM 370 Topic 8 rubric
Faculty grading the installed system evaluation reward evidence gathered before judgment. Excellent evaluations draw on tickets, workaround inventories, unfilled reports and surveys, and tie each finding to one of them. Credit goes to using a success framework to separate system, information and service quality from satisfaction. The rubric values distinguishing configuration fixes from new modules and acknowledging what the evidence cannot measure, such as net benefits. The highest level recommends a specific course with timelines and measures, and explains why replacement is or is not justified. Evaluations resting on satisfaction scores alone rarely reach the top band.
HIM 370 Topic 8 help: mistakes that cost marks
Evaluations that judge the EHR on what it can do, rather than on what this organization needs it to do, lose marks throughout. A capability list compared with a newer product's capability list repeats the feature comparison the course has warned against since its first topic. Papers that rely on satisfaction surveys alone mistake a mood for a measure, while workaround inventories and unfilled report requests show where the system actually falls short. Leaving interfaces out of the evaluation ignores the connections a replacement would have to rebuild. Recommending replacement without counting the cost of leaving assumes the organization can walk away from years of stored data at no expense. A verdict with no reversing condition reads as a preference rather than a judgment the organization could revisit when circumstances shift.
Get an HIM-370 Topic 8 example written to your instructions
Send the HIM-370 Topic 8 instructions, the rubric from your classroom and the system or organization your assignment describes. We write a custom example to those criteria, with current needs defined first, evidence sources weighed, fit rated need by need, interfaces counted and the cost of leaving set out before the recommendation, in 24 to 48 hours. The first one is free.
More HIM 370 papers and BS in Health Information Management samples
- HIM 370 Topic 1: System Type Inventory
- HIM 370 Topic 2: Data Element Trace
- HIM 370 Topic 3: Interface Failure Analysis
- HIM 370 Topic 4: Duplicate Record Impact Analysis
- HIM 370 Topic 5: System Limits Dq Post
- HIM 370 Topic 6: Weighted Requirements Matrix
- HIM 370 Topic 7: Data Migration Plan
- HIM 355 Topic 8: Procedure Code Audit Rebuttal
- HIM 350 Topic 8: Diagnosis Coding Audit Defense
- HIM 310 Topic 8: Classification Choice Defense
- HIM 200 Topic 8: Plain Language Records Policy
HIM 370 Topic 8 questions, answered
What evidence shows how well a system fits?
Evidence tied to work. Help desk tickets show recurring failures, a workaround inventory shows where staff have built around the system, unfilled report requests show what the data cannot answer, and observed documentation time shows the cost to clinicians. Surveys add perspective but not proof. The evaluation uses several sources and states what each one cannot show, so the verdict does not rest on the loudest complaint.
Is replacement usually the answer?
Not usually, and an evaluation that reaches it should show why optimization would not close the gaps. Many shortfalls come from configuration choices made at go-live, which can be revisited within the current contract. Replacement carries the full cost of migration, retraining and interface rebuilding. The evaluation treats keeping, optimizing and replacing as three real options and argues for one against the other two.
How is this different from the selection topic?
Selection judges products against requirements before anyone has lived with them. This evaluation judges one installed system against needs that have changed since, using evidence from years of use. The questions overlap, but the evidence is far better here, because workarounds, failures and unfilled requests are on record. If your assignment asks for both perspectives, the evaluation can compare the original requirements with what actually happened.
Where can I find a free HIM 370 Topic 8 sample paper?
The whole evaluation is on this page, with the question, the framework and evidence, three needs judged, what the evaluation could not show and the judgment. Tell us your system and needs for a free worked evaluation.
Why doesn't the EHR need replacing in HIM 370 Topic 8?
It meets the cross-campus need, can meet the stroke registry need by adding discrete fields and can meet the surgery center need with a module the vendor already offers.