ZeroPayHealth

FAQ Library

Role-based answers before the first call.

A structured question library that separates finance risk, hospital operations, and employer benefits concerns instead of forcing every stakeholder through the same generic FAQ.

Role tracks

3

Lenders, hospitals, employers

Indexed answers

18

Grouped by decision owner

Privacy posture

PHI-minimized

Employer and lender views stay scoped

Role-Based FAQ

Separate questions by the risk each role owns.

Lenders need repayment evidence, hospitals need operational clarity, and employers need privacy-safe savings documentation. Each tab answers the questions that usually slow down a deal.

A case is not lender-ready until California operations completes identity verification, background review, employment context, insurance or benefits eligibility checks, consent capture, and case completeness review. Lenders receive the finance-relevant packet while clinical details remain minimized unless a specific review role requires them.

Capital is routed only after the patient confirms a treatment pathway, the hospital package is accepted, and required finance documents are complete. The workflow is structured around documented milestones rather than an open-ended advance.

Settlement timing depends on the employer plan, claims audit, final hospital invoice, discharge packet, and any stop-loss or third-party administrator review. The platform keeps each case tied to a settlement ledger so lender teams can see the current status without needing clinical PHI.

The final finance agreement defines the economics for each approved case. Product logic is designed so employer savings can fund the bridge-finance payoff when the corridor delivers verified savings, while the patient-facing pathway remains positioned around approved $0 out-of-pocket participation.

Before a treatment milestone is reached, the case can be paused, re-priced, reassigned, or closed according to the agreement status. If a patient is no longer clinically eligible or declines the pathway, the workflow records the event and blocks further case progression.

The repayment file can include verification records, consent status, employment or eligibility confirmation, accepted hospital bid, treatment milestones, final invoice, discharge documentation, claims audit notes, employer savings evidence, and payout history.

Question Routing

The same case creates different questions for each stakeholder.

This page is built to intercept repeated conversations: lender risk reviews, hospital onboarding calls, and employer privacy or savings diligence.

Lenders

Default risk, repayment evidence, settlement cycle

CA verification, milestone funding, final audit packet

Hospitals

USD settlement, record translation, 3+3 bid logic

Bid packet, bilingual records, licensing review

Employers

Savings proof, employee privacy, California applicability

Claims comparison, non-clinical status, plan-specific review

Still Open

Escalate role-specific questions into the right portal workflow.