RecordKo
Product

12 EMR Features That Actually Matter for YAKAP Clinics

R
RecordKo TeamJuly 20, 2026 · 6 min read

The EMR features that actually matter for YAKAP clinics are the ones tied to a specific accreditation requirement or a specific line in your capitation payment — First Patient Encounter (FPE) capture, PCU liveness checks, the Digital YAKAP Empanelment Slip (YES), eKAS/ePresS generation, and XML claims validation top the list, because each one gates either your Statement of Accounts Payable (SAP) or your ability to stay accredited at all. Everything else is nice-to-have. Below is the full ranked list, tied explicitly to the requirement or payment outcome it affects.

The 12 features, ranked by claim impact

  1. FPE encoding and workflow — The First Patient Encounter is the trigger for your 40% capitation tranche (P680 of the P1,700 per-beneficiary rate). An EMR that makes FPE fast and complete, and clearly separates it from a regular consultation, directly protects that tranche. Per PhilHealth Circular No. 2025-0017, "the FPE is not a medical consultation," and beneficiaries who selected your clinic but never got an FPE are not retained into the next calendar year.
  2. PCU liveness check capture — Required at selection, before FPE, and before every consultation. PhilHealth explicitly requires "the PCU reference number, verification result, and date/time stamp" as part of the FPE record (PC 2025-0017), and full PCU utilization is a standing Performance Commitment obligation reiterated in PA 2026-0038.
  3. Digital YES (Empanelment Slip) via HCI Portal — Since May 2026 this is "the primary and required platform for beneficiary empanelment" (PA 2026-0029), and manual/printed YES submissions now mean longer processing. An EMR that fills the YES from data you've already encoded — instead of a separate re-entry step — is a direct payment-speed feature.
  4. eKAS (Konsulta Availment Slip) generation — The services/diagnostics record PhilHealth reviews per encounter. Auto-populated from the consultation instead of hand-typed twice.
  5. ePresS (electronic prescription) — Needs physician PRC/PTR/S2 details correctly attached every time, since GAMOT medicines dispense against it.
  6. Signed Mutual Care Agreement (MCA) capture — Required for first-tranche payment on every beneficiary and re-signed annually starting January 1, 2026 (PC 2025-0017); an EMR should track MCA status per patient, not per paper folder.
  7. Encrypted XML claim generation and validation — Claims are built as encrypted XML, run through validation, then submitted; each consultation gets one transmittal number and PhilHealth rejects duplicate uploads of the same encounter. A system that catches validation errors before submission avoids returned claims.
  8. Duplicate-transmittal prevention — A quieter feature, but it's what stops a clinic from accidentally resubmitting an encounter and getting it rejected outright.
  9. Masterlist sync — Keeps your registered-beneficiary list matched against what PhilHealth has on file, which matters for both the FPE count and beneficiary retention.
  10. Capitation and tranche tracking (40/60) — Per PC 2024-0013 Annex I, 40% of the P1,700 rate pays out monthly on FPE, 60% pays the following year on year-end performance. An EMR dashboard showing panel size, FPE count, and projected tranches turns an abstract policy into a number you can plan cash flow around.
  11. GAMOT medicine list with fixed fees — 242 preparations across roughly 75 molecules under PC 2025-0013 Annex A.2, with per-item fixed fees (e.g., Amlodipine 5mg at P4.50, Metformin 500mg at P4.75) and a P20,000/year cap per beneficiary. Built-in fee lookups prevent under- or over-dispensing errors.
  12. eKonsulta XML/CSV migration — Not a clinical feature, but the one deciding whether you keep your historical FPE and consultation data at all once eKonsulta shuts down.

Why FPE and PCU sit at the top

FPE and PCU rank highest because they are the two things PhilHealth checks before it releases any money. The FPE triggers the 40% tranche; the PCU liveness check is required at three separate points (selection, FPE, and every consultation) and its reference number, result, and timestamp must be attached to the FPE record itself. As of PA 2026-0029, a successful PCU check plus uploaded FPE data are explicit prerequisites for the first SAP payment — alongside a completed YES. An EMR that treats these as an afterthought, rather than a guided step in the encounter, is asking your front desk to remember compliance steps PhilHealth is willing to withhold payment over.

Why this list exists now, not later

PhilHealth's own timeline forced the question. Advisory 2025-0077 ordered eKonsulta decommissioned, and newly accredited YAKAP clinics from CY2026 onward must engage an EMR provider as an accreditation requirement outright. The original July 1, 2026 shutdown was pushed to December 31, 2026 by Advisory 2026-0038 — but only as breathing room for clinics still migrating, not a reprieve from the requirement. PhilHealth's leadership has been blunt about why: "This is not a checkbox requirement. It is how PhilHealth ensures every Filipino who walks into a YAKAP clinic gets the care they deserve," a spokesperson said in March 2026. Around the same time, roughly 800 private hospitals were reported at risk of being barred from YAKAP over the missing EMR requirement, per Philstar. When you finally do move, treat the cutover as final: once PhilHealth issues your new certified-EMR cipher key, the old eKonsulta key is killed immediately — there's no parallel run, so your migration plan and your feature checklist need to be ready at the same time, not sequentially.

If you're still comparing options, see our guide to picking the best EMR for YAKAP clinics, our breakdown of EMR pricing in the Philippines, and the 15 questions worth asking any vendor before you sign.

How RecordKo handles this end to end

RecordKo was built for YAKAP end-to-end, not retrofitted onto a generic clinic EMR. FPE is a distinct, guided step separate from consultations, with PCU liveness capture (reference number, result, timestamp) built into both new-patient registration and reception intake — including blood-pressure alerts at registration so high-risk patients surface immediately. eKAS and ePresS generate directly from the consultation record, with physician PRC/PTR/S2 details attached automatically. Claims XML is built, validated, and stored encrypted, with duplicate-transmittal protection per consultation. A capitation dashboard tracks FPE counts and projected 40/60 tranches against your panel in real time, and the GAMOT medicine list (all 242 preparations, PC 2025-0013 Annex A.2) is built in with fixed-fee lookups. For clinics still on eKonsulta, RecordKo supports XML/CSV batch import so your historical FPE and consultation data — not just future encounters — survives the migration. If you're weighing a switch, our safe EMR migration guide walks through the export-first approach we recommend before any cipher-key transfer.

Book a demo ↗

References

← All stories