| Course | HI595 Master's Capstone in Health Informatics |
|---|---|
| Unit | Unit 7 |
| Paper type | Draft deliverable |
| Length | About 880 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 HI595 Unit 7
Version 0.3, Written for Four Readers: A Unit 7 Capstone Draft Deliverable Specifying an Implant Record and MRI Screening Worklist
[Student Name]
Purdue University Global
HI595: Master's Capstone in Health Informatics
Unit 7 Draft Deliverable
[Instructor Name]
[Date]
Carrowby Health, its systems, fields and every rule are composite; the standards and sources cited are real.
Version Table
Version 0.1: first draft from interviews. Version 0.2: added exception rules after the tabletop test found outside implants unhandled. Version 0.3: separated the statuses Verified and Cleared after review; added the card template. Status: draft, not approved for configuration.
Part A: The Implant Entry (for operating room nurses and screening nurses)
One structured entry per implanted device, in the patient's implant list. Fields:
1. Device type, from a short pick list: pacemaker or defibrillator, neurostimulator, cochlear implant, programmable shunt, aneurysm clip, stent, joint replacement, other.
2. Device identifier, scanned from the package barcode at implantation where available.
3. Manufacturer and model, filled automatically from the identifier through the federal device database, or typed if no identifier exists.
4. MRI labeling: MR Safe, MR Conditional, MR Unsafe or Unknown, using the standard labeling terms (ASTM International, 2023).
5. Link to the manufacturer's MRI conditions, for conditional devices.
6. Implant date and site.
7. Source: Carrowby operating room log, outside record, patient card, or patient report.
8. Status: Recorded, Verified or Removed.
An operating room nurse creates the entry by scanning the device package, which the supply log already does; the entry posts to the record within one day. Entries for outside implants are created by screening nurses.
Part B: The Screening Worklist (for the imaging informatics analyst)
The worklist shows every outpatient MRI scheduled in the next fourteen days for a patient who has an implant entry or who answered yes to the implant question at scheduling. Nine columns, each with its source field:
1. Scan date, from the scheduling system.
2. Patient name and record number.
3. Device type, from Part A.
4. MRI labeling, from Part A.
5. Entry status, from Part A.
6. Screening status: Open, Verified, Cleared, Hold, or Closed unable to verify.
7. Days until scan, calculated.
8. Assigned screening nurse.
9. Note.
Status rules, each with an entry and an exit condition:
1. Open: entered automatically when the exam is scheduled; exits when a nurse begins verification.
2. Verified: the device identity and labeling are confirmed from a reliable source; exits to Cleared or Hold.
3. Cleared: a supervising radiologist has approved scanning under the stated conditions; final.
4. Hold: verification is incomplete within three business days of the scan; the exam is flagged to scheduling and the radiologist.
5. Closed, unable to verify: identity cannot be confirmed; the exam proceeds only under the safety committee's unknown-device protocol.
The due rule: verification must reach Verified at least three business days before the scan date. Worked examples: a scan on Friday the 20th is due Tuesday the 17th; a scan on Monday the 23rd is due Wednesday the 18th; a scan scheduled two days out is due immediately and opens as Hold.
Verified means the device is known; Cleared means a radiologist has said it may be scanned, and the specification keeps the two apart because a reader once took one for the other.
Part C: Exceptions (for screening nurses)
1. Outside implant with a card: record from the card, source Patient card, and request manufacturer confirmation if the model is unreadable.
2. Outside implant without documentation: request records from the implanting hospital; if none arrive before the due date, set Hold.
3. Patient reports a device removed: record as Removed only with a removal record; otherwise keep the entry and verify.
4. Retained fragments or leads: record as Other with the labeling Unknown and route to the radiologist.
Part D: Patient Letter and Card (for patients)
The letter, kept to plain words and short sentences that the patient advisor tested, explains that the hospital keeps a record of implants so MRI staff can plan safely, lists the patient's recorded devices, and asks the patient to call if anything is missing. The wallet card lists each device, manufacturer, model and MRI labeling, generated from Part A so the card and the record always agree. Because patients frequently misremember device models, the card prints exactly what the record holds, an approach consistent with radiology guidance on confirming devices from documentation (Harwood et al., 2024).
How the Parts Fit Together
The four parts depend on each other in one direction. Part A creates the data, Part B reads it, Part C handles what Part A cannot fill, and Part D reflects it back to the patient. A change to any field in Part A must therefore be checked against the worklist columns and the card template before it is approved. Version control on the cover records which parts each revision touched, so that the analyst configuring the worklist knows whether a revision affects her work.
Open Questions for Review
Whether the fourteen-day window is long enough for outside records, and whether surgeons should see the implant list in their own workflow, are open for the safety committee. Federal identifier rules make Part A's automatic fill possible for most devices placed since the rules took effect (21 C.F.R. § 830.300, 2024).
References
ASTM International. (2023). Standard practice for marking medical devices and other items for safety in the magnetic resonance environment (ASTM F2503-23). ASTM International.
21 C.F.R. § 830.300 (2024). https://www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-830/subpart-E/section-830.300
Harwood, M., Fahrenholtz, S. J., Wellnitz, C. V., Kawashima, A., & Panda, A. (2024). MRI in adult patients with active and inactive implanted MR-conditional, MR-nonconditional, and other devices. RadioGraphics, 44(3), e230102. https://doi.org/10.1148/rg.230102
HI595 Unit 7 instructions, in plain terms
The seventh unit usually asks for a draft of the capstone deliverable, complete in structure even where details await review. Expect a version history, every major part present, clear marking of draft status and open questions. Length depends on the artifact; specifications often run ten pages or more. Organize the document by reader so each part can be used without the others. Define every field and status precisely, with entry and exit conditions for statuses. Show rules as both statements and worked examples where arithmetic is involved. Include exceptions, because real cases rarely follow the main path. If the design reaches patients, include patient-facing materials. List open questions for reviewers rather than hiding them.
How the HI 595 Unit 7 example is put together
A version table records three drafts and current status. Part A defines eight fields for the implant entry and explains how operating room scans create it. Part B lists nine worklist columns with sources and five statuses with entry and exit conditions, and gives three worked examples of the due rule; the highlighted sentence explains the distinction between Verified and Cleared. Part C sets four exception rules, from outside cards to retained fragments. Part D describes a plain-language letter and a card printed from the entry. A section explains how the parts depend on each other, and open questions for the safety committee close the draft.
Reading the HI595 Unit 7 grading rubric
Draft deliverables are generally graded on completeness of structure, precision, usability for intended readers, handling of exceptions and honest marking of gaps. Precision and usability often weigh most: graders check that fields, statuses and rules could be implemented without guesswork. Completeness earns credit when every part exists, even if some values await approval. Exception handling shows the design was tested against real cases. A version history and open questions show professional practice. Patient materials, where relevant, add credit. A draft that is polished in one section and missing others, or that defines statuses by name only, tends to score lower. Worked examples for date rules are frequently singled out for credit, because they prevent the commonest configuration error.
Common HI595 Unit 7 mistakes, and how to avoid them
The most frequent weakness in draft deliverables is vague definitions that only the author understands. Another is a missing exceptions section. Some students submit an outline instead of a draft, which reviewers cannot judge. Due-date rules often lack worked examples, inviting misconfiguration. Version history is frequently absent, so reviewers cannot see what changed. Patient-facing materials may be left out even when the design depends on patients acting. Send the artifact type you committed to and your requirements, and we will draft it reader by reader with statuses and rules defined tightly enough to configure. Leaving draft status off the pages invites someone to configure from an unapproved version.
Get an HI595 Unit 7 example written to your instructions
Your artifact might be a specification, a dashboard design, a workflow or a set of templates. Tell us which, who will use it, and what your earlier units settled, with the Unit 7 instructions and rubric alongside. A first draft sample, written for that reader, costs nothing and lands inside 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 HI595 papers and MS in Health Informatics samples
- HI595 Unit 1: Discussion Board Post
- HI595 Unit 2: Project Proposal
- HI595 Unit 3: Scope Statement
- HI595 Unit 4: Literature Review
- HI595 Unit 5: Stakeholder and Approval Plan
- HI595 Unit 6: Methodology Outline
- HI595 Unit 8: Seminar Reflection
- HI595 Unit 9: Evaluation Plan
- HI595 Unit 10: Capstone Project Report
- HI501 Unit 7: Workflow Redesign Proposal
- HI580 Unit 7: Test Plan
- HI510 Unit 7: Patient Portal Evaluation
- HI575 Unit 7: Incident Response Plan
HI595 Unit 7 questions, answered
Can the deliverable be a specification if nothing gets built?
Often, yes. Many informatics capstones end at a specification, a configuration-ready design or an implementation plan, because building belongs to an IT department. The test is precision: could the team that owns the system configure from your document without calling you? If your program requires a working prototype, the rubric will usually say so plainly.
Where can I find a free HI595 Unit 7 sample paper?
The full Unit 7 draft is on this page, a four-part specification for implant entries, a screening worklist, exceptions and patient materials.
How finished should a capstone draft deliverable be?
Complete in structure, with every part present and gaps marked, so reviewers can judge the whole artifact and know exactly what still needs a decision.
Why define worklist statuses with entry and exit conditions?
Because a status name alone can be read differently by different users; conditions state exactly when a case enters and leaves each status.
Should a specification include worked examples?
Yes, where a rule involves arithmetic or dates. Examples let the person configuring the system check their reading of the rule against known answers.