Frequently asked questions

HealthPhil is a web-based community health operations platform for Philippine local health organizations. The Features page reads from current platform module settings; an organization’s subscription, configuration, and assigned access can further limit what its users see.

HealthPhil is designed for authorized community health workers, supervisors, and organization staff who coordinate local health services. The modules available to a person depend on the organization's account and assigned access.

Create an account and verify your email address, then follow the organization setup shown in the app. For a HealthPhil Connect LGU or barangay claim, Super Admin approval is required; the 30-day trial begins only after the claim is approved.

The app shell is cached as a Progressive Web App. After signing in and opening a barangay while online, the app can use a minimal cached patient roster and queue patient registration or edits, visit capture, immunization recording, and referral capture in the current supported forms. Reports, uploads, medicine dispensing, inventory changes, unvisited barangays, and full record history still require internet.

Queued patient, visit, immunization, and referral creates and supported patient edits synchronize when the app is open and reconnects, receives focus, or resumes in the foreground. Background synchronization is not guaranteed. The server rechecks the signed-in user's current permissions. Duplicate retries use stable operation IDs; edits are held for review if the server record changed.

HealthPhil can be added to the home screen or installed where the browser and operating system support it. Some browsers provide an in-page Install confirmation; on iPhone, iPad, and other unsupported browsers, follow the device's browser menu or Share-sheet instructions.

HealthPhil Connect provides public-facing barangay health center information pages and a searchable directory. Approved administrators can publish contact details, operating hours, services, and announcements that they maintain. It is not an appointment, telemedicine, emergency-response, or public patient-record system.

No. Unclaimed and unpublished pages are marked noindex and are omitted from the public portal sitemap. A Connect page can be indexed only after the location has an approved claim and an administrator publishes its page.

The claimant creates an account, verifies the email address, selects the barangay or city/municipality in the Directory, and submits the required contact and government-ID information. Super Admin manually reviews the request. Submitting a request does not grant administrative access.

The current workflow starts the 30-day trial after a Super Admin approves the claim and creates the organization. Signup and claim submission alone do not start the trial.

No. Claim ID images are converted to WebP before upload and stored in a private bucket for claimants and authorized Super Admin reviewers. They are not displayed on public Connect pages.

Access is assigned through active organization and barangay role grants. Authorized managers can give a person different grants for their work areas. The server checks the current grants and organization membership when protected operations are requested.

Yes. An authorized manager can assign separate role and barangay grants within an organization. The membership row links the person to the organization; active scoped grants determine their permitted work. Revoking a grant removes its authority for subsequent protected operations.

The application includes patient registry exports and reporting workflows. Available modules and report formats depend on current platform settings and the organization's configuration. FHSIS reports can be prepared in the app; direct DOH submission requires a separate integration and is not implied by report generation.

The PhilHealth Forms workspace prepares claim-related forms using organization records for manual review and submission. Live eligibility verification, direct claim submission, and status synchronization require a separate PhilHealth API integration. See the Features page for its current platform availability.

HealthPhil uses IndexedDB through Dexie for a minimal, barangay-scoped patient roster and encrypted queued changes. The queue is bound to the signed-in user and organization and has a 30-day recovery window. Do not clear browser storage while changes are pending. Reconnect the app, resolve conflicts or expired items, and protect the device with its screen lock.

For privacy, data handling, or account support questions, contact the HealthPhil team through the Contact page and include your organization name. Do not send patient health details through a general support message.