Keep your systems. We’ll connect them.

Whatever runs your practice, lab or hospital, G3 Flow connects to it: through the standards healthcare runs on, any file your system can export, an API, the screens your team already uses, or our team by hand while a new connection is built.

Six ways inStandards, files, API, screens, AI reading and people

X12, HL7, FHIRRead and written to the versions payers and EHRs expect

Any payerThrough Claim.MD, built in, or any other clearinghouse’s standard exchange

Swap any pieceEach step’s connection is a setting, so changing systems doesn’t change your work

Coming in

Any EHR, EMR, LIS or practice systemFHIR R4, HL7 v2, X12 837, CSV, Excel, JSON, PDF and scans

Every payer, through any clearinghouse271, 999, 277CA, 277 and 835

Any bankDeposit exports, a reconciliation tool, or the statement

One record of every claim and payment

Going out

Claims and inquiries, to any payer837P, 837I, 837D, 270, 276 and 275, or paper forms

Back to your EHR, LIS or billing systemHL7 DFT and A08, FHIR, files or the system’s own screens

Your own toolsREST API, FHIR R4, signed webhooks, warehouse exports, a SIEM feed

Six ways to connect

Every system reaches G3 Flow one way or another. Most connect through more than one, so there’s always a way in, and a better one when you’re ready.

Healthcare standards

X12 for claims, eligibility, status and remittances, HL7 v2 for orders, charges, scheduling and demographics, and FHIR R4 for modern EHR APIs. Any system that speaks them connects with nothing built just for it.

X12HL7 v2FHIR R4

Any file

CSV, Excel, JSON, PDF and 837 files, recognized by what’s inside them rather than their names. A spreadsheet’s columns are mapped once and read the same way every time after, by SFTP or a watched folder.

CSVXLSXJSONPDFSFTP

API and webhooks

A REST API with OAuth 2.0 and OpenAPI docs, a FHIR R4 API, and signed webhooks for claims, payments, denials and tasks, so your own systems can send, read and react.

RESTOAuth 2.0Webhooks

The screens your team uses

No interface? G3 Flow works a web-based system’s screens the way your team does. It checks the screens haven’t changed before it starts, and a person approves every live change. A browser extension records a workflow to build the automation from.

You approve

AI that reads paper

Scanned EOBs, requisitions and superbills are read with OCR and vision models. Patient details go only to AI covered by a business associate agreement.

OCRVisionPDFImages

People, while it’s built

Any connection can start as a person. Our team works that step from the Work queue to a deadline, so billing starts on day one and the automation takes over when it’s ready.

Systems we connect to

A sample of the systems organizations bring to G3 Flow, and how each kind connects. If yours isn’t here, it almost certainly still speaks one of the ways in.

EHR and EMR

FHIR R4, which certified EHRs must offer, HL7 v2 feeds, or the exports every system has.

Epic
Oracle Health (Cerner)
MEDITECH
athenahealth
eClinicalWorks
NextGen Healthcare
Veradigm (Allscripts)
Greenway Health
ModMed
Elation Health
DrChrono
Practice Fusion
AdvancedMD
Tebra (Kareo)
CureMD
Nextech
Compulink
Azalea Health
TruBridge (CPSI)
Altera Digital Health
MEDHOST
Office Ally EHR 24/7
ChartLogic
Amazing Charts
RXNT
CareCloud

Behavioral health, therapy and ABA

FHIR R4, HL7 v2 or the system’s exports, with session units and authorizations carried through.

Netsmart
Qualifacts
Valant
TherapyNotes
SimplePractice
Kipu Health
CentralReach
Rethink Behavioral Health
WebPT
Raintree Systems
Prompt Health
Theralytics

Laboratory and pathology

HL7 v2 orders and results, exports, or the LIS’s own screens, with corrections written back.

Orchard Software
Clinisys (Sunquest)
SCC Soft Computer
Epic Beaker
Oracle Health PathNet
LigoLab
Psyche Systems
CompuGroup Medical (LABDAQ)
NovoPath
LabWare
STARLIMS
LabVantage

Medical equipment and home care

Exports and HL7 v2, with rental periods and equipment modifiers on the claim.

Brightree
WellSky
HDMS
NikoHealth
Axxess
Homecare Homebase
MatrixCare

