Turning Healthcare Data Into
Actionable Care
Thesis
Transforming claims and quality data into workflows care teams could actually act on.
At Envolve, I led product development of claims-driven care-gap capabilities that translated HEDIS measures and payer data into actionable workflows for case managers, care support representatives, and health coaches.
Project snapshot
Company: Centene Corporation / Envolve
Role: Product Owner, Patient & Care Management Applications
Scope: Medicaid, Medicare, Marketplace; claims data; HEDIS; care management
My contribution: Product development, workflow design, intervention protocols, clinical/data translation
Users: Case managers, care support representatives, health coaches
Headline outcome: Scalable care-gap identification and intervention workflows across multiple lines of business
The problem
Healthcare organizations already had enormous amounts of data.
The challenge was making it useful at the point of care-management work.
Claims could indicate that a service may not have occurred. HEDIS measures could define the quality requirement. But exposing those data points alone still left the care-team user to determine what they meant and what to do next.
That cognitive burden limited the value of the underlying data.
The insight / strategy
The product's job wasn't simply to identify a care gap.
It needed to help close one.
That changed the unit of design from information to action.
Instead of asking how to surface more clinical and claims data, I focused on what a care-team user needed to understand, decide, and do once a potential gap had been identified.
Outcomes
We established claims-driven care-gap identification and intervention workflows supporting Medicaid, Medicare, and Marketplace populations.
The source material doesn't give us a defensible downstream clinical-outcomes metric for this particular initiative, so I would not put a manufactured percentage here. The portfolio is stronger if the outcome accurately reflects what we know.
Critical product decisions
A key distinction was separating what the data could tell us from what the user should do about it.
The product couldn't simply assume that a missing claim represented clinical truth.
Claims are an input into the workflow. The experience still needed to support appropriate interpretation and intervention by the care team.
That shaped how we surfaced information and where human judgment remained part of the process.
What I built / led
I led development of capabilities that mapped payer claims against HEDIS quality measures to identify open care and quality gaps across Medicaid, Medicare, and Marketplace populations.
I then designed care-gap action workflows and intervention protocols that translated those findings into structured next steps for case managers, care support representatives, and health coaches.
The work required close partnership across clinical, data, technology, and operations to turn complex healthcare rules into usable product behavior.
Leadership & scale
The product sat between multiple domains: healthcare data, clinical-quality measures, care-management operations, and software development.
My role was frequently one of translation—turning clinical and operational requirements into product behavior while making technical constraints understandable to nontechnical partners.
The resulting workflows needed to function across multiple populations and lines of business rather than solving for one isolated program.
What I took forward
Data creates product value when it changes what someone can do.
That idea has followed me through clinical platforms, personalization, analytics, and AI.
The interesting product problem is often the last mile between knowing something and taking the right action because of it.