What a preliminary outcome can—and cannot—mean
A preliminary review is a checkpoint against the question submitted. It may be performed by an intake or international office, a records team, a coordinator, or an authorised clinical service. The three labels in this guide are planning categories that help organise a conversation; they are not a universal hospital protocol and should not be presented as a guaranteed set of outcomes.
Read the source and scope before reading the label. “Proceed” might mean that an administrative step can be scheduled; “add information” might mean a file is missing; “pause” might mean the recipient cannot continue under current conditions. None of those phrases alone establishes a diagnosis, treatment recommendation, eligibility, price, appointment, or outcome.
Proceed: turn permission into a task list
If the response says to proceed, request the exact next deliverables: named institution or department, type of visit or review, expected documents, consent steps, language support, payment conditions, and a date or trigger for the next reply. Ask whether the message is an invitation to continue coordination or an official provider decision. Save the original wording and its date.
Then assign work. The patient or authorised representative verifies facts, consent, passport and travel constraints; the coordinator can route questions and track files; the institution owns its service, clinical, scheduling, and billing decisions. A proceed status is useful only when the next owner and the condition for completion are written down.
Add information: request a precise gap
When more information is requested, ask for a numbered gap list rather than uploading a complete archive. A useful row says: file or field, acceptable format, date range, purpose, recipient, and whether it blocks the next step. Examples include a missing report page, an unreadable scan, a medication dose, a consent form, or confirmation of the intended language.
Reply with a new version and a short change note. Preserve the old submission so the reviewer can see what changed, and label patient-reported information separately from documented findings. Additional information supports the reviewer’s task; it does not guarantee that the next response will be favourable or that a clinician has reached a medical conclusion.
Pause: clarify the route and protect decisions
A pause can reflect incomplete records, unavailable service capacity, unresolved identity or consent, travel constraints, a request outside the recipient’s remit, or a need for another authority. Ask which reason applies, whether another channel is appropriate, and what event would allow the request to be reconsidered. Do not infer that a pause confirms or rules out a disease.
If the pause affects a planned trip, stop non-refundable commitments until the responsible authority gives a written update. Check insurer, travel, and local-care options independently. A coordinator may document the status and look for a permitted route; the provider, insurer, immigration authority, and patient each retain their own decision-making role.
Close with evidence and a next review date
Ask for a concise written status record containing date, reviewer or team, scope, decision category, reason, missing items, next owner, and review date. If the response came by phone, send a neutral written recap and invite correction. WHO handover guidance emphasises accurate, necessary information and clear responsibility at transitions; that principle supports a traceable administrative handoff too.
Keep the status record beside the summary, attachments, translations, and receipts. Recheck it when new reports, dates, costs, or travel conditions appear. If urgent symptoms or deterioration are involved, use local emergency services or the treating team; an administrative status cannot triage illness. The useful result is a verifiable next action, with uncertainty named rather than hidden.