Practice management and billing

Their exports and reports, their screens where there’s no interface, or G3 Flow’s own ledger in their place.

CollaborateMD
Medisoft
Lytec
Office Ally PracticeMate
Greenway Intergy
MicroMD
NueMD
PracticeSuite
ChiroTouch
The billing side of every EHR above

Clearinghouses

Claim.MD’s API is built in. Every other connects through its standard X12 exchange over SFTP, or a person uploads on its website.

Claim.MD
Availity
Optum (Change Healthcare)
Waystar
TriZetto Provider Solutions
Office Ally
Experian Health
Inovalon
Payerpath
Apex EDI
MD On-Line
Jopari

Payers

Every payer your clearinghouse reaches, with coverage checked by phone or portal from a task when a payer has no real-time answer.

Medicare
Medicaid plans
Blue Cross Blue Shield plans
UnitedHealthcare
Aetna
Cigna
Humana
Elevance Health
Centene
Molina Healthcare
Kaiser Permanente
TRICARE
VA Community Care
Workers’ compensation carriers
Auto and liability carriers

Interface engines and FHIR servers

Your engine routes HL7 or FHIR to G3 Flow by SFTP, a folder or the API, and bulk FHIR exports arrive as NDJSON.

Mirth Connect (NextGen Connect)
Rhapsody
InterSystems HealthShare
Infor Cloverleaf
Corepoint
Iguana
Azure Health Data Services
Google Cloud Healthcare API
AWS HealthLake

Banks, deposits and patient payments

Any bank’s deposit export as CSV or Excel, a reconciliation tool, or the statement keyed in; patient payments online through Stripe.

Provia
Stripe
Chase
Bank of America
Wells Fargo
PNC
U.S. Bank
Truist
Any bank with a deposit export

Sign-in and accounts

Single sign-on through OpenID Connect, and accounts kept in step with SCIM 2.0.

Microsoft Entra ID
Okta
Google Workspace
Ping Identity
OneLogin
JumpCloud
Auth0
Keycloak
Duo

Email, texts and alerts

Any SMTP service for email, Slack for alerts, Twilio for patients’ statement texts, and signed webhooks to anything that takes HTTPS.

Microsoft 365
Gmail
Amazon SES
SendGrid
Postmark
Mailgun
Slack
Twilio

Data, reporting and warehouses

CSV and JSON Lines exports, de-identified or in full, plus the REST and FHIR APIs.

Snowflake
Google BigQuery
Amazon Redshift
Databricks
Azure Synapse
Power BI
Tableau
Looker
Excel

Security and monitoring

A SIEM feed of every patient-data view, Prometheus metrics, OpenTelemetry traces, error tracking and JSON logs.

Splunk
Microsoft Sentinel
Datadog
Elastic
Sumo Logic
Grafana
Prometheus
New Relic
Honeycomb
Sentry

Names and trademarks belong to their owners. A listing shows how G3 Flow connects to that kind of system, through the standards, files, screens or services named; it isn’t a partnership or certification. “Built in” marks a connector that ships with G3 Flow.

Every step, more than one way

Each step of the cycle can connect several ways, so you start with what you have and switch to something better whenever you like.

Step	Ways it connects
Orders, charges and patients	HL7 v2FHIR R4X12 837CSV, Excel or JSONPDF requisitionsThe LIS or EHR screensKeyed from paper
Coverage checks	Real-time 270/271Phone or payer portal, from a task
Claims out	Claim.MD APIAny clearinghouse over SFTPA shared folderUploaded on the clearinghouse’s websiteCMS-1500, UB-04 or ADA paper
Acknowledgments and status	999, 277CA and 277 from your clearinghouseSFTPA folder276 inquiries out
Remittances	835 from your clearinghouseFrom your billing systemA folderPaper EOBs read or keyed
Where payments are recorded	Your practice-management systemG3 Flow’s own ledger
Back to your EHR or LIS	HL7 DFT^P03HL7 ADT^A08FHIR PaymentReconciliationThe LIS screens
Bank deposits	Any bank’s CSV or Excel exportProviaKeyed from the statement
Patient payments	Stripe: card and US bank accountThe front deskPayment plans
Patient statements	Printed for your mailing vendorEmailTextThe patient portal
Alerts and digests	EmailSlackSigned webhooksA file outbox
Sign-in and accounts	OpenID ConnectSCIM 2.0Email, password and two-step
Your own data	REST APIFHIR R4CSV and JSON Lines exportsSIEM feed

