The point of AI in healthcare isn't to cut cost. It's to expand capacity.
I lead Data & AI product at NYC Health + Hospitals, the country's largest public health system — building the products that help 45,000 staff serve more than a million patients a year. 15+ years in healthcare before that.
NYC Health + Hospitals runs 70+ sites and serves more than a million New Yorkers a year. I own the data and AI product function — 12 product managers, owners, and designers building the tools that help a stretched public system do more with what it has.
I rebuilt AbbVie's international commercial data platform to work like a SaaS product: country affiliates as API consumers, modeled on Stripe's developer experience. 50+ countries, 40+ engineers, $12B in annual sales riding on the platform.
Eight years building analytics products for 2,000+ hospitals, growing from PM to Director. I grew two SaaS products 32% a year, shipped ML-based data normalization across 400+ health systems, and led a Snowflake data-sharing strategy that four of the ten largest US health systems adopted.
At Truven (now IBM Watson Health) I advised health plans, employers, and providers on payment methodology, and launched a bundled-payment product — an $8M portfolio built on claims data from 200 million lives — that landed a Fortune 100 employer and leading academic medical centers.
I started in J&J's IT Leadership Development Program, rotating through three companies in two years. The rotation that mattered: 15 months on-site at 17 hospitals, working with bariatric surgery programs. I sat in patient support groups and watched people describe what the clinic's process actually felt like. That's where I learned that discovery happens at the frontline — and it's driven every product role since.
On turning fragmented HL7, claims, and clinical feeds into the canonical data model that lets a stretched public system see and serve more patients in real time — without waiting for full modernization first.
Joined leaders from Mayo Clinic, UPMC, and AKASA to argue that the point of AI in a public system isn't to cut cost but to expand capacity — reaching more of the million New Yorkers who depend on us with the finite staff and space we have, and funding clinical AI with the revenue-cycle wins that pay for it. Read the recap.
I've stayed in healthcare because of the patients I met in bariatric support groups fifteen years ago. Product work is how I can help the most of them at once.
Two convictions run through everything I build. Data products should work like APIs — composable, reliable, built for adoption, not for a screenshot in a steering-committee deck. And AI in a health system should be measured by the capacity it creates, not the cost it cuts. Today I apply both as head of Data & AI product for the largest public health system in the country.
I'm open to speaking on AI in public health systems, and I'm always up for comparing notes with leaders standing up data and AI teams — especially in Chicago.
Based in Chicago. Reach me at kevinclamb@gmail.com or on LinkedIn.
I build data and AI product organizations, not just products — hiring and coaching product managers, setting outcome-based roadmaps, and holding the line that adoption is the only metric that matters.
I'm at home in the modern data stack — Snowflake, Palantir Foundry, retrieval-augmented and agentic LLM systems — and in the messy realities of healthcare data: claims, HL7, FHIR, and hospital finance.