Workflow
Billing company on top. Practices underneath. Walls in between.
The structure that lets one billing company serve many practices without ever mixing their data. Walk the diagram below to see who acts at each step — a person, MEDBIX, an AI agent, the clearinghouse, or money moving — and where a named decision is required.
Diagram
The steps
Each step shows who acts: a person, MEDBIX, an AI agent, the clearinghouse, or money moving.
- MEDBIX
- 1
Billing company (tenant)
MEDBIXYour company account and staff.
- 2
Client practices
MEDBIXOne space per client.
- 3
Patients, encounters, claims, statements
MEDBIXBelong to a practice.
The principles behind it
Database-level isolation
Row-level security in PostgreSQL.
Staff belong to the company
Roles sit at the company level.
Scoped billers
Assign billers to specific practices.
Ownership
Who does what
| Who | What they do in this workflow |
|---|---|
| Admin | Creates practices and users. |
| Supervisor | Sees all practices. |
| Biller | Works assigned practices. |
Features in this workflow
On the floor
What this looks like in practice
These cues come from the same workflow — useful when you are mapping MEDBIX to how your team already works.
system
Billing company (tenant)
Your company account and staff.
system
Client practices
One space per client.
system
Patients, encounters, claims, statements
Belong to a practice.
Next
Walk it live, or open a related feature
A demo follows this path with synthetic data. Feature pages spell out capabilities, roles and guardrails for each piece.
Other workflows
The full RCM loop
From insurance on file to money in the bank, in one loop.
Claim status lifecycle
Every status a claim can be in, and how it gets there.
The human approval gate
AI can suggest. Only your team can send.
Denial workflow
From denial to resubmission, with a person at the wheel.
Patient payment workflow
From balance to paid, in the fewest taps possible.
Deep dive
What Tenancy Model means in daily ops.
Practical context for Tenancy Model: how teams use it, where it sits in the loop, and what to ask in a demo.
- Tied to how billing work actually splits
- Clear on human vs machine responsibility
- Links into related MEDBIX areas

Practice
Where this shows up on a busy day.
From morning eligibility checks to end-of-day posting, Tenancy Model connects to the queues your team already lives in.
- Morning coverage and claim build
- Midday scrub and approval
- Afternoon denials and patient pay

Control
Keep a person on the send button.
Whatever page you're on, MEDBIX keeps AI in a propose role. Approvals, posting and rule activation stay human.
- Named approvals
- Visible AI proposals
- Immutable audit trail


Next
Walk Tenancy Model live
Bring your payer mix and the friction you feel today. We'll map it onto sample data in thirty minutes.
- Sample data only
- Your questions drive the agenda
- Written follow-up after
Common questions
Can two billing companies share a practice?
Each tenant's data is separate; talk to us about your situation.
Can a practice move to a new billing company?
Let's discuss migration specifics on a call.
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.
