Connectivity
Connected where it counts. Honest about the rest.
Clearinghouse-connected EDI for eligibility, claims and remittance sits at the center of the stack, with sandbox, production-test and production paths switched on deliberately. Stedi carries 270/271, 837 and 835 over a modern JSON API instead of hand-rolled X12; live production for each transaction type is confirmed with you, not assumed. Patient payments use Stripe Checkout pay links and optional Twilio SMS reminders, with opt-outs respected and card data never stored by MEDBIX. FHIR ingest for billing-relevant EHR data is available as a path; live connections to major EHRs remain on the roadmap and stay labelled as such. The status board below lists what is connected, demo-only or still ahead. Bring your current clearinghouse and practice systems to a call if you want a fit check against your stack.
Eligibility · 270/271
- Plan statusActive
- Specialist copay$40
- Deductible remaining$310 of $1,500
- Prior auth (imaging)Required
Status board
Everything MEDBIX connects to
Live connections first. Roadmap items stay labelled as roadmap.
Stedi
Clearinghouse: 270/271, 837, 835
Connected
Stripe
Patient checkout & webhooks
Connected
Twilio
SMS payment reminders
Connected
PostgreSQL 16
Row-level security per tenant
Core
LangGraph
Human-in-the-loop agent workflows
Core
FHIR
EHR billing data (demo path)
Demo
Epic / Cerner / athena
Live EHR connections
Roadmap
Sentry
Optional observability
Optional
Stedi clearinghouse
A modern JSON clearinghouse API instead of hand-rolled X12. It carries the three transactions billing runs on.
Eligibility
Can run on the live production path.
Claims
Production submission rolled out carefully.
Remittance
Production ERA confirmed payer by payer.
Modes
Three clearinghouse modes
So demos never touch real data and production is switched on deliberately.
Sandbox
Synthetic scenarios for demos and tests.
Production test
The real clearinghouse test API.
Production
Live path, gated and confirmed per transaction type.
Patient pay
Stripe and Twilio for patient payments
Statements carry a Stripe Checkout pay link; reminders go out by Twilio SMS with opt-outs respected. Card data never touches MEDBIX.
Cedar Family Medicine
Hi Sam, here's your balance.
Visit on Sep 2 · after insurance
$20.00
- Charged$180.00
- Insurance paid−$112.00
- Plan discount−$48.00
Secure checkout by Stripe
Text message · Today 10:14
Integration roadmap
What's next on the wire
EHR connections
A FHIR ingest path runs today in demo form. Live connections to Epic, Cerner, eClinicalWorks or athena are on our roadmap and not available yet.
Recurring card charges
Pay links are live. Recurring automatic charges are not yet.
Built on these pipes
Features that depend on integrations
Clearinghouse
Stedi for the three transactions billing runs on.
270/271 eligibility, 837 claims and 835 remittance through a modern JSON clearinghouse API — with sandbox, production-test and production modes.
- Synthetic sandbox for demos
- Production-test before go-live
- Production gated per transaction type
Patient pay
Stripe Checkout and Twilio SMS — card data never in MEDBIX.
Statements carry a pay link. Reminders go out by SMS with opt-outs respected. Recurring auto-charges stay on the roadmap.
- Pay links on statements
- SMS reminders with opt-out
- No card storage in MEDBIX
EHR path
Honest about Epic, Cerner and athena.
A FHIR ingest path runs in demo form today. Live major EHR connections are roadmap — not something we imply in a sales deck.
- FHIR demo path available
- Live EHR connections on roadmap
- Import paths for client data today
Core
PostgreSQL and LangGraph under the hood.
Row-level security per tenant and human-in-the-loop agents are core — not optional add-ons you bolt on later.
- RLS as a platform primitive
- Agents that require human decisions
- Optional observability via Sentry
Common questions
Can we keep our current clearinghouse?
MEDBIX is built on Stedi. We'll talk through what moving looks like for your payers.
Do you have an API?
Ask us about your use case; integration needs are scoped during onboarding.
Which EHRs do you support?
FHIR ingest exists in demo form. Major EHR connections are on the roadmap.
Want to walk MEDBIX against your real claim mix?
Thirty minutes with sample data. We'll follow one claim through the gate, then talk about your payers, practices and where the rework hurts today.
Notes from the billing floor
Occasional, practical writing on denials, A/R and running a billing company. No spam, unsubscribe any time.