The Function of the Message

Tuesday afternoon. A 78-year-old woman on the cardiology floor, day three of admission for decompensated heart failure. Five clinicians will say something about her in the next forty-five minutes, each compressing the patient differently for a different audience.

The hospitalist on the receiving end of sign-out, around six, gets the handoff: "Mrs. M, decompensated HF on diuresis, net negative 2L today, K is 3.4 and she just got 40 mEq, recheck mag in the morning, pending echo. Watch for sudden room-air desaturation overnight; she had a brief episode at noon, resolved on her own. Call if it recurs."

The cardiology fellow gets a consult question from the medicine team: "Should we resume her metoprolol now that she's volume-down, or wait until tomorrow?"

The PCP, two days from now, will read the discharge summary: "Admitted with NYHA III decompensation in setting of medication non-adherence after spouse's hospitalization. Improved with IV diuresis. Discharged on oral regimen including resumed metoprolol at half-dose. Follow-up echo in two weeks."

The chart note for today reads differently still: "Day 3 HFrEF exacerbation, improving. Net -2L today, -6.5L cumulative. K 3.4 repleted. Brief episode of self-resolving desat at noon, no clear precipitant; will reconsider PE workup if recurs. Plan to titrate metoprolol back tomorrow. Discharge anticipated 1-2 days."

And on rounds, the attending tells the resident: "Notice she desaturated at noon. Volume is coming down but the right heart has not had time to remodel. That is why you do not restart beta-blockade until the diuresis is complete and the vitals have stabilized."

Five compressions of the same patient in the same afternoon. Each one is the right message for its job. Each one would be the wrong message in any of the other four contexts.

Compression is purpose-relative

The principle the rest of this series rests on, stated plainly: compression is purpose-relative. There is no universally optimal compression of a patient. The right summary depends on what the communication is trying to do: what decision it is supporting, what risk it is warning about, what evidence it is justifying, what concept it is teaching, what handoff of ownership it is performing.

Same patient, different functions, different compressions. And the "good" compression is judged against the function the message has to perform, not against completeness, not against brevity in the abstract, not against any other message that did a different job. This is the first move that has to land before the rest of the curriculum can mean anything. Parts 3 through 6 will operationalize the principle (at what abstraction level to start, how to order the elements, what to leave out, what to keep when in doubt). Each of those is downstream of knowing what function the message is doing.

Compression is purpose-relative because information utility is objective-relative. A fact has no intrinsic value to a clinical message. It has value only insofar as it changes the receiver's ability to act, monitor, decide, coordinate, teach, document, or reconstruct the patient state, given what the receiver is trying to do. A true fact can be high-utility, low-utility, or even negative-utility depending on context. Negative-utility facts distract, overload, mislead, and bury the active decision; including them costs the receiver attention without paying back in better action. The unit of value in a clinical message is not the fact. It is the fact's expected contribution to the receiver's objective.

The function map

Clinical communication performs at least five distinct jobs. Naming them helps see what each demands.

State transfer (handoff). The receiver is taking over care. They need to reconstruct enough of the patient to make the next decisions, in the right order, with the right thresholds for what would change the plan. The handoff demands: trajectory, outstanding work, anticipated decision points, and what to call about. It does not need the full admission history, the imaging archive, or every lab value since arrival. The clinician inheriting the patient will be making decisions in the next twelve hours, not writing a paper.

Decision support (consult question). The receiver is being asked something specific. The compression must lead with the question. The consultant's time is finite, the question is concrete, and the evidence relevant to it is a small subset of the chart. "Should we resume her metoprolol now that she is volume-down" is the right shape: bounded question, decision context implicit, the relevant variables (volume status, ejection fraction, medication tolerance) implied. The full HF history is available if the consultant wants it; the question does not require its prefiguration.

Risk warning (sign-out, escalation precaution). The receiver may need to act on a deterioration that has not happened yet. Compression here is dominated by what could go wrong and what to do. "Watch for sudden room-air desaturation; she had a brief episode at noon, resolved on her own" tells the next clinician exactly what to look for and signals what to do without the receiver having to reconstruct the reasoning. The function is anticipation, not exhaustive description.

Documentation (chart note). The future reader is unknown. Compression must preserve enough fact base for someone six months from now, possibly without context, to reconstruct what happened and why. This is the most fact-dense and slowest-reading of the functions; future readers can take their time. Numbers, dates, doses, and reasoning chains belong here in ways they do not belong in a handoff or a consult.

Teaching (rounds, attending feedback). The receiver needs to learn a pattern. The case is the vehicle. What matters in a teaching compression is what discriminates: which findings would change the diagnosis, which actions would change the trajectory, which reasoning would generalize to the next patient. The attending who says "you do not restart beta-blockade until the diuresis is complete" is teaching a rule by hanging it on one case, not summarizing the patient.

