| Course | HIM 515 Foundations and Concepts of Health Care Informatics |
|---|---|
| Topic | Topic 5 |
| Paper type | Note readership analysis |
| Length | About 980 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 5
Five Readers, One Progress Note, and Two Lines of Reasoning: Who a Hospitalist's Note Actually Serves
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HIM-515: Foundations and Concepts of Health Care Informatics
Topic 5 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.
Five Readers, One Progress Note, and Two Lines of Reasoning: Who a Hospitalist's Note Actually Serves
The Note
The note analyzed here is a composite hospital day three progress note written by a hospitalist at Sotol Creek Health's regional hospital caring for a man of 64 whose heart failure had worsened enough to need admission. It prints to four pages. The first page and a half is an imported table of laboratory values, every result from the past 72 hours, including repeated basic metabolic panels. A physical examination follows, copied forward from the admission note with one line edited. A review of systems comes next, completed from a template of 14 systems with all but two marked negative. Medications are imported from the active order list. Then, near the bottom of page four, comes the assessment and plan: two lines on heart failure noting that the patient is 2.1 kilograms below admission weight and that the diuretic will be changed to oral, and one line on kidney function.
Most of the page is imported, templated or copied. The reasoning, the part only the hospitalist could write, occupies a small fraction of it. This analysis reads the note five times, once for each person who will read it, to ask whom each part actually serves.
The Cross-Covering Physician
At 2 a.m. a night physician is paged because the patient's potassium is 3.2. She needs to know what the day team was thinking: whether the diuretic change was meant to slow diuresis, whether potassium was already being replaced, and what the team is worried about. She opens the note and scrolls past a page and a half of laboratory values she can see elsewhere in the record, an examination she cannot tell is current and a review of systems that tells her nothing. The two-line assessment gives her the diuretic change but not whether potassium was addressed. Hirschtick (2006) described how copied text makes notes longer and harder to trust, and this reader bears that cost most directly: she needs the smallest part of the note and must search the whole of it to find it.
The Coder, the Auditor and the Lawyer
The coder and clinical documentation specialist read for diagnoses and their specificity. For them, the assessment is essential, and it falls short: heart failure is not specified as systolic or diastolic, acute or chronic, which generates a query. The imported laboratory values are useful to the documentation specialist, who uses them to decide whether a query about a condition such as hyponatremia is supported.
A payer's auditor reviewing the claim reads for evidence that the documented work supports the level of service billed. The examination, the review of systems and the imported data all serve this reader, since they make the note look thorough. Much of the note's length exists because of this reader, whether or not anyone intended it.
A lawyer reviewing the stay years later reads for what was known and when. The timestamped laboratory table is useful here, but the copied examination is a liability: it records findings on day three that were observed on day one, and a reader cannot tell which parts were actually examined that day.
The Patient
The patient can read the note through the portal, often within hours of signing. Delbanco et al. (2012), studying primary care patients invited to read their physicians' notes, found that most who read them reported benefits such as better understanding of their care, and few physicians reported that visits took longer. For this patient, the laboratory table is unreadable, the templated review of systems contradicts what he remembers telling the physician about his breathing, and the two-line assessment, which is what he most wants to understand, uses abbreviations he does not know. Shared notes also change what a clinician can write plainly. A hospitalist who suspects the patient skipped home diuretic doses before admission must decide how to say so in a note the patient will read, which is a reason to write it carefully, not a reason to leave it out.
Where the Readers Pull Against Each Other
The five readers want incompatible things from the same page. The auditor rewards completeness, and the cross-covering physician needs brevity. The coder wants diagnostic terms at the highest specificity, and the patient needs plain language. The lawyer wants every observation dated to when it was made, and copy-forward, which saves the author time, erases that distinction. Coiera (2000) argued that informatics had focused on computation and undervalued communication, and that some information is better exchanged in conversation than in documents. The progress note has been asked to be both a message to the next clinician and an archive for everyone else, and its template was shaped mostly by the archive's readers.
A Note Rebuilt Around Reasoning
The proposal reorders the note so that the assessment and plan come first, written by problem, with a required line for each active problem stating what changed today and what the covering physician should watch for overnight. Laboratory values and medications are linked rather than pasted: the note shows a small set of results the author selects as relevant, with a link to the full table. The examination is written fresh, with a template limited to the systems relevant to the admission, and any copied section is marked with the date it was originally observed.
The cross-covering physician gains the most. The coder gains a clearer assessment. The patient gains a note that begins with what matters to him. The auditor loses something, since the note will look shorter, and the proposal accepts that trade on the grounds that documented reasoning, not documented volume, is what supports medical necessity. The hospital's compliance officer and HIM coding manager should review the template before it goes live, so that the loss to that reader is a decision rather than a surprise.
References
Coiera, E. (2000). When conversation is better than computation. Journal of the American Medical Informatics Association, 7(3), 277-286. https://doi.org/10.1136/jamia.2000.0070277
Delbanco, T., Walker, J., Bell, S. K., Darer, J. D., Elmore, J. G., Farag, N., Feldman, H. J., Mejilla, R., Ngo, L., Ralston, J. D., Ross, S. E., Trivedi, N., Vodicka, E., & Leveille, S. G. (2012). Inviting patients to read their doctors' notes: A quasi-experimental study and a look ahead. Annals of Internal Medicine, 157(7), 461-470. https://doi.org/10.7326/0003-4819-157-7-201210020-00002
Hirschtick, R. E. (2006). Copy-and-paste. JAMA, 295(20), 2335-2336. https://doi.org/10.1001/jama.295.20.2335
HIM 515 Topic 5 instructions, in plain terms
HIM-515 Topic 5 asks students to analyze clinical documentation as communication. Many papers list documentation requirements or criticize note bloat in general. The assignment rewards analyses that take a specific note and identify each of its readers, what each needs and which parts of the note serve each one. Students should show where readers' needs conflict, include the patient as a reader now that notes are shared, explain how the template and the payment environment shaped the note and propose a redesign that states plainly which reader it serves less and why that trade is acceptable.
How this HIM 515 Topic 5 example is built
The finished analysis reads one composite hospitalist progress note five times, once for each person who will read it. The note runs long: an imported table of laboratory values, a physical examination copied forward from admission, a review of systems selected from a template, and two lines of assessment where the clinical reasoning lives. Each section is then assigned to the reader it actually serves: the cross-covering physician at night, the coder and documentation specialist, a payer's auditor, a lawyer reviewing the stay years later and the patient reading through the portal. The analysis finds that most of the page serves the auditor, and that the cross-covering physician, who most needs the reasoning, gets the least of it. Coiera's argument that informatics has undervalued communication frames the finding.
HIM 515 Topic 5 rubric: what Excellent looks like
GCU's rubric for the readership analysis rewards reading an actual note. Excellent analyses name several readers and match the imported tables, copied examination and templated review to the readers they really serve. Credit goes to locating the cause of bloat in templates and audit incentives rather than in physician habit. The rubric values treating the patient as a reader with needs of their own, supported by research on shared notes. The highest level proposes a reordered note and admits the reader who loses under it. Analyses that consider only the next clinician tend to earn partial credit.
HIM 515 Topic 5 help before you submit
Papers that describe documentation requirements and never read an actual note lose credit early, since the subject is a page and the people it serves. An analysis naming a single reader, usually the next clinician, has missed that billing and legal readers shaped most of the template. Blaming physicians for bloat, without noticing that the template and the audit environment reward it, puts the cause in the wrong place. Some drafts treat copy-forward purely as a compliance risk and skip what it does to the reader searching for today's reasoning. The patient reader is frequently left out, even though shared notes now reach many patients by default. A redesign that claims to serve every reader better has not faced the conflicts the analysis is supposed to surface.
Get an HIM-515 Topic 5 example written to your instructions
Send the HIM-515 Topic 5 instructions and the rubric posted in your classroom, with any note or template you were given. We write a custom example to those criteria, with each reader named, every part of the note assigned to the reader it serves, conflicts shown and a redesign that admits its trade-off, 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 6: Encoded Knowledge Critique
- HIM 515 Topic 7: Sociotechnical Root Cause Analysis
- HIM 515 Topic 8: Informatics Accountability Position
- HIM 615 Topic 5: Vendor Contract Obligations Review
- HIM 650 Topic 5: Legacy System Retirement Plan
HIM 515 Topic 5 questions, answered
Why does it matter who a note was written for?
Because the intended reader shapes what gets recorded and what gets left out. A note built to satisfy an auditor carries completeness and repetition, while a note built for the next clinician carries reasoning and uncertainty. When the template serves one reader and the organization assumes it serves another, reuse goes wrong: a reader looks for reasoning in a page written to document billable work.
Where does the patient fit in this analysis?
As a real reader. Patient access to clinical notes, studied in the OpenNotes work led by Delbanco and colleagues and now widespread under federal information access rules, means clinicians write knowing the patient may read the note the same day. That changes tone, what is abbreviated and how uncertainty is expressed. Treat it as a design constraint on the note rather than as an afterthought.
Is copy-forward always a problem?
Not always. Carrying forward stable information can save time and keep facts consistent. The problem is unmarked carry-forward, where an examination or plan from days ago reads as though it were observed today, and readers cannot tell fresh information from inherited text. The analysis distinguishes the two and focuses on what the reader loses, rather than treating every copied line as misconduct.
Where can I find a free HIM 515 Topic 5 sample paper?
Everything is on this page: the note, the cross-covering physician, the coder, auditor and lawyer, the patient, where the readers conflict and the rebuilt note. Send your documentation topic for a free worked paper.
Who does most of the progress note serve in HIM 515 Topic 5?
The payer auditor. The imported data, copied examination and templated review of systems make the note look thorough, while the covering physician who needs the reasoning gets the least of it.