WRITING IN HEALTHCARE: DOCUMENTATION AND HANDOFF

Healthcare is the one workplace where a sentence can change a dose. The chart is not a diary of what you did; it is a working instrument that the next clinician reads at 0300 with four other patients waiting, that a billing auditor reads two months later, and that an attorney may read out loud to a jury four years later. This chapter teaches the specific writing skills that record demands: turning an observation into a defensible line of documentation, choosing a note structure and filling it without padding, compressing a twelve-hour shift into a ninety-second handoff that survives interruption, correcting a mistake without creating a bigger one, and writing discharge instructions a frightened person can actually follow in a parking lot. Every rule here comes with a weak version and a better version, because in clinical writing the difference between the two is usually six words and one specific number.

Section 1The Record and Its Readers

Six readers, one document

Most students learn documentation as a compliance chore: fill the boxes, satisfy the instructor, move on. That framing produces bad charting because it imagines a single reader who already knows the story. The real health record has at least six readers, and they arrive at different times with different questions. The nurse coming on at 1900 wants to know what changed and what to watch. The hospitalist rounding tomorrow wants the reasoning behind yesterday’s decisions. The physical therapist wants function, not lab values. A coder wants documented specificity that supports the billed level of care. A quality reviewer wants evidence that a required assessment happened. And a plaintiff’s attorney, years later, wants to know what a reasonable clinician knew and when.

Good clinical writing serves all six without writing six documents. It does that through a habit you can practice: every entry answers what did I observe, what did I think it meant, what did I do, and what happened next. That four-beat pattern is the spine underneath every charting format in this chapter. When a note feels thin, one of the four beats is usually missing — most often the third and fourth, because clinicians document findings and then forget to document their own response to the findings.

Consider a single line. Weak: “Patient c/o SOB.” That satisfies nobody. Better: “0215 — Patient reports shortness of breath, new since 0130. RR 28, SpO2 88% on room air, accessory muscle use, bilateral crackles to mid-lung. Placed on 2 L nasal cannula, head of bed elevated to 45 degrees. SpO2 94% at 0225. Paged Dr. Okonkwo 0218; no response at 0230, escalated to charge nurse.” The second version answers all four beats, gives the coder specificity, gives the next shift a baseline, gives the reviewer evidence of escalation, and gives you a defense.

What “legal document” actually means

You will hear that the chart is a legal document, usually as a warning. The more useful version is that the chart is evidence — specifically, it is generally admissible as a business record because it is made contemporaneously by people with a duty to record accurately. That single sentence explains most documentation rules. Contemporaneous means timing matters. Duty to record accurately means the entry must be what you actually observed, in your own assessment, not a template’s guess. Business record means the chart is expected to look like routine work, which is exactly why a note that suddenly turns defensive or unusually detailed around a bad outcome draws attention.

The maxim “if it isn’t documented, it didn’t happen” is a teaching slogan, not a legal rule, and it is worth understanding precisely. Courts do accept testimony about undocumented care, and clinicians routinely testify to routine practice. But undocumented care is far harder to prove: memory of a specific shift years ago is weak, and opposing counsel will argue that the absence of an entry is evidence of absence of care. So the accurate version is: undocumented care is not legally nonexistent, but it is legally expensive. Document accordingly, and never chart care that did not occur in order to make the record look complete — that is falsification, and it converts a defensible case into an indefensible one.

One more consequence of “evidence” deserves emphasis. In an electronic record, the audit trail — who opened the chart, who edited what, at what second, from which workstation — is itself data and is generally discoverable. That means the record now documents your documenting. A note entered at 0400 describing events at 2200, with no late-entry label, tells a story you did not intend to tell.

Purpose drives format

Before choosing a structure, decide what the entry is for. A routine shift assessment, an event note, a procedure note, a communication note and a discharge summary are different genres with different obligations, and students lose points — and later, credibility — by writing all five the same way. An event note needs a tight timeline and an escalation trail. A procedure note needs consent, technique, tolerance and post-procedure status. A communication note needs who, when, by what method, what was said, and what was agreed.

