The platform
One provider record. Every workstream reads from it.
Credentialing, privileging and payer enrollment are not three products — they are three destinations for the same file, and each one draws a different part of it.
Provider recordProvider-held · identity-bound
- IdentityAuthenticated at enrollment
- State licensureAZ · exp 04 / 2028
- DEA registrationExp 11 / 2027
- EducationMD · 2009
- TrainingResidency · MFM fellowship
- Board certificationABOG · MFM
- Work history5 positions · no gaps
- MalpracticeCOI · exp 09 / 2026
- Sanctions screeningOIG LEIE · SAM
6 of 9 domains read · 0 re-collected
Select a destination to light the domains it reads. Fields are illustrative of the record’s structure, not of any one provider’s file.
Portability
The record travels. What each destination produces does not.
A board certification means the same thing at every facility. Permission to operate at one says nothing about the next.
| Travels with the provider | Belongs to the organization or the plan |
|---|---|
| Identity, authenticated once | Privileges granted under one facility’s bylaws |
| Licensure, DEA, education and training | The delineation form and its criteria |
| Board certification and work history | A plan’s application and its effective date |
| Malpractice history and sanctions screening | Roster membership and delegation status |
| Attestation and verification history | Committee approvals and FPPE conditions |
This is why one record is possible and one form is not.
Where to start
Six ways into the same file.
Every page below is a different workstream, and the same record underneath it.
Questions we get
The architecture, plainly.
Is this one product or six?
One record, with six ways of working on it. A credentialing team does not buy a file — they run onboarding, enrollment, privileging and reappointment, and each of those is a page here. What none of them do is collect the same data twice.
Where does verification happen?
Against the issuing source. Licenses are verified with the issuing state board by direct contact, exclusions are screened against OIG LEIE and SAM, and every check is written to the file with its date and its source. The destinations read that result rather than repeating it.
Does this replace CAQH?
No. CAQH is where health plans read a provider profile, and Bip aligns to that shape so a provider does not enter the same thing twice. Bip sits on the facility side, holding the file the provider owns. It complements CAQH; it does not replace it.
Facilities all have their own requirements. What is actually shared?
The record. Requirements, forms and privileges are local to one facility or one plan, and they stay there. Identity, licensure, education, training, work history and verification history mean the same thing everywhere, so a second organization inherits them instead of rebuilding them.
Bring one provider. We will walk all three destinations.
One file, everything it feeds, and nothing collected twice.