FUSIC Pathway
How to write FUSIC scan notes
A practical guide to writing scan reports for the FUSIC logbook — what to include, the structure to use, and how to phrase findings clearly.
What every report should include
1
Indication
The clinical question driving the scan — why was it done?
2
Image quality
Good / acceptable / poor, with a brief reason if not good
3
Views obtained
List each view you achieved during the scan
4
Findings
Structured by view or by anatomical region
5
Conclusion
The answer to the clinical question, in plain language
6
Suggested actions
Further imaging or clinical steps — if relevant
Structure
Use the same order every time. It makes reports easier to read for whoever reviews them, and easier for you to write under time pressure.
Patient identifier (anonymised) and date
Indication
Image quality
FindingsView by view, or region by region
Conclusion + clinical significance
Recommendation for further investigationIf needed
Common pitfalls
Reporting what you didn’t actually image — stay within what the views you obtained could demonstrate
Speculating beyond the scan — a FUSIC scan is targeted, not comprehensive
Forgetting to flag image quality limitations — if views were suboptimal, say so
A conclusion that doesn’t answer the indication — your conclusion should directly answer why the scan was done
Worked example
Worked example coming soon
An anonymised worked example will be added here — indication, findings, conclusion — drawn from a recent training scan.