Here is the genre difference in one comparison. A routine assessment can reasonably read: “1400 — Neuro intact, alert and oriented x4, no deficits noted. Tolerating diet. Ambulated to bathroom with standby assist.” An event note about the same patient two hours later cannot be written in that register: “1610 — Found on floor beside bed, supine, awake. States she was reaching for her phone. No LOC witnessed or reported. Denies head strike; no scalp hematoma or laceration palpated. Vitals 138/82, HR 92, RR 18, SpO2 97% RA. Moves all extremities, denies pain except right hip 3/10 with movement. Neuro checks initiated per protocol. Dr. Reyes notified 1615, orders received for hip and pelvis X-ray. Daughter Ms. Alvarez notified by phone 1628.”

Notice what the event note does not contain: any statement about why the fall happened, whether anyone was at fault, whether the bed alarm was on, or whether the patient “should have” called. Those belong in a separate safety report, discussed in Section 5. The clinical record documents the patient. It does not adjudicate the system.

Section 2Writing the Clinical Note

Choosing a skeleton

Every charting format is a device for making sure you do not forget a beat. SOAP — Subjective, Objective, Assessment, Plan — separates what the patient told you from what you measured, then forces you to say what you think and what you will do. APSO is the same content reordered so Assessment and Plan appear first; many inpatient services adopted it because readers want the conclusion before the raw data. DAR or focus charting — Data, Action, Response — organizes an entry around one problem and is common in nursing because it captures the intervention loop cleanly. PIE (Problem, Intervention, Evaluation) is a close cousin. Narrative charting is free prose in chronological order; it is flexible and terrible at retrieval. Charting by exception documents only deviations from a defined, published standard of normal, which saves enormous time and creates real risk if the standard is not actually defined or if the reader does not know what “within defined limits” covers.

Here is one clinical situation written three ways, so the differences are visible rather than theoretical. DAR: “Focus: Acute pain, post-op day 1 right total knee. Data: Reports 8/10 aching pain right knee at rest, grimacing, guarding, declines to participate in PT. HR 104, BP 152/88. Incision clean, dry, intact; no erythema; drainage scant serosanguinous. Last oxycodone 0510. Action: Oxycodone 5 mg PO given 0915 per order. Ice applied, knee elevated on two pillows. PT session deferred and rescheduled for 1100. Response: 1000 — reports 3/10, resting quietly, HR 88. Participated fully in 1100 PT session, ambulated 20 feet with front-wheeled walker.”

SOAP covers the same ground but sorts by source rather than by loop: the patient’s report goes in S, the vitals and wound exam go in O, “uncontrolled post-operative pain limiting mobility, no signs of wound infection” goes in A, and the medication, ice, elevation and rescheduled therapy go in P. Narrative would say all of it in paragraph form and would be perfectly adequate for a reader with time and completely useless to a covering clinician scanning for the pain trend. Pick the structure your unit uses, then fill it honestly — the format is scaffolding, not the point.

Observation, inference and the sentences in between

The most transferable skill in clinical writing is separating what you saw from what you concluded, then labeling the conclusion as yours. Charts get into trouble when an inference is written in the grammar of an observation. “Patient is anxious” reads like a measurement; it is an interpretation. “Patient is drug-seeking” reads like a finding; it is an accusation, and it is not a clinical entity. “Patient is non-compliant” assigns a stable trait when the observable fact may be that the pharmacy is nine miles away and the bus does not run on Sundays.

This is not merely a matter of politeness. Experimental work published in Journal of General Internal Medicine in 2018 by Goddu and colleagues found that medical trainees who read a vignette written with stigmatizing language held more negative attitudes toward the patient and made less aggressive pain-management choices than trainees who read a neutral version of the same case. Subsequent chart-review research, including a 2021 analysis in JAMA Network Open, documented that such language appears in real notes and is unevenly distributed across patient groups. The mechanism is simple: your note is the next clinician’s first impression, and impressions are sticky.

The repair is mechanical. Replace the label with the behavior, the time and the number. Keep your clinical judgment — you are paid for it — but mark it as judgment with a hedge that is honest rather than mushy: “appears,” “consistent with,” “my impression is,” “cannot exclude.” And when you quote the patient, quote them: direct quotation in quotation marks is both more accurate and more protective than your paraphrase of what they meant.

Sentence craft inside the chart

