| Course | HIM 490 Health Information Management Capstone |
|---|---|
| Topic | Topic 2 |
| Paper type | Baseline measurement report |
| Length | About 970 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 2
One Number and Everything Needed to Reproduce It: A Baseline Measurement Report for Saltbush's Duplicate Record Creation Rate
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HIM-490: Health Information Management Capstone
Topic 2 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.
One Number and Everything Needed to Reproduce It: A Baseline Measurement Report for Saltbush's Duplicate Record Creation Rate
The Metric, Defined Before the Data
This capstone aims to prevent duplicate medical records at Saltbush Regional Medical Center by changing how patients are identified at registration. Its baseline measure is the duplicate creation rate: the number of confirmed duplicate records created in a period, divided by the number of new medical record numbers issued in the same period. That is a different figure from the share of duplicates sitting in the master patient index as a whole, which reflects years of accumulated records and cleanup. The capstone uses the creation rate because its intervention acts on new registrations; a project that prevents new duplicates could succeed while the index-wide share barely moved, since the backlog would remain until it was cleaned. The index-wide figure is reported once, for context, and not used to judge the project.
How Each Part of the Number Is Counted
The numerator counts duplicates confirmed by the HIM data integrity specialist, who reviews every potential duplicate the enterprise master patient index flags and merges those that are the same person. A duplicate is attributed to the period in which the second record was created, not the period in which it was confirmed, so the count for a month is not final until the review queue for that month is cleared; at Saltbush, 97% of potential duplicates are resolved within 30 days, so each month's figure is reported 45 days after the month ends. The denominator counts new medical record numbers issued in the period, taken from the registration system.
Three exclusions apply to both parts. Test patients created by information technology are removed. Newborn records created with temporary names, such as a surname with "Baby Girl," are removed, because their later merge with the named record is an expected process, not an identification failure. And records created during downtime and reconciled afterward are counted separately, since downtime registration follows a different procedure.
The Baseline
Table 1
Baseline Duplicate Creation, With Its Sources
| Measure | Twelve months ending June |
|---|---|
| New medical record numbers issued, after exclusions | 41,300 |
| Confirmed duplicates created, after exclusions | 612 |
| Duplicate creation rate | 1.48% |
| Share created at scheduled outpatient registration | 58% (355) |
| Share created in the emergency department | 24% (147) |
| Share created at clinic front desks | 18% (110) |
| For context: estimated duplicates in the whole index | About 2.1% of records |
What the Baseline Shows
The rate is 1.48%, about 51 new duplicates a month, and it is concentrated where the capstone expected. Scheduled outpatient registration, where staff create records by telephone before the patient arrives, produced 58% of new duplicates while issuing about 40% of new numbers. The review of each duplicate's pair of records found why: scheduling staff search by name and date of birth while speaking to the patient, and a misheard name or a birth date given in a different order, day before month, produces no match and a new record. Just et al. (2016), analyzing records with confirmed duplicates across several organizations, found mismatches in names and other identifying fields to be common causes, and Saltbush's pattern matches theirs.
The emergency department's share was lower than expected. Its registrars see the patient and often scan a photo identification, which reduces misheard names, and its duplicates came mostly from patients unable to give identifying information on arrival.
Checks on the Number
Two checks support the baseline. First, the data integrity specialist's confirmation decisions were sampled: a second reviewer examined 50 confirmed duplicates and 50 flagged pairs the specialist had judged to be different people, and agreed in 97 of 100. Second, the query was run independently by an analyst in information technology from the same definitions, and produced 609 duplicates rather than 612, the difference traced to three records created in the last hour of June and counted in different months. The report adopts 612, with the rule that a record belongs to the month of its creation timestamp.
The creation rate also depends on how well the index's matching algorithm flags potential duplicates in the first place, since a duplicate never flagged is never counted. Grannis et al. (2019) found that standardizing some identifying fields changed matching sensitivity only modestly and could reduce specificity, a reminder that algorithm settings shape what is counted. The baseline therefore holds the algorithm's settings fixed for the project's duration, so that a change in the rate reflects registration, not matching.
What the Baseline Does Not Measure
The creation rate counts duplicates; it does not count overlays, in which two different people end up sharing one record. Overlays are rarer and more dangerous, and an intervention that pressures registrars to find a match could increase them while reducing duplicates. The capstone therefore tracks confirmed overlays as a balancing measure, with a baseline of seven in the twelve months, and will treat any rise as a signal to adjust the intervention. The rate also does not measure the cost of each duplicate, in staff time to merge records across systems and in the clinical risk of care delivered on an incomplete record. Those costs are described qualitatively in the capstone's problem statement, from the specialist's log of merge time, about 25 minutes per duplicate, but they are not part of the baseline metric, because the data on hand would not capture them consistently across both periods.
Reproducing the Baseline
The report's appendix contains the two queries, the exclusion lists and the confirmation log, so that the post-intervention measure uses exactly the same method. The Office of the National Coordinator's report on patient matching emphasized that consistent measurement of matching performance is itself a gap many organizations face (Office of the National Coordinator for Health Information Technology, 2014). A capstone that changes its metric midway cannot show that it changed anything, and this report fixes the metric before the intervention begins.
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.
What the HIM 490 Topic 2 instructions ask for
The Topic 2 instructions in HIM-490 ask each student to establish a baseline for the capstone's chosen measure. Weak submissions report a number without saying how it was counted. The assignment rewards reports that define the numerator and denominator before presenting data, explain why this measure rather than a similar one fits the intervention and document the time period, data sources and exclusions. Students should break the baseline down in ways that point toward causes, test the number with at least one independent check, state honestly what it leaves out and give enough detail that another analyst could reproduce it from the same data.
How the HIM-490 Topic 2 example is put together
The finished report fixes one number and everything needed to reproduce it. The metric is defined before any data appears: confirmed duplicate records created in a period, divided by new registrations in that period, which is a different figure from the share of duplicates sitting in the whole index. The report explains why the capstone uses the creation rate, since the project aims at prevention at registration rather than cleanup of the backlog. Potential duplicates flagged by the matching algorithm are separated from those confirmed on review, and the review rules are stated. The period, the source reports and the role that ran them are recorded. Known weaknesses are listed, including duplicates the algorithm never flags. A closing line states the baseline in the exact form the target will later take.
Where the marks sit in the HIM 490 Topic 2 rubric
Faculty grading the baseline report reward a number that can be rebuilt. Excellent reports define the metric precisely and justify it against alternatives, such as a creation rate rather than an index-wide share. Credit goes to showing how each part of the figure is counted and where duplicates arise by site and registration type. The rubric values independent checks on the number and a plain account of its limits. The highest level provides reproduction steps concrete enough to be followed, since the same query will judge the project later. Reports that present a baseline without its method usually lose marks.
HIM 490 Topic 2 help before you submit
Most lost marks here trace to a baseline that cannot be reproduced. A figure quoted from a vendor dashboard, with no numerator, denominator or period, gives the capstone nothing it can compare against later. Drafts that report the share of duplicates across the whole index and then set a target for new registrations compare two different measures and call the gap progress. Treating every algorithm flag as a confirmed duplicate inflates the starting point, which makes almost any intervention look successful. Many papers skip the breakdown by registration area and later propose a fix for the wrong desk. Reports that never admit what the measurement misses overstate their precision to a panel that will ask. Some drafts slip a proposed solution into the baseline, which quietly shapes the measurement around proving it.
Get an HIM-490 Topic 2 example written to your instructions
Send the HIM-490 Topic 2 instructions and your classroom rubric, with any data, reports or project scope your assignment provides. We write a custom example to those criteria, with the metric defined before any data appears, flagged and confirmed counts separated, the review rules stated and the baseline written in the target's units, 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 3: Regulatory Constraint Analysis
- HIM 490 Topic 4: Implementability Options Matrix
- HIM 490 Topic 5: Forgotten Constraint Dq Post
- HIM 490 Topic 6: Owned Implementation Timeline
- HIM 490 Topic 7: Internal Consistency Audit
- HIM 490 Topic 8: Capstone Panel Defense
- HIM 200 Topic 2: Legal Record Boundary Memo
- HIM 452 Topic 2: Abstraction Judgment Log
- HIM 310 Topic 2: Diagnosis Hierarchy Analysis
- HIM 430 Topic 2: Stewardship Role Charter
HIM 490 Topic 2 questions, answered
What if I cannot get real data for the baseline?
Then the baseline section describes exactly how the figure would be produced, names the reports and the period, and labels any number shown as illustrative. Your instructions may allow a scenario dataset. What a capstone should not do is present an invented figure as measured, since the first panel question will concern its origin and the whole project rests on it.
Why distinguish potential from confirmed duplicates?
Because matching algorithms are usually tuned to flag more pairs than are truly the same person, leaving a reviewer to decide. Counting flags inflates the problem and makes improvement easy to claim. Counting only confirmed pairs, under stated review rules, produces a smaller and more defensible figure. The report prints both counts side by side and explains why the confirmed one carries the project.
Does the baseline need a comparison benchmark?
Not necessarily. A benchmark from another organization can give context, but only if its definition matches yours, and published duplicate figures often use different numerators. The capstone's own baseline, measured consistently, is what later topics compare against. When a benchmark is required, cite its source and state any difference in definition beside it.
Where can I find a free HIM 490 Topic 2 sample paper?
The full report sits above, with the metric defined first, how each part is counted, the baseline, what it shows, checks on the number, its limits and how to reproduce it. Share your capstone measure for a free worked baseline.
What is the baseline in HIM 490 Topic 2?
The hospital created 612 confirmed duplicate records among 41,300 new registrations in twelve months, a duplicate creation rate of 1.48 percent, most of them at scheduled outpatient registration.