Encoding Lab Results in YAKAP: Getting Diagnostics Into the Claim

Encoding a lab result in YAKAP means recording the diagnostic outcome onto the exact consultation that originally ordered it, then reflecting that result in the eKAS and the T2 XML claim — not a separate record. Get the ordering-vs-resulting split wrong and you risk a claim that doesn't match the printed slip and a lower lab-utilization score on your year-end capitation.

Ordering vs. Resulting: Two Different Moments

Ordering and resulting are not the same encounter, and treating them as one step is where clinics go wrong. Ordering happens during a consultation, after the doctor's assessment: the PhilHealth YAKAP FAQ states that "after the first consultation and doctor's assessment, the doctor may order needed laboratories" — done at the YAKAP Clinic or a partner diagnostic facility, with a referral plus prescription from the registered clinic's doctor required. Resulting happens later, sometimes days later, when the specimen is processed or the partner facility reports back — a separate physical event from the visit where the order was written.

For clinics still thinking in eKonsulta terms: PhilHealth Circular No. 2024-0013 defines the interim eKonsulta system as being for "encoding the client's encounter data/consultation records to include diagnosis, diagnostic tests done with corresponding results and prescribed/dispensed medicines" — tests done AND their results, one continuous data thread, not two unrelated entries.

Why Results Must Attach to the Ordering Consultation

A lab result belongs on the consultation that ordered it, never on whichever visit happens to be open when the result comes back — because the claim, the eKAS, and the performance count all trace back to that original transaction number:

If Dr. Santos orders a lipid profile Tuesday and the patient returns Friday with results, those results must be encoded onto Tuesday's consultation record, not a new Friday entry.
The consultation's T2 claim XML must carry the diagnostic result data tied to the same case that ordered the test, so the claim reflects what was actually done at that visit.
The eKAS for that visit is only credible if what's checked on the slip matches what's encoded in the consultation's diagnostic data — a mismatch between the printed slip and the underlying record is an audit flag, not just a paperwork inconsistency.

This is also why staffing matters here: PC 2024-0013 explicitly allows capitation funds to pay for "non-healthcare workers such as encoders" — PhilHealth anticipates resulting is a distinct administrative workflow needing dedicated attention, separate from the clinical visit itself.

For the mechanics of the very first visit of the year, see The First Patient Encounter (FPE): Step-by-Step Guide for YAKAP Clinics — the FPE itself is not a medical consultation, so diagnostic ordering typically starts at the first true consultation that follows it.

What YAKAP Actually Covers

Under PC 2024-0013, the Konsulta/YAKAP benefit table lists 15 covered laboratory and diagnostic examinations: CBC with platelet count, lipid profile, FBS, OGTT, HbA1c, creatinine, chest X-ray, sputum microscopy, ECG, mammogram, ultrasound (upper abdomen, pelvic, and breast only), urinalysis, Pap smear, fecalysis, and fecal occult blood test.

The eKAS services grid (Annex H) tracks 13 of these — mammogram and ultrasound route separately through the cancer-screening referral pathway. Beyond the base 15, YAKAP also covers six cancer screening tests — mammogram, breast ultrasound, low-dose chest CT scan, alpha fetoprotein, liver ultrasound, and colonoscopy — available upon referral from the clinic doctor per the PhilHealth YAKAP FAQ, with no separate facility fees charged. See What Is the eKAS? The YAKAP Konsulta Availment Slip, Explained for how the grid gets generated per visit.

How the Result Reaches the eKAS and the Claim

Once a result is encoded onto the correct consultation, two artifacts depend on that data being right. The eKAS, printed "immediately after each patient encounter" per PC 2024-0013, marks Performed, Date Performed, and Performed by for each diagnostic — it should reflect exactly what's saved in the consultation's diagnostic data, never filled in from memory. The T2 XML claim built from that consultation must carry the diagnostic results alongside the diagnosis and any prescribed medicines; PhilHealth's certified-EMR requirement (see the eKonsulta decommissioning advisory) exists so this diagnosis-diagnostics-medicine bundle gets encoded once and transmitted, not re-typed across two systems.

All health data must be encoded in a PhilHealth-certified application and uploaded via the HCI Portal (or the LHIO) daily, on or before the 7th calendar day of the following month, per PC 2024-0013 — first-tranche computation depends on complete data as of 11:59 PM of the 7th. A late or misattached result can miss that window entirely.

The Performance-Indicator Stakes

Lab encoding decides how much of your second-tranche capitation the clinic actually collects. PC 2024-0013's Annex I performance factor weighs four indicators: primary care consultation (100% target, 30% weight), utilization of laboratory services (50% target, 30% weight), antibiotic dispensing for communicable disease (15% target, 10% weight), and NCD medicine dispensing (20% target, 30% weight).

The laboratory indicator is unique beneficiaries who received a lab service divided by total registered beneficiaries with a validated FPE — and that numerator only counts what was actually encoded and submitted, since PC 2024-0013 states plainly that "services not reported to PhilHealth shall not be counted as part of performance." A clinic can run every ordered test correctly and still score zero here if the results never reach the claim data.

At P1,700 maximum capitation per beneficiary per year — P680 as the 40% first-tranche FPE payment, up to P1,020 as the 60% second tranche multiplied by the performance factor — a weak lab-utilization score shrinks the larger of the two payments. See How YAKAP Clinics Get Paid for the full tranche math.

Common Encoding Mistakes That Cost Clinics

The costliest mistakes are quiet ones — they surface only at claim rejection or year-end reconciliation:

Creating a new consultation for the resulting visit instead of attaching results to the original order, splitting one clinical episode into two disconnected records.
Filling out the eKAS from memory rather than from the saved diagnostic data, so the slip and the claim disagree.
Losing track of pending results — an order with no result encoded is invisible to the lab performance indicator, even if the test was done.
Missing the monthly upload window, so results roll into the next SAP1 cycle instead of the one they belong to.
Treating diagnostics as paperwork separate from the SOAP note, inviting the same double-encoding that made eKonsulta painful.

Encoding also connects to the PCU liveness check that should precede the visit — see The PhilHealth PCU Liveness Check: What It Is and How to Do It Right — and to any medicines prescribed alongside the order, covered in ePresS: How Electronic Prescriptions Work Under YAKAP.

How RecordKo Handles Lab Results Encoding

RecordKo's Labs tab keeps ordering and resulting as two connected states of the same record, not two separate ones. Every diagnostic ordered in a consultation shows up under Pending Lab Results until staff encode the outcome — which writes directly back onto the consultation that ordered it, so its eKAS grid and T2 XML stay in sync automatically, with no re-typing. Built for YAKAP end-to-end, the same encoded result feeds the laboratory-utilization indicator on your capitation dashboard in real time, and clinics migrating off eKonsulta before its shutdown can import prior XML batches so historical results aren't lost.

Book a demo ↗