Clinical prose has its own compression rules, and the goal is speed of retrieval, not elegance. Lead with the time. Use the patient’s numbers, not your adjectives — “output 320 mL over 8 hours” beats “good urine output.” Prefer active voice with a named actor for anything involving accountability: “I notified Dr. Bell at 0342” rather than “the provider was notified.” Passive voice is fine for the routine, dangerous for the critical, because the reader in year four wants to know who did what.

Avoid three habits that quietly damage notes. First, the unclosed loop: you document that you paged someone and never document whether they answered. Every notification needs an outcome, even if the outcome is “no response by 0400; escalated.” Second, the editorial aside — “as usual,” “finally,” “yet again,” “despite repeated instruction.” These read as contempt on a printed page held by a jury. Third, hedging without content: “patient seems to be doing okay” commits you to nothing and helps no one.

Length is not virtue. A dense eight-line event note beats a forty-line note assembled from imported data. The test is whether a competent stranger could reconstruct your reasoning and your actions from the note alone. If they could, stop writing.

Section 3Handoff: SBAR, I-PASS and the Spoken Record

The highest-risk paragraph you will ever compose

A handoff — also called handover or sign-out — is the transfer of both information and responsibility. It happens at shift change, at transfer between units, at discharge to a skilled facility, and every time a covering clinician takes your pager. It is spoken, usually under time pressure, frequently interrupted, and then it disappears. That combination is why communication failures have long ranked among the most frequently identified contributors in serious-event reviews, and why accreditation standards in the United States have required a standardized handoff process, including an opportunity to ask and answer questions, since the mid-2000s.

Treat handoff as writing even when you say it out loud. You are composing a paragraph with a fixed structure, delivering it, and then confirming it landed. The failure modes are the same as in any writing: burying the important thing, assuming shared context you do not have, and omitting the conditional — what to do if the situation changes. That last omission is the one that hurts people. An incoming clinician who knows the patient’s history but not your worry has been given data instead of a handoff.

Two structures dominate. SBAR is for escalation and focused communication about a single concern. I-PASS is for full transfer of care. Learn both; they are not interchangeable, and using the wrong one is a common student error. Calling a physician at 2 a.m. and reciting an entire I-PASS is a way to lose your listener before you reach the reason you called.

SBAR: getting a decision from someone who is busy

SBAR — Situation, Background, Assessment, Recommendation — originated in United States Navy nuclear submarine communication and was adapted for healthcare at Kaiser Permanente in the early 2000s; it is now embedded in AHRQ’s TeamSTEPPS training. Its power is that it front-loads the problem and ends with an explicit ask. Novices consistently fail at the R. They describe a patient beautifully and then stop, leaving the physician to guess what is wanted. Say what you want.

Here is the weak call, close to verbatim from real practice: “Hi, this is Dana on 4 West, sorry to bother you, it’s about Mr. Fitzgerald in 412, he had his gallbladder out yesterday, and he’s been fine most of the night, his daughter was here earlier, um, his blood pressure was a little soft earlier and he’s kind of warm, I just wanted to let you know.” The physician now has to conduct an interview at 2 a.m. to find the emergency. Compare the structured version in the table below — same facts, forty seconds, one clear request.

Two refinements make SBAR much stronger. Assemble your data before you dial: current vitals, relevant labs, last dose and time of key medications, allergies, code status, and the chart open in front of you. And in the Assessment, say your level of concern in words, because clinicians calibrate on that phrase: “I think he may be septic” or “I am worried this is bleeding” changes the response you get. If you are unsure, say “I am not sure what this is, but I am concerned” — that is honest, and it is actionable.

I-PASS and the receiver’s half of the job

I-PASS — Illness severity, Patient summary, Action list, Situation awareness and contingency planning, Synthesis by receiver — was developed by a multi-site collaborative and published by Starmer and colleagues in the New England Journal of Medicine in 2014. The original nine-site pediatric residency study reported a 23 percent reduction in medical errors and a 30 percent reduction in preventable adverse events after implementation. It is fair to say the evidence has been influential; it is also fair to note that later multi-site work across adult and mixed settings has produced more mixed effect sizes, and researchers continue to debate how much of the benefit comes from the mnemonic itself versus from protected time, a standard template and a culture that permits questions. The honest teaching position: the structure is worth learning, and the conditions around it matter at least as much.

