A corporate medical evacuation policy for Indonesia needs six fixed elements: clear trigger criteria, a named decision-maker with 24-hour authority, a site register with GPS and airstrip data, insurer and assistance-company contacts, a written activation path to a coordination desk, and drills with measurable KPIs — not a document that assumes a helicopter is available at night.
What Should Trigger an Evacuation Call-Out?
A policy that leaves “serious injury” undefined puts the decision on whoever is on shift when it happens. Better documents set clinical and operational triggers in plain language: loss of consciousness, uncontrolled bleeding, suspected spinal or head trauma, chest pain with cardiac history, or any condition the site medic cannot stabilize within a stated window.
For remote operations in Papua, Kalimantan mining sites, or Raja Ampat liveaboards, the trigger list should also cover distance: if the nearest adequate hospital is more than a set number of hours away by road or boat, that alone can turn a moderate injury into a medevac case.
Decree 882/Menkes/SK/X/2009 sets out the underlying medical evacuation guidelines and the fit-to-fly concept used by flight doctors and air nurses in Indonesia. A corporate policy does not need to reproduce the clinical detail, but it should point staff to the same standard so a field decision is not made in isolation.
Who Holds the Authority to Activate Evacuation?
This is the section most policies skip, and it is the one that costs the most time during an actual incident. A workable policy names a primary decision-maker, a backup, and the site supervisor who can act if neither is reachable within 15 minutes. It should state explicitly that authority does not require sign-off from a head office asleep in a different time zone.
| Policy Section | What It Must Specify | Common Gap |
|---|---|---|
| Trigger Criteria | Clinical and distance-based thresholds | Vague terms like “serious injury” |
| Decision Authority | Primary + backup decision-maker, response window | No named person, assumes HQ sign-off |
| Site Register | GPS coordinates, nearest airstrip/helipad, road/boat time to hospital | Register not updated after site changes |
| Insurer & Assistance Contacts | Policy numbers, 24-hour lines, pre-authorization steps | Contacts filed with HR, not with site staff |
| Coordination Desk Activation | Who calls the desk, what information to give first | No single external contact point |
| Family Communication | Who calls the family, in what order, what is disclosed | Left to whoever is free |
| Drill Calendar | Frequency, scenario rotation, night-case runs | Drills only cover daytime scenarios |
| KPI Dashboard | Response time, activation time, review cadence | No KPIs tracked at all |
| Legal & Compliance Notes | Duties under Health Law 17/2023, licensing basis | Not cross-referenced to current law |
| Document Owner & Review Date | Named owner, annual review trigger | Policy untouched for years |
What Site and Location Data Does the Policy Need?
Each work site needs its own register entry: exact coordinates, the nearest airstrip or helipad and its operating hours, and the realistic travel time to the nearest hospital capable of handling trauma.
For Papua sites this often means Timika, Jayapura-Sentani, Merauke, or Wamena as the nearest air link. For Kalimantan operations it is typically Balikpapan, Banjarmasin, Samarinda, or Pontianak. Mentawai sites route through Padang or Tuapejat.
Indonesia has multiple private and government medevac providers but, according to the 2024 readiness study on Indonesian air medical evacuation, no single integrated national coordination authority and no regulation that definitively governs stakeholder integration exist as of 2026. That is exactly why a company’s own register and contact chain matter more than assuming a provider will simply “know” the site.
Many HR and HSE teams pair this policy with a separate corporate medevac retainer arrangement, so a coordination desk is already briefed on the site register, insurer details, and escalation order before an incident happens, instead of being handed the policy for the first time mid-call. That retainer detail sits in its own document; this policy should reference it by name and review date rather than assume the reader already has it open.
How Should Insurer and Assistance-Company Liaison Work?
The policy should list, per site or per employee category, the insurer’s 24-hour line, the policy or membership number, and any pre-authorization step that must happen before an aircraft is tasked.
Where a case involves repatriation from Jakarta or Bali toward Singapore, Kuala Lumpur, Penang, Bangkok, or Australia, the insurer’s assistance company typically runs its own coordination in parallel with any on-ground desk. The policy should state who briefs whom first, so two parties are not working the same case without talking to each other.
What Is a Coordination Desk’s Role in Activation?
A coordination desk is a broker function, not a flight operator. It holds the site register, insurer contacts, and decision-authority chain on file, and it relays the case to licensed medevac and hospital-transfer providers once activated.
Juara Holding Group operates this kind of independent coordination desk — reachable via WhatsApp at 6281139414563 or bd@juaraholding.com — for corporate and expedition clients nationally and internationally. It arranges services through vetted licensed operators rather than owning aircraft or ambulances itself, and it does not hold itself out as affiliated with any single named provider.
How Should Family Communication Be Handled?
The policy should fix the order of calls: site supervisor to HR or the named decision-maker, decision-maker to the coordination desk, and a single designated person — not multiple colleagues independently — to contact the family with confirmed information only.
Unconfirmed details reaching a family before the company has verified them is one of the most common complaints in post-incident reviews. It is preventable with one paragraph naming who calls and what they are permitted to say at each stage.
What Drills and KPIs Keep the Policy Alive?
A policy that has never been drilled is a document, not a procedure. Quarterly tabletop drills and at least one full-scale drill a year, including a night scenario, expose the gap most policies have: an assumption that a helicopter is available around the clock.
Indo Jet Medic, one of several providers operating in Indonesia, states helicopter evacuation as daytime only, 06:00-18:00 local time — an operational constraint a drill will surface but a document review will not.
| KPI | Target Use | Review Frequency |
|---|---|---|
| Time from incident to decision | Flags authority gaps | Every incident |
| Time from decision to desk activation | Flags contact-chain gaps | Every incident |
| Time from activation to aircraft/vehicle tasked | Provider-dependent, tracked not guaranteed | Every incident |
| Drill completion rate | Confirms readiness, not just documentation | Quarterly |
| Register accuracy at drill | Confirms site data is current | Quarterly |
| Insurer pre-authorization time | Flags policy paperwork gaps | Annually |
What Legal Duties Apply Under Health Law 17/2023?
Health Law 17/2023 obliges health professionals and facilities to give first aid in emergencies and disasters. That is the backdrop against which a corporate policy should be written — it does not create an obligation on the company to own medevac assets, but it does mean any on-site medical staff named in the policy have a first-aid duty the policy should not contradict.
Permenkes 14/2021 governs risk-based licensing for the health sector generally, which is worth citing in the document’s legal-notes section so the policy is reviewed against current regulation rather than a version from several years back. As of 2026, subject to change, companies should treat this as a living cross-reference, not a one-time citation.
What Mistakes Do Corporate Policies Most Often Make?
The two recurring mistakes are naming no decision-maker at all — leaving the call to whoever happens to be senior on-site that day — and assuming a night helicopter evacuation is available by default, when named providers in the market state daytime-only helicopter operating windows.
A third common gap is a site register that was accurate at the project’s start but was never updated after camp relocations, new airstrips opening, or personnel changes. The document meant to save time in an emergency instead sends the first call to a contact who has not worked there in a year.
A fourth gap, specific to companies with sites in more than one region, is writing a single generic policy and assuming it covers Papua, Kalimantan, and Mentawai equally. Each region has a different nearest-airport map, a different typical response window, and different provider coverage; a policy that does not name these differences by site will read fine on paper and fail on the day it is tested.
Where a Coordination Desk Fits Before an Incident, Not Just During One
Companies that treat the coordination desk as a resource to call only after something goes wrong lose the briefing advantage a retainer-style relationship provides. A desk that already holds the current site register, insurer numbers, and named decision-makers can start relaying a case in minutes rather than spending the first call gathering information that should have been on file. Aligning the corporate policy’s document-owner review cycle with the desk’s own contact-list refresh is a simple way to keep both current at the same time, without adding a second administrative process.