Frequently asked questions
What to know before you start.
Product scope, patient consent, integration readiness, and the decisions that remain with people and institutions.
01What problem does AG2 solve?
AG2 helps the owner of a production AI system decide whether a prompt, model, tool, policy, or runtime change should ship. It joins repeatable scenarios, production evidence, release gates, action governance, and an exportable decision record.
02How does Lotuspond Health connect patients and hospitals?
Lotuspond Health is a consent-led patient and hospital claims experience. Patients use one account to connect participating hospitals and follow documents, status, and next actions. Hospital teams use a tenant-scoped desk for intake, evidence checks, payer follow-up, denials, appeals, and settlement history.
03How do patient consent and hospital access work?
A patient registers once, then explicitly requests a connection to each Lotuspond network hospital. Every connection carries its own status and consent scope, and a new claim requires an active connection. Hospital-owned records remain isolated while patients can follow claims across the hospitals they have chosen to connect.
04Does Lotuspond decide whether an insurance claim is approved?
No. Lotuspond Health helps hospital teams prepare evidence, check completeness, route claim packets, track payer events, and surface exceptions. The insurer or TPA remains responsible for authorization, adjudication, denial, and settlement decisions; authorized people retain the consequential decision.
05Are all payer and NHCX connections live from day one?
Connectivity is staged, not assumed. Each hospital completes payer routing, participant identities, credentials, secure callbacks, and sandbox verification before a controlled go-live. Lotuspond Health supports controlled hospital pilots and NHCX sandbox onboarding; live coverage depends on issued credentials and participation from each payer or TPA.
06What is the best way to start?
Start with one bounded workflow and a measurable baseline. For AG2, choose one agent release path, connect outcome receipts and telemetry, define the scenarios it must pass, and run the process in shadow mode before enforcing a gate. For Health, choose one hospital and claim cohort, confirm patient consent, onboard the payer route, and measure turnaround and exceptions through a controlled pilot.