The last element is the one students skip and the one that does the work. Synthesis by receiver means the person taking over says the plan back in their own words. This is the same principle as the required read-back for verbal orders and critical test results, where the receiver repeats the complete order and the sender confirms it. Read-back catches the sound-alike drug, the transposed digit, the missing decimal. A handoff without synthesis is a broadcast, and broadcasts are not transfers of responsibility.

The contingency element deserves the same attention. “If X, then Y” statements convert your clinical judgment into something the next person can act on at 0300 without paging anyone. Write them as explicit conditionals with a threshold and an action: not “watch her pressures,” but “if systolic drops below 90, give a 500 mL bolus and call me.”

Section 4Corrections, Abbreviations and the Copy-Forward Problem

Fixing what is already written

You will make errors in the record. The professional skill is not avoiding them; it is correcting them in a way that preserves the original and shows the correction. Never obliterate. On paper, draw a single line through the entry so the original stays legible, write a brief reason, and add your initials, date and time. In an electronic record, use the system’s amendment or addendum function rather than editing text in place, because the amendment carries a timestamp and an author while a silent edit looks like concealment.

Word choice matters here more than students expect. Many risk-management departments prefer “mistaken entry” or “charted in error — wrong patient” over the bare word “error,” because in later litigation “error” can be read as an admission of a clinical mistake rather than a clerical one. Practice varies by institution and this is a genuine difference of opinion among healthcare attorneys; follow your facility’s policy, and in all cases state what was wrong and what is correct.

A late entry is legitimate and common. Document it as one. Weak: writing a 2200 assessment into the chart at 0330 as though it were written at 2200. Better: “0330 — Late entry for 2200. Patient assessed at 2200: alert, oriented x4, lungs clear, no distress. Entry delayed due to concurrent rapid response on the unit.” Both the time of the event and the time of the entry appear. That version is honest, explains the gap, and is far stronger than a backdated note that the audit trail will contradict.

Four situations come up constantly, and each has a correct move. A wrong value typed into a flowsheet gets the correction function and an explanatory line, not a silent overwrite: “Correction — 1400 BP entered as 168/94 in error; actual 118/74. Corrected 1512, D. Whitfield RN.” An entry made on the wrong patient is marked as a mistaken entry per policy and never deleted, then documented accurately in the correct chart, with the records department or supervisor notified. A colleague’s inaccurate entry is not yours to change: document your own observation, with your own time and signature, and raise the discrepancy through your supervisor rather than annotating their note. And when a patient disputes what is written, remember that United States federal privacy rules give them the right to request an amendment — the original entry is not deleted, and if the request is denied the patient may file a statement of disagreement that travels with the record. In none of these cases does the fix involve making something disappear.

Abbreviations, decimals and dose

A small set of writing conventions in medication documentation exists purely because people have died. The Joint Commission maintains a minimum do-not-use list that applies to handwritten entries, free-text computer entry and pre-printed forms, and the Institute for Safe Medication Practices publishes a longer list of error-prone abbreviations, symbols and dose designations. Two conventions deserve to be memorized cold. Never write a trailing zero after a decimal — “1.0 mg” read without the decimal becomes 10 mg. Always write a leading zero before a decimal less than one — “.5 mg” becomes 5 mg, a tenfold overdose.

Do not treat the list as trivia to pass an exam. Treat it as a proofreading pass you run on anything you write that contains a number and a unit. Read the dose aloud. If it can be misheard, rewrite it.

Copy-forward, templates and note bloat

Copy-forward (also called copy-paste or cloning) is the practice of carrying yesterday’s note into today’s. It saves real time and it propagates real errors. One widely cited analysis of inpatient progress notes in a large academic system found that only about eighteen percent of note text had been manually entered by the author; the remainder was copied or imported. The clinical consequence is the fossil: a problem list that still says “day 2 post-op” on day nine, an allergy that was ruled out three admissions ago, a line about a chest tube that came out last Thursday.

Templates and auto-population create a second problem, sometimes called note bloat: a four-page document in which the reader must hunt for the two sentences of original thought. When every note contains every lab value, no note emphasizes anything. Some institutions have responded by adopting APSO ordering, by restricting auto-import of results into the narrative, or by limiting copy-forward for assessment and plan sections specifically.

