Free Network Build Assessment
Score your buildIndependent Practice Association (IPA) contracts can simultaneously solve dozens of specialty gaps with a single agreement, or create single-point-of-failure network risk. Here's how to evaluate and structure IPA relationships in a network build.
An Independent Practice Association is a legal entity formed by independent physicians, physicians who maintain their own individual practices, to contract collectively with payers. The key distinction from a medical group is ownership and employment structure: in a medical group, physicians are employed by or are partners in a single practice entity. In an IPA, member physicians remain independent; they contract individually with their own patients and run their own practices, but they delegate contracting authority to the IPA for purposes of health plan negotiations.
A Physician-Hospital Organization (PHO) combines hospital and physician interests under a single contracting entity, creating a hybrid structure that includes both facility and professional services. IPAs, by contrast, are physician-only. This distinction matters for adequacy purposes because an IPA agreement covers professional services from member physicians but does not automatically include facility services at any affiliated hospital. Plans contracting with an IPA for network adequacy are contracting for physician professional capacity, not institutional capacity.
IPAs vary enormously in their governance, membership depth, and geographic coverage. Some IPAs are loose associations of a few dozen primary care physicians in a single county. Others are regional entities with hundreds of member physicians across multiple specialties and geographies. Understanding the specific IPA's composition, which specialties, which counties, and how many providers per category, is essential before any adequacy model credit is assigned to an IPA relationship.
The most compelling case for IPA contracting is administrative efficiency. When an IPA has executed the authority to contract on behalf of its member physicians, a single participating provider agreement with the IPA covers all member physicians simultaneously. A well-constructed IPA agreement in a specialty-rich market can replace dozens or hundreds of individual provider agreements, each of which would otherwise require individual negotiation, separate credentialing of the entity, and ongoing contract management.
This efficiency advantage is most pronounced in markets where independent practice remains robust. In those markets, a regional IPA may represent the most efficient path to broad specialty coverage across a multi-county service area.
From a rate negotiation perspective, IPA agreements also allow plans to establish a single fee schedule framework across a large provider group, simplifying billing and claims adjudication. Individual provider agreements in the same specialty can result in significant fee schedule variation within a plan's network, which creates member confusion and claims complexity. An IPA agreement with a single rate structure for all member physicians in a category eliminates that variation within the IPA's membership.
For plans entering a new market or expanding into new counties, IPA relationships can accelerate the time to an adequate network. Instead of spending months building one-off provider relationships across a multi-county geography, a plan that identifies and contracts the dominant IPA in that market can stand up a substantial network framework much sooner, with individual contracting filling residual gaps in categories the IPA doesn't cover.
One of the most important operational questions in IPA contracting is the credentialing model. In most plans, a provider isn't loaded as participating until credentialing is approved. For IPA contracts, that can be handled in two ways: the plan can credential each IPA member physician individually through its own program, or the plan can delegate credentialing to the IPA under a formal delegation agreement.
Delegating to an IPA is efficient but introduces risk if the IPA's program doesn't meet the standards the plan is held to. Under a delegation agreement, the plan remains responsible for the outcomes even though the IPA is performing the work.
Plans entering a delegation arrangement should audit the IPA's credentialing program before signing and on a regular schedule after that. The audit should assess whether the IPA is performing all required primary source verifications, keeping up with recredentialing, and appropriately excluding providers with adverse actions. Make sure the agreement gives the plan audit rights.
Timing matters too. If the IPA performs credentialing, its cycle, which may differ from the plan's own, determines when newly joining physicians are ready. Build the IPA's turnaround time into your build schedule.
A credentialing delegation agreement is a formal contract that authorizes the IPA to perform credentialing and recredentialing on the plan's behalf. It should cover the scope of delegated functions, the IPA's obligations for reporting adverse actions to the plan, the plan's audit rights, and what happens if the IPA's program falls short. If your plan is accredited, check the current NCQA or URAC standards for what the agreement must contain.
Delegation audits should use a standard tool that evaluates the IPA's program across several areas: primary source verification, timeliness of credentialing decisions, recredentialing compliance, sanctions screening frequency, and peer review. NCQA's verification time limits are set element by element, so check file ages against the current table rather than a single flat limit.
Beyond credentialing, plans may also delegate other functions to IPAs: utilization management, quality improvement activities, and in some cases claims processing. Each delegated function needs its own terms and oversight. Make sure the oversight program covers all delegated functions, not just credentialing.
The efficiency of IPA contracting comes with a corresponding concentration risk that many plans underestimate until they experience it. When a single IPA agreement accounts for a substantial portion of your contracted capacity in a specialty or county, the termination of that agreement, or the IPA's dissolution or restructuring, creates an outsized adequacy impact compared to the loss of any individual provider.
IPA concentration risk is especially pronounced in markets where a dominant regional IPA has aggregated the majority of independent specialist capacity. If that IPA holds most of your contracted cardiologists across a multi-county service area and terminates its agreement, you face a gap across every one of those counties at once. Individual provider contracting may not fill it fast enough.
Network operations teams should track how much of each specialty in each county depends on one IPA, and set a limit that fits their risk tolerance. IPAs above that limit should have a contingency plan in place before anything goes wrong, including ongoing relationships with individual providers who could be contracted directly.
IPA financial health and governance stability are also risk factors worth monitoring. IPAs that are financially stressed, experiencing member physician departures, or undergoing governance disputes are higher-risk contracting partners. Network intelligence about IPA stability, available through industry contacts, provider relations field teams, and market monitoring, should feed into your ongoing network risk assessment.
CMS scores the providers and locations on your HSD tables, not the contracting entity. So an IPA contract doesn't itself satisfy adequacy. What counts is where each member physician actually practices. Because CMS's criteria aren't restricted by county boundaries, a group of cardiologists clustered in one county can help a neighboring county only if enough of that county's beneficiaries are within the time and distance limits.
Each IPA member physician must appear on your HSD tables with the right specialty and the practice location where they see patients. CMS's guidance says providers must be listed at the office where they see patients for consultations, so using the IPA's corporate address will misplace them.
Open panels matter too. IPA agreements that don't require member physicians to take plan members, or that don't give the plan visibility into panel status, can produce adequacy on paper that members can't use. Separately, since the CY2024 rule, 42 CFR 422.112(a)(6)(i) sets appointment wait-time standards in MA for primary care and behavioral health, so availability is a requirement of its own.
The decision framework for IPA vs. individual contracting should be driven by market structure, adequacy gap analysis, and risk tolerance rather than administrative preference. In markets where independent practice remains robust and a well-organized IPA covers the specialties and geographies you need, IPA contracting is often the right primary strategy, because one agreement does the work of many.
In markets where IPA organizations are fragmented, poorly governed, or focused on specialties you don't need, individual provider contracting may deliver better adequacy outcomes even at higher administrative cost. A market analysis that maps available IPAs against your adequacy gap profile will quickly reveal whether IPA contracting is a primary solution or a supplemental one.
Individual contracting should always be pursued as a complement to IPA relationships in high-concentration risk situations. Even in markets where an IPA covers your primary adequacy needs, maintaining a portfolio of directly contracted individual providers in key specialties provides a buffer against IPA failure. Blueprint's adequacy scoring shows which providers a county depends on, which helps a team see where a county leans on one IPA's members.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.