| Course | HI595 Master's Capstone in Health Informatics |
|---|---|
| Unit | Unit 3 |
| Paper type | Scope statement |
| Length | About 850 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 3
Read for Its Exclusions: A Unit 3 Capstone Scope Statement With Five Items In and Nine Out, Each With a Reason
[Student Name]
Purdue University Global
HI595: Master's Capstone in Health Informatics
Unit 3 Scope Statement
[Instructor Name]
[Date]
Carrowby Health, its departments and every assumption are composite; the sources cited are real.
Document Control
Title: Scope Statement, Implant Record and MRI Screening Specification Project. Version 1.0. Date: week 3. Owner: capstone author. Approver: vice president of imaging services. Changes after approval require a change request signed by the approver.
In Scope
1. Outpatient MRI exams scheduled at Carrowby's two hospitals.
2. Adult patients, eighteen and older.
3. Implanted medical devices with MRI labeling, active (such as pacemakers, neurostimulators and cochlear implants) and passive (such as aneurysm clips, joint replacements and stents).
4. The four deliverables named in the proposal: the implant entry specification, the screening worklist specification, exception rules, and the patient letter and card.
5. The baseline audit and the evaluation plan.
Out of Scope
1. Inpatient and emergency MRI. Reason: screening for these patients runs through a separate, staffed process with immediate radiologist review, and its timing problems differ.
2. Pediatric patients. Reason: pediatric MRI at Carrowby is performed at a partner children's hospital with its own screening system.
3. CT, nuclear medicine and other modalities. Reason: implant concerns differ by modality, and including them would double the requirements.
4. Contrast allergy documentation. Reason: a separate allergy project owned by pharmacy is already under way.
5. Dental implants, tattoos and body piercings. Reason: these are handled by technologist screening on the day, with established practice, and they rarely require device-specific labeling.
6. Device programming before and after scanning, such as pacemaker reprogramming. Reason: these are clinical procedures governed by cardiology and the MRI safety committee, not information design.
7. Building or purchasing a device labeling database. Reason: the specification will reference the federal identification database and manufacturer labeling rather than maintain its own.
8. Changes to the MRI safety policy or zone access rules. Reason: policy belongs to the MRI safety committee; the project supplies information to it.
9. Configuration of the record and go-live. Reason: configuration requires informatics resources and approvals beyond the term; the project delivers a specification ready for that decision.
Every exclusion names a reason tied to feasibility, guidance or ownership, so that a sponsor reading the list can disagree with a reason rather than with a hunch.
Assumptions
1. The operating room supply log captures implant identifiers for most devices placed at Carrowby since 2019. If coverage is lower, exception rules will carry more weight.
2. Data access approval for the baseline audit will be granted by week 5.
3. The imaging informatics manager will review the draft for feasibility in week 11.
4. The MRI safety officer will serve as clinical reviewer throughout.
Constraints
1. The term ends in week 15, which fixes the end date.
2. No budget is available; all work uses the author's time and existing reports.
3. The project may observe screening but may not change any screening practice during the term.
Boundary Cases Decided Now
1. Implants placed at outside hospitals are in scope; they are the hardest cases and the exception rules exist for them.
2. Patients who have had a device removed are in scope, because a record that still lists a removed device delays scans as much as a missing one.
3. Retained fragments, such as surgical wires left after device removal, are in scope only when documented in a structured field; otherwise they are referred to technologist screening.
Why Scope Matters Here
MRI safety guidance assigns screening decisions to trained staff and a responsible radiologist under local policy (Harwood et al., 2024). A capstone that drifted into policy or device programming would cross into decisions it has no authority to make. Improvement reporting standards also ask projects to define the context and boundaries of an intervention clearly so that results can be interpreted (Ogrinc et al., 2016). Federal identification rules supply the device identifier that makes structured recording possible (21 C.F.R. § 830.300, 2024), which is why the project can stay within information design.
Dependencies Outside the Project
Two dependencies sit outside the project's control. The operating room's supply log must remain available as a data source; if its vendor changes during the term, the specification will reference the identifier field generically rather than by system. The MRI safety committee meets monthly, so its review of the draft must be requested by week 9 to fall within the term. Neither dependency changes the scope, but both are written down here, so that any slip can be pinned on the dependency that caused it. The approver has agreed that a delay caused by either one extends the matching milestone rather than counting as a missed date.
Change Control
Any change to the in-scope list requires a written request naming the effect on schedule and deliverables. Scope may narrow without approval if a risk is realized, for example reducing the audit sample, but may not widen.
References
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
Ogrinc, G., Davies, L., Goodman, D., Batalden, P., Davidoff, F., & Stevens, D. (2016). SQUIRE 2.0 (Standards for QUality Improvement Reporting Excellence): Revised publication guidelines from a detailed consensus process. BMJ Quality & Safety, 25(12), 986-992. https://doi.org/10.1136/bmjqs-2015-004411
The Purdue Global HI595 Unit 3 instructions
The third unit commonly asks for a scope statement that defines exactly what the capstone will and will not include. Expect in-scope and out-of-scope tables, assumptions, constraints and a change control rule, set out as a controlled document with version and approver. Three pages is typical. Write in-scope items precisely, naming populations, settings and deliverables. Give every exclusion a reason a sponsor could accept, tied to feasibility, existing programs, guidance or ownership. State assumptions that could change the plan, such as data coverage. Decide boundary cases now rather than mid-project. Note dependencies outside your control. Close with how scope may change, allowing narrowing more easily than widening.
How the HI 595 Unit 3 example is put together
A document control block names the version, owner and approver. Five in-scope items follow, then nine out-of-scope items, each with its reason, from inpatient MRI's separate process to configuration beyond the term, and the highlighted sentence explains why reasons make exclusions arguable. Four assumptions and three constraints come next. A section decides three boundary cases in advance: outside implants, removed devices and retained fragments. A section on why scope matters links the boundary to radiology guidance on who owns screening decisions, improvement reporting standards and federal identifier rules. Dependencies outside the project and a change control rule that permits narrowing but not widening close the statement. The result is a page a sponsor can sign without wondering what was left unsaid.
Where the points sit in the HI595 Unit 3 rubric
Scope statements are usually scored on precision of the in-scope definition, quality of exclusions and their reasons, realism of assumptions and constraints, and change control. The exclusions and their reasons often decide the grade, because they show the student understands where the project's authority ends. Precision earns credit when populations, settings and deliverables are named exactly. Assumptions should be specific enough to fail. Boundary cases decided in advance are often rewarded. Change control is judged on whether it would actually prevent scope creep. Document format with version and approver is expected. A scope statement that repeats the proposal's boundary paragraph without reasons for exclusions tends to score poorly.
HI595 Unit 3 help: mistakes that cost points
The most frequent weakness in this unit is an out-of-scope list with no reasons. Another is in-scope wording so broad that almost anything could fit. Some students list assumptions that cannot fail, such as the project will be completed on time. Boundary cases are often left for later, where they cause arguments. Change control is sometimes missing or allows scope to grow without approval. Dependencies outside the student's control go unmentioned. If your project sits in another service, such as laboratory or pharmacy, list the edges you are unsure about and we will settle each one in the statement with a stated reason. Reasons that only say not feasible, without saying why, are almost as weak as no reasons.
Get an HI595 Unit 3 example written to your instructions
A scope statement depends on where your project stops, so share your proposal, anything you already suspect belongs outside the line, and the Unit 3 rubric with its instructions. Your first sample is free, drafted within 24-48h, with exclusions and reasons drafted to fit your setting and the sponsor you answer to. 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 4: Literature Review
- HI595 Unit 5: Stakeholder and Approval Plan
- HI595 Unit 6: Methodology Outline
- HI595 Unit 7: Draft Deliverable
- HI595 Unit 8: Seminar Reflection
- HI595 Unit 9: Evaluation Plan
- HI595 Unit 10: Capstone Project Report
- HI501 Unit 3: Structured Data Memo
- HI580 Unit 3: Current Workflow Map
- HI510 Unit 3: Application Comparison
- HI575 Unit 3: Threat and Vulnerability Analysis
HI595 Unit 3 questions, answered
How many exclusions are enough?
Enough that anyone reading could foresee what the project will refuse. Six to ten rows is common for a capstone, and the example carries nine. The strongest exclusions name something a sponsor or colleague might reasonably assume was included, because those are the requests that would otherwise arrive mid-term and stall the work.
Is a scope statement the same as the proposal's boundary section?
It grows out of that section but does more. The proposal draws the line in a paragraph; this document turns it into tables, adds assumptions and constraints, and sets a rule for changing scope. Many instructors expect the two to agree exactly, so the statement often opens by citing the approved proposal.
Can I change scope after this unit?
Usually, if the change is written down and approved by whoever sponsors the project. Instructors tend to accept a narrower scope later more readily than a wider one. Keep a short log of any change and its reason, since the final report is often expected to explain why the finished project differs from the proposal.
Where can I find a free HI595 Unit 3 sample paper?
The full Unit 3 scope statement is posted here, with five items in scope, nine exclusions with reasons and three boundary cases decided in advance.
Why should every exclusion in a scope statement have a reason?
A reason lets the sponsor disagree with a specific judgment instead of a hunch, and it shows that each boundary reflects feasibility, ownership or guidance rather than convenience.