HI580 Unit 1 Discussion Board Post Example

Course	HI580 Information Systems Design and Implementation
Unit	Unit 1
Paper type	Discussion board post
Length	About 530 words, 2 pages double-spaced
Format	APA 7 discussion post
School	Purdue University Global
Program	MS in Health Informatics
Updated	October 2026

Free sample paper for HI580 Unit 1

The Specification Was Wrong, Not the Software: A Unit 1 Discussion Post on Why Labor Nurses Went Back to Paper

HI580 · Unit 1 Discussion Board Post

Posted by [Student Name]

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

What this part is doingPutting the claim in the first sentence lets every later paragraph argue a point instead of telling a story.

Initial Post

The documentation system Brackenridge Medical Center installed on its eighteen-room labor unit four years ago worked exactly as specified. The specification was wrong. Within three months the nurses had returned to paper worksheets for tracing interpretations, and I think the reasons sit in decisions people made, not in the software.

Design came first. The system assumed nurses would chart fetal heart rate interpretations at the central station, where the workstations were. A nurse caring for a laboring patient does not leave the room every thirty minutes to type. Nurses kept a paper sheet in the room and copied it into the system afterward, so the electronic record became a delayed copy of the paper. The question no one asked: where is the nurse when the information is created?

Build came second. The build team was made up of analysts and one nurse educator who had not worked a labor shift in six years. Flowsheet rows followed the vendor's default order, not the order of a labor assessment. The question no one asked: who on the team actually does this work today?

Launch came third. Go-live happened on a Monday with two days of classroom training two months earlier and no at-the-elbow support on nights. Night nurses, who chart the most monitoring intervals, met the system alone. The question no one asked: who will be standing next to the nurse at 3 a.m. in week one?

Each cause began with a question that would have cost almost nothing to ask during planning and a great deal to fix afterward.

I will concede that the software had real faults. Sign-in was slow and the flowsheet scrolled badly. But the same nurses tolerated a slow medication system without abandoning it, which suggests the faults were not decisive. Reviews of health IT projects find that failure usually comes from how work, people and organization fit the system, rather than from the technology itself (Kaplan & Harris-Salamone, 2009), and implementation research points to organizational choices such as involvement and support as the deciding factors in adoption (Cresswell & Sheikh, 2013).

So my position: the retreat to paper was a planning failure that looked like a software failure. Which of these three questions do you think your organization asks least often?

Reply to Grace

Grace, you blamed the vendor for not putting workstations in the rooms. I wonder whether that was the vendor's decision or the hospital's. The contract specified central station charting, and the hospital approved that design. Would a different vendor have changed anything if the same specification went out?

Reply to Malik

Malik, you suggested that more classroom hours would have solved the launch problem. I agree training was thin, but the bigger gap seems to be who was there on the first night shifts. Would you trade some classroom time for super users scheduled across all shifts in the first two weeks?

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

What the HI580 Unit 1 assignment asks for

The first unit typically asks you to analyze a health IT implementation that struggled or failed and identify its causes. Prompts usually want a clear claim, causes supported by evidence, reference to the implementation literature and something to ask the group. An opening post near 450 words, followed by two shorter replies, is what most sections expect. State your claim in the first sentence so every paragraph argues rather than narrates. Order causes in a way that teaches something, such as the sequence of project phases, and end each with the question that decision should have asked. Acknowledge real technical faults rather than dismissing them. Replies work best when they test a classmate's diagnosis against the facts of the case, for example by asking who actually made the decision being blamed.

Inside the HI580 Unit 1 example

The opening paragraph states the claim and the retreat to paper. Three paragraphs follow, one for each cause: design assumed charting at the central station while nurses stay in the room; the build team lacked a nurse who had worked a recent labor shift; and launch came with thin training and no night support. Each paragraph ends with the question no one asked. The highlighted sentence observes how cheap those questions were compared with the fix. A concession paragraph admits slow sign-in and scrolling, then compares the nurses' tolerance of a slow medication system, citing reviews of health IT success and organizational adoption research. One reply asks whether the vendor or the hospital chose central charting; the other weighs classroom hours against night support.

HI580 Unit 1 rubric: what earns full points

Discussion posts in HI580 are commonly marked on the strength of the analysis in the initial post, use of implementation literature, quality of replies and writing. The initial post usually earns most of the credit when its causes are specific to the case, supported by evidence and connected to decisions people made. A source earns its place by explaining one of the causes. Replies score by pushing a classmate's reasoning with a question or counterpoint grounded in the case. Many sections also give points for posting early in the week and replying on separate days. Writing quality and APA form take the last slice of points, and posts that blame the vendor or the users in general terms, without tracing a cause to a specific decision, tend to lose most analysis points.

Common HI580 Unit 1 mistakes, and how to avoid them

The most common shortfall in this post is blaming the software without examining the specification or the plan. A second is listing many causes without evidence for any of them. Some drafts spend most of their words retelling the case. Others pretend the software had no faults at all, which a careful reader will not believe. Replies that agree politely and add nothing earn few points, while a reply that asks who made a decision usually earns full credit. Watch for claims that one fix would have solved everything. If your case is a different implementation, perhaps a barcode medication system or a patient portal, send the case summary and the prompt, and we will draft a Unit 1 post that traces its failure to decisions in the same way.

Get an HI580 Unit 1 example written to your instructions

Unit 1 prompts vary in the failure they ask about: a vendor rollout, a local build, a case from the reading. Share yours with the instructions and rubric, and a custom post will trace that failure to the decisions behind it. A first sample is free and reaches you within 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 1 questions, answered

Can the post use a real, publicly reported system failure?

Yes, where the prompt allows it and the account is published, cited and described accurately. A composite case serves the example because it needs details, such as where nurses stood while charting, that public reports rarely include. Whichever you choose, keep claims about named organizations to what the sources support, and label any composite as one.

Is it acceptable to argue that technology did contribute?

Certainly, and a one-sided post often reads as weaker. The example concedes a slow login and awkward scrolling, then explains why those faults do not account for the retreat to paper. What graders reward is the weighing: which causes were decisive and what evidence separates them from the ones that were merely irritating.

How many causes should the initial post discuss?

Few enough to support each with evidence. The example stops at three, one each from design, build and launch, because that structure shows the failure accumulating across the project. A post listing eight causes in a sentence apiece usually reads as a textbook summary rather than an argument about one case.

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

This page carries the whole Unit 1 post with two replies, tracing a labor unit's retreat to paper to three planning decisions.

Why do health IT implementations fail when the software works?

Often because the specification, the build team or the launch plan did not match how the work is actually done, which no software fix can correct afterward.