In the complex landscape of modern healthcare, the ability to translate massive amounts of patient data into actionable clinical insights is often the difference between reactive treatment and proactive wellness. For many health systems, the default strategy has been to rely on third-party vendors to manage population health data. However, Corewell Health is challenging this norm by pivoting toward internal development to solve the persistent gap between clinical complexity and enterprise analytics.
Dr. Robert Jarve, the Associate Chief Medical Information Officer (CMIO) of Population Health at Corewell Health, suggests that the traditional reliance on external vendors often falls short when faced with the nuanced needs of a diverse patient population. By building their own patient-centered data models, Corewell Health aims to create a more precise bridge between the raw data collected in a clinical setting and the high-level analytics required to manage the health of an entire community.
This shift toward internal builds represents a broader trend in medical innovation where health systems seek greater control over their digital infrastructure to improve patient outcomes. For clinicians, the goal is to move away from rigid, vendor-defined metrics and toward a system that reflects the actual lived experience and medical needs of the patients they serve.
The move toward internal data modeling is not merely a technical upgrade but a strategic decision to ensure that population health management is driven by clinical reality rather than software limitations. As health systems grapple with increasing data volume and the need for more personalized care, the “build versus buy” debate is becoming central to healthcare policy and operational efficiency.
The Limitations of Vendor-Driven Population Health
Population health management involves the aggregation of patient data to identify health trends, manage chronic diseases, and allocate resources to high-risk groups. Traditionally, health systems have purchased software suites designed to automate these processes. While these tools offer scalability, they often struggle with “clinical complexity”—the nuanced, often unstructured data that physicians use to make decisions.
When a health system relies solely on a vendor’s data model, they are limited by how that vendor defines a “high-risk” patient or a “successful” outcome. If the vendor’s logic does not align with the specific demographics or clinical priorities of a local population, the resulting analytics can be misleading or incomplete. This disconnect can lead to a collapse in the effectiveness of population health initiatives, as the data fails to trigger the right interventions at the right time.
By transitioning to internal builds, Corewell Health is attempting to reclaim the definition of these metrics. An internally developed model allows the organization to integrate specific clinical workflows and local health determinants that a generic vendor product might overlook. This ensures that the analytics are tailored to the actual needs of the patients in the Grand Rapids and broader Michigan regions.
Bridging the Gap: Corewell Health’s Internal Approach
Dr. Bob Jarve has detailed the necessity of this transition, emphasizing a patient-centered approach to data. Rather than fitting the patient into a pre-existing software mold, the internal build allows the software to be molded around the patient’s clinical journey.
The primary objective of this internal effort is to bridge the gap between clinical complexity and enterprise analytics. Clinical complexity refers to the multifaceted nature of patient health, including comorbidities, social determinants of health, and varying responses to treatment. Enterprise analytics, conversely, often prioritize streamlined, standardized data for reporting and financial forecasting.
When these two worlds are disconnected, the “enterprise” view of a patient may not match the “clinical” view. An internal build allows for a more fluid exchange of information, where the data model is informed by the physicians who treat the patients. This alignment ensures that the insights generated by the data model are clinically valid and practically useful for the care teams on the ground.
The Role of Clinical Leadership in Health IT
The success of such a transition depends heavily on the intersection of medicine, and informatics. Dr. Robert Jarve embodies this dual role. A board-certified physician in both internal medicine and pediatrics, Dr. Jarve brings a clinical perspective to his role as a physician executive at Corewell Health.
Having earned his medical degree and completed his residency at Wayne State University School of Medicine, Dr. Jarve’s background in diverse patient care—ranging from infants to older adults—provides the necessary context for designing data models that work across the entire lifespan. This clinical grounding is critical when overseeing the development of population health tools, as it prevents the technical implementation from drifting away from the primary goal: patient care.
the integration of an MBA and MSc into his professional profile indicates a strategic approach to healthcare management. The ability to balance the financial and operational requirements of a large health system with the ethical and clinical requirements of patient care is essential for any organization attempting to build its own complex data infrastructure.
What In other words for the Future of Healthcare Data
The move by Corewell Health to prioritize internal builds suggests a shift in how healthcare organizations view their relationship with technology. For years, the industry has moved toward standardization, but there is a growing realization that “standard” is not always “optimal” for specific patient populations.
Who is affected by this shift?
- Patients: May experience more personalized care as health systems better identify their specific risks and needs through more accurate data.
- Clinicians: Gain tools that reflect their actual practice and reduce the friction caused by inaccurate or overly simplistic vendor analytics.
- Health IT Vendors: May face pressure to move away from “one-size-fits-all” products and toward more flexible, modular platforms that allow health systems to integrate their own custom logic.
- Other Health Systems: May gaze to the Corewell model as a blueprint for reducing dependency on external vendors for critical population health functions.
As the industry moves toward 2026 and beyond, the ability to manage “considerable data” will no longer be about the volume of information collected, but about the precision of the models used to interpret it. The transition from buying a solution to building a solution marks a maturation of health informatics, where the clinical voice becomes the primary architect of the digital tool.
For those interested in the intersection of healthcare and technology, the evolution of population health data models provides a clear look at the next frontier of medical innovation. The focus is shifting from the acquisition of data to the architecture of insight.
Corewell Health continues to refine its patient-centered data models as part of its broader commitment to community health. Updates regarding the implementation and outcomes of these internal builds are typically shared through institutional reports and professional healthcare informatics forums.
We invite our readers to share their perspectives on the “build vs. Buy” dilemma in healthcare IT. Do you believe internal builds provide a superior clinical outcome, or does the risk of technical debt outweigh the benefits? Join the conversation in the comments below.