Designing a YAKAP Clinic Workflow: From Reception to Doctor to Claim

A well-designed YAKAP clinic workflow splits the visit into four handoffs — reception captures identity and vitals, the doctor completes the clinical record, support staff close out labs and dispensing, and the encoded data becomes an XML claim — with a PCU check anchoring every step. Blurred handoffs cost clinics both time and delayed claims.

The Four Stages of a Compliant YAKAP Visit

Every YAKAP encounter — a First Patient Encounter (FPE) or a regular consultation — moves through the same four stages, each with a distinct owner:

Reception — PCU check, vitals, chief complaint, and (on a first-ever visit) the Annex G health-screening data.
Doctor — HPI, physical examination, assessment (ICD-10), and plan, including referrals for labs or cancer screening.
Post-visit support — encoding diagnostic results once labs come back and recording medicine dispensing, often on a different day.
Submission — encoding the encounter into a PhilHealth-compliant XML file, validating it, and transmitting it as a claim.

Getting the FPE right matters disproportionately: it's the "initial episode of patient contact for the year" that establishes a beneficiary's basic health data, and PhilHealth is explicit that "the FPE is not a medical consultation" (PhilHealth Circular No. 2025-0017). The full availment sequence is Registration, Selection, FPE, and Empanelment. Deeper dive: The First Patient Encounter (FPE) Guide.

Reception: PCU, Vitals, and Chief Complaint

Reception verifies who the patient is, captures objective numbers, and records why they came — it does not diagnose. Three tasks, in order:

Run the PCU liveness check. The PhilHealth Check Utility verifies PhilSys registration and PhilHealth membership via facial recognition, confirming identity before anything else proceeds (PhilHealth Circular No. 2025-0017). It's required for every encounter, not just the FPE, and generates a PCU Transaction Number now required on SAP 1 submissions — claims without it "will likely encounter delays in processing or non-payment" (PhilHealth Advisory No. 2025-0072). Full mechanics: The PCU Liveness Check Guide.
Take vitals. BP, heart rate, respiratory rate, height, weight, BMI, and temperature belong in the record from the start — also the natural place to flag dangerous BP so a high-risk patient gets prioritized.
Record the chief complaint. A short statement of why the patient is here saves time and gives the doctor a starting point for the HPI.

On a first-ever encounter, reception (or any trained staff — an FPE may be rendered by barangay health workers, RHU nurses/midwives, medical clerks, or allied health staff, not only physicians) also completes the Annex G form: client profile, an 8-question review of systems (a "Yes" to any flags the beneficiary for a doctor), history checklists, physical-exam basics, and a consented photo as proof of visit (PhilHealth Circular No. 2024-0013).

Doctor: HPI, Physical Exam, Assessment, and Plan

The doctor's job starts where reception's stops: turning a chief complaint and vitals into a diagnosis and a plan — the actual "medical consultation" the FPE is not. A complete doctor-side record has four parts:

HPI — onset, duration, character, aggravating/relieving factors.
Physical examination — findings by body system, building on reception's vitals.
Assessment — a diagnosis coded to ICD-10. GAMOT rules require the physician to "abide by International Classification of Diseases 10th Edition coding standard and shall accurately encode the appropriate diagnosis(es) for each prescription" (PhilHealth Circular No. 2025-0013).
Plan — treatment, medicines, and referrals. After the first consultation, the doctor may order YAKAP-covered labs and refer for cancer screening; a referral and prescription from the patient's registered YAKAP Clinic doctor is required for labs, screening, and GAMOT medicines (PhilHealth YAKAP FAQs).

Before prescribing, check existing active prescriptions and honor, revise, or cancel-and-reissue (PhilHealth Circular No. 2025-0013). GAMOT caps maintenance prescriptions at three months (pharmacy dispenses one month at a time), so set a follow-up date. Print the eKAS after each encounter, and the ePresS for prescribed medicines (PhilHealth Circular No. 2024-0013) — see What Is the eKAS? and ePresS Explained.

After the Visit: Labs and Medicine Dispensing

A YAKAP consultation often doesn't end when the patient leaves the doctor — lab results and dispensing happen later, and both must write back to the original consultation. This is the stage most workflows lose track of.

Diagnostic results get recorded against the consultation that *ordered* them, whenever they come back. The eKAS's 13-row services grid (CBC with platelet count, lipid profile, FBS, OGTT, HbA1c, creatinine, chest X-ray, sputum microscopy, ECG, urinalysis, Pap smear, fecalysis, fecal occult blood test) tracks whether each was performed, when, and by whom (PC 2024-0013 Annex H).
Medicine dispensing needs the same discipline: what was handed over, by whom, and when, tied back to the prescribing consultation.

This is more than recordkeeping — it's the difference between full and partial capitation. The second-tranche performance factor weights four indicators: consultation (30%), lab utilization (30%), antibiotic dispensing (10%), and NCD medicine dispensing (30%), each measured as unique beneficiaries served over registered beneficiaries with a validated FPE (PhilHealth Circular No. 2024-0013). A lab done but never encoded doesn't count toward it.

Where the Visit Becomes a Claim

The visit becomes a claim once its data is encoded into a PhilHealth-compliant XML file, validated, and transmitted — on a fixed rhythm. Per Annex E of PC 2024-0013: verify registration → conduct the FPE → save the photo → consult, screen, and dispense → encode all data → generate the eKAS/ePresS (PhilHealth Circular No. 2024-0013).

Daily encoding, monthly deadline. XML reports go through the HCI Portal (or the LHIO) daily, on or before the 7th of the following month. SAP1 generates on the 8th and capitation is released within 60 days if data passes validation — late FPEs simply roll into the next SAP1.
Year-end second tranche. Consultation data is due through end of January; SAP2 uses data as of January 7 and generates January 8.
eKonsulta is shutting down. It's decommissioned by July 1, 2026; after shutdown, clinics must daily encode, download the XML, and submit via the HCI Portal or LHIO (PhilHealth Advisory No. 2025-0077).

More on payment mechanics: How YAKAP Clinics Get Paid.

Designing the Handoff So Nothing Gets Lost

The principle that prevents leakage across all four stages: build one continuous record, not four disconnected forms. Vitals should carry from reception into the doctor's screen without re-entry; a lab order should surface as a pending item until someone encodes the result; a prescription should surface as a pending dispense until someone records it. Every re-typed field is a place where a transaction number or lab result quietly disappears — and a missing result is a lost performance-indicator point at year-end, not just a paperwork gap.

How RecordKo Handles This

RecordKo is built for YAKAP end-to-end around this exact handoff: reception captures the PCU result, vitals, and chief complaint on one screen that opens directly into the doctor's HPI/PE/assessment/plan workflow, with a live queue timer between the two. Pending labs and dispensing surface as their own worklists, writing back to the original consultation and feeding the eKAS and ePresS automatically. Each consultation compiles into the encrypted XML PhilHealth expects, with capitation and performance-indicator tracking on the same underlying data — no separate encoding pass required.

Book a demo ↗