| Course | HIM 490 Health Information Management Capstone |
|---|---|
| Topic | Topic 6 |
| Paper type | Owned implementation timeline |
| Length | About 980 words, 3 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | BS in Health Information Management |
| Updated | September 2026 |
Free sample paper for HIM 490 Topic 6
Every Task Has a Name Beside It: An Owned Implementation Timeline for Duplicate Record Prevention at Saltbush
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HIM-490: Health Information Management Capstone
Topic 6 Assignment
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Every Task Has a Name Beside It: An Owned Implementation Timeline for Duplicate Record Prevention at Saltbush
What the Timeline Must Deliver
Saltbush Regional Medical Center creates duplicate patient records at a rate of 1.48% of new registrations: 612 confirmed duplicates among 41,300 registrations over the twelve-month baseline. Each duplicate splits a patient's history across two records, so a clinician may see one allergy list while the other holds the allergy that matters. Just et al. (2016) found discrepancies in key identifying fields such as name, date of birth and address in a large share of master patient index records, and the Saltbush baseline showed the same pattern: most duplicates were created at scheduled outpatient registration, when a registrar searched with a misspelled name, found no match and created a new record.
The capstone's intervention has two parts. The first is an identity check at scheduled registration: registrars search using the date of birth and the first three letters of the last name before any new record can be created, and they confirm identity against photo identification. The second is a change to the matching configuration in the registration system, so that the system presents likely matches with a lower score threshold and standardizes addresses before comparing them. Grannis et al. (2019) found that standardizing address and name fields before matching improved matching accuracy, which is the basis for the second part.
The target is a duplicate creation rate below 0.8% within six months of go-live, measured the same way as the baseline.
The Timeline
Table 1
Owned Implementation Timeline
| Weeks | Task | Owner | Done when |
|---|---|---|---|
| 1 | Submit matching configuration request to change control | Registration systems IT analyst | Request number issued |
| 1 to 2 | Write the search-before-create procedure and identification script | Patient access supervisors (two) | Procedure approved by patient access manager |
| 2 to 3 | Set up weekly duplicate report and confirm baseline method | HIM data integrity specialist | Report reproduces the baseline figure of 1.48% |
| 3 to 5 | Train all 46 scheduled registration staff | Patient access supervisors | Attendance log shows 46 of 46 |
| 5 to 6 | Build and test configuration in test environment | IT analyst; HIM specialist tests | Test script passed on 200 known duplicate pairs |
| 6 | Procedure goes live at scheduled registration | Patient access supervisors | First weekly report issued |
| 7 to 9 | Configuration moves to production in the release window | IT analyst | Change ticket closed |
| 9 to 30 | Weekly duplicate rate reported by registrar and site | HIM data integrity specialist | Report sent each Monday |
| Monthly | Review results with the sponsor and decide on adjustments | Patient access manager (sponsor) | Decision recorded in minutes |
Why the Owners Are Who They Are
Each owner holds the authority for the task beside their name. The HIM department does not supervise registrars, so the procedure and the training belong to the patient access supervisors, who can set expectations for their staff and correct them. HIM's role is measurement and the correction of duplicates once they exist, which is already the data integrity specialist's job. The matching configuration belongs to the IT analyst who maintains the registration system, since no one outside information technology may change production configuration. The sponsor is the patient access manager rather than the HIM director, because most of the change happens in patient access.
An early draft named the capstone student as the owner of several tasks. That draft would have failed the moment the student's rotation ended. A task owned by someone without authority over the work either stalls or is done informally and then abandoned, and the final version therefore names the people who will still hold these roles when the capstone is over.
Dependencies and Slack
The timeline has one hard dependency. The configuration change cannot reach production before the monthly release window in week eight or nine, so the request goes in during week one, and the procedure goes live first. This ordering also gives the measurement a useful feature: for about three weeks the procedure runs without the configuration change, so the weekly report can show how much of the improvement comes from each part. Federal work on patient matching has treated it as dependent on both the process at registration and the technical matching that follows (Office of the National Coordinator for Health Information Technology, 2014), and separating the two effects is useful to other hospitals deciding where to spend first. A hospital with a limited information technology budget may find that the procedure alone delivers most of the gain, while one with a strong registration process may need the configuration more.
Training has one week of slack built in. Scheduled registration staff work across three sites and two shifts, and the supervisors estimated that four sessions would reach everyone within two weeks, with a third week for those absent. If the change control board defers the configuration request, the procedure still goes live in week six and the configuration follows in the next release.
How Progress Will Be Judged
The weekly report shows the duplicate rate by registrar and by site. Registrars with high rates are coached by their supervisor, not disciplined, since a high rate often reflects a difficult patient population rather than carelessness. At the monthly review, the sponsor looks at three things: the overall rate against the 0.8% target, the share of registrations in which the search step was recorded and the number of potential matches the new configuration presented that registrars overrode. A high override count would suggest either that the threshold is too low or that registrars are skipping the step. Either finding leads to an adjustment, not to abandoning the change.
The timeline ends at week 30 with a handoff: the weekly report becomes part of the HIM data integrity specialist's standing duties, and the procedure becomes part of new registrar orientation. Without that step, the improvement would last only as long as the attention of the people who started it.
References
Grannis, S. J., Xu, H., Vest, J. R., Kasthurirathne, S., Bo, N., Moscovitch, B., Torkzadeh, R., & Rising, J. (2019). Evaluating the effect of data standardization and validation on patient matching accuracy. Journal of the American Medical Informatics Association, 26(5), 447-456. https://doi.org/10.1093/jamia/ocy191
Just, B. H., Marc, D., Munns, M., & Sandefer, R. (2016). Why patient matching is a challenge: Research on master patient index (MPI) data discrepancies in key identifying fields. Perspectives in Health Information Management, 13(Spring), 1e.
Office of the National Coordinator for Health Information Technology. (2014). Patient identification and matching final report. U.S. Department of Health and Human Services.
HIM 490 Topic 6 instructions, in plain terms
The Topic 6 instructions in HIM-490 ask students to build an implementation timeline for their capstone. Weak submissions list tasks and dates with the student's own name beside most of them. The assignment rewards timelines in which every task has an owner who holds authority over that work, a clear signal that it is done and a realistic duration. Students should identify dependencies such as approval queues and release windows, build in slack where schedules are uncertain, describe how progress will be monitored and what would prompt an adjustment, and plan a handoff so the change survives after the capstone ends.
How this HIM 490 Topic 6 example is built
The finished timeline is a table of actions with a short narrative on either side. Each action states what happens, who owns it by role, the date it starts, the date it finishes and the action it depends on. Owners come from the department holding the relevant authority: patient access supervisors own registration workflow changes, an information technology analyst owns the matching configuration request, and the HIM data integrity specialist owns daily duplicate review and feedback. No action is assigned to a department that has not agreed to it, and each agreement is recorded with its date. The change request appears early, with its review and testing time shown, so the build date follows from the queue rather than from hope. Measurement checkpoints recur at fixed intervals, reported in the baseline's units.
Where the marks sit in the HIM 490 Topic 6 rubric
Faculty grading the implementation timeline reward ownership matched to authority. Excellent timelines assign training to the supervisors of the staff being trained and configuration to the analyst who maintains the system, and they explain those choices. Credit goes to done-when tests that anyone could verify. The rubric values sequencing around hard dependencies, such as launching the procedure before the configuration reaches production, and using that gap to measure each part's effect. The highest level ends with a formal handoff into standing duties. Timelines owned by the student or by committees without authority usually receive partial credit.
Common HIM 490 Topic 6 mistakes, and how to avoid them
Timelines lose marks first where owners are departments rather than roles. An action assigned to patient access in general belongs to nobody who could be asked about it at the next checkpoint. Drafts assigning work to a department that never agreed contradict the constraint analysis and fall apart in the defense. Many versions give every action a date without any predecessor, so a build appears in production before its change request was even submitted. Checkpoints reported in a new unit, or against a different population, break the link to the baseline and leave the project unable to show improvement. Some examples list schedule risks without anyone assigned to watch each. A timeline with no rule for what happens when nothing moves describes a project that can only succeed or be forgotten.
Get an HIM-490 Topic 6 example written to your instructions
Send the HIM-490 Topic 6 instructions, your classroom rubric and the recommendation your project reached. We write a custom example to those criteria, with agreements recorded, owners assigned by role, dependencies setting the order, measurement checkpoints in the baseline's units and a stated rule for no movement, in 24 to 48 hours. The first one costs nothing.
More HIM 490 papers and BS in Health Information Management samples
- HIM 490 Topic 1: Actionable Problem Statement
- HIM 490 Topic 2: Baseline Measurement Report
- HIM 490 Topic 3: Regulatory Constraint Analysis
- HIM 490 Topic 4: Implementability Options Matrix
- HIM 490 Topic 5: Forgotten Constraint Dq Post
- HIM 490 Topic 7: Internal Consistency Audit
- HIM 490 Topic 8: Capstone Panel Defense
- HIM 200 Topic 6: Records Profession Role Survey
- HIM 452 Topic 6: Submission Obligations Calendar
- HIM 310 Topic 6: Mapping Loss Analysis
- HIM 430 Topic 6: Classification and Access Policy
HIM 490 Topic 6 questions, answered
Should the timeline name people or roles?
Roles in the timeline, with names kept in a separate working roster where the instructions call for one. A role survives staff changes and keeps the example de-identified, while a name tells a panel little about authority. What matters is that each role belongs to a department holding the authority the action needs, and that the department agreed to carry it.
How are dates set without knowing the IT queue?
By stating an assumption, labeling it and showing what depends on it. A timeline that assumes a review and testing period, marked as an assumption to confirm with the system owner, earns more trust from a panel than a schedule that ignores the queue. The critical path then shows which dates move if the assumption is wrong, which is exactly the question a panel tends to ask.
What is a critical path in a project timeline?
The longest sequence of dependent actions, which sets the earliest date the project can finish. Delay on any action along it delays the whole project, while actions off it have some slack. In many HIM capstones the path runs through a system change request, because review and testing take longer than workflow changes, and naming it tells a reader where attention belongs.
Where can I find a free HIM 490 Topic 6 sample paper?
This page carries the whole timeline, with what it must deliver, the owned task table, why each owner was chosen, dependencies and slack, and how progress will be judged. Send your plan for a free worked timeline.
Why doesn't the student own any tasks in HIM 490 Topic 6?
The student's rotation ends and the owners' roles do not. Tasks owned by someone without authority over the work stall or are dropped once the capstone is over.