Decide what the summary is for
A good summary answers one operational question: “Can this team tell me what documents are needed for a preliminary review?” or “Can the hospital’s international office confirm whether it handles this enquiry?” Put that question at the top, followed by the desired reply and a date. Do not ask a coordinator to make a diagnosis or select treatment on the basis of an anonymous paragraph.
Treat the summary as a handoff document with a limited audience. Name the intended recipient—international office, records team, insurer, or clinician—and state whether the attached information is for routing, document review, or an official provider decision. This prevents a useful routing note from being mistaken for a clinical conclusion or a hospital acceptance.
Choose fields that do not identify you directly
Use a code such as CASE-27 and keep the code key separately. Give an age band, country or region, preferred language, and broad timing such as “symptoms began in spring 2025”; omit name, exact birth date, passport number, address, employer, phone, email, and social-media handles. A rare occupation, exact travel date, or unusual combination of facts can identify someone indirectly.
List only context that changes the routing question: whether care is planned or urgent, the relevant body area or specialty in ordinary language, and whether a local clinician has already provided a written finding. The ICO explains that pseudonymised information can still be personal data when another person holds the key, so store that key separately and share it only through an approved process.
Build a factual timeline
Use four columns: approximate date, event, source, and confidence. For example: “2025 Q2 — imaging performed — radiology report — documented”; “2025 Q3 — medication changed — prescription list — documented”; “2026 Q1 — symptoms more limiting — patient report — not independently verified.” This makes the difference between a record and a recollection visible without adding a long narrative.
Do not quietly convert a report into your own diagnosis. Quote a short label only when necessary, preserve the report date, and write “not stated” when the document does not answer a question. If dates conflict, flag the conflict instead of averaging it away. A recipient can then request the exact report or explain which date controls the next administrative step.
Attach evidence and questions deliberately
Create an attachment index with file name, type, date, language, and purpose. A small first set might include one recent report, a medication list, and the question that the report is meant to inform; imaging files can be offered when the receiving team confirms the required format. Keep high-resolution originals and a redacted sharing copy in separate folders.
End with numbered questions that can receive specific answers: “Which team reviews this request?”, “Is a translation required?”, “Which missing document blocks the next step?”, and “Will the reply be administrative or clinical?” Avoid asking “What treatment should I have?” in an intake summary. Questions with a clear owner reduce back-and-forth and show what the recipient is actually being asked to do.
Send, record, and refresh safely
Before sending, search the sharing copy for names, identity numbers, barcodes, embedded metadata, and visible labels in scans. Use the agreed private channel, state who may access the files, and ask how long they will be retained. A code does not make a file safe for a public chat, and removing a name does not remove every route to identification.
Save the submitted text, attachment list, receipt, and reply in a dated folder. When a new report arrives, issue a new version and highlight the changed fact rather than silently replacing the old one. The summary is ready for a first review when another person can identify its purpose, evidence, unanswered question, and next owner without needing the identity key.
