Whether G3 Flow is up.
The status page shows each part of the service, a 90-day history, incidents that affect every customer, and maintenance that is scheduled or underway. Updates name the component. They leave out organization names and any count of a customer’s work.
The live board is published when this server’s public status page is turned on. Signed-in organizations still see incidents that affect their own work, from the app.
What the page reports.
Eight parts of the service. A disruption is labeled on the part it affects, with the updates posted while it is open and after it is resolved.
Claim submission
Claims sent to clearinghouses and payers.
Acknowledgments (999/277CA)
Clearinghouse and payer acknowledgments of the claims that were sent.
ERA retrieval and posting
Remittances retrieved, matched to deposits, and posted.
Eligibility checks
Coverage checked before visits and before billing.
Patient statements and payments
Statement notices, the online payment portal, and payment plans.
Billing-system write-back
Payments and corrections written back to the billing and source systems.
Reports and exports
Claim status, month-end revenue, reconciliation, and report packs.
Dashboard and API
The G3 Flow dashboard, the API, and webhook deliveries.
Two views of the same service.
On this status page
Published incidents that affect every customer, scheduled maintenance, and the state of each component over the last 90 days. Nothing on the public page names an organization.
When you are signed in
Your organization also sees published incidents that affect its own work. Those stay in the app. They are not added to the public page.