The First Patient Encounter (FPE): Step-by-Step Guide for YAKAP Clinics

The First Patient Encounter (FPE) is the annual health-data-gathering visit that starts every beneficiary's YAKAP journey — and it is the event that triggers your clinic's first-tranche capitation payment of P680 per registered beneficiary. A compliant FPE in 2026 has five moving parts: a PCU liveness check, the Annex G health-screening data, a consented photo, a signed Mutual Care Agreement (MCA), and same-day encoding and upload.

What the FPE Is — and Is Not

Under PhilHealth Circular No. 2025-0017, the FPE is "the initial episode of patient contact for the year whereby a PC Clinic takes and/or updates the basic health data of an eligible beneficiary to identify their health risk." PhilHealth is explicit: the FPE is not a medical consultation. It sits third in the four-step YAKAP availment sequence — Registration, Selection, First Patient Encounter, Empanelment.

Two operational points many clinics miss, both from PhilHealth Circular No. 2024-0013:

The doctor does not have to do it. An FPE may be rendered on the clinic's behalf by barangay health workers, BHS/RHU nurses and midwives, authorized medical clerks or interns, nurses of employers' on-site clinics, physicians, or any duly trained allied health support staff.
Registration can happen in the same visit. FPEs conducted before registration remain valid, provided the beneficiary registers within the applicable year.

Step 1: Run the PCU Liveness Check

Every patient encounter — including the FPE — starts with a PhilHealth Check Utility (PCU) liveness check. PhilHealth Advisory No. 2025-0072 makes this mandatory: the check validates identity and eligibility and generates a PCU Transaction Number, and effective January 1, 2026, every SAP 1 submission must carry that transaction number plus the MCA — claims without them "will likely encounter delays in processing or non-payment."

Practical details from PC 2025-0017:

PCU checks the PhilSys database first, then PhilHealth membership. Non-PhilSys-registered walk-ins need a valid government ID for manual validation.
Verification can run on the beneficiary's own phone or a clinic terminal.
Until PCU is integrated with the YAKAP System, capture a photo or screen capture of the verification result and keep it for audit.
For FPE records, PhilHealth requires the PCU reference number, verification result, date/time stamp, and the signed MCA.

Full walkthrough: The PhilHealth PCU Liveness Check: What It Is and How to Do It Right.

Step 2: Take the Health Data (Annex G)

The official Health Screening/FPE form (Annex G of PC 2024-0013) defines exactly what "complete" means:

Client profile and chief complaint
8-question review of systems — a "Yes" to any of the 8 questions means the beneficiary needs to consult a doctor
Smoking and alcohol history
Past-medical-history checklist: cancer, allergies, diabetes, hypertension, heart disease, stroke, asthma, COPD, TB
Physical exam findings: blood pressure, heart rate, respiratory rate, visual acuity, height, weight, BMI, temperature
Pediatric anthropometrics for children 0–24 months
Blood type

Leaving fields blank is the most common way an FPE fails validation later — encode everything.

Step 3: Photo, with Consent First

PC 2024-0013 requires that "a photo shall be taken as proof of actual visit and stored in the KPP together with the client's record." Photo consent must be secured first using the Annex F template. The photo itself has specs: colored, at least 35mm x 45mm, full face, front view, eyes open, head centered, even lighting, no distracting shadows.

Step 4: Sign the MCA / YAKAP Empanelment Slip

The MCA (executed via the YAKAP Empanelment Slip) is required at every FPE of new and rolled-over members, and it is a stated requirement for first-tranche payment. Key rules from PC 2025-0017 and PA 2025-0072:

Beneficiaries sign a new MCA annually; parents or legal guardians sign for minors.
After FPE and MCA signing, the beneficiary is empaneled to your clinic for at least a year; transfers are allowed only in the fourth quarter, barring closure or loss of accreditation.
Deadline alert: for rolled-over CY2025 members, MCA and PCU compliance must be completed on or before June 30, 2026 — beyond that, clinics must return SAP1 payments for every rolled-over beneficiary without a signed MCA.

More detail: The YAKAP Empanelment Slip (YES): When You Need It and How It Works.

Step 5: Encode, Print the eKAS, Upload the XML

All health data must be encoded in a PhilHealth-certified application system, and the eKAS must be generated and printed immediately after each patient encounter, with the beneficiary signing it (thumbmark if unable to write; parent/guardian for minors). XML reports go up through the HCI Portal daily, on or before the 7th calendar day of the succeeding month — first-tranche computation uses only the data uploaded as of 11:59 PM of the 7th. Note that PhilHealth Advisory No. 2025-0077 decommissions the eKonsulta system by July 1, 2026, so this workflow now lives in your certified EMR. See What Is the eKAS? for the slip's contents.

Why Completeness Triggers the P680

Under PC 2024-0013, the maximum per-capita capitation is P1,700 per year. The first tranche — 40%, or P680 per registered beneficiary with FPE — is what a valid FPE unlocks. The remaining 60% (up to P1,020) is the performance tranche, computed on your FPE count as of December multiplied by the performance factor. SAP1 is generated on the 8th of the succeeding month and released within 60 days, but only if the records pass system validation; late or incomplete uploads roll into the next SAP1. Payment is credited to the accredited PC Clinic regardless of who performed the FPE — and the clinic is accountable for all of them. See How YAKAP Clinics Get Paid.

Common FPE Mistakes

No PCU Transaction Number logged — since January 1, 2026 this alone can stall or void SAP1 payment.
Unsigned or missing MCA — no MCA, no first tranche; rolled-over members without one past June 30, 2026 trigger payment recovery.
Missing or non-compliant photo, or no consent form — the photo is proof of actual visit.
Incomplete Annex G data — skipped vitals, blood type, or ROS answers weaken validation and the year-end FPE count.
Ignoring "Yes" ROS answers — the form requires a doctor consultation; skipping it also costs you the consultation performance indicator.
Uploading after the 7th — the FPE misses that month's SAP1.
Assuming year-two FPEs are optional — the succeeding-year first tranche is paid without a new FPE only if the beneficiary had at least one medical consultation the previous year; beneficiaries who never had an FPE are not retained at all.

How RecordKo Runs the FPE End-to-End

RecordKo was built for YAKAP end-to-end and designed for the certified-EMR era: the registration and reception flow captures the PCU result, transaction number, and proof PDF on every encounter; the intake wizard mirrors the required FPE data (vitals with automatic high-BP alerts, history checklists, pediatric anthropometrics); eKAS and ePresS render instantly for signing; and encrypted XML claims, empanelment slips, and capitation tracking are generated from the same record — encoded once, submitted on time. Migrating from eKonsulta? RecordKo imports your existing XML batches.

Book a demo ↗