HIM 615 Topic 6 go-live strategy decision paper example

Health Care Information Systems and Technology Grand Canyon University Free custom sample in 24 to 48h

This HIM 615 Topic 6 sample paper is a go-live strategy decision paper recommending that a three-hospital system switch on its new EHR at every site at once. It belongs to GCU HIM 615, Health Care Information Systems and Technology, the course listed as HIM-615 in the Grand Canyon University MS in Health Informatics. The deciding fact is patient movement: about 2,100 transfers a year and 400 clinicians working at more than one site. The phased option is argued at its strongest, then rejected because it would split records for up to eleven months. The paper prices the concentrated risk, sets proficiency checks, super user ratios, downtime drills and readiness criteria, and says when it would reverse itself.

CourseHIM 615 Health Care Information Systems and Technology
TopicTopic 6
Paper typeGo-live strategy decision paper
LengthAbout 960 words, 3 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramMS in Health Informatics
UpdatedSeptember 2026

Free sample paper for HIM 615 Topic 6

1

One Night, Three Hospitals: Why Paloma Basin Should Go Live on Its New EHR Everywhere at Once, and What That Choice Costs

[Author Name]

College of Nursing and Health Care Professions, Grand Canyon University

HIM-615: Health Care Information Systems and Technology

Topic 6 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.

What this page is doingThe title states the recommendation and promises its price, since a single go-live concentrates risk that a phased plan would spread. Paloma Basin and its figures are composites; the studies cited are real.
2

One Night, Three Hospitals: Why Paloma Basin Should Go Live on Its New EHR Everywhere at Once, and What That Choice Costs

The Choice and the Fact That Dominates It

Paloma Basin Health must decide how to switch on its new enterprise electronic health record across three hospitals and twelve clinics: all at once on a single night, or in phases, one site at a time over about a year. The choice is often made by reputation, with a single go-live called risky and phasing called safe. This paper argues that the right answer depends on how patients and staff move in a particular system, and that at Paloma Basin one fact dominates. Patients move between the sites constantly. Last year there were about 2,100 transfers between the three hospitals, and 31% of patients admitted to the two smaller hospitals had a clinic or emergency visit at another Paloma Basin site within 30 days. About 400 nurses and physicians work shifts at more than one site.

The Phased Option at Its Strongest

The case for phasing is serious. The first site teaches the project what the build got wrong, and the lessons are fixed before the second site goes live. Problems affect one hospital's patients rather than all of them. Support staff, trainers and vendor experts can be concentrated at one site at a time, with at-the-elbow help for every clinician on the first shifts. If the first site struggles, the others can wait. Many organizations have gone live this way successfully, and the approach makes most sense when sites are independent.

The costs at Paloma Basin are specific. A three-phase plan would leave some patients' records split across two systems for up to eleven months, joined only by temporary interfaces between the old and new records. Transferred patients would arrive with orders and medication administration records that must be re-entered by hand. Staff who work at more than one site would switch between two systems within a week, using different workflows for the same task. Each of these is a known source of error, and together they would last for most of a year.

The Single Go-Live Option and Its Concentrated Risk

A single go-live ends the split record on the first night. Every transfer after that moves within one record, and every clinician uses one system. The risk it creates is concentrated rather than removed. Every clinician learns at the same time. Support is stretched across three campuses on the same shifts, and no site can lend its experts to another, because every site is busy. Problems in the build appear everywhere at once. The paper recommends this option because its risk is shorter and can be planned for, while the phased option's risk would last for months and depends on temporary interfaces that are hard to test fully.

What this page is doingThe paper states the chosen option's risk as plainly as its benefits, which is what makes the recommendation credible.
3

Workflows Tested by the People Who Will Use Them

Future-state workflows were designed with clinicians and then tested in integrated testing, in which clinicians from each department performed their daily work on test patients, from registration through discharge and billing. Workflow design done only by analysts moves the disruption to the first shift after go-live, when it is most expensive to fix. Cresswell et al. (2013) described the importance of engaging end users throughout large health information technology implementations and of treating implementation as a change in work as well as technology.

Training and Proficiency

Training is role based, and no one receives access to the new system until they pass a proficiency check that asks them to complete typical tasks for their role on a test patient. Classroom hours alone do not show whether a clinician can place an order set or document a medication given late. Longhurst et al. (2019), studying organizations in a national collaborative, found that users who rated their training highly reported greater satisfaction with their record. Clinic schedules will be reduced to 75% for four weeks after go-live, and hospital units will have one trained super user for every eight staff on each shift for the first two weeks.

Command Center and Downtime

A command center will operate around the clock for three weeks, with clinical, technical and vendor staff triaging issues by severity and reporting open safety issues to the chief medical officer daily. Downtime procedures will be rehearsed at every site before cutover, because a new system's first weeks are when staff most need a fallback they know. Larsen et al. (2018), analyzing patient safety event reports related to downtime, found that nearly half described downtime procedures that were not followed or not in place, and that laboratory orders and results were the most common area affected. Every unit will run a one-hour downtime drill, including laboratory results by paper, in the month before go-live.

Readiness Criteria for Cutover

Table 1

Conditions That Must Be Met Before Cutover

CriterionThresholdOwner
Integrated testingAll critical scenarios passed; no open critical defectsChief information officer
Proficiency95% of clinicians with access passed the checkChief nursing officer and chief medical officer
Super user coverageOne per eight staff on every shift for two weeks, at all sitesProject director
Downtime rehearsalEvery unit completed its drillSite nursing directors
InterfacesAll 64 tested end to endIntegration manager

When the Recommendation Would Reverse

