Who it’s for / Physician groups and MSOs
Every provider, times every location, times every plan.
A group does not credential a provider once. It keeps that provider current at every site they practice and every network it bills under.
| Plan | Service location | Group NPI · TIN | Effective |
|---|---|---|---|
| Regional Blue plan | Central campus | Group A · TIN ▮▮-▮▮▮1 | Eff 09 / 01 |
| Regional Blue plan | North Valley | Group A · TIN ▮▮-▮▮▮1 | Eff 09 / 01 |
| National commercial plan | Central campus | Group A · TIN ▮▮-▮▮▮1 | In review |
| National commercial plan | Mesa specialty | Group B · TIN ▮▮-▮▮▮7 | In review |
| Medicaid MCO | Chandler clinic | Group B · TIN ▮▮-▮▮▮7 | Submitted |
| Medicaid MCO | North Valley | Group A · TIN ▮▮-▮▮▮1 | Submitted |
One provider, entered once. The identity block is the same on every destination; only the service location, the contracting entity and the effective date change per enrollment.
The shape of the job
Your provider count is not the size of the job.
- A physician adds a second site
- A service location on every plan they participate in, and a change on the next roster cycle.
- A hire starts in six weeks
- A credentialing file, then an application per plan, each with its own effective date and none billable before it lands.
- A physician leaves in March
- A dated term on every plan. Miss one and it keeps listing them in September.
The plan’s roster and your record drift quietly. You find out on a denial.
What changes
One record, driven into every destination.
Not one system of record per workflow, joined by people retyping between them.
- 01
The provider keeps it
The file is theirs, maintained in their own app and attested on a date, rather than chased for a copy of something they already hold.
- 02
Locations are fields
A physician at four of your sites is one record carrying four locations, not four files that have to agree.
- 03
Plans take their own shape
The plan’s own form where you apply per provider; a roster file on the cycle where you are delegated. Same record, two doors.
- 04
Disagreement surfaces first
Roster ingest matches on NPI and puts every discrepancy in front of a person. Nothing is silently overwritten.
Nothing auto-submits. A coordinator resolves the flags and sends it.
When the group grows
An acquired practice arrives as a spreadsheet.
The providers are real and mostly fine. The handover is what you cannot trust.
Nothing in it says which expirations were typed rather than read off a document, or which enrollments were ever finished.
So Bip starts from the providers instead. Each holds and confirms their own file, and the spreadsheet is reconciled against it field by field, with every conflict going to a person rather than overwriting anything.
Questions we get
Groups and MSOs, plainly.
We run several entities and tax IDs. Does that work?
Do we need privileging?
What do our providers actually have to do?
Send us one roster file.
We will hand back the rows that disagree with the plan, and you can tell us which you already knew about.