| Course | HIM 515 Foundations and Concepts of Health Care Informatics |
|---|---|
| Topic | Topic 7 |
| Paper type | Sociotechnical root cause analysis |
| Length | About 990 words, 3 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | MS in Health Informatics |
| Updated | September 2026 |
Free sample paper for HIM 515 Topic 7
Every System Worked and the Letters Kept Coming: A Sociotechnical Root Cause Analysis of a Diabetes Reminder Sent to the Wrong Patient
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HIM-515: Foundations and Concepts of Health Care Informatics
Topic 7 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 System Worked and the Letters Kept Coming: A Sociotechnical Root Cause Analysis of a Diabetes Reminder Sent to the Wrong Patient
A Letter Nobody Could Explain
In March a 41-year-old woman called Sotol Creek Health's outreach line holding a letter reminding her that she was overdue for her annual diabetic eye examination. It was the third such letter in two years, and she had also received two reminders about diabetic foot examinations. She does not have diabetes. She had gestational diabetes during a pregnancy four years earlier, which resolved after delivery, and her glucose tests since have been normal. The outreach coordinator could not explain the letters, and the patient's primary care physician, when asked, said she had assumed they were a mailing error.
The symptom was noticed by the patient and by staff outside the clinical system long before anyone inside it. This analysis traces the letter backward to its source and then uses a sociotechnical model to locate the cause.
The Trace, Backward From the Letter
The letter was produced by the outreach tool, which mails reminders to every patient on the diabetes registry who lacks a documented eye examination in the past twelve months. The tool behaved as designed. The registry adds any patient with an active diabetes entry on the problem list or two diabetes diagnosis codes on claims within two years. The patient had no recent diabetes claims, but she had an active problem list entry for type 2 diabetes mellitus without complications. The registry behaved as designed. The reminder rule in the clinic record, which also displays care gaps at each visit, draws on the same registry and behaved as designed.
The problem list entry was added at a prenatal visit four years earlier. The obstetric clinician, needing a diagnosis on the problem list to order diabetes education and glucose monitoring supplies, selected the first diabetes term the search returned. The correct entry, gestational diabetes, would have been resolved automatically at delivery under the system's pregnancy episode logic, but the general entry had no such logic. After delivery, no one resolved it. Two primary care visits since then displayed the entry; neither changed it.
Eight Dimensions, One at a Time
Sittig and Singh (2010) proposed a sociotechnical model with eight dimensions for studying health information technology in the settings where it is used. The model is useful here only if each dimension is used to rule a cause in or out.
Table 1
The Sociotechnical Model Applied
| Dimension | Finding | Evidence |
|---|---|---|
| Hardware and software | Clean | Registry, outreach tool and reminder rule processed their inputs correctly |
| Clinical content | Contributing | The problem list search returns type 2 diabetes above gestational diabetes for the query "diabetes" |
| Human-computer interface | Contributing | Problem list entries display with no date added or author unless the user opens each one |
| People | Clean as a cause | The clinicians involved acted reasonably given what they saw |
| Workflow and communication | Primary | Adding an entry is part of ordering; resolving one is part of no one's workflow |
| Organizational policies and culture | Primary | No policy assigns responsibility for keeping the problem list current |
| External rules and pressures | Contributing | Quality measures reward registry size and completed care gaps, not registry accuracy |
| Measurement and monitoring | Contributing | No one monitors stale problem list entries |
The Practice at the Center
The two primary findings describe the same practice. At Sotol Creek, problem list entries are added by whoever meets the problem, often because an order requires a diagnosis, and resolved by nobody in particular. A query of the network's records found 1,340 active type 2 diabetes entries on patients with no diabetes diagnosis code on any claim in three years and no hemoglobin A1c above 6.4% in that period. Not all of those are errors, since some patients with well-controlled diabetes managed elsewhere would match, but a review of 50 of them found 19 that were clearly resolved or never correct, including nine arising from gestational diabetes.
Weed (1968) proposed the problem-oriented record so that a patient's problems would organize the care and teaching around them. The problem list he described was a working document maintained by the clinicians caring for the patient. In current practice it has become, in part, a collection of diagnoses entered to satisfy order requirements and billing edits, maintained by no one. Some errors live in the joins between clinicians and software rather than in either one (Ash et al., 2004), and this case is one: each component worked, each clinician acted reasonably, and the result was wrong.
An Algorithm Considered and Rejected
The informatics team first proposed an automated rule: expire any diabetes entry added during a pregnancy episode at delivery unless a clinician confirms it. The rule would have fixed this patient and the nine similar ones found in the review. It was rejected because it treats one pattern while leaving the practice that produces every other stale entry, from resolved hypertension to a pneumonia listed as active for three years. A software fix for one symptom would also signal that problem list accuracy is a technical matter, which the analysis found it is not.
Recommendation: Assign the Resolving
The recommendation assigns responsibility for problem list review to the patient's primary care clinician at the annual wellness visit, and to the obstetric clinician at the postpartum visit, with a list review step added to both visit templates. The interface should display the date each entry was added and its author, so that an entry added at a prenatal visit four years ago is visible as such. The clinical content team should reorder the search so that gestational diabetes appears when the patient has an active pregnancy episode. Monitoring should include a quarterly count of registry patients without supporting codes or laboratory values, reported to the population health committee. Registry accuracy should become a measure the organization watches, alongside registry size, so that the letters that reach the wrong patient are counted rather than explained away.
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
Sittig, D. F., & Singh, H. (2010). A new sociotechnical model for studying health information technology in complex adaptive healthcare systems. Quality and Safety in Health Care, 19(Suppl 3), i68-i74. https://doi.org/10.1136/qshc.2010.042085
Weed, L. L. (1968). Medical records that guide and teach. New England Journal of Medicine, 278(11), 593-600. https://doi.org/10.1056/NEJM196803142781105
What the HIM 515 Topic 7 instructions ask for
HIM-515 Topic 7 asks students to analyze a health IT problem using a sociotechnical model. Many papers list the model's dimensions as headings with a sentence under each. The assignment rewards analyses that trace the problem from its symptom back through every system and person involved, then use each dimension to rule a cause in or out with evidence. Students should locate the primary cause, distinguish individual error from practice patterns, test whether the problem extends beyond one case, weigh a software fix against a change in practice and recommend who should own the change.
How this HIM 515 Topic 7 example is built
The finished analysis starts from a reminder that keeps arriving for the wrong patient. A composite woman receives letters about diabetic eye and foot examinations years after gestational diabetes resolved, because a general diabetes entry added during pregnancy was never marked resolved. The reminder rule, the outreach system and the registry all behaved as designed. The analysis then walks the problem through Sittig and Singh's eight sociotechnical dimensions, from hardware and software through clinical content, interface, people, workflow, organizational features, external rules and monitoring. Software and interface come back clean. The cause is located in a documentation practice: problem list entries are added by whoever meets the problem and resolved by nobody in particular. Ash, Berg and Coiera's work on unintended consequences supports reading the error as one that arose between people and systems.
Where the marks sit in the HIM 515 Topic 7 rubric
GCU's rubric for the root cause analysis rewards a model used to decide. Excellent analyses give some dimensions a clean result and identify the primary causes, such as a workflow in which adding problem list entries is routine and resolving them belongs to no one. Credit goes to a trace that follows the data through each component that consumed it. The rubric values evidence that the pattern is widespread, which moves blame from an individual to a practice. The highest level considers and rejects a narrow automated fix and assigns resolution to specific roles and visits. Analyses that fix the reminder rule usually land in a middle band.
HIM 515 Topic 7 help before you submit
Papers that stop at the reminder rule and recommend changing its logic have fixed a symptom in the one component that was working. The sociotechnical model loses its value when it is listed as eight headings and never used to rule anything in or out. Some drafts assign every dimension a finding, which makes the model look applied while saying nothing about where the cause actually sits. A trace that skips the registry and jumps straight to the prenatal visit misses the two places where the entry was consumed without question. Blaming the obstetric clinician misreads a practice problem as an individual error, since the same pattern appears across specialties. Recommendations that rely entirely on software, such as automatic expiry, leave the documentation habit untouched and the next stale entry already on its way to someone else.
Get an HIM-515 Topic 7 example written to your instructions
Send the HIM-515 Topic 7 instructions, the rubric from your classroom and any incident, case or framework the assignment names. We write a custom example to those criteria, with the failure traced past the software, a sociotechnical model used to rule causes in and out, the documentation practice identified and a defended owner, in 24 to 48 hours. The first one costs nothing.
More HIM 515 papers and MS in Health Informatics samples
- HIM 515 Topic 1: Informatics Boundary Paper
- HIM 515 Topic 2: Clinical Fact Capture Analysis
- HIM 515 Topic 3: Secondary Use Fitness Analysis
- HIM 515 Topic 4: Controlled Vocabulary Critique
- HIM 515 Topic 5: Note Readership Analysis
- HIM 515 Topic 6: Encoded Knowledge Critique
- HIM 515 Topic 8: Informatics Accountability Position
- HIM 615 Topic 7: Post-implementation Adoption Review
- HIM 650 Topic 7: Quality Control Placement Audit
HIM 515 Topic 7 questions, answered
What is the Sittig and Singh sociotechnical model?
An eight-dimension model for studying health IT in real settings, covering hardware and software, clinical content, the human-computer interface, people, workflow and communication, internal organizational features, external rules and regulations, and system measurement and monitoring. Its central claim is that these dimensions interact, so a failure rarely belongs to one alone. The analysis uses it to rule dimensions out as well as in.
Why not fix the problem in software?
Because the software was working. An automatic expiry for certain entries would stop this letter, but problem lists go stale for many reasons across every specialty, and a rule written for one pattern leaves the rest in place. Software can support a practice, for example by prompting review at an annual visit, yet the analysis argues the practice itself needs an owner first.
What did Weed intend the problem list to be?
Lawrence Weed's problem-oriented medical record placed a maintained list of problems at the front of the record, organizing notes and plans around each one. The list was meant to be the record's index, kept current by the clinicians using it. Citing that purpose shows how far a list maintained by habit has drifted, and it gives the recommendation a standard to aim at.
Where can I find a free HIM 515 Topic 7 sample paper?
This page holds the complete analysis: the letter, the backward trace, the eight dimensions in a table, the practice at the center, the rejected algorithm and the recommendation. Tell us your incident for a free worked analysis.
Why was the automatic expiry rule rejected in HIM 515 Topic 7?
It would fix stale diabetes entries from pregnancy but leave the practice that produces every other stale entry, since resolving problem list entries belongs to no one's workflow.