The individual habits are simple and worth building now, before the shortcuts become reflex. Copy structure, not conclusions. Never carry forward an assessment you have not re-formed today. After pasting, read every line and delete anything you did not personally verify this shift — if you would not testify to it, it should not be in your note under your name. And when you use a template with checkboxes, make sure the narrative and the boxes agree; a note stating “patient ambulating independently” alongside a flowsheet documenting bed rest is the internal contradiction that ends a legal defense.

Section 5Writing to Patients, Families and the Safety System

The patient is now a reader

The most consequential change in clinical writing this decade is that patients read the notes. In the United States, information-blocking provisions implemented under the 21st Century Cures Act have, since April 2021, prohibited practices that delay a patient’s access to their own records; in practice most clinical notes and test results now post to the portal as soon as they are signed. The exceptions are narrow — psychotherapy notes, information compiled for legal proceedings, and cases meeting a specific harm exception. Practically, this means the person you are writing about may read your assessment before you have spoken to them.

The advice that follows is not “soften everything.” Clinical honesty is still the obligation, and hedging a serious finding to spare feelings is its own harm. What changes is precision and tone. Write findings that are true and specific rather than labels that are vague and loaded. “Patient is obese” can become “BMI 34; discussed weight and activity, patient interested in referral to nutrition.” “Poor historian” — a phrase that blames the patient for a difficult history — can become “history limited by short-term memory difficulty; corroborated with daughter by phone.” Both versions carry the same clinical content. Only one damages the relationship you need for the next visit.

Anticipate the reading, too. If you order a test that may return an alarming result before you can call, say so out loud and document that you did: “Explained that the CT result will appear in the portal, possibly before I can reach her; agreed I will call by end of day regardless.” That one sentence prevents a large fraction of distressed portal messages.

Discharge instructions that survive the parking lot

Discharge instructions are the highest-stakes patient-facing document most clinicians write, and they are usually written at a reading level the recipient cannot use while frightened, in pain and on hydrocodone. The working targets are widely taught: aim for roughly a sixth- to eighth-grade reading level, use short sentences, put the action first, and name the specific thing the person must do. AHRQ’s health-literacy guidance recommends treating limited literacy as a universal precaution — you cannot tell by looking who will struggle, so write for everyone.

Three moves fix most instruction sheets. First, convert clinical categories into observable events: not “signs of infection,” but the specific things to look at, with numbers. Second, put the trigger before the action, because a stressed reader scans for their own situation: “If your temperature is 100.4 degrees or higher, call us” is easier to use than “Call us in the event of a fever.” Third, close with teach-back — ask the patient to explain the plan in their own words, framed as a check on your own clarity: “I want to make sure I explained this well. Tell me how you’ll take the water pill tomorrow.” Then document what they said, not merely that you educated them.

Safety reports, messages and everything beside the chart

An incident report — also called an occurrence, event or safety report — is a separate administrative document created so the organization can learn from an event. It is not part of the clinical record, and this distinction has practical consequences. Write only facts: what happened, when, who was present, what was observed, what was done. Leave out blame, speculation about cause, opinions about staffing, and any characterization of the event as an error. Those belong in the review process, not the initial report.

Critically, do not reference the incident report in the patient’s chart. Charting “incident report completed” can, in many jurisdictions, be used to argue that the report was incorporated into the medical record and therefore is discoverable, potentially weakening whatever protection it had. Note that the strength of that protection genuinely varies — peer-review and quality-improvement privileges differ by state and by whether the work falls under a federally listed Patient Safety Organization, and courts have reached different conclusions. The safe, universal practice is simple: document the patient’s condition and care in the chart, and document the event in the safety system, and never let the two cross-reference each other.

The same discipline applies to secure messages, texts to colleagues and portal replies. Write every one as if it will be printed and attached to the chart, because much of it can be. Weak: “This is the third time pharmacy has screwed this up, unbelievable.” Better: “The 1400 vancomycin dose has not arrived on the unit; this is the third delayed dose for this patient in 24 hours. Requesting a status update and escalation to the pharmacy supervisor.” Same frustration, same urgency, no sentence you would regret seeing on a screen in a deposition. Chapter 10 covers the broader legal exposure of workplace writing; the clinical version of that lesson is that in healthcare, your informal writing lives in a regulated system and rarely disappears.

Words worth knowing