| Course | HIM 370 Health Care Information Systems |
|---|---|
| Topic | Topic 4 |
| Paper type | Duplicate record impact analysis |
| 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 370 Topic 4
Two Transposed Digits: A Duplicate Record Impact Analysis Following a Second Identity Through Every System at Bajada
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HIM-370: Health Care Information Systems
Topic 4 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.
Two Transposed Digits: A Duplicate Record Impact Analysis Following a Second Identity Through Every System at Bajada
How the Duplicate Was Born
Mrs. R., 58, arrived at Bajada Community Hospital's emergency department at 2 a.m. with abdominal pain. She had been a patient twice before, most recently for a hysterectomy three years earlier, and her existing record noted a severe penicillin allergy. The registrar searched the master patient index by name and date of birth, but keyed her birth date as 03/12 instead of 03/21. The search returned no match, the registrar did not try a second search by name alone, and the system issued a new medical record number. From that moment Mrs. R. had two identities at Bajada, and the second one knew nothing of the first.
The error is common. Just et al. (2016), analyzing nearly 400,000 records with confirmed duplicates across several sites, found that discrepancies in identifying fields were widespread, with misspellings of names and mismatches in fields such as Social Security number among the most frequent causes, and concluded that technology alone cannot remove human entry errors.
Following the Second Identity Outward
Table 1
The Second Identity Across Bajada's Systems
| System | What happened under the new identity | Consequence |
|---|---|---|
| EHR | New chart opened with no history, no allergy list, no prior medications | Clinicians saw a patient with no known allergies |
| Laboratory information system | New patient record; prior results not linked | A comparison with her baseline kidney function was unavailable |
| Radiology system and image archive | New patient; the CT from her hysterectomy workup not shown as a prior | Radiologist read the new CT without comparison |
| Pharmacy system | New patient with no allergy on file | Allergy check could not fire |
| Revenue cycle | Claim sent under a new record with insurance entered from the card | Claim accepted, but two account histories now exist |
| Patient portal | No portal account linked to the new record | Mrs. R. could not see this visit's results in her existing portal account |
The Allergy
The most serious consequence was the allergy. The emergency physician diagnosed acute diverticulitis and ordered intravenous piperacillin-tazobactam, a penicillin-class antibiotic. Because the new chart had no allergy recorded, neither the order entry system nor the pharmacy system warned. Mrs. R. was asked about allergies at triage, but she was in pain and said "none that I know of," and the triage nurse documented no known allergies. A nurse preparing the first dose happened to see her wrist, where Mrs. R. wore a medical alert bracelet for penicillin, stopped the infusion before it began and called the physician. The antibiotic was changed.
This is the pattern Ash et al. (2004) described, in which information systems appear to hold complete information while actually holding a fragment, and clinicians reasonably trust what they see. The allergy existed in Bajada's systems. It was simply attached to an identity no one was looking at.
Detection and the Merge
Bajada's enterprise master patient index runs a nightly matching routine that compares identifying fields and scores possible duplicates. The next morning, Mrs. R.'s two records scored high: same name, same address, same phone number, birth dates differing by two transposed digits. A health information management analyst reviewed the pair, confirmed they were the same person from her insurance member number and her surgical history, and initiated a merge. The EHR merged the records and sent merge messages to the connected systems. The laboratory and pharmacy systems processed them. The radiology archive did not, because its interface had never been configured to receive merge messages, and a radiology technologist had to merge the imaging records by hand two days later.
A federally commissioned report on patient matching found the problems widespread and recommended standardizing the demographic data captured and improving matching processes (Office of the National Coordinator for Health Information Technology, 2014). Bajada's case shows that even a well-run matching routine is only as good as the downstream systems' ability to act on a merge.
The Opposite Error, and Why It Is Worse
A duplicate splits one patient into two records. The opposite error, an overlay, merges two patients into one: a registrar who chooses the wrong existing record from a list of similar names files a new patient's visit into someone else's chart. Bajada's analysts treat overlays as more dangerous than duplicates, and the Mrs. R. case helps explain why. In a duplicate, the patient's history is missing from the new record, and clinicians see an incomplete picture that at least belongs to the right person. In an overlay, the record contains another person's history, allergies, blood type and medications, and clinicians see a complete picture that is wrong. Separating overlaid records also takes far longer, because every entry must be assigned to the right person by reviewing its context, and some entries cannot be assigned with certainty.
The registration change adopted after this case, a second search before issuing a new number, would reduce duplicates but could increase overlays if registrars were pressured to find a match. The training that accompanied it therefore teaches registrars to confirm a match with at least two independent identifiers, such as phone number and prior address, before selecting an existing record, and to issue a new number and flag it for review when they cannot.
What the Hospital Changed
Three changes followed. Registration staff now run a second search by name and phone number before issuing a new number to any adult, and the registration system warns when a search returns no match for a patient who reports prior visits. The radiology archive's interface was configured to receive and apply merge messages, and every other system was checked for the same gap; one more, the dietary system, had it. And the emergency department now reconciles allergies against any wristband or alert jewelry at triage. The department also calculated what the duplicate cost: about eleven hours of staff time across registration, health information management, radiology and billing, before counting the harm that nearly occurred.
References
Ash, J. S., Berg, M., & Coiera, E. (2004). Some unintended consequences of information technology in health care: The nature of patient care information system-related errors. Journal of the American Medical Informatics Association, 11(2), 104-112. https://doi.org/10.1197/jamia.M1471
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.
Reading the GCU HIM 370 Topic 4 instructions
The Topic 4 instructions in HIM-370 ask students to analyze the effects of a duplicate medical record across an organization's systems. Weak papers define duplicates and overlays and cite general statistics. The assignment rewards analyses that show how a specific duplicate was created, follow the second identity into every system that received it and describe the clinical, financial and operational consequences in each. Students should explain how the master patient index detects possible duplicates, how merges propagate and where they fail, compare duplicates with overlays and recommend changes to registration practice and system configuration, supported by research on patient matching.
How this HIM 370 Topic 4 example is built
The finished analysis starts with how the duplicate was born. A composite patient arrives at the emergency department, a registrar's search misses the existing record because two digits of the date of birth were keyed in the wrong order, and a new medical record number is issued. The analysis then follows that second identity outward: the laboratory, pharmacy and radiology systems each receive it through admission messages and open their own records under it. An allergy documented during an earlier clinic visit sits on the first record; the emergency medication order goes to the second. Consequences are then separated into three kinds, clinical, operational and reporting. A closing passage explains what happens when the index merges the two records later, and why some downstream systems keep them apart until a merge message is processed.
Reading the HIM 370 Topic 4 rubric
Faculty grading the duplicate record analysis reward following consequences outward. Excellent analyses show each downstream system opening records under the new identity and what clinicians could no longer see. Credit goes to connecting the duplicate to a patient safety risk, such as a hidden allergy, and to explaining how merge messages can fail to reach some systems. The rubric values distinguishing duplicates from overlays and anticipating how a fix for one could increase the other. The highest level recommends specific registration, matching and interface changes supported by patient matching research.
Common HIM 370 Topic 4 mistakes, and how to avoid them
Drafts that treat a duplicate as a filing problem underestimate it from the first paragraph. The topic asks what the second record does once other systems begin to use it, and an answer confined to the registration desk never reaches the systems where the harm occurs. Papers that report a duplicate rate and stop have measured the problem without following one case to the patient. Confusing duplicates with overlays is a costly slip, since an overlay puts one person's results in another person's chart and calls for a different response. Some analyses assume a merge in the index fixes every system at once, which is rarely true when ancillary systems hold their own copies. Proposals that end with more registrar training, and never touch the matching settings, leave the system that created the error unchanged.
Get an HIM-370 Topic 4 example written to your instructions
Send the HIM-370 Topic 4 instructions, the rubric from your classroom and any case, index report or scenario you were given. We write a custom example to those criteria, with the duplicate traced from registration, its spread across systems shown, consequences sorted and repair and prevention placed in the right system, in 24 to 48 hours. The first one costs nothing.
More HIM 370 papers and BS in Health Information Management samples
- HIM 370 Topic 1: System Type Inventory
- HIM 370 Topic 2: Data Element Trace
- HIM 370 Topic 3: Interface Failure Analysis
- HIM 370 Topic 5: System Limits Dq Post
- HIM 370 Topic 6: Weighted Requirements Matrix
- HIM 370 Topic 7: Data Migration Plan
- HIM 370 Topic 8: Installed System Evaluation
- HIM 355 Topic 4: Modifier Justification Table
- HIM 350 Topic 4: Principal Diagnosis Selection Paper
- HIM 310 Topic 4: Terminology Versus Classification Paper
- HIM 200 Topic 4: Release of Information Case Review
HIM 370 Topic 4 questions, answered
What is the difference between a duplicate and an overlay?
A duplicate is one person holding two or more records, so their history is split. An overlay is two different people sharing one record, so their histories are mixed. Both are identity errors, but an overlay is usually treated as the more urgent, since a clinician can act on another person's allergies, results or diagnoses. The analysis defines both and states which one the composite case represents before measuring anything.
How does an index decide two records match?
By comparing identifying fields such as name, date of birth, sex, address and identifiers, using rules that are either deterministic, requiring exact agreement on chosen fields, or probabilistic, weighting agreement across many fields into a score. Thresholds decide what is matched automatically, what is sent for human review and what is treated as a new patient. Settings too strict create duplicates; settings too loose create overlays.
Should the analysis include a duplicate rate?
Only a rate you actually have, from the case or data your instructor supplies. Inventing a figure to make the paper look quantitative undermines it. Where a rate is available, it belongs beside the traced case rather than in place of it, because a percentage says how often the problem occurs and the trace says what it does. Composite examples here avoid invented numbers for that reason.
Where can I find a free HIM 370 Topic 4 sample paper?
The whole analysis appears here, with how the duplicate was born, the second identity across systems, the allergy, detection and the merge, why overlays are worse and what the hospital changed. Send your case for a free worked analysis.
Why was the allergy invisible in HIM 370 Topic 4?
The penicillin allergy was recorded under the patient's original identity. The new record had no allergy on file, so neither order entry nor the pharmacy system could warn when a penicillin-class antibiotic was ordered.