Switching EMRs Without Losing Your YAKAP Data: A Safe Migration Guide

You can switch EMRs without losing YAKAP data if you follow the order PhilHealth's own guidance implies: export everything from your current system first, move it into the new EMR through the XML batch import path, protect your empanelment and masterlist records during the switch, and only then request the cipher-key handover that makes the new system live.

Why Clinics Are Switching Right Now

Clinics are switching because eKonsulta is being retired and every YAKAP clinic must integrate with a PhilHealth-certified EMR provider to keep getting paid. PhilHealth Advisory No. 2025-0077 ordered eKonsulta decommissioned, and PhilHealth Advisory No. 2026-0038, signed June 30, 2026, extended eKonsulta's operation to December 31, 2026 for clinics still mid-migration — a firm final date, not a reprieve. As PhilHealth put it when defending the mandate, "This is not a checkbox requirement. It is how PhilHealth ensures every Filipino who walks into a YAKAP clinic gets the care they deserve" (GMA News).

Clinics already on a paid EMR also switch when a vendor stalls on features, support, or pricing. Either way, the risk is the same: losing patient history, empanelment status, or capitation continuity mid-transition. If you haven't picked a system yet, see Best EMR for YAKAP Clinics (2026 Guide) and 15 Questions to Ask Any EMR Vendor Before You Sign.

Step 1: Export Your Data First

The first move is exporting your existing data, not negotiating with the new vendor. Under PhilHealth Advisory No. 2025-0077, clinics still on eKonsulta already do this daily as a matter of compliance: encode all data after each encounter, download the XML file, and submit it via the HCI Portal or your Local Health Insurance Office (LHIO). Every downloaded XML file is a portable record of a real encounter — your migration asset.

Before committing to a new EMR, confirm you can pull:

Patient demographics and full consultation history, not just PhilHealth-bound fields
Every submitted encounter's XML file, not just a summary report
Your empanelment/masterlist data — the beneficiaries tied to your clinic
PCU liveness-check logs (transaction numbers, results, timestamps) tied to FPEs and consultations

The advisory itself notes migration assistance "can be extended by their selected EMR provider" — a real vendor obligation, not a nice-to-have. Ask any vendor to demonstrate export before you sign, not after.

Step 2: Use the XML Batch Import Path

The practical route into a new EMR is XML batch import, not manual re-encoding. This is an established pattern among certified providers — vendors including mWell publicly describe migration support built around eKonsulta XML import and masterlist uploads. Batch import preserves the structured data PhilHealth validates (diagnoses, prescriptions, lab orders) and avoids transcription errors.

A safe batch-import process:

Export in bulk — pull every XML file for the full date range, not a spot sample.
Validate before importing — run files through the new system's validation logic to catch malformed records early.
Cross-check counts — imported consultations should match your eKonsulta submission log exactly; missing records mean missing FPE credit.
Spot-check patients — confirm vitals, diagnoses, and prescriptions render correctly, not just that a file "imported."

See 12 EMR Features That Actually Matter for YAKAP Clinics for what else to look for.

Step 3: Protect Empanelment and Masterlist Continuity

Empanelment continuity is where clinics most often lose ground, because it isn't stored the same way consultation data is. Under PhilHealth Circular No. 2025-0017, beneficiaries with at least one consultation are retained in next year's first-tranche FPE count; those with FPE but no follow-up consultation are retained but must consult or redo FPE; those who merely selected your clinic without completing FPE are not retained. A migration that drops FPE-consultation linkage can silently cost you retained beneficiaries — and capitation.

Since PhilHealth Advisory No. 2026-0029 (May 5, 2026), the digital YAKAP Empanelment Slip (YES) via the HCI Portal is the required platform for empanelment, and SAP 1 payment requires a successful PCU liveness check, a conducted FPE with uploaded XML data, and the signed YES together. Confirm your new EMR can preserve each beneficiary's FPE date and history, reference the original PCU transaction numbers, and reproduce signed MCA/YES records for beneficiaries already empaneled.

Empaneled beneficiaries can only formally transfer clinics in the fourth quarter of the year — a migration isn't a transfer, but your masterlist import must map cleanly onto your existing panel. See how YAKAP clinics get paid for why this linkage drives your P1,700-per-beneficiary capitation.

Step 4: Plan the Cutover

The technical cutover is a hard switch, so your "parallel run" has to happen before it, not during it. Once PhilHealth issues a new cipher key to your chosen provider, the old eKonsulta cipher key is killed immediately — as one certified vendor's migration guide puts it, "There is no parallel run" at the submission layer (SeriousMD).

The safe version of a "parallel run" is a shadow period before the cipher-key request: keep eKonsulta as your system of record while you stand up the new EMR, import historical XML, train staff, and reconcile a sample of encounters between the two systems. A realistic sequence:

Select and declare your certified provider (the conforme process under Advisory 2025-0077)
Stand up the new EMR and complete XML batch + masterlist import
Run new encounters in both systems for 1–2 weeks and compare outputs
Train reception, doctors, and pharmacy on the new system during the shadow period
Request the cipher-key transfer only once reconciliation is clean
Submit exclusively through the new EMR from that point forward

Build in buffer before December 31, 2026 — don't schedule the cipher-key request for the last week of the year.

What to Ask Vendors Before You Commit

Ask whether a prospective vendor's migration support covers export, not just import. Confirm they're on PhilHealth's official certified service provider list under YAKAP 1.1, ask for their XML validation process, and ask what happens to your data if you leave later — a vendor unwilling to guarantee export on the way out is a warning sign on the way in. See 15 Questions to Ask Any EMR Vendor Before You Sign and How Much Does an EMR Cost in the Philippines? for cost comparisons.

How RecordKo Handles Migration

RecordKo is built for YAKAP end-to-end, with migration as a first-class workflow. It supports XML batch upload from other EMR systems, including eKonsulta exports, plus batch XML download of your own records, so you keep full ownership of every encounter you've submitted. PCU liveness-check results and transaction numbers are captured directly in the FPE and consultation flow, eKAS and ePresS generate automatically from the same consultation data, and capitation tracking ties FPE and performance-tranche numbers back to your actual panel — so empanelment continuity isn't something you reconstruct by hand after cutover.

Book a demo ↗