---
title: "Cityblock Health Is Medicaid Care Infrastructure, Not a Clinic Chain"
canonical: "https://theupsidejournal.com/articles/cityblock-health-medicaid-care-infrastructure/"
published: "2026-11-03"
column: "The Stack"
author: "Olusegun (Olu) Olufunmiloye"
subtitle: "The conventional description treats Cityblock as a healthcare provider that happens to use software. That description is directionally true and analytically thin. A provider sells services to patients"
description: "Cityblock Health's partner releases describe a Medicaid care coordination layer built on plan partnerships: five parts, what each source discloses and omits."
---

# Cityblock Health Is Medicaid Care Infrastructure, Not a Clinic Chain

*The conventional description treats Cityblock as a healthcare provider that happens to use software. That description is directionally true and analytically thin. A provider sells services to patients*

## Executive Summary

Cityblock Health is not best read as a clinic chain or a health-technology company. The partner announcements it has issued disclose a coordination layer: a multidisciplinary care team, round-the-clock access, purpose-built technology, and a payment relationship with a Medicaid plan. The repeated plan-partner structure shows that the unit of distribution is the **payer relationship**, not the patient. This article reads those disclosures as a system with five parts, states which source discloses each part, and lists what the sources do not state, including payment terms and outcome figures.

## Introduction: why is Cityblock usually described as a provider?

The conventional description treats Cityblock as a healthcare provider that happens to use software. That description is directionally true and analytically thin. A provider sells services to patients or bills for visits; a company in Cityblock's position is introduced to the public through announcements with Medicaid health plans, and each announcement is framed around a defined group of plan members, not around walk-in demand.

