Back to all projects

Healthcare / App case study

YAKAP Consulta

A financial-monitoring prototype connecting beneficiary readiness, service costs, receivables, payments, co-payments, variances, and reports through role controls and traceable audit history.

Internal financial-monitoring prototype

01 / Overview

What it’s built for.

Reconcile beneficiary readiness, service costs, receivables, payments, and program-year financial reports in one traceable workflow.

Who it serves

Administrators, encoders, finance officers, and read-only auditors.

02 / Features

Inside the app.

Readiness and services

Track beneficiary-year readiness, encounters, service utilization, and cost.

Financial reconciliation

Manage SAP receivables, payments, co-payments, variances, and immutable year-effective policy snapshots.

Reports and auditing

Use role controls, masked identifiers, non-destructive voiding, and financial report exports.

03 / Workflow

From task to outcome.

  1. Register a beneficiary and review program-year readiness.

  2. Record service encounters and associated costs.

  3. Generate financial snapshots and reconcile receipts and variances.

  4. Review reports and audit history through the appropriate role.

04 / Technical layers

How the pieces work.

Interface

React · TypeScript · Inertia · Recharts

Role-specific screens visualize readiness and financial-monitoring records.

Application

Laravel · PHP

Year-effective policies and reconciliation rules preserve the originating reporting period.

Database

SQLite

Beneficiaries, encounters, policy versions, payments, and audit history support the documented local prototype.

Privacy and reporting

Encrypted identifiers · DomPDF

Identifiers are masked and uniqueness-hashed; reports exclude biometric images and detailed clinical notes.

05 / Limitations

What to keep in mind.

  • Demo records and financial values are fictional.
  • The app does not submit data to PhilHealth or establish accreditation, certification, or an eClaims integration.
  • Its program-year reconciliation is not a cash-basis general ledger.

06 / Evidence

Follow the source.

These descriptions were reviewed against the linked source snapshot on October 12, 2026. Repository code and documentation may evolve after this review.