These five do not exhaust the space. Patient explanation, billing documentation, transfer of ownership across services, family communication, persuading a reluctant consultant: each is its own function with its own demands. The functions are heterogeneous, and the compression that fits one rarely fits another.

Receiver architecture

The function-matching rule is necessary but not sufficient. A message is not small in the abstract. It is small for a receiver. The same representation can be effortless for one architecture and burdensome for another, and what counts as "the smallest message" depends on which architecture is doing the decompressing.

Consider four representations of the same patient state. A chest X-ray image is information-dense; for a trained radiologist it decompresses in under a second, and for a language-only AI fluent only in text it is far more expensive to interpret. A handoff sentence like "EF 25 percent, cold and wet, rising creatinine, failed outpatient diuresis" is compact for a clinician but points at nothing for a layperson. A structured table of vitals trends is awkward for a clinician to scan mid-shift, but trivial for a database to query and trivial for a dashboard to render. A vector embedding of the patient is information-rich for a retrieval system and useless to any human reader. Same patient state, four representations, four wildly different costs depending on who is doing the work.

The total cost of a message is the sum of its transmission cost, its decoding cost, the attention it claims, the computation it requires, and the risk of error it carries. The "smallest" message is not the one with the fewest tokens or the most compact form. It is the one that minimizes total cost for a particular receiver while still carrying the information the function requires.

This matters specifically for clinical AI. The representation that is most efficient for the model to reason over is rarely the representation the clinician can act on. The representation the clinician naturally produces is rarely the one the model can index efficiently. Communication across that gap requires translation, and translation is itself a compression operation that has to be tuned to its own receiver. The system that helps does this translation work invisibly, hiding the cost on each side from the other.

What this rules out

The most common failure of clinical communication is function-mismatch. The handoff that reads like a discharge summary. The consult request that reads like a chart note. The progress note that performs anticipation work the future chart-reader cannot act on. The teaching point compressed into a one-liner so dense the trainee cannot decompose it.

A second class of failure is receiver-mismatch. The chart note written in radiology shorthand handed to a primary care reader. The vitals dashboard exported to a clinical AI that has no native handling for tabular streams. The clinical-AI output emitted in dense natural language to a clinician who is mid-procedure and cannot read prose. Each is a representation that would have been fine for a different receiver and is wrong for this one.

The dashboard a clinical AI emits at the bedside is another instance of both failures stacked. A general-purpose differential copilot that returns the same shape of output whether the clinician is signing out, ordering, asking a question, or charting is doing the same thing as a clinician who hands every audience the same paragraph. The output may be true. It will not be the right message for the job the clinician was doing when they opened the screen, and it will not be in a form the clinician can decompress at the cost they have available right then.

The operational rule

The best message is the lowest-cost sufficient representation for the receiver's objective and architecture.

Cost means total cost: transmission, storage, decoding, attention, computation, and risk of error. Sufficient means the message carries the information the receiver needs to perform the function, judged by each fact's expected contribution to that objective rather than by completeness. Receiver's architecture means the substrate that will be doing the decompression: a trained clinician, a layperson, a database, a language model, a retrieval system, a junior trainee, a senior attending. The same information can be sent in many shapes; the right shape is the one whose total cost is lowest for the receiver who will actually do the work.

This sentence is the principle the rest of the curriculum depends on. Part 3 (The Highest Accurate Abstraction) operationalizes how to pick the abstraction level once the function and receiver are known. Part 4 (The Decompression Order) operationalizes how to order the elements within that level. Part 5 (The Minimum Sufficient Message) operationalizes what to leave out for a receiver with the relevant codec. Part 6 (The Grounding Constraint) operationalizes what to keep when in doubt about the receiver's decompression. Each of those is downstream of this one: there is no universal smallest message, only the smallest one that does the job for the receiver in front of the writer.

At the bedside

The five messages about Mrs. M on Tuesday afternoon are a sign of clinical communication working as it should, not of disorganization: each compression fit to its function, each one wrong everywhere else, each one the right thing in the place it actually goes. A clinical AI that helps with any of them has to know which function it is helping with. Otherwise it will return the right shape of message for the wrong job, and the right shape for the wrong job is the same thing as the wrong message.

---

Compressed Medicine · 1. The Compression Substrate · 2. The Function of the Message · 3. The Highest Accurate Abstraction · 4. The Decompression Order · 5. The Minimum Sufficient Message · 6. The Grounding Constraint · 7. The Belief-State Object · 8. The Same Wall · 9. The Defense Architecture · 10. The Temporal Loop · 11. The Irreversible-Action Check