b.well Connected Health: The $120M Infrastructure Play Quietly Powering Every Major Health AI Launch of 2026
Table of Contents
Introduction: The Un-AI Company
What b.well Actually Built
The Partnership Sequence That Changes the Story
The Technical Architecture Nobody Talks About
The Data Refinery as a Real Moat
Health Skills and the Product Roadmap Signal
The Competitive Risks Worth Taking Seriously
The Investment Thesis
Abstract
b.well Connected Health is a Baltimore-based health data infrastructure company founded in 2015 by Kristen Valdes and Bryan Jones. Total disclosed funding is approximately $116M across 10+ rounds, with the most recent being a $40M Series C in February 2024 followed by $20M in Trinity Capital growth debt in July 2025. The company has not publicly disclosed a valuation but is trading on Nasdaq Private Market.
Key facts: 2.4 million provider connections, 350+ health plan and lab connections, FHIR-native canonical data model, 13-step proprietary Data Refinery, four SDK surfaces (Web TypeScript, Android Kotlin, iOS Swift in progress, AI via MCP), white-label AI assistant called bailey, and a compliance product line tied to NCQA-certified digital quality measures.
Partnership sequence Oct 2025 through Mar 2026: Google (Oct 2025), SDK launch (Dec 2025), OpenAI/ChatGPT Health (Jan 2026), bailey white-label (Feb 2026), athenahealth point-of-care workflow (Feb 2026), Samsung/Kill the Clipboard (Mar 2026), Perplexity Health (Mar 2026).
Confirmed tech stack via sub-processor disclosure (effective Jan 5, 2026): AWS (infrastructure), Databricks (data processing), MongoDB (database), Redis (caching), Fivetran (ETL), Sigma Computing (analytics/BI), Groundcover (observability), Sentry (errors), Wiz (cloud security), Descope (identity), CLEAR (identity verification), CloudBees (feature flags), Mixpanel (app analytics), Iterable/Twilio (communications), [Tonic.ai](http://Tonic.ai) (synthetic data/de-identification).
Additional confirmed from GitHub and 2021 tech blog: Apache Kafka (event streaming), Elasticsearch (search), ClickHouse (OLAP analytics), GraphQL (query layer), CQL (clinical quality logic), Kubernetes/Helm (deployment), Python (data engineering), Node.js (FHIR API server).
Open investment questions: current valuation unknown, no disclosed revenue or customer metrics, iOS SDK still listed as coming soon, Torch acquisition by OpenAI creates internalization risk, Microsoft chose HealthEx over b.well for Copilot Health.
Introduction: The Un-AI Company
There is a company sitting at the center of the most important AI health launches of the past six months that has not raised a mega-round, has not been on the cover of anything, and most people in health tech have never heard of. That company is b.well Connected Health, and the reason it does not get written about is exactly the reason it is worth understanding. It is not building AI. It is building the thing AI needs before it can work in healthcare at all.
To get the full picture, back up to January 7, 2026. OpenAI announced ChatGPT Health, its dedicated health AI product that allows users to connect their actual medical records to their conversations with the model. The announcement was huge. The coverage was everywhere. The thing most of that coverage missed, buried in the press release, was that the health data connectivity infrastructure powering the whole thing was b.well. Not OpenAI’s in-house data team. Not a bespoke API integration built by some well-funded startup. A Baltimore company with under $120M in disclosed capital that had spent the better part of a decade building the plumbing nobody else wanted to build.
That is not a lucky break. By the time the OpenAI deal landed, b.well had already signed Google (October 2025), launched the first SDK designed specifically for health AI assistants (December 2025), introduced a white-label AI assistant called bailey (February 2026), partnered with athenahealth on bidirectional point-of-care data sharing (February 2026), expanded a two-year Samsung partnership into a full Kill the Clipboard implementation at HIMSS (March 2026), and signed Perplexity for its new health product (March 2026). That is five major platform partnerships in five months, each one with one of the most prominent technology companies on earth, all funneling through the same data layer.
The framing that matters here is infrastructure versus application. Applications get acquired, disrupted, or commoditized. Infrastructure, if it becomes the standard, gets buried into the foundation and stays. The question for investors and founders watching this space is whether b.well has actually become infrastructure, or whether it just looks that way from the press release cadence.
What b.well Actually Built
The company’s official description calls it a FHIR-native digital health platform with a connected health data network. That is technically accurate and almost completely useless for understanding what it does. Here is the more useful version.
b.well spent roughly a decade quietly onboarding as a trusted third party to every major payer and provider in the country, leveraging the information blocking rules and patient access API mandates created by the 21st Century Cures Act and CMS interoperability regulations. By the time those regulations had teeth, b.well already had two million provider connections and three hundred payer connections. That network is the foundation. Everything else, all the AI products, all the SDK surfaces, all the enterprise software, runs on top of that foundation.
The network connects through multiple interoperability rails simultaneously. Patient Access APIs mandated under ONC (g)(10), which are the richest data pathway because they require USCDIv3 content including unstructured clinical notes. TEFCA QHINs for the national exchange layer, though TEFCA only operates at USCDIv1, meaning it is less data-rich than the direct API connections. Regional HIEs and HINs. CMS Blue Button for Medicare. The VA. Proprietary pharmacy and lab networks. Payer claims APIs. The March 2026 technical blog post by Yelena Balin on the resource hub makes the competitive argument plainly: companies that claim 90% coverage by counting EHR vendor logos are using a meaningless metric because a single physician can document care across four different EHR systems at four different organizations, and if you are only counting vendor relationships you are missing three of those four. Real completeness requires NPI-level onboarding at individual clinic locations, not just system-level agreements.
On top of the network sits the Data Refinery. b.well describes it as a 13-step proprietary process that has been in development for a decade. What that means in practice is a pipeline that ingests data in every format healthcare has ever produced, including X12 claims, HL7 v2 messages, C-CDA documents, CSV files, and JSON APIs, converts everything into standardized FHIR R4 resources, and then runs a sequence of cleansing, validation, deduplication, normalization, enrichment, and compression steps before the data touches any downstream application or AI system. The CTO Imran Qureshi published a detailed technical walkthrough of this in January 2026 on the resource hub, including a worked example of a single prescription generating six separate records across EMR, HIE, pharmacy, insurance, patient app, and refill systems, each with overlapping but incomplete information, and how the refinery reconciles those into one clean current-state record. That is not a marketing story. That is the actual problem, and it is actually hard.
The refinery’s commercial importance for AI is the 10x LLM token reduction claim. Raw FHIR bundles are verbose, redundant, and expensive to process. A patient’s complete medication history as raw FHIR JSON might cost several hundred tokens per medication entry. The refinery compresses, reconciles, and structures that into a dense, AI-optimized representation. The compressed-fhir repository on GitHub is the technical implementation of that. Multiply the cost difference across every ChatGPT Health user who connects their records and runs health conversations, and the economic case for b.well sitting between the patient’s data and the language model becomes obvious.
The Partnership Sequence That Changes the Story
