How to Choose an EMR for Your YAKAP Clinic: A 10-Point Checklist

Choose an EMR by verifying five things in order: it appears on PhilHealth's certified list, it covers the full YAKAP workflow (FPE, PCU, eKAS, ePresS), it automates XML claims end-to-end, it commits to real support and training in writing, and it publishes its price. Everything else on this checklist protects you from the failure modes clinics hit after signing.

The stakes are set by regulation, not marketing. PhilHealth Advisory No. 2026-0038 confirms that all YAKAP Clinics are required to transition to a PhilHealth-certified EMR service provider, with eKonsulta remaining operational only until December 31, 2026 for clinics that have not finished migrating. Pick wrong, and you repeat the migration under deadline pressure — see our December 2026 deadline guide.

1. Is the vendor on PhilHealth's certified list?

This is the only non-negotiable item: if the vendor is not on the official PhilHealth Certified Service Providers page, stop evaluating. That page listed 29 certified YAKAP 1.1 EMR providers as of July 8, 2026, each with a certification number and date. Ask the vendor for their exact certificate number and match it against the list yourself.

Certification is not new — PhilHealth Advisory No. 2016-0040 established the validation regime in 2016 and stopped re-accrediting primary-care providers without a validated EMR from January 1, 2017. Note also that you must choose exactly one validated EMR for your facility. How validation works is covered in our certification explainer.

2. Does it cover the full YAKAP workflow, not just claims?

The EMR must handle the entire encounter chain that PhilHealth audits: PCU liveness check, First Patient Encounter (FPE), Digital YES empanelment, SOAP consultation, and the output documents. Under PhilHealth Circular No. 2025-0017, clinics must run the PCU on beneficiaries before the FPE and before every consultation, and PCU logs serve as the basis for capitation payment validation and fraud monitoring.

Specifically verify the software supports:

PCU capture — recording the transaction number and result for every check, plus the required photo/screen capture of the verification result while PCU–YAKAP integration is pending.
FPE encoding — the FPE is not a medical consultation; it is its own data-collection event with its own XML.
Digital YES — since PhilHealth Advisory No. 2026-0029, the Digital YES via the HCI Portal is the required platform for empanelment, and SAP 1 payment requires the YES, a successful PCU liveness check with transaction number, and uploaded FPE XML.
eKAS and ePresS generation — per Annex H of PC 2024-0013, the eKAS is the proof of availment of services and the ePresS the proof of availment of medicines, generated for every encounter.

3. How automated are claims, really?

The right answer: the EMR builds the encrypted XML, validates it against PhilHealth's web service, submits it, and stores the transmittal number — without you touching a file. YAKAP claims run on XML uploaded against a validating web service; files that fail validation must be corrected and re-uploaded, as documented in PhilHealth Advisory No. 2023-0003. Each consultation gets one transmittal number, and PhilHealth rejects duplicate uploads. PA 2026-0038 is blunt: only complete and accurate claims are validated and processed. The mechanics are unpacked in How YAKAP claims actually work.

4. Will it migrate your eKonsulta data — and handle the hard cutover?

Migration is a one-way door: when PhilHealth issues a cipher key to your new certified EMR provider, your eKonsulta cipher key is automatically deactivated, so data must be exported first. PhilHealth Advisory No. 2025-0077 made data migration the clinic's obligation with assistance expected from the chosen provider, and warned that non-compliance may directly affect processing of your Statement of Accounts Payable. Ask the vendor exactly which eKonsulta exports (XML, masterlist) they import, and how long it takes. Full steps in the eKonsulta migration guide.

5. Does it track your capitation money?

YAKAP capitation is P1,700 per registered beneficiary per year under PhilHealth Circular No. 2024-0013, split 40% on completed FPEs (P680) and 60% as a performance tranche tied to encoded consultations, labs, and prescriptions. A good EMR shows you, per beneficiary: FPE done or not, consultations logged, and which performance indicators you are hitting. PC 2025-0017's retention rule makes this existential — beneficiaries with an FPE plus at least one consultation are retained in next year's first-tranche count; those without an FPE are not.

6. What happens when the internet drops?

The vendor must have a documented answer, because the regulatory duty is theirs: Advisory 2016-0040 requires EMR providers to assist clinics in securely transmitting data during connectivity failures. This matters in the Philippines — one in five barangays has no internet service provider per the DICT digital infrastructure policy note, even as PA 2026-0038 lists reliable 24/7 connectivity among YAKAP's digitalization requirements.

7. Is it compliant with the Data Privacy Act?

Health records are sensitive personal information under Republic Act No. 10173, its most protected category, and unauthorized processing carries 3–6 years' imprisonment and fines up to P4,000,000. Ask about encryption at rest and in transit, access controls per role, audit logs, and breach-notification support. Remember: the clinic, not the vendor, is the personal information controller PhilHealth and the NPC will look at.

8. Is there a written MOA and SLA?

Advisory 2016-0040 requires a MOA and a Service Level Agreement covering uptime, mean time between failures, mean time to repair, and fault-reporting responsibility. If a vendor cannot produce an SLA template with actual numbers, that tells you how support will go.

9. How concrete are support and training?

Look for named commitments: onboarding duration, training for reception and physicians separately, Filipino-language support channels, and response-time targets in the SLA. Competitor migration guides estimate roughly a month of staff training — budget for it, and make the vendor own it.

10. Is pricing published and predictable?

Most certified vendors publish no prices at all, and cost is a live controversy — in March 2026, private hospital group PHAPI cited EMR costs of close to P400,000 per facility and called the requirement "coercive and unfair," per Philstar's reporting. Demand a written quote covering setup, per-user or per-claim fees, migration, training, and what happens to your data if you leave. Weigh it against what YAKAP pays — see how YAKAP clinics get paid.

Scoring the checklist

Treat items 1–3 as pass/fail, items 4–7 as high-risk, and items 8–10 as negotiation levers. Any vendor failing certification, workflow coverage, or claims automation is disqualified regardless of price.

How RecordKo approaches this checklist

RecordKo is built for YAKAP end-to-end and designed for the certified-EMR era: PCU liveness capture with transaction numbers and PDFs at registration and every consultation, a reception-to-doctor FPE and SOAP workflow, on-the-fly eKAS and ePresS generation, encrypted XML claims with validation and transmittal tracking, capitation and performance-indicator dashboards, and eKonsulta XML batch import for migration. Ask us the ten questions above — including price — and we will answer in writing.

Book a demo ↗