The recommendation depends on staffing support at all three sites at once. If, eight weeks before go-live, Paloma Basin cannot staff one super user per eight staff on every shift at every site, or if proficiency is below 85% with no path to 95%, the concentrated risk of a single go-live would exceed the cost of the split record, and the paper would recommend delaying and then phasing, starting with the regional hospital and its clinics together. A go-live that cannot be supported everywhere should not happen everywhere.

References

Cresswell, K. M., Bates, D. W., & Sheikh, A. (2013). Ten key considerations for the successful implementation and adoption of large-scale health information technology. Journal of the American Medical Informatics Association, 20(e1), e9-e13. https://doi.org/10.1136/amiajnl-2013-001684

Larsen, E., Fong, A., Wernz, C., & Ratwani, R. M. (2018). Implications of electronic health record downtime: An analysis of patient safety event reports. Journal of the American Medical Informatics Association, 25(2), 187-191. https://doi.org/10.1093/jamia/ocx057

Longhurst, C. A., Davis, T., Maneker, A., Eschenroeder, H. C., Jr., Dunscombe, R., Reynolds, G., Clay, B., Moran, T., Graham, D. B., Dean, S. M., & Adler-Milstein, J. (2019). Local investment in training drives electronic health record user satisfaction. Applied Clinical Informatics, 10(2), 331-335. https://doi.org/10.1055/s-0039-1688753

Reading the GCU HIM 615 Topic 6 instructions

The Topic 6 instructions in HIM-615 ask students to choose and defend an implementation approach. Weak submissions choose by reputation, calling one approach safe and the other risky. The assignment rewards papers that identify the facts about their organization that decide the question, argue the rejected option at its strongest and state the risks of the chosen option plainly. Students should describe how workflows were tested by the clinicians who will use them, require proficiency before system access, plan downtime procedures and support, set readiness criteria with owners and name the condition that would reverse the recommendation.

How the HIM-615 Topic 6 example is put together

The finished paper chooses how a composite three-hospital system should switch on its new EHR and defends the choice against the one it rejects. Patients move between the three hospitals and their shared clinics every day, and the paper shows that a phased rollout would leave many of them with records split across two systems for months, joined only by temporary interfaces. It therefore recommends a single go-live across all sites, then prices the risk that decision concentrates: every clinician learning at once, support stretched across three campuses and no site able to lend help to another. Mitigations follow, including future-state workflows validated by clinicians in integrated testing, role-based training with a proficiency check before access, reduced clinic schedules, a command center and downtime procedures rehearsed before cutover.

Where the marks sit in the HIM 615 Topic 6 rubric

Faculty grading the go-live paper reward a choice driven by local facts. Excellent papers show how patient and staff movement between sites decides the approach. Credit goes to stating the phased option's real strengths and the single go-live's concentrated risk. The rubric values proficiency checks before access, super user ratios and downtime rehearsal grounded in evidence about downtime harm. The highest level sets measurable readiness criteria with owners and states when the recommendation would reverse. Papers that describe training only as classroom hours usually receive partial credit.

HIM 615 Topic 6 help before you submit

Papers that choose an approach by reputation, calling big bang risky or phased safe, lose marks at once, because the right choice depends on how patients and staff move in the particular system. A recommendation that never states the rejected option at its strongest looks like taste dressed up as analysis. Drafts often describe training as hours in a classroom and never require proficiency before access, which is where go-live problems are cheapest to catch. Workflow redesign done by analysts, and never tested by the clinicians who inherit it, moves the disruption to the first shift. Downtime planning is commonly left out, even though a new system's early weeks are when staff most need a rehearsed fallback. What the change costs clinicians, in reduced schedules and slower documentation, belongs in the paper as a cost, not an inconvenience.

Get an HIM-615 Topic 6 example written to your instructions

Send the HIM-615 Topic 6 instructions and your classroom rubric, with the organization, sites or implementation scenario the assignment describes. We write a custom example to those criteria, with both rollout options argued, the rejected one at full strength, workflows tested by users, readiness conditions and the clinician's cost included, returned in 24 to 48 hours. The first one is free.

More HIM 615 papers and MS in Health Informatics samples

HIM 615 Topic 6 questions, answered

Is big bang or phased implementation better?

Neither in general. A single go-live avoids long periods of split records and temporary interfaces, which matters most where patients move between sites. A phased rollout lets lessons from one site reach the next and concentrates support, which suits sites that operate largely independently. The paper decides for one composite system based on how its patients and staff actually move, and says what would change the answer.

Where does downtime planning fit in an implementation paper?

In the readiness conditions, before cutover. Staff need rehearsed procedures for working when the system is unavailable, including paper forms, read-only access to recent records and a process for entering data afterward. ONC's SAFER Guides include one on contingency planning that many organizations use as a checklist. The paper treats rehearsal, not the existence of a binder, as the condition.

How should the paper account for the clinician's cost?

As a real cost in time and strain, stated in the same terms as other costs. Reduced clinic schedules, training hours taken from practice and slower documentation in the first weeks all fall on clinicians. The paper names them, estimates them where the case allows, labels any estimates and shows how the plan limits them. Leaving them out makes the implementation look cheaper than it is.

Where can I find a free HIM 615 Topic 6 sample paper?

The complete paper appears on this page, with the choice and deciding fact, the phased option, the single go-live and its risk, workflows, training, command center and downtime, readiness criteria and the reversal condition. Describe your system for a free worked paper.

Why go live everywhere at once in HIM 615 Topic 6?

Patients and staff move between the three hospitals daily, so phasing would split records across two systems for up to eleven months, joined only by temporary interfaces.