| Course | HI501 Health Informatics |
|---|---|
| Unit | Unit 2 |
| Paper type | Capture workflow analysis |
| Length | About 1,000 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MS in Health Informatics |
| Updated | October 2026 |
Free sample paper for HI501 Unit 2
Eleven Stops to Feed the Record During One Transfusion: A Unit 2 Capture Workflow Analysis Sorting Each Step Into Care, Capture or Both
[Student Name]
Purdue University Global
HI501: Health Informatics
Unit 2 Capture Workflow Analysis
[Instructor Name]
[Date]
The unit, the nurses and the timings are composite; the sources cited are real.
Method
I observed one afternoon transfusion of a single unit of red cells on a composite oncology unit, from the moment the blood arrived from the bank until the final set of vital signs about two hours later. Details are composite and times are rounded to the minute. Each action the primary nurse took was recorded with its elapsed minute, who acted, where the nurse stood and what the record received. Each action was then sorted into one of three categories: care, meaning work done for the patient; capture, meaning work done only to put information into the record; and both, meaning a single action that served the patient and the record at once, such as scanning a wristband that also checks identity.
Timeline of Observed Actions
1. Minute 0: blood arrives; nurse checks the order on the workstation screen. Capture. Workstation.
2. Minute 2: nurse and second nurse verify the unit against the patient at the bedside, reading aloud. Care.
3. Minute 4: nurse scans the wristband and the unit label with the handheld scanner. Both. Bedside.
4. Minute 5: nurse records pretransfusion vital signs on the bedside monitor and validates them into the flowsheet. Both. Bedside.
5. Minute 7: second nurse walks to the workstation to co-sign the verification on a separate screen. Capture. Workstation.
6. Minute 9: nurse starts the infusion at the prescribed rate. Care.
7. Minute 10: nurse documents the start time and rate, opening a collapsed flowsheet section to find the transfusion rows. Capture. Bedside.
8. Minute 24: nurse takes and validates 15-minute vital signs, asking about chills or back pain. Both. Bedside.
9. Minute 25: nurse documents the reaction assessment in a separate transfusion row. Capture. Bedside.
10. Minute 26: nurse increases the rate. Care.
11. Minute 27: nurse documents the rate change. Capture. Bedside.
12. Minute 70: nurse takes and validates hourly vital signs. Both. Bedside.
13. Minute 128: infusion ends; nurse flushes the line. Care.
14. Minute 129: nurse documents end time and volume infused. Capture. Bedside.
15. Minute 130: nurse takes and validates final vital signs. Both. Bedside.
16. Minute 133: nurse returns to the workstation to complete the transfusion summary, which will not save from the bedside device. Capture. Workstation.
17. Minute 136: nurse scans the empty bag's label into the record before discarding it. Capture. Workstation.
18. Minute 138: nurse returns to the bedside to check the patient once more. Care.
Tally
Of the 18 observed actions, 5 were care alone, 5 served both care and the record, and 8 were capture alone. Adding the eight capture-alone actions to the three combined steps, at minutes 24, 70 and 130, where validating vital signs meant extra screen work, the record caused eleven stops. Four of those stops, the order check, the co-signature, the summary and the bag scan, took place at a workstation away from the bedside. Capture alone took about 19 minutes of the roughly 130-minute window, or about 15 percent. National time and motion work has found that documentation takes a large share of medical-surgical nursing time (Hendrich et al., 2008), and this transfusion fits that pattern on a small scale. The densest capture comes in the first fifteen minutes, the period when a transfusion reaction is most likely and the nurse's attention is most needed at the bedside.
Three Interruptions Worth Redesigning
The co-signature at the workstation. The second nurse verified the unit at the bedside, then walked away to sign on a separate screen. Two minutes later, the record shows the verification, but if the second nurse had been called away on the walk, the record would show it as missing even though it happened. The co-signature captures a fact the bedside scan could have recorded at the moment it occurred. The collapsed flowsheet section. The transfusion rows sit inside a section that opens collapsed, so the nurse searched for them at minute 10 and again at minute 25. Each search took under a minute, but it took place while the nurse was watching for early signs of a reaction. Watching nurses on hospital wards, Westbrook and colleagues linked each interruption during drug rounds to a higher chance of an administration error, and of a more serious one, (Westbrook et al., 2010), and a transfusion is a drug administration in every sense that matters. The summary that will not save from the bedside. At the end, the nurse left the patient to finish a summary at the workstation because the bedside device timed out on that form. The data reached the record six minutes after the infusion ended, and the patient was alone for that time.
Cost in Minutes and Late Data
1. Nurse minutes spent on capture alone: about 19 per transfusion.
2. Minutes away from the bedside for capture: about 9, across four trips.
3. Data entered late: the co-signature by 3 minutes, the summary by 6 minutes.
4. On a unit giving about 6 transfusions a day, capture alone takes about 114 nurse minutes daily, nearly two hours.
What the Analysis Suggests
The analysis does not argue for less documentation. Transfusion records exist for good reasons, including traceability of the unit and early detection of reactions. It argues for moving capture to the moment and place where the event happens: a co-signature scanned at the bedside, transfusion rows that open expanded during an active transfusion, and a summary form that saves from the bedside device. Each change would cut a trip, not a data element. Health information systems create work of their own when they separate recording from doing (Ash et al., 2004), and the first fifteen minutes of a transfusion are the wrong place for that work.
References
Ash, J. S., Berg, M., & Coiera, E. (2004). Some unintended consequences of information technology in health care: The nature of patient care information system-related errors. Journal of the American Medical Informatics Association, 11(2), 104-112. https://doi.org/10.1197/jamia.M1471
Hendrich, A., Chow, M. P., Skierczynski, B. A., & Lu, Z. (2008). A 36-hospital time and motion study: How do medical-surgical nurses spend their time? The Permanente Journal, 12(3), 25-34. https://doi.org/10.7812/TPP/08-021
Westbrook, J. I., Woods, A., Rob, M. I., Dunsmuir, W. T. M., & Day, R. O. (2010). Association of interruptions with an increased risk and severity of medication administration errors. Archives of Internal Medicine, 170(8), 683-690. https://doi.org/10.1001/archinternmed.2010.65
What the HI501 Unit 2 assignment asks for
Unit 2 typically asks you to observe or reconstruct one clinical task and analyze how information is captured during it. Expect to define the task's start and end, record each step with its time, location and actor, and classify steps by whether they serve the patient, the record or both. Many prompts ask you to identify the interruptions that pull clinicians away from care or delay data, and to estimate their cost. A timeline, table or numbered list usually carries the observation, followed by analysis. You are not asked to eliminate documentation but to see where capture could happen closer to the moment of care. Cite a time and motion study or work on interruptions and clinical system effects. Keep the setting and people composite, and say plainly what one observation can and cannot show.
Inside the HI501 Unit 2 example
A method paragraph bounds the observation to one transfusion and defines the three categories with examples. The timeline follows as eighteen numbered actions with minute, category and location. A tally counts care, capture and combined steps, totals capture minutes and links the share to national time and motion findings. The highlighted sentence points out that capture is heaviest when the reaction risk is highest. Three interruptions each get a paragraph: the walk to co-sign, the search through a collapsed flowsheet section during the watch for early reactions, and the trip to a workstation to finish a summary. A cost list converts the findings into nurse minutes per transfusion and per day and minutes of late data. A closing section proposes moving capture to the bedside without removing any data element.
Reading the HI501 Unit 2 grading rubric
Workflow analyses in this course are generally scored on observation quality, analysis, interpretation and writing. Observation points reward a defined boundary, consistent recording and a classification someone else could apply. Analysis earns credit for an accurate tally and for costs expressed in time or delay rather than adjectives. Interpretation is where the larger share sits: the grader wants to know why the pattern matters, for example its overlap with periods of clinical risk. Students lose many points by recommending that documentation simply be reduced, which ignores why the data are needed. Expect credit for evidence linking interruptions to error risk and for honest limits. Recommendations should target where and when capture happens. A clear timeline or table, consistent units and APA citations complete the rubric.
Common HI501 Unit 2 mistakes, and how to avoid them
The usual weakness in Unit 2 is a timeline without a boundary, so the analysis wanders across the shift and no total can be trusted. Another is classifying every documentation step as waste, when many steps serve the patient and the record together. Some students count interruptions without explaining what each one costs or risks. Others propose a new system when the problem is where an existing screen is used. Analyses that skip the method paragraph leave the grader unsure whether the times were observed or guessed. A single observation presented as a rate also draws deductions. If you have a task you have watched at work, describe its steps and rough times along with the prompt, and the analysis can be shaped into a timeline with each capture step costed.
Get an HI501 Unit 2 example written to your instructions
Share the clinical task assigned in Unit 2, a transfusion, an admission, a wound check or anything else, along with the rubric and any observation rules your section sets. The sample times that task and labels each step. It returns inside 24-48h, and a first custom sample carries no charge. 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 HI501 papers and MS in Health Informatics samples
- HI501 Unit 1: Discussion Post
- HI501 Unit 3: Structured Data Trade-off Memo
- HI501 Unit 4: Decision Support Rule Design
- HI501 Unit 5: Usability Walkthrough
- HI501 Unit 6: Adoption Evaluation
- HI501 Unit 7: Workflow Redesign Proposal
- HI501 Unit 8: Patient Engagement Analysis
- HI501 Unit 9: Seminar Reflection
- HI501 Unit 10: Informatics Project Brief
HI501 Unit 2 questions, answered
Where can I find a free HI501 Unit 2 sample paper?
You can read the whole Unit 2 analysis here, timing one transfusion and sorting each action into care, capture or both.
What does capture mean in a clinical workflow?
Work done to put information into the record, as opposed to care for the patient; some steps, like scanning a wristband, do both.
How much transfusion time went to documentation in the sample?
About 19 of 130 minutes went to capture alone, with four trips to a workstation.
Why does the timing of capture matter?
In the sample, capture is heaviest in the first fifteen minutes, when a transfusion reaction is most likely and attention belongs at the bedside.
Does the analysis recommend less documentation?
No. It recommends recording each fact at the bedside when it happens, cutting trips rather than data.