Medical case coordination in China for international patients

Live route version

Record sending point, operating flight, arrival point, receiver, current timings and who last approved each change.

Decision owners

Keep clinicians responsible for medical needs, carriers for carriage, facilities for acceptance and payer for authorisation.

Exception log

Capture delayed discharge, flight move, equipment mismatch and failed handover with a named escalation and resolution.

A route version prevents one change from becoming three errors

Imagine the flight moves from PVG to SHA while a vehicle remains assigned to Pudong and the receiving ward still expects the original arrival. The case coordinator should record the new flight and airport, get the transport provider’s revised acceptance, update the ward, and note who authorised additional cost. A messaging thread alone is a weak master record because different participants may read different fragments. Keep one current route and an exception log accessible to authorised teams. The coordinator reports these decisions; clinical suitability and hospital acceptance remain with their respective professionals.

Maintain one route version for all participants

The working record should identify current flight or vehicle, both endpoints, handover contacts, equipment, open decisions and the time each status was confirmed. When a flight changes, update the version first and tell every affected party which prior instruction is superseded. A driver should not receive an airport change only through an old forwarded email; a receiving ward should not be surprised by a new arrival hour. Use a decision owner for each line: clinician, carrier, receiving institution, payer or supplier. The coordinator records outcomes rather than creating those approvals.

Escalate an exception without manufacturing certainty

If the vehicle is late, the patient’s support changes or the destination bed is withdrawn, record what happened, who was contacted and the decision needed before continuing. Distinguish a supplier replacement from a medical change: the former needs operational and payer approval; the latter needs clinical reassessment and may reopen carrier acceptance. Send the family a concise status with next action and responsible person. A good handover log confirms who accepted custody of records, medication and equipment, but it should not publish patient details or imply that every contingency can be resolved immediately.

A final operational check

The version record should distinguish what is known from what is inferred: flight booked, airline medical request pending, ward release estimated, receiver accepted until a particular hour. This makes the next call obvious. If an old route is circulated after a change, explicitly withdraw it so a provider does not dispatch to the previous airport.

Decision pathway

If a dependency changes, update the shared route before instructing the next team; unresolved clinical issues return to the responsible clinician.

Information for a useful first enquiry

Case owner; route version; all segment contacts; pending approvals; support and equipment; preferred update cadence.

For detailed clinical records, use a direct authorised exchange rather than this public page.