| Course | HI300 Information Systems for Health Care |
|---|---|
| Unit | Unit 2 |
| Paper type | Requirements list |
| Length | About 850 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | BS in Health Information Management |
| Updated | October 2026 |
Free sample paper for HI300 Unit 2
Twelve Requirements, Each With the Moment That Produced It: A Unit 2 Requirements List Derived From Two Shifts of Observation on a Labor and Delivery Unit
[Student Name]
Purdue University Global
HI300: Information Systems for Health Care
Unit 2 Requirements List
[Instructor Name]
[Date]
The unit, the shifts and the observations are composite; the sources cited are real.
Method
An analyst spent one day shift and one night shift on the composite unit, which has eight labor rooms, two operating rooms and about 1,900 births a year. She recorded what nurses, physicians, midwives and the unit clerk did with information: what they wrote, where, how often and what they had to look up. Each requirement below is written as a statement that a test could pass or fail, because a requirement that cannot be tested cannot be used to score a product later (Cresswell et al., 2013). Must means the unit cannot go live without it; should means the unit would accept a workaround for a defined period.
Functional Requirements
1. Must: the nurse can enter an interpretation of the fetal tracing in three or fewer actions from the tracing view. Observation: on the night shift, one nurse recorded eleven interpretations in four hours, each on both the strip and the flowsheet.
2. Must: every entry carries a time from one shared system clock. Observation: the monitor clock and the wall clock differed by four minutes, and the nurse corrected times by hand.
3. Must: a documented tracing category that calls for action notifies the charge nurse and the responsible provider within one minute. Observation: a nurse left a laboring patient's room to find the charge nurse in person.
4. Must: the newborn record is created at birth and linked to the mother's record, carrying the delivery time, type of delivery, Apgar scores and the mother's blood type. Observation: the unit clerk typed the same delivery details into three places.
5. Should: a summary view shows every laboring patient's status, last cervical exam and last tracing category on one screen at the nurses' station. Observation: the charge nurse kept a paper grid on a clipboard and updated it every hour.
6. Should: medication administration in labor, including oxytocin rate changes, is documented at the bedside and shown beside the tracing. Observation: rate changes were written on a separate infusion sheet.
Requirement 2 looks technical and trivial. It came from watching a nurse correct four minutes on every entry, and it may matter more in a review of a bad outcome than any other line on this list.
Technical Requirements
7. Must: the tracing and all annotations remain viewable at the bedside for at least four hours of network loss. Observation: during a twenty-minute network outage on the day shift, nobody could view the previous hour's tracing from the nurses' station.
8. Must: the system receives admission, transfer and discharge messages from the hospital's registration system so a patient moved to the operating room is followed without new registration. Observation: a patient taken for a cesarean section appeared twice on the census board.
9. Should: user sign-on works with the badge readers already installed on the unit's workstations. Observation: nurses signed on to shared workstations an average of fourteen times in a shift.
The technical items are fewer than the functional ones, and that is deliberate. The hospital's information services team will add its own list on security, hosting and support. What the unit can contribute is the evidence of where technology already fails its staff, such as the census board that showed one patient twice and the twenty minutes when the last hour of tracing could not be seen.
Reporting Requirements
10. Must: the system produces the perinatal measures the hospital already reports, including cesarean rates for first-time mothers and early elective deliveries, without manual abstraction. Observation: an HIM analyst spent two days a month abstracting these from paper.
11. Should: a nurse manager can run a report of tracing interpretations by time to response for any shift. Observation: the manager had no way to see how long notifications took.
12. Should: the complete record, including tracings, can be produced as one legal record on request. Observation: release of information staff gathered strips from a separate archive for every request.
What the Observation Changed
Before the shifts, the project team's draft list had thirty items, most copied from a vendor's feature sheet, the pattern that reviews of failed projects warn against (Kaplan & Harris-Salamone, 2009). Nine of the twelve requirements above were not on it, including the shared clock, the bedside view during outages and the badge sign-on. Studies of health IT in complex settings find that the most important needs often come from how people actually work around the tools they have (Sittig & Singh, 2010). Two shifts are not enough to see everything, and the list names that limit: no observation covered a weekend, a shoulder dystocia or a mass casualty day. The next step is to show the list to the nurses who were observed and ask what is missing.
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
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
HI300 Unit 2 instructions, in plain terms
The second unit typically asks you to observe or imagine one department and write the requirements a new system must meet. You are expected to describe your method briefly, then list requirements in a consistent, testable form. Most prompts want each requirement categorized, often as functional, technical and reporting, and prioritized as mandatory or desirable. Strong submissions link each requirement to an observation, a regulation or a stated goal, so the reader can see where it came from. Some instructors provide a template table; others accept a numbered list with short explanations. Ten to fifteen requirements is common. Plan on citing a published source about requirements gathering or implementation. A short reflection on what the observation revealed, or could not reveal, is often requested at the end.
How the HI 300 Unit 2 example is put together
The sample begins with a method paragraph naming who observed, which shifts and what was recorded, plus the definitions of must and should. Six functional requirements follow, each with a measurable target and the observation behind it, and a highlighted line explains why the shared clock matters more than it appears. A margin note points out that each requirement names a number a vendor can meet or miss. The technical section adds three requirements and a paragraph on why the unit's technical list is short. Three reporting requirements cover quality measures, response times and the legal record. The closing section compares the list with the team's earlier thirty-item draft, cites research on how real work reveals needs, and lists the situations two shifts did not cover.
HI300 Unit 2 rubric: what earns full points
Requirements lists are usually graded on quality, coverage and traceability. The largest share rewards requirements that are specific and testable; vague items such as user friendly lose points quickly. Coverage counts next, meaning a balance of functional, technical and reporting needs rather than a list of screens. Traceability earns credit when each requirement points to an observation, a rule or a goal. Prioritization is often its own rubric line, since a list where every item is mandatory gives a selection team nothing to weigh. Instructors also reward a short, honest account of method and its limits. APA citations and clean formatting make up the remaining points. Lists copied from a vendor's feature sheet are usually easy for graders to recognize and score poorly.
HI300 Unit 2 help from the desk
The most frequent weakness is requirements that cannot be tested, such as fast or easy to use with no number attached. Another is mixing solutions into requirements by naming a product feature instead of stating the need. Some students skip the technical and reporting categories entirely, while others mark every item mandatory. Lists without any link to observation or policy read as guesses, even when the items are reasonable. Leaving out downtime and identity matching is common and costly in a clinical setting. We can write a requirements list for the department in your assignment, traced to observations or to the scenario your instructor provided. Send the prompt, the department, any template and notes from your observation if you made one, and we will keep every item testable.
Get an HI300 Unit 2 example written to your instructions
Send the department or scenario your Unit 2 assignment names, plus any workflow notes, the instructions and the rubric. The requirements list comes back numbered, grouped and traced to each step, with acceptance tests filled in. First samples cost nothing, and delivery runs 24-48h. Where a template fixes the columns, the list follows that template exactly. 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 HI300 papers and BS in Health Information Management samples
- HI300 Unit 1: Discussion Post
- HI300 Unit 3: Systems Evaluation
- HI300 Unit 4: Interface Analysis
- HI300 Unit 5: Implementation Checklist
- HI300 Unit 6: User Access Matrix
- HI300 Unit 7: Audit Trail Review
- HI300 Unit 8: Downtime Procedure
- HI300 Unit 9: Seminar Reflection
- HI300 Unit 10: System Recommendation Report
- HI255 Unit 2: Operative Report Analysis
- HI253 Unit 2: Index and Tabular Exercise
- HI230 Unit 2: Census Computation Worksheet
- HI135 Unit 2: Authorization Review
HI300 Unit 2 questions, answered
Where can I find a free HI300 Unit 2 sample paper?
This page has the complete Unit 2 requirements list: twelve testable requirements for a labor and delivery system, each traced to an observed moment on two shifts.
What makes a system requirement testable?
It names a measurable result, such as three actions to save an entry or notification within one minute, so a demonstration can show whether a product meets it.
What is the difference between must and should requirements?
A must requirement is one the unit cannot go live without. A should requirement is wanted but can be met by a workaround for a defined period.
Do requirements need sources in HI300?
Each requirement should point to an observation, a regulation or a goal. Most instructors also expect one or two scholarly sources on requirements or implementation.
How many requirements should a Unit 2 list have?
Ten to fifteen is common. Fewer, well-tested requirements usually score better than a long list copied from vendor materials.