The founder story is covered in [the profile of Toyin Ajayi and the Medicaid infrastructure she helped build](https://theupsidejournal.com/articles/toyin-ajayi-cityblock-medicaid-infrastructure/), and is not repeated here. This piece does a different job. It treats Cityblock the way an operator would: as a machine, asking what it is calibrated to do, which parts can be verified from public statements, and which parts are invisible from outside.

The evidence is deliberately narrow. Every statement below about Cityblock comes from two partner announcements, and every statement about Medicaid comes from a federal enrollment report, all read between 29 and 30 October 2026. Cityblock's own website was not used, and no outcome figure from any source is stated.

## What does the public record actually say Cityblock does?

Two dated announcements carry the record. The first was issued on 7 February 2024 and describes a partnership with Fidelis Care in New York. The second was issued on 7 January 2026 and describes a partnership with Meridian Health Plan of Illinois.

The Fidelis release states that the partnership covers eligible members of Fidelis Care's Medicaid Managed Care and HealthierLife (HARP) plans in the New York City area and Long Island who have complex medical and behavioural health conditions. It lists a care team that includes primary care providers, behavioural health specialists, community health partners, nurse care managers and pharmacy navigators. It says Cityblock offers round-the-clock access and, in the company's words, that "modern technology is at the core of our care model", using custom-built tools for care team operations and member interactions.

The Meridian release states that the partnership will serve 10,000 Medicaid beneficiaries across 17 counties in the greater Springfield and St. Louis Metro East areas of Illinois. It describes the model as built on multidisciplinary clinical expertise, purpose-built technology and data insights, plus an engagement strategy. It says wrap-around services are available around the clock and cover primary and urgent care extension, behavioural health and social care, among other areas, and that clinical pharmacy and care management are included.

Read together, the two releases describe the same architecture in two states. The verdict follows from the text: the public record describes a defined population served by a standing team, not a clinic that members choose to visit.

## How is the system built? Five parts and what discloses each

A system explained as a list of services hides its structure. The more useful reading separates five parts: clinical care, behavioural care, social care, technology, and the plan payment relationship. Each part is examined below against the source that discloses it. The reading of how the parts fit together is this article's inference, labelled as such; the facts about each part are the sources' own.

### Clinical care: who delivers it?

The Meridian release states that care is delivered by licensed physicians and other practitioners employed by Cityblock Medical Practice, P.A. That detail matters because it identifies who holds the clinical relationship: the clinicians' employer is Cityblock Medical Practice, P.A. The Fidelis release adds the roles around the physician: nurse care managers, pharmacy navigators and primary care providers.

The Meridian release also lists clinical pharmacy within the service set. For an operator, the point is that pharmacy sits inside the care team's remit instead of downstream of it. Neither release describes caseload sizes, staffing ratios or visit frequency, so the intensity of clinical contact cannot be stated from public sources.

Verdict: clinical care is the visible layer of the system, and it is also the layer least informative about how the system earns its place.

### Behavioural care: is it a referral or part of the team?

Both releases place behavioural health inside the model rather than beside it. The Fidelis release names behavioural health specialists in the care team, and the population it describes is defined by complex medical *and* behavioural health conditions together. The Meridian release lists behavioural health among its wrap-around services.

The architectural implication is a reading, not a disclosed fact: when behavioural specialists sit on the same team as primary care and care management, the handoff that normally happens between separate organisations becomes an internal one. The releases do not say how many members use behavioural services, or how referrals to outside providers are handled.

Verdict: the disclosed design removes an organisational boundary; the sources do not show how much traffic crosses what used to be that boundary.

### Social care: what does the model include beyond medicine?

The Fidelis release lists community health partners in the care team. The Meridian release lists social care among the wrap-around services. Neither release defines what social care consists of, which services are delivered directly, or how they are paid for. That silence is itself informative: the coordination layer includes a function that medical billing does not conventionally cover, and the public record does not state its cost.

Verdict: social care is disclosed as a role in the model and undisclosed as a line of cost, so any claim about its economics goes beyond the evidence.

### Technology: what does it do inside the model?

The Fidelis release says Cityblock uses custom-built tools for care team operations and member interactions. The Meridian release says the technology gives the care team a data-driven view of member needs and risks. Those two statements identify two functions: managing the team's work, and surfacing member risk to the team.

Neither release names a product, a data source, or a measured effect. Claims that Cityblock's technology reduces cost or improves outcomes cannot be sourced from these releases. The Fidelis release does record the company's own statement that round-the-clock access helps reduce unnecessary emergency department visits and inpatient admissions; that is a company claim and no figure accompanies it.

Verdict: technology is the connective tissue the sources describe, and the sources describe its purpose without measuring its effect.

### The plan payment relationship: why does it define the unit of distribution?

Each announcement is a partnership with a Medicaid plan. The Meridian release identifies Meridian as a company of Centene Corporation and states that this is the fourth regional partnership between Centene and Cityblock. It also states that the Centene–Cityblock partnership exists in New York, Ohio and Florida in addition to Illinois, and that Cityblock partners with plans and health systems across more than ten states.

The structure carries the argument. On this article's reading, a new market opens when a plan partnership defines a group of members to serve, and the release states the group's size before it states anything about services. The payment terms between Cityblock and its plan partners are not disclosed in any source read, and this article does not estimate them.

Verdict: on this article's reading, the thing Cityblock is selling into is the plan relationship, which is why the announcements can be read as distribution agreements, though neither release describes them that way.

## How does the framework compare across sources?

| Part of the system | What the sources disclose | Disclosing source | What is not stated |
| --- | --- | --- | --- |
| Clinical | Licensed physicians employed through Cityblock Medical Practice, P.A.; nurse care managers; pharmacy navigators; clinical pharmacy | Meridian release (7 Jan 2026); Fidelis release (7 Feb 2024) | Staffing ratios, visit frequency |
| Behavioural | Behavioural health specialists in the care team; population defined by medical and behavioural conditions | Fidelis release; Meridian release | Utilisation, referral handling |
| Social | Community health partners; social care as a wrap-around service | Fidelis release; Meridian release | Scope, cost, delivery model |
| Technology | Custom-built team and member tools; data view of member needs and risks | Fidelis release; Meridian release | Product detail, measured effect |
| Plan payment relationship | Defined member group per plan; repeated plan partnerships | Meridian release; Fidelis release | Payment terms and structure |

Verdict: three of the five parts are disclosed as roles and none is disclosed as a cost, which is the gap an investor or operator would need to close before treating the model as portable.

## Why does the Medicaid managed-care structure matter here?

The plan relationship is not incidental, because most Medicaid enrollees are already in plans. The federal Medicaid managed care enrollment report for data as of 1 July 2023, published with a Winter 2026 cover date, records 99,780,667 Medicaid enrollees, of whom 76,433,074 were in comprehensive managed care, or 76.6 percent. By calculation from those two figures, 23,347,593 enrollees were outside comprehensive managed care. The report counts Medicaid enrollees.

That distribution explains the commercial logic the announcements reveal. A company that wants to serve Medicaid members at scale meets most of them through a plan, and the plan is the party that holds the member relationship and, in the report's term, the managed care contract. The 2023 data point is the latest year in the report read; enrollment has since changed and this article does not estimate the current figure.

Scale comparisons need care. The Meridian release says Cityblock serves more than 100,000 members and that the Meridian partnership will serve 10,000. By calculation, the Meridian group is therefore at most 10 percent of Cityblock's stated member total, since the stated total is a floor. The figure for the whole Medicaid population is far larger, and this article draws no conclusion about Cityblock's share of it.

Verdict: the plan is where Medicaid members are, so a model that distributes through plans is following the market's structure, not creating a new channel.

## Where Cityblock fits: what this article does not cover

Three boundaries keep this piece to its job. The founder's biography belongs to the profile linked above. The wider argument that Medicaid is an infrastructure problem, as opposed to a coverage problem, belongs to a forthcoming article and is not made here. The transferable operator framework drawn from Cityblock's approach belongs to a later playbook article. Workforce infrastructure, the supply side of clinical labour, is covered in [the analysis of Iman Abuzeid and Incredible Health's workforce infrastructure](https://theupsidejournal.com/articles/iman-abuzeid-incredible-health-workforce-infrastructure/), which is the right comparison: that case builds the supply of clinicians, while Cityblock coordinates the delivery of care to a defined group of members.

The architecture also has a close parallel in a different sector. [The explainer on Zilch and consumer credit infrastructure](https://theupsidejournal.com/articles/zilch-digital-consumer-credit-infrastructure/) follows the same form, an apparently consumer-facing product resting on a decisioning and data layer. Likewise, [the Esusu rent-reporting case](https://theupsidejournal.com/articles/esusu-rent-reporting-credit-infrastructure/) shows a data pipeline turned into infrastructure that other institutions depend on. Cityblock's coordination layer is the healthcare version of the same pattern, with the plan in the position that lenders and credit bureaus occupy in those cases.

These cases belong to the wider thesis in [the pillar on the rise of diaspora operators](https://theupsidejournal.com/articles/the-rise-of-diaspora-operators-how-african-founders/), which places Cityblock among founders who built institutional infrastructure in sectors outside the usual technology categories.

## Why this matters for investors and operators

For investors, the disclosed structure changes the diligence question. A provider is assessed on utilisation and margin per visit. A coordination layer delivered through plan partnerships is assessed on the durability of the plan relationship, the terms under which the plan pays, and the evidence that the model changes outcomes. The sources read supply the first element, a repeating partnership pattern, and none of the other two.

For operators in healthcare, the model suggests that the contract with the payer is the product definition. The services listed in the releases are what the team delivers; on this article's reading, the partnership that defines the member group is what makes delivery possible. An operator designing a comparable model would begin with the payer agreement and work backwards to the care team, not the reverse.

For policy and plan executives, the announcements describe a partnership to serve a defined group of members; on this article's reading, the plan keeps the member relationship, though neither release says how responsibility is divided. Whether that arrangement lowers cost for the plan is not established by any source read here.

## Key Takeaways

- Cityblock's public record describes a coordination layer between Medicaid plans and fragmented services, not a clinic network or a software product.
- The five parts of the system are clinical, behavioural, social, technology and plan payment, and the sources disclose all five as roles but none as a cost.
- The unit of distribution is the payer relationship: each announcement defines a plan's member group before it describes services.
- With 76.6 percent of Medicaid enrollees in comprehensive managed care as of 1 July 2023, a plan-based channel follows the market's structure.
- Payment terms and outcome figures are absent from every source read, so claims about the model's economics remain unestablished.

## Conclusion

The record read for this article supports one reading of Cityblock: a standing multidisciplinary team, supported by purpose-built technology, delivered to a defined group of plan members under an agreement with the plan. It does not support claims about cost, outcomes or payment terms, and this article makes none. The next articles in the series take the structural problem and the transferable operating model; both depend on the payment and outcome evidence that the public announcements leave out.
