Citizen-facing services · Health and welfare

PBB Natalium / Natalium

A local health workflow module for patient registry, community health programs, continuity of care, referrals, and reporting.

Integrated · Production hardening Baseline node service
Primary placement
Health-center node; Barangay node; City or municipal health node; Field health node
Primary users
Community health workers, Practitioners, Health-center administrators, Patients and citizens, Health program managers

What it is

A practical part of one local platform

PBB Natalium is a local-node health application for health-center and field workflows. It brings patient registry, program enrollment, appointments, queue and care tasks, encounters, maternal and child health, birth-defect surveillance, referrals, prescriptions, reports, and exports into one local service.

Natalium integrates with PBB Account for sign-in and app-admin user provisioning. Its health records and document paths are local; no Relay outbox or upstream health-data synchronization was confirmed in the reviewed implementation.

Problem it solves

The operational gap

Community health teams need dependable access to patient context and care workflows even when external connectivity is unreliable. Natalium keeps these operational records and processes on a designated local node rather than depending on a continuous cloud connection.

Core workflow

How Natalium supports local work

  1. Enter through local identity

    A staff member or citizen signs in through the node's PBB Account integration and receives an app-local session and capabilities.

  2. Establish patient context

    Authorized staff review a profile application, duplicate checks, identity requirements, and the local patient record.

  3. Coordinate local care

    Teams manage programs, appointments, queues, tasks, encounters, referrals, prescriptions, and supported maternal or child health workflows.

  4. Review and export

    Authorized management users review reports, snapshots, exports, audit information, and controlled operations tools.

Who uses it

Designed around local service roles

  • Community health workers
  • Practitioners
  • Health-center administrators
  • Patients and citizens
  • Health program managers

Offline-first behavior

What continues locally—and what does not

Works on the local node

  • Authenticated patient, program, care, maternal and child health, referral, prescription, reporting, and document workflows are backed by the local database and storage paths.
  • The module can serve users over the designated node LAN without relying on a remote health database.

Required local services

  • PBB Account is used for new SSO sign-ins and app-admin provisioning.
  • Natalium requires its local Laravel application, MySQL database, and protected document or backup storage.

When a route returns

  • Account app-admin synchronization can update Natalium's local linked user records when the local identity service is reachable.
  • Natalium can read configured Relay hub JSON for node context; this is not health-record synchronization.

Connectivity-dependent

  • A new sign-in depends on the configured PBB Account service being reachable.
  • Any future transfer outside the node would require an approved and implemented integration that is not currently confirmed.

Not currently synchronized

  • No Relay outbox, retry queue, conflict strategy, or upstream synchronization for health records was confirmed.
  • Realtime and MapServer integration were not confirmed for Natalium.

Deployment placement

Where it fits

Special deployment

Health-center node; Barangay node; City or municipal health node; Field health node

Hardware, connectivity, power, training, travel, and field logistics remain deployment-specific.

Practical questions

Frequently asked questions

Can Natalium work without an internet connection?

Yes. Natalium can use its database and files over the local PBB network. New sign-ins still require the local PBB Account service to be working.

Are Natalium health records synchronized to the cloud?

No cloud transfer of health records has been confirmed. Patient and care records should be treated as staying on the local node unless a limited and formally reviewed sharing process is added later.

What health workflows are implemented?

The reviewed version includes patient registration, health programs, appointments, queues and staff tasks, consultations, maternal and child health, birth-defect monitoring, referrals, prescriptions, reports, exports, and operating tools.

Why does Natalium use PBB Account?

PBB Account handles sign-in and helps administrators set up users. Natalium then manages what each signed-in user may do inside the health application.

Is Natalium ready for unrestricted live health deployment?

Not yet. The foundation is strong, but the owner and pilot team must first approve privacy rules, how long records are kept, backups, document access, restoration, and day-to-day operating procedures.

Where are documents and backups stored?

Natalium can use chosen folders on the local node for documents and backups. These folders should not be publicly accessible, and approved rules must cover who can use them, how long files are kept, and how they are restored.

Status and readiness

Integrated

Core registry, program, care, maternal and child health, surveillance, referral, prescription, reporting, export, and Account integration workflows are implemented.

Remaining hardening work

  • Approve privacy, retention, backup, and document-access policy before live health deployment.
  • Define local login procedures when Account is unavailable for a new sign-in.
  • Decide whether health records remain node-local or gain a future selective upstream contract.

Connected platform

Local-node foundation

Briefing and pilot discussion

Discuss Natalium in a local PBB deployment

Explore how a local-node deployment could support practical service continuity in your community.

Request a briefing