How PhilHealth Certifies an EMR: The Validation Process Explained

PhilHealth certifies an EMR by putting the software through a formal validation process: the vendor must prove its system can produce complete, accurate, correctly structured claims data — encrypted XML files that pass PhilHealth's own server-side validation — and support the required clinic workflows before any clinic is allowed to use it for YAKAP. Only providers that pass appear on the official Certified Service Providers list, and every YAKAP clinic is now required to use one of them.

What "certification" actually means

Certification means PhilHealth has tested the software, not the clinic. The clinic still gets accredited separately; the EMR vendor separately proves that its system speaks PhilHealth's language correctly. PhilHealth Advisory No. 2026-0038 states plainly that all YAKAP Clinics "are required to transition to a PhilHealth-certified Electronic Medical Record (EMR) service provider," and points clinics to the CSP page as the authoritative registry.

That registry is concrete: as of July 8, 2026 it listed 29 certified YAKAP 1.1 EMR providers (and 38 certified eClaims 3.0 providers as of May 28, 2026), each with a certification number and certification date. Certificates follow a numbered per-provider format, issued individually to each vendor. When a vendor claims to be "PhilHealth-ready," ask for that number and check it against the official list.

Where the process came from: the 2016-0040 lineage

The validation regime is not new — it dates to PhilHealth Advisory No. 2016-0040, which required Primary Care Benefit providers to engage EMR providers whose software "passed the validation of the Joint DOH and PhilHealth validation team." Key precedents set in 2016 still shape the rules today:

Accreditation tied to EMR use. From January 1, 2017, PhilHealth would no longer re-accredit primary-care providers that did not use a validated EMR. Today's mirror: newly accredited YAKAP clinics from CY 2026 must engage an EMR provider as an accreditation requirement, per Advisory 2025-0077.
One system per facility. Providers had to choose exactly one validated EMR for their facility.
Six pioneer systems. The first validated batch was iClinicSys (DOH), CHITS (UP-NTHC), Seg-RHIS, eHatid LGU, SHINE OS+, and WAH-EHR.
Contracts and uptime. Clinics had to sign a MOA and an SLA with the vendor covering uptime, mean time between failures, mean time to repair, and fault reporting — still a sharp checklist item when evaluating vendors.
Data privacy. Clinics had to obtain signed Informed Consent Forms under RA 10173 and keep them for audit.
Connectivity fallback. EMR providers were required to help clinics securely submit data during connectivity failures — the regulatory root of offline and store-and-forward support.

The program itself has been renamed repeatedly — PCB1, Expanded Primary Care Benefit, Tsekap, Konsulta, and now YAKAP, per PhilHealth Circular No. 2025-0017 — but the certification logic has been continuous for a decade.

What PhilHealth tests during validation

Validation centers on whether the EMR can produce claims and records that PhilHealth's systems accept without manual repair. Based on the published mechanics, the tested surface includes:

XML claim generation and validation. YAKAP claims are encrypted XML files validated then submitted to PhilHealth; each consultation gets one transmittal number, and duplicate uploads of the same consultation are rejected. Advisory 2023-0003 shows the server side of this: XML files that fail validation (for example, "No dependent record found" or pediatric Z-score checks for ages 0–60 months) must be corrected and re-uploaded.
Web-service integration. The Konsulta/YAKAP web service exposes named service methods that EMRs must call correctly — 2023-0003 references methods like isATCValid for validating Authorization Transaction Codes.
Required documents. The eKAS (proof of availment of services) and ePresS (proof of availment of medicines) must be generated for every patient encounter, per Annex H of PC 2024-0013.
Identity and empanelment workflows. PC 2025-0017 requires a PCU liveness check before the First Patient Encounter and before every consultation, with PCU logs serving as the basis for capitation payment validation and fraud monitoring. Since May 5, 2026, the Digital YES is the required empanelment platform, where a second PCU liveness check serves as the patient's digital signature.
Real-time submission capacity. PC 2025-0017's Annex I requires clinics to have the technological capacity for registrations and FPEs to reflect in PhilHealth systems in real time — which the EMR must actually deliver.

For a deeper walkthrough of the claims pipeline itself, see How YAKAP Claims Actually Work: XML, Validation, and Transmittals.

Why the certificate matters when you choose software

The certificate is the difference between getting paid and not. Advisory 2026-0038 is explicit: "Only complete and accurate claims are validated and processed." Concretely:

Payment prerequisites run through the EMR. SAP 1 (first-tranche) payment requires the YES, a successful PCU liveness check with a transaction number, and a conducted FPE with uploaded FPE XML data (Advisory 2026-0029). YAKAP capitation is P1,700 per registered patient per year under PhilHealth Circular 2024-0013, split 40% on FPE (P680, paid monthly) and 60% on performance the following year — an uncertified or broken EMR blocks both tranches.
Non-compliance has teeth. Failing to migrate off eKonsulta constitutes non-compliance under Section V.A of PC 2025-0017 and can directly affect processing of the clinic's Statement of Accounts Payable (Advisory 2025-0077).
The deadline is real. eKonsulta's shutdown was deferred once, but only to December 31, 2026 (Advisory 2026-0038). See December 2026: The Certified-EMR Deadline Every YAKAP Clinic Must Meet and, if you are still on eKonsulta, our migration guide.

When comparing vendors, verify the certificate number on the CSP page, ask how the system handles XML validation failures, and confirm PCU, eKAS/ePresS, and Digital YES support — our 10-point EMR checklist covers the full evaluation.

How RecordKo handles the certified-EMR era

RecordKo is built for YAKAP end-to-end: FPE and SOAP consultation workflows, PCU liveness-check capture with transaction numbers and exportable logs, eKAS and ePresS generation on every encounter, encrypted XML claim building with per-consultation transmittal tracking, capitation and performance-indicator dashboards, and eKonsulta XML import so migrating clinics keep their patient history. If you are evaluating EMRs against PhilHealth's validation requirements, see it live.

Book a demo ↗