Each step’s connection is a setting. Moving to a new clearinghouse, billing system or bank changes that setting, not how your team works.

Standards

Read and written to the versions payers and trading partners expect.

X12 claims: 837P 005010X222A1837I 005010X223A2837D 005010X224A2
Professional, institutional and dental claims, in and out, with coordination of benefits, attachments and drug details.
X12 answers: 999277CA277835
Acknowledgments matched to the claims they answer, claim status, and remittances checked to balance.
X12 requests: 270/271276275
Eligibility and benefits, claim status inquiries, and claim attachments.
HL7 v2: ORMORUADTDFTSIU
Orders, results, demographics, charges and scheduling in; ADT^A08 updates and DFT^P03 payments back out.
FHIR R4: ClaimChargeItemServiceRequestAppointmentCoverageExplanationOfBenefitPaymentReconciliation
Bundles or bulk NDJSON in, with patients, coverage and practitioners; a read API for claims, EOBs and coverage; payment updates back to your EHR.
Files: CSVXLSXJSONPDFImages
Spreadsheets with a saved column mapping, superbills and requisitions from PDF, and scans read with OCR.
Transport: SFTPHTTPSWatched foldersSMTP
However your systems hand data off, by mailbox, endpoint, folder or email.
Identity: OpenID ConnectSCIM 2.0OAuth 2.0
Single sign-on, account provisioning and machine-to-machine access.
Paper: CMS-1500UB-04ADA 2019
For payers that still want paper.

Don’t see yours? We’ll connect it.

A system on a standard works as soon as its feed runs. One that needs building gets a connection request, and you can follow it from your go-live plan.

RequestedYou name the system during setup.
ScopedWe agree what moves and how, with your team.
BuiltA standard feed, a file mapping or a screen automation.
TestedRun against your own data before it goes live.
LiveThe automation takes over the step.

Until it’s live, the work still gets done. That step goes to the Work queue, and our team works it by hand, so nothing waits on the build.

G3 Flow’s Customers screen: each customer’s go-live checklist progress, and two interface requests, a MEDITECH HL7 feed in testing and an Orchard Harvest LIS feed in build, each with an owner and a target date. — **Interface requests.** Each connection we build has a status, an owner and a target date, and going live switches the customer over from manual work.

For your developers

An API, FHIR, webhooks and SCIM, documented in the product.

REST API with OAuth 2.0

Client credentials issue one-hour tokens with scopes for claims, eligibility, remittances, patients, webhooks, FHIR and status. Post claims, read their status, acknowledgments, remittances and payments. OpenAPI docs come with it.

Claims in any format

Post X12 837, HL7 v2, FHIR R4, CSV, Excel, JSON or PDF to the same endpoint. G3 Flow tells the formats apart by their content and answers with each claim it read and anything that needs repair.

FHIR R4 read API

Claim, ExplanationOfBenefit and Coverage resources with a CapabilityStatement, paged searches, and patient details only for clients granted them.

Signed webhooks

claim.submitted, claim.accepted, claim.rejected, payment.posted, denial.opened, task.created, eligibility.checked and incident updates, signed with HMAC-SHA256 and retried up to 12 times.

SCIM 2.0 and a SIEM feed

Provision people from your identity provider, and pull the patient-data access log into your security tools as JSON Lines.

Exports for your warehouse

Claims, remittances, payments, denials and work as CSV or JSON Lines, with a manifest, de-identified or, with an audit record, in full.

# a token for your integration, good for one hour
POST /oauth/token
grant_type=client_credentials&scope=claims:write claims:read

# send claims as X12, HL7, FHIR or CSV; read back where each one stands
POST /api/v1/claims
GET  /api/v1/claims/{claim_id}/status

# the same claims as FHIR
GET  /fhir/R4/Claim?_count=20

Start with what you already run.

Your go-live plan lists every connection your services need, who owns it and when it’s due.

Talk to us See the go-live plan