What a CIN is

A clinically integrated network is not a legal entity type. It is a program, and it usually runs inside an entity that already exists: an IPA, a physician-hospital organization, or a health system subsidiary. What makes it a CIN is what the program does. It applies selective participation criteria, runs on shared clinical protocols and a common measure set, connects the data across practices that use different systems, and removes physicians who do not perform.

The label matters because of what it buys. Competing, independently owned practices get to sign one payer contract at one set of rates without committing price fixing, on the theory that the joint contracting is necessary to make the integration work.

Feb and Jul 2023
DOJ rescinded the health care antitrust policy statements in February 2023; the FTC withdrew them on July 14, 2023 by a 3-0 vote.
20% / 30%
The withdrawn safety-zone shares for exclusive and non-exclusive physician network joint ventures, by specialty, in a market.
2009 and 2013
The FTC advisory opinions on clinical integration, TriState Health Partners and Norman PHO, that still show what a passing program looks like.

Why clinical integration is the legal hinge

Start with the constraint. Section 1 of the Sherman Act treats naked price agreements among competitors as per se unlawful, and independently owned practices in the same market are competitors. If they get together and set a rate, the analysis is over before it starts.

Statement 8 of the 1996 FTC and DOJ health care policy statements described two ways a physician network joint venture escapes that treatment and gets judged under the rule of reason instead:

  • Substantial financial risk sharing. Capitation, a global fee for a defined set of services, or a meaningful withhold tied to network performance. This is the route most capitated IPAs take.
  • Clinical integration. An active, ongoing program to evaluate and modify practice patterns and create real efficiency, where joint contracting is reasonably necessary to the program.

The second route is the CIN. The same statement set safety zones for the first: non-exclusive physician networks with 30 percent or fewer of the physicians in each specialty with active hospital privileges in a market, and exclusive networks with 20 percent or fewer.

The FTC then applied that standard case by case. TriState Health Partners (April 13, 2009) and Norman PHO (February 13, 2013) were both physician-hospital organizations proposing joint fee-for-service contracting on the strength of a clinical integration program, and in both the FTC said it had no present intention to challenge the arrangement. Norman's review took roughly a year and nine months, which is a fair signal of how much documentation the standard takes.

What clinical integration actually requires

Across the 1996 statement and the advisory opinions applying it, the same elements keep showing up. A network that has all of them is defensible. A network missing the last two is a contracting vehicle wearing a lab coat.

  • Selective membership. Written participation criteria, applied. Everyone who applies getting in is a bad fact.
  • Shared, interoperable data. Physicians can see each other's performance and their patients' records across the network.
  • Clinical protocols and a measure set. Written, adopted by the physicians, with targets.
  • Active performance review. Someone reviews the data, gives feedback, and follows up on outliers.
  • Remediation and removal. Physicians who do not improve leave the network. This is the element most often missing.
  • Physician investment. Money and, more importantly, committee time.
  • Contracting tied to the program. Joint negotiation limited to what the integration needs, with non-exclusive membership so practices can still contract on their own.

What the 2023 withdrawal changed, and what it did not

On July 14, 2023 the FTC withdrew both the 1996 statements and the October 2011 statement on ACOs in the Medicare Shared Savings Program, saying they were "outdated and no longer reflect market realities" and that the Commission would "continue its enforcement by evaluating on a case-by-case basis" using general antitrust principles. The vote was 3-0. DOJ had rescinded the same statements in February 2023.

What went away is the map: the numerical safety zones and the written description of what a passing clinical integration program looks like. What did not go away is the law. Restraints that are genuinely ancillary to a real integration still get rule-of-reason treatment, and the FTC's own advisory opinions remain published and remain the clearest account of how the agency thinks about these programs.

The practical effect is that a network formed today has no share threshold to sit under and no safe harbor to cite. Documented program activity is what a CIN has instead, which raises the cost of running one and raises the cost of faking one.

CIN vs ACO vs IPA

The three answer different questions. A CIN answers "why is joint contracting lawful here." An ACO answers "which payer program are we accountable under." An IPA answers "how are these practices organized to contract at all."

CINACOIPA
What defines itA clinical integration program that makes joint contracting lawfulParticipation in a payer program holding it accountable for the cost and quality of an attributed populationA contracting entity of independently owned practices
Where the rules come fromAntitrust law and FTC and DOJ enforcementProgram rules, such as 42 CFR Part 425 for the Medicare Shared Savings Program42 CFR 417.1 and payer delegation requirements
Who it contracts withCommercial payers, usually fee-for-service with incentivesMedicare, or a commercial payer running the modelHealth plans, usually Medicare Advantage or Medicaid managed care
How providers are paidNegotiated rates plus incentives tied to the measure setFee-for-service plus shared savings, and losses in two-sided tracksCapitation, or fee-for-service against a risk pool
Does it require clinical integrationYes, that is what makes it a CINNot as an antitrust matter; program rules require care coordinationNo, if the network shares substantial financial risk instead

These overlap constantly in practice. One organization can run a CIN for its commercial contracts, an MSSP ACO for its Medicare fee-for-service population, and an IPA holding capitation for Medicare Advantage, with largely the same physicians in all three.

How a CIN runs day to day

The governance is the visible half: a physician-majority board, a clinical integration committee that owns the measure set, a credentialing or membership committee that applies the participation criteria, and a payer contracting committee.

The operating half is measurement. The network picks a measure set, usually anchored on HEDIS and Star Ratings measures the payers already use, aggregates data across practices that run different EHRs, produces physician-level results, tiers or ranks them, distributes incentive dollars against them, and runs a remediation track for the bottom group. Every one of those steps has to actually happen and be documented, because the documentation is the antitrust file.

Where CINs fall apart

Integration on paper. A committee charter with no committee, a measure set with no consequence, a data platform nobody logs into. It is the most common failure and the most dangerous one, because the joint contracting continues regardless.

Assuming the ACO does double duty. Running an MSSP ACO is not clinical integration for antitrust purposes, and the FTC withdrew the ACO statement along with the 1996 statements.

Never removing anyone. If no physician has ever left for performance, the participation criteria are decoration.

Measuring from claims alone. Claims arrive months late and miss the clinical results a measure set depends on. Feedback that lands in September about January's care changes nothing.

One report per payer. The network's own measure set gets buried under six plan gap lists in six portals, and the physicians stop reading any of them.

How Pelica supports a CIN

A CIN's obligation is to measure and change practice patterns across practices it does not own. That is a data problem for about a week and a workflow problem forever after.

Pelica pulls claims, EHR, pharmacy, lab, and ADT feeds into one member record, computes gaps continuously against the current HEDIS and Star Ratings specs rather than in a quarterly batch, and produces provider-level scorecards and practice visit agendas the network's staff can take into a practice. At HealthCare Partners, weekly assignment prep went from 8 hours to 15 minutes and quality gap closure improved 41%.

Related terms

An IPA is the entity a CIN program most often runs inside. An MSO supplies the administration behind it. An ACO is the program-defined cousin, and MSSP is the Medicare program most ACOs join. Capitation is the financial-risk route to lawful joint contracting, and value-based care is the shift that makes any of it worth the trouble.

Sources