China medical assistance for global mobility programs

Programme entry and eligibility

Define who may open a case, which China cities and family members are within scope, and where employees find the emergency or non-urgent channel. Do not promise local coverage everywhere or a response time that has not been contracted. Keep a separate clinical emergency pathway under local services.

Interface with insurance and employer

The mobility team may manage relocation while a TPA or insurer decides benefit, GOP and claims. State which party authorises hospital deposits, interpretation, ambulance or repatriation. An employer may elect to fund an uncovered component; that decision should be documented rather than inferred from a broad duty-of-care statement.

Local service catalogue with conditions

Describe the tasks that may be coordinated—hospital appointment, records, interpreter, ground handover or return travel planning—and the conditions for each. Hospitals decide acceptance and suppliers confirm availability. A programme playbook should show who to call and what data to collect, not a guaranteed list of treatment outcomes.

Case feedback and privacy

Agree what operational milestones the mobility manager receives, what clinical information remains with authorised care teams and how a case is closed. Track repeated process gaps without turning the public site into a patient database. A named case owner can improve handover between time zones.

Build an intake that routes the right case

A mobility programme may cover assignees, dependants and travellers under different benefits. Its first questions should distinguish emergency clinical care, non-urgent appointment help, hospital discharge, a medical ground leg and cross-border return. State who can open a case after hours, which insurer or TPA is contacted and where employee consent is captured. A single generic “medical support” button without escalation ownership can delay a local decision. Programme documentation should show conditional service pathways rather than promise that every city or hospital has identical availability.

Learn from completed cases

After a case, review whether the employee found the right channel, whether insurer and employer authorisations were clear, and whether local hospital or transport contacts received sufficient information. Aggregate process lessons without using patient histories as public marketing examples. A programme owner can update approval matrices and multilingual guidance, while each new patient’s acceptance, cost and clinical needs still require case-level confirmation. If the organisation changes insurer or assistance contractor, update contacts and GOP instructions before reusing the playbook. The coordinator’s remit is local execution and communication, not benefit design or claim adjudication.

Decision pathway

First define programme boundaries and decision owners; then test the intake with a specific hypothetical route or anonymised service scenario. For a live patient, obtain consent and make separate case-level acceptance and funding decisions.

Information for a useful first enquiry

Company programme owner, eligible population and cities, existing insurer/TPA contacts, intended services, approval matrix, data-sharing rules and case reporting needs.

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