eKonsulta Is Shutting Down: Your Clinic Migration Guide (July 2026)

Yes — PhilHealth is permanently shutting down the eKonsulta system, and every YAKAP clinic must move to a PhilHealth-certified EMR. The original shutdown date of July 1, 2026 under PhilHealth Advisory No. 2025-0077 has been deferred: under PhilHealth Advisory No. 2026-0038, eKonsulta stays operational only until December 31, 2026 for clinics that have not finished migrating. That extension is breathing room, not a reprieve — the mandate itself did not change.

The shutdown timeline: what was announced, and what changed

The decommissioning was ordered in December 2025 and softened once in June 2026 — the end state is unchanged. Here is the full sequence:

December 23, 2025 — PhilHealth signs Advisory No. 2025-0077, ordering eKonsulta ("eKon") decommissioned by July 1, 2026 as part of YAKAP improvements.
April 1, 2026 — deadline for eKonsulta clinics to declare their chosen EMR service provider by submitting a conforme (Annex A) to their Local Health Insurance Office (LHIO).
April to June 2026 — the official window to migrate all patient data from eKonsulta to the new EMR provider, with hands-on assistance expected from that provider.
June 30, 2026 — Advisory No. 2026-0038 defers the shutdown: eKonsulta remains operational until December 31, 2026 for clinics still mid-migration. Philstar reported the deferral on July 3.

Why kill it at all? As BusinessMirror reported, PhilHealth says eKonsulta was a temporary mechanism that can no longer support YAKAP's data-processing needs — real-time electronic validation, interoperability, and faster claims processing. New clinics don't get a grace period either: for facilities accredited as YAKAP clinics from CY 2026 onward, engaging an EMR service provider is part of the accreditation requirements. We track the endgame in detail in December 2026: The Certified-EMR Deadline Every YAKAP Clinic Must Meet.

What happens to your existing data and empanelments?

Your empanelments survive the migration — if you migrate properly. Empanelment is the formal care relationship established after the First Patient Encounter (FPE) under PhilHealth Circular No. 2025-0017, and it lives in PhilHealth's systems, not inside eKonsulta. But the records that prove your performance — encoded consultations, prescriptions, lab results — sit in eKonsulta until you move them, and they directly determine money:

Beneficiaries with an FPE plus at least one consultation are retained in your FPE count for next year's first tranche. Selection without an FPE is not retained.
The second (60%) tranche of the P1,700-per-patient capitation is tied to encoded consultations, labs and prescriptions under PhilHealth Circular No. 2024-0013 — records you cannot afford to strand in a dead system.
Failure to migrate is non-compliance under Section V.A of PC 2025-0017 and, per Advisory 2025-0077, may directly affect processing of your Statement of Accounts Payable (SAP).

One critical operational detail: treat the cutover as one-way. Once PhilHealth issues credentials (the cipher key) to your new certified EMR provider, plan on your eKonsulta access ending — export everything from eKonsulta *before* you trigger the switch. There is no parallel-running safety net.

Migration steps: how to move without breaking anything

The safe sequence is declare, export, import, verify, then cut over. Concretely:

Pick a certified provider. Only EMRs on PhilHealth's Certified Service Providers list count — 29 YAKAP 1.1-certified providers were listed as of July 8, 2026. Our 10-point EMR checklist covers how to compare them.
File your declaration. If you missed the April 1 conforme deadline, coordinate with your LHIO or PhilHealth Regional Office for the late-declaration paperwork rather than waiting.
Export everything from eKonsulta first. Patient records, consultation XMLs, and your Konsulta Registration Masterlist (downloadable via the HCI Portal, per Advisory 2023-0003).
Bulk-import into the new EMR. See the XML/CSV section below.
Verify before cutover. Spot-check patient counts against the masterlist, confirm FPE records and consultation histories imported, and run a live claim end-to-end.
Train staff, then switch. Budget real training time — reception, doctors, and whoever handles claims all touch the new workflow.

The XML/CSV bulk import option

You do not need to re-encode patients by hand — YAKAP already runs on structured files, and a good EMR ingests them in bulk. Two import paths matter:

XML import. Every eKonsulta consultation exists as an XML claim file — the same files clinics upload through the HCI Portal, validated server-side by PhilHealth (per Advisory 2023-0003). A capable EMR imports these batch XMLs directly, reconstructing enlistments and consultation histories. We break down the file mechanics in How YAKAP Claims Actually Work.
Masterlist ingest. The Konsulta Registration Masterlist download gives you the authoritative roster of registered beneficiaries; importing it lets you reconcile your migrated patient list against what PhilHealth actually has on record.

Ask any prospective vendor to demonstrate both — with your files, not a demo dataset — before you sign.

What you must keep doing while still on eKonsulta

Until your cutover, PhilHealth expects business as usual, daily. Per Advisory 2025-0077 and Advisory 2026-0038:

Encode all data after each patient encounter, download the XML file, and submit it via the HCI Portal or your LHIO — after every transaction. Only complete and accurate claims are validated and processed.
Run PCU liveness checks after every patient encounter, and issue the YAKAP Empanelment Slip (YES) after the FPE. Since May 5, 2026, the Digital YES via the HCI Portal is the required platform for empanelment transactions.
Remember the broader digitalization bar you are migrating toward: full PCU utilization, Digital YES, certified-EMR integration, and reliable 24/7 internet connectivity.

How RecordKo handles the eKonsulta migration

RecordKo is built for YAKAP end-to-end and designed for the certified-EMR era — including the messy middle of migration. It bulk-imports eKonsulta XML batch files and ingests your Konsulta Registration Masterlist so enlistments and consultation histories carry over intact; from day one it runs the full workflow PhilHealth now expects: PCU liveness capture with transaction numbers at registration and every consultation, FPE and SOAP encoding, eKAS/ePresS generation, encrypted XML claims with validation before submission, and capitation tracking so you can see your first- and second-tranche position per patient. If you are staring at a December 31 deadline, we will walk your actual export files through a test import with you.

Book a demo ↗