The most revealing CareFlowIQ sales pitch is not about artificial intelligence. It is about a PDF. A primary-care doctor describes receiving a 115-page patient record and having neither the time nor the appetite to march through it line by line. Somewhere inside are medications, lab results, diagnoses, stale duplicates and perhaps the one fact that changes today's decision. The record is technically available. Practically, it is hiding.
Milliman Pluritem Health built a company around that distinction. Its CareFlowIQ platform retrieves medical information from EHRs, national health networks, HL7 and FHIR feeds, notes, PDFs, faxes, images, devices and pharmacy records. Then it does the thankless middle work: matching identities, resolving conflicts, removing duplicates, standardizing codes and units, restoring context, and linking every cleaned detail back to a source. The output is a longitudinal patient story a clinician can search, or structured data a healthtech team can consume through an API.
This is enterprise plumbing dressed for a clinical shift. It also explains why a ten-person company from Asheville, North Carolina, made sense to Milliman, the global actuarial and consulting firm that acquired Pluritem Health in August 2024. Milliman did not disclose the price. Pluritem did not disclose conventional venture rounds or revenue. The visible evidence is what the buyer did next: it kept the team, put the platform beside its healthcare risk expertise, and launched it under the CareFlowIQ name in October 2025.
“Reliable clinical data infrastructure is deceptively complex and typically underestimated.”Chris Fierer, product leader, IntelliScript
The product is an assembly line, not a magic trick
CareFlowIQ explains itself in six verbs. Acquire the source material. Transform it into usable structure. Consolidate the overlapping versions. Refine names, codes, dates and units. Analyze care gaps, utilization and trends. Deliver the answer through a web interface or secure API. The sequence is useful because it shows where healthcare AI usually breaks: long before a model makes a prediction.
The whole-patient view is the clinician-facing expression of that pipeline. It puts recent findings, care gaps, risk flags and trends near the surface, without asking a doctor to toggle among documents. Healthtech customers buy the same engine for a different reason: they can add clinical retrieval and normalization to an analytics tool, patient-engagement app or treatment platform without staffing their own interoperability department.
Two old friends picked an old problem
Ben Newton and John Clark founded Pluritem Health in 2021. They were longtime friends with complementary scars. Newton had spent more than two decades in enterprise software, leading product and sales teams through three IPOs and working across security, automation, analytics and AWS. Clark had worked in practical machine learning and clinical-data ingestion, including at Gliimpse, which Apple acquired before incorporating its work into Apple Health. Their premise was not that healthcare lacked records. It was that healthcare had plenty of records arranged badly.
Gary Wald joined as chief operating officer in 2023, bringing an operator's view of telehealth. He was an original founder of Teladoc and had worked at Medtronic MiniMed, Verizon and NBC. That mix matters. Clinical interoperability is not merely a database problem. It crosses product design, security reviews, patient consent, clinical judgment, procurement and implementation. A clever parser without enterprise distribution becomes a science project; a polished dashboard without reliable inputs becomes confident decoration.
Who pays - and what it costs
CareFlowIQ is B2B enterprise SaaS. The buyer might be a direct-primary-care practice onboarding a new patient, an onsite clinic proving its impact, a care-management team hunting gaps, a self-insured plan watching population risk, or a healthtech company that needs clean data under its own product. The company says most organizations can begin retrieving data within days, with minimal setup. There is no public price list, seat rate or usage schedule. The Pluritem acquisition price is also undisclosed.
That opacity is ordinary in enterprise healthcare, where price depends on data volume, integration scope, security work and contracted support. It also means outsiders cannot calculate return on investment from a brochure. The proper question is narrower: does the platform cost less than the integration engineers, clinical abstractors, delayed launches, duplicated tests and missed care opportunities it replaces? Every prospect must supply its own numbers.
Subscription price: not public. Acquisition value: not public. Traditional funding: not announced. The defensible buying case is avoided build cost plus time returned to clinical and product teams.
What failed first?
There is no public postmortem describing a failed Pluritem product or a dramatic founder reversal. The failure in this story is the industry workflow the founders chose to attack. EHRs are optimized around individual institutions. Claims are built for payment and often arrive well after care. Exported records become bulky documents. Names, dates and codes conflict. The patient crosses systems; the context does not reliably follow.
That is also the cleanest answer to what changed Milliman's mind. No private deliberation has been published, but its stated acquisition logic was direct: Pluritem complemented Milliman's healthcare intelligence products and could multiply the analytic capabilities offered to clients. The relaunch made the thesis visible. CareFlowIQ combined Pluritem's clinical-data pipeline with Milliman's risk models and healthcare expertise, then offered the package to both care providers and software builders.
Three layers, three different jobs
Illustrative utility for point-of-care decisions - not a measured performance claim. Claims remain essential for financial analysis.
Proof arrives as partnerships, not fireworks
CareFlowIQ's public progress is concrete but still early. In November 2025, it added Surescripts Medication History for Reconciliation. The integration brings a 12-month prescription history, including cash-pay transactions, patient matching and data delivered within 24 to 48 hours of pharmacy activity. Medication reconciliation is exactly the kind of boring, consequential workflow that fits the company: the value is finding the drug a patient forgot to mention before another one is prescribed.
In January 2026, Heuro Health selected CareFlowIQ for its obesity and metabolic-care platform. Heuro plans to segment patients into medical cohorts and monitor measures such as HbA1c, weight trajectory, adherence and comorbidity improvement. That relationship moves CareFlowIQ from a general data promise into a specific loop: identify risk, tailor care, watch the markers, adjust. The company also presents relationships with Hint Health and AWS, while Lantern Health physician Ben Aiken supplies the memorable 115-page-PDF testimonial.
What builders can copy
The transferable lesson is not “start a healthcare data company.” Regulation, long sales cycles and brittle integrations make that advice almost comic. The useful pattern is to locate a necessary layer that customers repeatedly underestimate, solve it against ugly production inputs, and package one engine for two adjacent buyers. Pluritem gave clinicians a usable view and developers an API. Milliman added brand, risk expertise and distribution.
Lead with the 115-page PDF and the time returned, not the sophistication of the parser.
A result is easier to trust when the user can inspect where each fact came from.
Let operators use a finished workflow while builders consume the same capability by API.
The right acquirer or partner already sells to the people who feel the problem.
Where the wager breaks
CareFlowIQ cannot produce a complete story when the underlying data is unavailable, incorrectly matched or never recorded. FHIR compliance does not guarantee semantic agreement. An accurate summary still fails if it arrives outside the clinician's workflow, floods the screen with alerts, or cannot explain its source. A buyer without data rights, governance, an accountable implementation owner and a specific decision to improve will simply purchase a tidier silo.
Nor is clinical data automatically superior for every job. Claims remain useful for cost, utilization and reimbursement analysis. Native EHR tools may be enough for a small practice living inside one system. Large organizations with mature interoperability teams may prefer to build. CareFlowIQ is most persuasive when records cross institutions, unstructured documents matter, speed has economic value, and the customer lacks the desire - or the patience - to maintain the plumbing.
The company sits in a crowded market alongside interoperability networks, clinical-data APIs, EHR-native analytics and internal engineering teams. Its differentiation is the attempt to join retrieval, normalization, clinical logic, analytics, provenance and delivery. Whether that bundle wins will be determined less by an AI slogan than by precision in ordinary moments: the right medication, the missed gap, the useful fact on page 87 appearing before the appointment ends.