HI580 Unit 10 Post-Implementation Evaluation Example

Reviewed by Chester Goodwin, MBA Information Systems Design and Implementation Purdue University Global Free custom sample in 24 to 48h

This HI580 Unit 10 post-implementation evaluation returns to baselines recorded before a composite hospital's labor unit system went live and measures them again at 30, 90 and 180 days. As the closing assignment of Purdue Global HI 580 in the MS in Health Informatics, it judges whether the implementation worked. The sample restates seven measures and methods, then shows re-entry falling from 40 minutes to 3, bedside entry rising to 91 percent and tracing retrieval dropping from three days to twenty minutes. It separates adoption from 99.7 percent uptime, reports bedside sign-in time worsening from 9 to 27 seconds with a fix, and states the limits of its evidence.

CourseHI580 Information Systems Design and Implementation
UnitUnit 10
Paper typePost-implementation evaluation
LengthAbout 1,100 words, 6 pages double-spaced
FormatAPA 7 student paper
SchoolPurdue University Global
ProgramMS in Health Informatics
UpdatedOctober 2026

Free sample paper for HI580 Unit 10

1

Baselines First, Then the Results: A Unit 10 Post-Implementation Evaluation at 30, 90 and 180 Days on a Labor Unit

[Student Name]

Purdue University Global

HI580: Information Systems Design and Implementation

Unit 10 Post-Implementation Evaluation

[Instructor Name]

[Date]

Brackenridge Medical Center, its unit, staff and every measured value are composite; the sources cited are real.

What this part is doingRestating measures and baselines before any result shows that the measures were chosen in advance, not selected afterward to flatter the system.
2

Measures Fixed Before Go-Live

Six measures were chosen during planning, each tied to a requirement or a workaround from the current-state map:

1. Minutes of re-entry per twelve-hour shift, tied to the bedside worksheet.

2. Delay between a tracing segment and its charted interpretation, tied to REQ-11.

3. Share of interpretations entered from the patient's room, tied to REQ-08.

4. Time for risk management to retrieve an archived tracing, tied to REQ-28.

5. Newborn record creation delay after birth, tied to REQ-19.

6. A ten-item staff usability survey, the same instrument at every round.

A seventh, bedside sign-in time, was added during planning after the interface review raised it as a risk.

Methods

The same procedures were used at baseline and at every follow-up. Re-entry minutes came from direct observation of four nurses across day and night shifts, using the same observer and timing sheet. Entry delay and bedside share came from audit-log extracts comparing each interpretation's signed time with its tracing segment time and the workstation location. Retrieval time was measured by asking the risk manager to retrieve five randomly chosen tracings from the prior year. Newborn delay came from comparing the newborn record's creation time with the shared clock's birth time. The survey was sent to all fifty-four labor nurses at each round.

Results

Each measure is given at baseline and at 30, 90 and 180 days.

1. Re-entry minutes per shift: 40 at baseline; 12 at 30 days; 4 at 90 days; 3 at 180 days.

2. Median delay from tracing to charted interpretation: 52 minutes; 18; 9; 7.

3. Share of interpretations entered from the room: 0 percent; 61 percent; 84 percent; 91 percent.

4. Time to retrieve an archived tracing: 3 days; 40 minutes; 25 minutes; 20 minutes.

5. Median newborn record delay: 14 minutes; 6; 3; 2.

6. Usability survey mean, on a 1 to 5 scale: 2.4; 2.9; 3.6; 3.8.

7. Median bedside sign-in time: 9 seconds at the old central station; 31 seconds; 28 seconds; 27 seconds.

Six of seven measures improved, and the one that worsened is the one nurses mention first when asked about the new system.

Use Versus Uptime

The system was available 99.7 percent of the time over 180 days, with one planned upgrade and one twenty-minute interface outage, during which queued interpretations posted correctly. Uptime answers whether the system runs. It does not answer whether nurses use it as designed. The share of interpretations entered from the room, rising from 61 percent at 30 days to 91 percent at 180, is the better measure of adoption, because it shows nurses abandoning the old habit of charting later. Implementation research distinguishes adoption, the extent to which staff take up a system in practice, from its technical availability, and treats the first as the harder and more telling outcome (Cresswell & Sheikh, 2013).

The Measure That Worsened

Bedside sign-in time rose from about nine seconds to nearly thirty, because room workstations require a full sign-in with a password, while the old central station stayed signed in for the charge nurse. Nurses sign in about twenty times a shift, which adds roughly six minutes, offsetting part of the re-entry saving. The evaluation does not bury this. It recommends badge tap sign-in for room workstations, already approved by information security, and projects that sign-in time would fall to about five seconds.

Interpreting the 30-Day Results

The 30-day figures show a unit still learning. Re-entry had not disappeared, because some nurses kept writing on paper out of habit, and the usability score was barely above baseline. By 90 days most measures had reached a plateau. Evaluating only at 30 days would have underestimated the system's benefit; evaluating only at 180 days would have hidden the difficult first month that staff remember. Reporting all three time points lets leaders see both.

Sociotechnical Lessons

The results reflect changes in several parts of the system together, not the software alone. Room workstations, a facilities change, made bedside charting possible. The shared clock, an infrastructure change owned by biomedical engineering, made entry delay measurable at all. Newborn registration moved to a different role. A sociotechnical view predicts that outcomes depend on how these parts fit (Sittig & Singh, 2010), and the evaluation suggests the fit improved most between 30 and 90 days as workflow, people and technology settled together.

What Staff Said

The survey's open comments matched the numbers. At 30 days, the most frequent comments concerned sign-in time and a category list that required scrolling on the smaller room screens; the list was reordered at week five. By 90 days, comments shifted toward handoff, with several nurses writing that marked segments made the night report shorter. At 180 days, the most common comment was a request to extend the room workstations to the triage bays, which still use the central station. One nurse wrote that she no longer carries a pen for the worksheet, which is perhaps the plainest summary of the change.

