| Course | HIM 515 Foundations and Concepts of Health Care Informatics |
|---|---|
| Topic | Topic 2 |
| Paper type | Clinical fact capture analysis |
| Length | About 1,050 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 2
Not Taking, Reason Unknown: Following One Patient's Sentence From the Admission Interview Into the Saved Record
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HIM-515: Foundations and Concepts of Health Care Informatics
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.
Not Taking, Reason Unknown: Following One Patient's Sentence From the Admission Interview Into the Saved Record
The Fact as It Was Spoken
During an admission interview at Sotol Creek Health's regional hospital, a 71-year-old woman admitted with pneumonia told the admitting nurse: "I stopped the blood pressure pill, the amlodipine, about two weeks ago. It made me dizzy when I stood up. I haven't told Dr. Reyes yet." The sentence carries at least three facts: the medication was stopped, it was stopped because of a side effect the patient experienced, and her prescriber does not know.
The sentence also supports more than one clinical meaning, and each would call for a different record. It could describe an intolerance, a reaction that should inform future prescribing. It could describe nonadherence, a patient not taking what was prescribed. Or it could describe a deliberate stop agreed with nobody, which is both and which leaves the outpatient medication list wrong. This analysis follows the fact through four stages, perceiving, interpreting, representing and saving, to find where each part of it survived or was lost.
Perceiving and Interpreting
The nurse heard the statement accurately. Her notes on the paper worksheet she used during the interview, which the hospital allows as a memory aid and discards after entry, read "amlodipine stopped 2 wks, dizzy, MD unaware." Perception was complete.
Interpretation was also sound. The nurse understood the dizziness as orthostatic, the kind of effect amlodipine can cause, and she understood that the prescriber's ignorance mattered: the clinic list would still show amlodipine as active, and the hospital team might restart it at discharge. To confirm her reading she would have needed to ask whether the dizziness had resolved after stopping, and she did; it had. At the end of the interview, the nurse held all three facts and their clinical significance.
Representing: The Screen Beside the Fact
Table 1
The Medication Reconciliation Screen Beside the Patient's Statement
| Part of the fact | Where the screen could hold it | What was recorded |
|---|---|---|
| Medication stopped | Status: taking, not taking, unknown | Not taking |
| About two weeks ago | Last dose date, optional | Blank; the field accepts only an exact date |
| Because of dizziness on standing | No field on the medication screen; the allergy list is the only coded place for a reaction | Nothing |
| Prescriber unaware | No field | Nothing |
| Dizziness resolved after stopping | No field | Nothing |
Why the Nurse Chose What She Chose
The representing stage is where the fact broke apart. The reconciliation screen offered three statuses for each home medication. Not taking was the closest match, and the nurse chose it. The screen had no place for why. The allergy list could hold a reaction, and some nurses enter side effects there, but the hospital's policy reserves the allergy list for immune-mediated reactions and true intolerances confirmed by a clinician, and dizziness from a vasodilator is neither. The nurse followed the policy. A free-text comment box exists, but it sits on a separate tab of the reconciliation module that opens only when a user selects "add comment" from a menu, and in a 22-minute admission with four other tasks waiting she did not open it.
Blaming the nurse would misread the problem. She chose the most accurate option the structure offered. Ash et al. (2004) described how overly structured data entry can force clinicians to fit what they know into categories that lose its meaning, and this is a clear instance: the structure had a place for the status of the fact and none for its cause.
Saving: What a Later Reader Meets
The saved record reads: amlodipine 5 mg daily, not taking. A hospitalist reconciling medications at discharge sees a blood pressure medication the patient is not taking and a blood pressure of 148/86 on the day of discharge. The record cannot tell her whether the patient forgot, could not afford it, or stopped because of a side effect. The easy reading is nonadherence, and the easy response is to resume the medication with advice to take it. The patient, back home, would then resume a drug that made her dizzy, a fall risk at 71.
Pippins et al. (2008) found that most potentially harmful unintended medication discrepancies at hospital admission arose from errors in taking the preadmission medication history. This case shows a related failure that such studies may not count: the history was taken correctly, and the error entered afterward, when the record could not hold what the history had found.
The Two Gulfs Placed on the Case
Norman (2013) described two gulfs between a person and a system. The gulf of execution is the distance between what a person intends and what the system allows them to do. The gulf of evaluation is the distance between what the system shows and what the person needs to know about whether their intention was achieved. Both appear here, at different stages.
The gulf of execution sits at representing. The nurse intended to record an intolerance and an uninformed prescriber, and the screen offered her three statuses. The gulf of evaluation sits at saving. After she selected not taking, the screen displayed a green check beside the medication, the same confirmation shown for every completed row. Nothing told her that the reason and the prescriber's ignorance had been lost. From her side, the reconciliation was complete. The second gulf is the more dangerous of the two, because it hides the first.
A Field Change and What It Costs
The proposed change adds a coded reason field that appears when a user selects not taking, with five choices: side effect, cost or access, patient choice, prescriber instructed, and unknown. Selecting side effect opens a short free-text qualifier limited to one line, for the effect itself, and a checkbox for "prescriber aware." Coded reasons can drive a discharge alert when a stopped medication is about to be resumed; the qualifier preserves what codes cannot.
The change is not free. In a timed walkthrough with two nurses, the extra fields added about 15 seconds for each medication marked not taking. At Sotol Creek, where the average admission involves about 1.3 such medications, that is under half a minute per admission. The proposal asks nursing leadership to accept that cost, and it would be reviewed after three months against the number of discharge prescriptions changed because of a recorded reason.
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
Norman, D. A. (2013). The design of everyday things (Rev. and expanded ed.). Basic Books.
Pippins, J. R., Gandhi, T. K., Hamann, C., Ndumele, C. D., Labonville, S. A., Diedrichsen, E. K., Carty, M. G., Karson, A. S., Bhan, I., Coley, C. M., Liang, C. L., Turchin, A., McCarthy, P. C., & Schnipper, J. L. (2008). Classifying and predicting errors of inpatient medication reconciliation. Journal of General Internal Medicine, 23(9), 1414-1422. https://doi.org/10.1007/s11606-008-0687-9
Reading the GCU HIM 515 Topic 2 instructions
The Topic 2 instructions in HIM-515 ask students to analyze how clinical information is captured and represented in the record. Weak submissions describe a screen or a documentation policy. The assignment rewards analyses that follow a single clinical fact through distinct stages, from what the clinician perceived and understood to what the structure let them enter and what a later reader will meet. Students should identify the stage where meaning was lost, explain why the clinician's choice was reasonable given the options, apply a human factors or cognitive framework to specific stages and propose a design change with its cost in clinician time.
How this HIM 515 Topic 2 example is built
The finished analysis follows one fact from the moment it is spoken to the moment it is saved. A composite patient tells the admitting nurse she stopped a blood pressure medication two weeks earlier because it left her dizzy, and her prescriber does not know. The analysis sets out what the nurse understood, then what the reconciliation screen allowed her to say: taking, not taking or unknown, with an allergy list as the only place for a reaction. She selects not taking. The saved record now holds a status and no reason, and a later reader cannot tell intolerance from forgetfulness. Norman's gulfs of execution and evaluation frame the loss: what the nurse meant could not be expressed, and what the screen displayed afterward gave her no sign that anything had been lost.
HIM 515 Topic 2 rubric: what Excellent looks like
Faculty grading the capture analysis reward tracing rather than describing. Excellent analyses keep the stages apart and show exactly which parts of the fact had no place in the structure. Credit goes to placing the gulf of execution where intention met the options offered and the gulf of evaluation where the screen confirmed an entry that had lost information. The rubric values a downstream consequence, such as a stopped medication resumed at discharge. The highest level proposes a field change and states how many seconds it adds per entry. Analyses that blame the clinician for the choice usually lose marks.
HIM 515 Topic 2 help before you submit
The commonest weak version describes the screen and never follows a fact through it, which turns an informatics analysis into a user manual. Papers that blame the nurse for choosing not taking miss that she chose the closest option the structure offered. Drafts that call for more free text ignore what narrative costs downstream, where nothing can count or alert on it. The opposite shortcut, more pick lists, forces facts into categories that were never designed for them. Human factors frameworks named in the introduction and never placed on a stage of the case earn little credit at this level. Where a paper proposes a field change without stating the entry time it adds, it has quietly assumed the clinician's minutes are free, and graduate readers notice that assumption quickly.
Get an HIM-515 Topic 2 example written to your instructions
Send the HIM-515 Topic 2 instructions, the rubric posted in your classroom and any scenario or screen supplied. We write a custom example to those criteria, with one fact followed from speech to storage, the structure's limits shown against it, a human factors framework placed on the case and a costed design change, 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 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 7: Sociotechnical Root Cause Analysis
- HIM 515 Topic 8: Informatics Accountability Position
- HIM 615 Topic 2: Vendor Demonstration Script
- HIM 650 Topic 2: Master Data Change Impact Assessment
HIM 515 Topic 2 questions, answered
Why follow one fact instead of a whole record?
Because loss happens to particular facts at particular moments, and a whole-record view averages it away. Following one statement from the patient to the saved field shows exactly which part of the meaning had nowhere to go and why the screen gave no warning. The single fact also keeps the paper honest, since every claim about the structure can be checked against what happened to it.
Is structured data better than narrative?
Neither is better in general. Structured entries can be counted, exchanged and used to trigger alerts, but they hold only the distinctions someone designed into them. Narrative keeps nuance and context, yet it resists reuse. The informatics literature on documentation treats this as a trade-off to be managed field by field, and the analysis argues for one balance on one field instead of settling the question for every record.
What are the gulfs of execution and evaluation?
Donald Norman's terms for two gaps between a person and a device. The gulf of execution is the distance between what someone intends and the actions the interface permits. The gulf of evaluation is the distance between what the device displays and what the person can tell has happened. Both apply to clinical documentation, where intent often exceeds the options offered and the saved result looks complete.
Where can I find a free HIM 515 Topic 2 sample paper?
The complete analysis sits above: the fact as spoken, perceiving and interpreting, the screen beside the fact, why the nurse chose not taking, what a later reader meets, the two gulfs and a field change. Share your case for a free worked analysis.
Where was the information lost in HIM 515 Topic 2?
At representing. The screen offered taking, not taking or unknown, with no place for the reason or the prescriber's awareness, so the saved record held a status without its cause.