Practice ops
Multi-practice tenancy
One company account. Many client practices. Clean walls between them. Your billing company is the tenant. Each client practice sits underneath it with its own patients, encounters, claims and statements. Running fifteen clients across fifteen logins, or one shared spreadsheet, is how mistakes and data leaks happen. What ships here includes billing company as tenant; unlimited structure of client practices. Used day to day by admin, supervisor roles, with availability marked available. Open the sample screen on the right, then walk the steps below — or book a demo and put your hand on the same flow with synthetic data.
Northside Billing Co.
tenant · 12 staff
Lakeview Ortho
patients · claims · statements
Bayside Derm
patients · claims · statements
Cedar Family Med
patients · claims · statements
What it is
Your billing company is the tenant. Each client practice sits underneath it with its own patients, encounters, claims and statements. Billers can be scoped to specific practices. Other billing companies can never see your data.
The problem it solves
Running fifteen clients across fifteen logins, or one shared spreadsheet, is how mistakes and data leaks happen.
Process
How it works, step by step
- 1
Your company is the tenant
Everything you do lives inside your company account.
- 2
Add client practices
Each practice gets its own space for patients, claims and statements.
- 3
Scope your staff
Assign billers to the practices they work.
- 4
Isolation underneath
PostgreSQL row-level security keeps tenants apart at the database level.
What's included
Everything below is part of multi-practice tenancy today.
- Billing company as tenant
- Unlimited structure of client practices
- Practice-scoped billers
- Row-level security in PostgreSQL
- Company-wide views for supervisors
- Solo practices can be their own tenant
The guardrail
Isolation is enforced by the database, not just by the screens.
Where it fits: tenancy model
The structure that lets one billing company serve many practices without ever mixing their data.
- 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.
Audience
Who uses it
These roles work with this feature day to day. Access always follows what your admin assigns.
Works closely with
Deep dive
What Multi Practice Tenancy means in daily ops.
Practical context for Multi Practice Tenancy: 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, Multi Practice Tenancy 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
See Multi Practice Tenancy against your volume
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 a solo practice use MEDBIX?
Yes. They onboard as their own billing company tenant and act as the tenant admin.
Can practices log in themselves?
Practice staff can be users inside your company account with the right role.
Is data really separated?
Yes, by row-level security in PostgreSQL, not just by filters in the interface.
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.