What this part is doingPairing survey comments with the measured results shows that the numbers reflect what staff actually experienced.
3

Costs and Benefits in Brief

The project's largest measurable benefit is nurse time: about 37 fewer minutes of re-entry per shift, partly offset by about six more minutes of sign-in. Across the unit's staffing, that returns roughly 70 nursing hours a month to patient care. The retrieval improvement has a different kind of value. Risk management's last request under the old system took three days and an outside vendor fee; the new archive produces a tracing in minutes.

Recommendations

1. Install badge tap sign-in for room workstations within the next quarter and remeasure sign-in time.

2. Continue the quarterly audit of bedside entry share, with a target of 95 percent.

3. Repeat the usability survey at one year.

4. Share the retrieval improvement with risk management and legal, since retrieval fell from days to minutes.

Limits

Observation covered four nurses per round, so re-entry minutes are estimates. Survey response rates fell from 78 percent at 30 days to 55 percent at 180, and later respondents may be the most satisfied. The evaluation cannot attribute improvements to the system alone, since staffing and census also changed over six months. Health IT evaluations commonly share these limits, and stating them openly is part of reporting results credibly (Kaplan & Harris-Salamone, 2009).

What this part is doingStating the falling survey response rate, and what it might mean, shows the grader that the evaluation weighed its own evidence honestly.
4

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

Kaplan, B., & Harris-Salamone, K. D. (2009). Health IT success and failure: Recommendations from literature and an AMIA workshop. Journal of the American Medical Informatics Association, 16(3), 291-299. https://doi.org/10.1197/jamia.M2997

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

Reading the HI 580 Unit 10 instructions

The final unit commonly asks for an evaluation of a health information system after go-live, using measures defined before implementation. Expect restated measures with baselines, methods, results at several time points, interpretation, recommendations and limitations. Eight pages built around one results table is typical. Show that measures were chosen in advance by stating baselines first. Use the same methods at baseline and follow-up. Report every measure, including any that worsened, and explain it. Distinguish adoption, whether staff use the system as designed, from technical availability. Interpret early and late results together. Recommend specific next steps and be honest about weaknesses such as falling survey response.

How the HI 580 Unit 10 example is put together

The evaluation restates seven measures tied to requirements and workarounds. A methods section describes observation, audit-log extracts, retrieval tests and an unchanged survey. Results give baseline and three follow-up values for each measure, and the highlighted sentence notes that the one worsening measure is the one nurses mention first. A section separates use from uptime, citing implementation research on adoption. The sign-in result is explained with a badge-tap fix. Sections interpret the 30-day results, apply a sociotechnical lens, report staff comments and summarize costs and benefits. Four recommendations and a limits section on sample size, response rates and attribution close the evaluation. Each section ties back to a requirement or workaround named in earlier units.

Reading the HI580 Unit 10 grading rubric

Post-implementation evaluations are generally scored on the quality of measures and baselines, rigor of methods, honest reporting of results, interpretation and recommendations. Honest reporting and interpretation often carry the most points: graders reward evaluations that report negative results and distinguish adoption from uptime. Measures and baselines earn credit when set before go-live and tied to requirements. Rigor is judged on consistent methods across rounds. Recommendations score when specific and tied to findings. Limitations must be stated plainly. One results table that a reader can scan in a minute is worth real credit. Evaluations that report only successes or rely on uptime as proof of success tend to lose points. Reading the first and last rounds side by side, rather than quoting only the last, tends to earn interpretation credit.

HI580 Unit 10 help from the desk

Evaluations in this unit are often returned because measures were chosen after go-live to show success. Another weakness is changing methods between baseline and follow-up, which makes comparisons meaningless. Some students omit a measure that worsened. Uptime is frequently presented as if it proved adoption. Results at a single time point miss the learning curve. Limitations sections can be generic rather than specific to the data, and recommendations sometimes repeat the findings instead of saying who should do what next. If your evaluation concerns a different system, perhaps a portal or a clinical decision support rule, bring your baseline measures and we will structure the follow-up results and interpretation around them.

Get an HI580 Unit 10 example written to your instructions

Your evaluation should measure the system and setting your course has followed, so send the Unit 10 prompt, the rubric and any baseline figures or scenario data available. A custom evaluation will compare them honestly across time points, worsened results included. The first sample costs nothing and arrives in 24-48h. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.

More HI580 papers and MS in Health Informatics samples

HI580 Unit 10 questions, answered

What if my scenario provides no baseline data?

State that plainly and design the evaluation around what a baseline would have measured, then use bracketed or scenario-supplied figures labeled as such. The example brackets every value because it is composite. Graders mainly assess whether measures were chosen before results and whether methods stayed constant, both of which can be shown without real data.

How is adoption different from implementation success?

A system can be implemented on schedule and still go unused as designed. Adoption measures ask whether staff actually work in the new way, such as the share of interpretations entered at the bedside rather than retyped later. The example keeps those measures separate from uptime and completion milestones, which only show the system exists and runs.

Should the evaluation report negative results?

Yes, and it strengthens the paper. The example gives rising bedside login time the same attention as any improvement and traces it to a configuration choice. An evaluation reporting only gains reads as advocacy rather than assessment, and reviewers in this field tend to notice when a new system appears to have had no costs at all.

Why measure at 30, 90 and 180 days instead of once?

Early results show the learning curve and late results show where performance settles. Reporting only one point would either understate the benefit or hide the hard first month.

Where can I find a free HI580 Unit 10 sample paper?

The complete Unit 10 evaluation is posted on this page, comparing seven baseline measures at 30, 90 and 180 days and reporting the one that worsened.