| Course | HI580 Information Systems Design and Implementation |
|---|---|
| Unit | Unit 2 |
| Paper type | Stakeholder requirements list |
| Length | About 840 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 HI580 Unit 2
Forty-One Lines, Eleven Roles, One Fit Criterion Each: A Unit 2 Stakeholder Requirements List for Labor Unit Documentation
[Student Name]
Purdue University Global
HI580: Information Systems Design and Implementation
Unit 2 Stakeholder Requirements List
[Instructor Name]
[Date]
Brackenridge Medical Center, its staff, interviews and every requirement are composite; the sources cited are real.
Stakeholder Register
Eleven roles, with how each was reached:
1. Labor nurse: interviews with four nurses across day and night shifts.
2. Charge nurse: interviews with two.
3. Obstetrician: interviews with two.
4. Certified nurse-midwife: interview with one.
5. Anesthesiologist: interview with one.
6. Neonatal nurse: interview with two.
7. Unit clerk: interview with one.
8. Risk manager: interview with one.
9. Health information management: interview with the release supervisor.
10. Biomedical engineering: survey only.
11. Interface analyst: survey only.
Two roles were reached by survey because scheduling interviews failed, and their requirements are marked for confirmation.
How Requirements Are Written
Each requirement states what the system must do, never how. Each has an identifier, the requirement in one sentence, the source role, a rationale, a fit criterion and a priority from 1, essential, to 3, desirable. A fit criterion is the measurable test of the requirement: if no one could check whether it was met, it is not yet a requirement (Robertson & Robertson, 2012). Requirements are grouped along the course of a labor so that a gap at any stage shows.
Admission and Triage
REQ-01, labor nurse: the patient's identity and prenatal record are available at the bedside within one minute of triage registration. Fit: in testing, 19 of 20 registrations display in under sixty seconds. Priority 1.
REQ-02, unit clerk: a triage patient sent home is closed out without creating an inpatient encounter. Fit: no inpatient encounter created in 10 of 10 test discharges from triage. Priority 1.
REQ-03, charge nurse: the unit board shows each room's patient, nurse and monitoring status. Fit: board updates within thirty seconds of a room change. Priority 2.
Surveillance and Documentation
REQ-08, labor nurse: interpretations can be charted from inside the patient's room. Fit: a nurse completes an interpretation entry at the bedside in under ninety seconds in a usability test. Priority 1.
REQ-09, obstetrician: tracings are classified using the three-tier categories in national use. Fit: entry choices match the categories published in the 2008 workshop report (Macones et al., 2008). Priority 1.
REQ-11, labor nurse: an interpretation records both the time charted and the time of the tracing segment it describes. Fit: both times display on every entry in testing. Priority 1.
REQ-12, risk manager: any charted interpretation can be linked to the exact tracing segment it describes. Fit: from an entry, the segment opens in two clicks. Priority 1.
REQ-14, anesthesiologist: epidural placement and dosing appear on the same timeline as the tracing. Fit: entries display on the tracing timeline within one minute. Priority 2.
Delivery and Newborn
REQ-19, neonatal nurse: a newborn record created at delivery is linked to the mother's record and carries the exact birth time. Fit: in 10 of 10 test deliveries, including twins, each newborn record shows the correct mother and birth time. Priority 1.
REQ-21, certified nurse-midwife: delivery documentation can be completed by a midwife without a physician co-signature. Fit: midwife sign-off finalizes the delivery note in testing. Priority 1.
Transfer and Archive
REQ-28, health information management: archived tracings are retrievable by patient and date for the full retention period. Fit: a release clerk retrieves a five-year-old tracing in under ten minutes. Priority 1.
REQ-30, risk manager: the archive preserves tracings in a form that cannot be altered. Fit: no edit function exists for archived tracing data in testing. Priority 1.
Availability and Downtime
REQ-36, biomedical engineering (to confirm): monitors continue to display and store tracing data locally if the network fails. Fit: four hours of local storage verified in testing. Priority 1.
REQ-38, labor nurse: a downtime procedure lets charting continue on paper and be entered later with original times. Fit: a downtime drill completes with all entries carrying original times. Priority 1.
REQ-41, interface analyst (to confirm): monitors, central display and the record share one synchronized clock. Fit: times agree within five seconds across all three. Priority 1.
REQ-41 came from the role with the least contact with patients, and it may decide whether every other timestamp in the record can be trusted.
The Remaining Lines
The full list in the appendix holds forty-one requirements: thirty-one at priority 1, seven at priority 2 and three at priority 3. Priority was set by the source role and reviewed by the charge nurse and the unit's medical director together.
Why This Matters for the Project
Health IT projects often fail when requirements come from analysts rather than from the people doing the work (Kaplan & Harris-Salamone, 2009). The earlier documentation system at Brackenridge was specified around a central station because no labor nurse was asked where charting happens. This list puts the bedside first, in REQ-08, and every later unit can trace its decisions back to these lines.
References
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
Macones, G. A., Hankins, G. D. V., Spong, C. Y., Hauth, J., & Moore, T. (2008). The 2008 National Institute of Child Health and Human Development workshop report on electronic fetal monitoring: Update on definitions, interpretation, and research guidelines. Obstetrics & Gynecology, 112(3), 661-666. https://doi.org/10.1097/AOG.0b013e3181841395
Robertson, S., & Robertson, J. (2012). Mastering the requirements process: Getting requirements right (3rd ed.). Addison-Wesley.
The Purdue Global HI580 Unit 2 instructions
Unit 2 usually asks you to identify stakeholders for a health information system and document their requirements before selecting a product. Expect a stakeholder register showing who was consulted and how, followed by a requirements table with identifiers, sources, rationale, testable criteria and priorities. Many sections suggest about forty requirements for a unit-level system. List stakeholders first so gaps are visible, and note any role reached only by survey. Write each requirement as what the system must do, leaving design for later units. Give every requirement a fit criterion, a number or observable condition someone could check. Group requirements in an order that follows the work, such as the stages of care, so missing stages stand out. Include availability and downtime requirements, which are easy to forget.
How this HI580 Unit 2 example is built
The register lists eleven roles with how each was reached, from four labor nurses interviewed across shifts to biomedical engineering by survey. A section explains the requirement format and defines a fit criterion, citing the Volere approach. Requirements follow in groups along the course of a labor: admission and triage, surveillance and documentation, delivery and newborn, transfer and archive, and availability and downtime. Selected lines show identifiers, sources, fit criteria and priorities, including bedside charting under ninety seconds, three-tier tracing categories from the 2008 workshop report and newborn linking tested on twins. The highlighted sentence notes the shared clock requirement's source and importance. A summary of all forty-one by priority and a section linking the list to the earlier failure close the paper.
HI580 Unit 2 rubric: what earns full points
Requirements lists are typically graded on stakeholder coverage, quality of requirements, testability, traceability and organization. Testability usually carries the most weight: graders reward fit criteria that state a number or condition and penalize vague words such as user-friendly or fast. Stakeholder coverage earns credit when every affected role appears, including support roles such as biomedical engineering and health information management, and when the method for each is stated. Traceability is judged on whether every requirement names its source. Organization earns points when grouping follows the workflow. Correct citations and a clean table complete the rubric. A list that mixes design decisions into requirements, such as naming a product feature, or that leaves priorities unexplained, tends to lose points in several rows at once.
HI580 Unit 2 help: mistakes that cost points
Graders most often mark down lists whose lines have no fit criterion at all. Another common issue is stakeholder coverage that stops at clinicians and skips the clerk, risk manager or interface analyst. Some students write requirements as solutions, naming a screen or vendor feature instead of the need. Downtime and archive requirements are often missing entirely. Priorities sometimes appear without any explanation of who set them. Requirements that cannot be traced to a source are hard to defend later. If your project concerns a different unit or system, such as an emergency department tracking board or an oncology order set, tell us which roles you could reach and we will build the register and requirements around them.
Get an HI580 Unit 2 example written to your instructions
A requirements list depends on who your scenario names. Send the Unit 2 prompt, its rubric and the assigned setting, and a custom list will trace each line to a role and attach a measurable condition to it. The first sample is free, returned in 24-48h and formatted as your course expects. 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: Discussion Board Post
- HI580 Unit 3: Current Workflow Map
- HI580 Unit 4: System Selection Matrix
- HI580 Unit 5: Proposed Workflow Design
- HI580 Unit 6: Interface Specification
- HI580 Unit 7: Test Plan
- HI580 Unit 8: Seminar Reflection
- HI580 Unit 9: Go-live Plan
- HI580 Unit 10: Post-implementation Evaluation
- HI575 Unit 2: Data Inventory
- HI501 Unit 2: Capture Workflow Analysis
- HI570 Unit 2: Case Brief
- HI510 Unit 2: Setting Requirements Brief
HI580 Unit 2 questions, answered
What is a fit criterion?
A measurable condition that shows whether a requirement has been met, such as a time limit, a count or an observable outcome. The term comes from requirements engineering practice, and the example attaches one to every line. Without it, a requirement like fast retrieval cannot pass or fail a test, and the later acceptance scripts have nothing to check against.
Can I include requirements from roles I could not interview?
Yes, if the paper says how they were gathered. The example reaches two roles by survey and marks those rows, so a reader knows their evidence is thinner. Published role descriptions or scenario materials can also stand in, labeled as such. What graders object to is a requirement attributed to a role with no indication of where it came from.
Should the list rank requirements?
Most rubrics expect some prioritization, and the method matters less than its discipline. The example uses three levels and explains what separates each, with patient safety and legal retention requirements held at the top. A list where nearly every line is top priority gives the selection unit no way to separate candidates that meet different subsets.
What is a fit criterion in a requirements list?
The measurable condition a demonstration or test must meet for the requirement to count as satisfied, such as a time limit or an error count.
Where can I find a free HI580 Unit 2 sample paper?
The full Unit 2 list is on this page, with an eleven-role register and requirements grouped along the course of a labor, each with a fit criterion.