What does not transfer
What you can reuse
Genuine savings, if your first-state hygiene was good:The Blues are separate companies
This surprises people expanding from a Blue-dominated market. “Blue Cross Blue Shield” is an association of roughly thirty independent licensee companies, each operating in its own geography. Your relationship with the Colorado Blue is not a relationship with the Arizona Blue: new contract, new credentialing, new everything. What does work across Blues is BlueCard, the program that lets you bill your local Blue for a member of an out-of-area Blue. That handles the traveling patient. It does not substitute for network participation where you have an office. See BCBS Association.Medicare in the new state
Medicare enrollment is federal but administered regionally through Medicare Administrative Contractors (MACs). Practically:- The new PC needs its own CMS-855B group enrollment
- Each clinician needs CMS-855I and a reassignment of benefits to the new group
- CMS-588 for EFT to the new PC’s bank account
- A different MAC may process it, with different local coverage determinations that affect medical necessity denials
Medicaid is a different program entirely
Not a variation, a separate program with its own statute, portal, provider types, screening levels, site-visit requirements, and revalidation cycle. Budget the most time here. And remember the two-layer structure: enrolling with the state Medicaid agency is necessary but often not sufficient. Most Medicaid beneficiaries are in managed care plans (Centene brands, Molina, regional plans), and each MCO requires its own contract and credentialing on top of state enrollment. A state with five Medicaid MCOs is six enrollments. See Enroll in state Medicaid.Managing the revenue gap
The new PC will have expenses for months before it has revenue. Handle it deliberately: Sequence the launch around enrollment, not the lease. Start payer applications the moment the new PC has an EIN and Type 2 NPI, before you sign a lease, before you hire, before you have a location. Applications don’t require an operating practice. Fund the gap properly. The MSO covering the new PC’s costs is fine; the MSO covering them with no documentation is not. Use a written intercompany promissory note with a real rate — no less than the applicable federal rate for the term — and a repayment schedule. See Intercompany loans between MSO and PC. Consider a phased opening. Cash-pay or self-pay services can start before network participation. Just be clear with patients about their out-of-network status and comply with Good Faith Estimate requirements for uninsured and self-pay patients under the No Surprises Act. See The No Surprises Act, briefly. Ask for retro-effective dates in writing at application time, not after. Some payers grant them; you will never get one you didn’t ask for.The tracking grid, expanded
Your single-state grid becomes a three-dimensional one. Track, per row:
At two states and three payers this fits in a spreadsheet. At five states and ten payers with twenty clinicians it does not, and credentialing software becomes worth its cost. See Track licenses, revalidations, and expirables.
Checklist
- New PC’s Type 2 NPI obtained
- Existing payers’ provider relations contacted about adding the new Tax ID
- Applications submitted before the lease, not after
- Medicare 855B, 855I, and 588 submitted for the new entity
- State Medicaid application submitted
- Every Medicaid MCO identified and separately applied to
- Clinician CAQH profiles updated with the new state license and location, and re-attested
- Retro-effective dates requested in writing
- EDI, ERA, and EFT enrolled per payer, with EFT pointed at the new PC’s account
- Revenue gap funded with a documented note, not an undocumented transfer
- Tracking grid expanded to entity × payer × clinician
Next
Banking and books for entity #3
Where multi-entity operations start to hurt.