The report confirms what the exam documented
Good documentation is part of the exam — not a clerical task that starts after the patient leaves the room[1,2]. A reliable normal exam closes four points that must speak to one another: the request's question, the scan performed on the patient, the saved images and the written report. If one of these parts does not agree with the others, the exam is weak.
The order that sustains this: understand the request; scan before photographing; save images that prove the assessment; measure when the measurement matters; and write the report without adding what was not demonstrated. This chapter closes the fundamentals module begun in how to think through an exam and assumes the B-mode from image optimization.
Before the transducer, the question
Read the request and confirm which exam will be done: is there laterality? Is the indication clear? Is there a prior exam for comparison? Then confirm the scope — an upper abdomen does not include everything a full abdomen does, a thyroid is not the same as a complete cervical region, and a Doppler may require a different protocol[1,4].
Quick checklist: correct exam; correct side; indication understood; mandatory structures listed; prior exams checked; foreseeable limitations noted.
Scan, interpret and document
Scanning is exploring the anatomy with the transducer; interpreting is understanding what that image means; documenting is saving a set of images and measurements that allows the exam to be reviewed later[1,3]. The beginner's mistake is photographing too early: they find a reasonable image, press save and move on, ending with many images and little real documentation. The teaching sequence goes from broad to specific — scan wide to understand the anatomy, focus on the mandatory structures, save representative images, measure what the protocol requires and write the findings in logical order.
The scope of the exam
The name of the exam is a commitment. Before writing "no abnormalities," ask: no abnormalities in what, exactly? In the main organ? In the protocol's mandatory structures? In the region of complaint?[4] Scope keeps the report from looking larger than the exam — and the reverse, a well-done exam poorly documented because the report does not make clear what was covered.
In practice: mentally list the mandatory structures; save the protocol's minimum images; do not turn an incidental finding into a complete exam of another territory; if you widen the assessment, record why; and if something important stayed out of scope, do not suggest it was assessed.
A well-labeled minimum image
A documentable image must be understood outside the exam room: whoever looks later should know structure, side, plane and, when present, measurement[2,3]. Use a simple rule — identify the structure, state the side when there is a side, use plane or orientation when it helps, include a legible measurement when it is part of the finding, do not crop the structure you are documenting, and keep enough context for the image to make sense. In the clinical setting, images keep identification, date and technical data per the local system; in the Academy's teaching images, patient data never enters.
Measurements when indicated
Measuring makes the report verifiable, but not every image needs a measurement and not every measurement helps[1,3]. Measure when the protocol requires it, when size defines normality, when there is follow-up, when there is a focal finding, or when you intend to use words like enlarged, dilated, thickened, reduced, bulky or mass. Avoid mixing units unnecessarily, measuring a poorly sectioned structure, saving a measurement without a comprehensible plane, and using "large" or "small" without a number when size matters.
Labels, side and plane
Good documentation uses simple words in the right place. The side must be clear — right, left or bilateral — and the plane must appear when it changes how the image reads. The structure must be named without obscure abbreviation, and, if there was a maneuver, it must be stated: compression, Valsalva, standing, rest, mobilization or sonopalpation[1,2]. Rule of thumb: if you would not understand the image six months from now, it is not well documented today.
The normal report, annotated
The normal report should be clear, short and supported — it does not need long sentences, it needs to say what was assessed and what was not found[1,5]. A reasoning model: exam title; indication; findings by structure; relevant measurements; absence of the searched-for finding; comparison with prior, if any; short conclusion. Avoid putting in the conclusion something that did not appear in the findings — in a normal exam, "normal ultrasound appearance" is usually more honest than promising absolute clinical normality.
Comparison with prior exams
Do not write "no abnormalities" if you did not see the prior exam. If a prior was available, say which was used and what changed or did not change[1,5]:
Compared with the ultrasound of MM/DD/YYYY, no significant change.
There was an increase compared with the exam of MM/DD/YYYY.
Prior exams were not available for direct comparison.
Do not invent evolution: if the prior source is not accessible, the information stays pending.
Technical limitation
Recording a technical limitation does not weaken the report — it shows honesty about the exam's reach[1,2]. The problem is writing vaguely: "poor window" says almost nothing. Better to state what limited it, where it limited, and whether that reduced diagnostic confidence, with a useful structure: probable cause; affected structure or segment; impact on interpretation; next step, if the exam did not answer. Excessive hedging gets in the way — the limitation should be precise, not a cloud of uncertainty over everything.
Vague phrases and conclusion errors
Some phrases seem safe because they are common, but they are merely vague: "within normal limits" can hide what was assessed, "no abnormalities" can ignore the indication, "poor window" does not say which structure was limited[1,5]. Replace automatic phrases with anatomical ones — the goal is not to write more, it is to write better.
The conclusion should not bring a new finding, create a diagnosis the body of the report does not support, or list unlikely possibilities just to look complete. In a normal exam it can be short:
- exam with no significant ultrasound abnormalities in the assessed structures;
- no ultrasound findings that justify the searched-for complaint, when the protocol actually assessed that complaint;
- exam within ultrasound limits for the requested scope, if that is the locally approved wording.
The central point: the conclusion must fit within the findings.
When pathology enters
Once the learner can document the normal, pathology becomes organized addition[1,4]. For a focal finding, think of precise location, two planes when applicable, measurements, echogenicity and content, margins, effect on neighboring structures, Doppler when indicated (see essential Doppler) and comparison with prior, if any. The per-exam handouts go deeper; here the bridge is enough — well-documented normal first, pathology after.
Is the exam performed the exam requested?
Was the scope respected?
Were the mandatory structures seen?
Do the saved images prove it?
Were the important measurements taken?
Does the conclusion repeat only what the findings support?
Does any technical limitation need to be recorded?
If the answer is no, go back to the matching step: scanning, image, measurement or text. A good normal report does not try to impress — it makes clear the exam was well done. Annotated real cases are in the case library.