Staff Product Manager, Longitudinal Patient Record

At Counterpart Health, we are transforming healthcare and improving patient care with our innovative primary care tool, Counterpart Assistant. By supporting Primary Care Physicians (PCPs), we deliver improved outcomes at lower cost through early diagnosis and longitudinal care management of chronic conditions. We're hiring a Staff Product Manager to own the longitudinal patient record, one trusted view of the care each patient receives across every setting, from the primary care office to the specialist to a hospital stay. Every Counterpart product builds on this record. Our clinical data comes from hundreds of sources, including health information exchanges, EHRs, labs, ADT feeds, pharmacy fills, prior authorizations, and claims from our health plan customers. Each one captures part of a patient's care. The longitudinal record connects them into one history of the patient's visits, conditions, medications, and results. You will ensure completeness and consistency in how those sources come together, so providers walk into each visit with the full picture, care gaps get closed, and quality and risk adjustment programs capture the care patients actually received. Our AI reasons over the same record, so improvements to the record expand what our AI can reliably do. That work takes clear clinical definitions, sound data modeling, and AI applied where it adds scale, such as classifying documents and connecting records across sources. The result is that every AI tool we build works from the same view of each patient. You will report to the Director of Product, Clinical Data Products, and lead the Longitudinal Patient Record pod. You will partner closely with engineering, our clinical team, and data consumers across the company. What you will own and improve • Product strategy. Set the vision and roadmap for the longitudinal record. Find the highest-value problems across the products and programs that depend on it, and make the trade-offs among completeness, accuracy, timeliness, and investment. • A trusted record. Define how care events and their dates, settings, providers, and facilities are represented consistently, and how medications, conditions, labs, and procedures connect to those events and to the patient's history over time. Set clinically grounded rules for combining sources that each describe part of the same care, so every fact can be traced to the evidence behind it. • A unified record of acute events. One record of each hospitalization, ED and post-discharge care management built from multiple sources such as: ADT notifications, prior authorization and admission notices, facility claims, medical records (especially discharge documentation), and where the patient went at discharge. Anyone working with the patient sees the whole stay, from admission through discharge to the next setting of care. • Data for every use case. The record serves providers at the point of care and the programs that depend on complete care history: quality measurement (HEDIS), risk adjustment and RADV audits, payment integrity, and revenue operations. Providers, quality analysts, and operational teams all work from the same care history. • How every source becomes part of the record. You own patient matching, deduplication, normalization, and clinical terminology mapping, which turn raw data from each source into a trusted part of the patient's record. Every new source runs through them, so improvements are built once and reused across products. • Adoption. A canonical field counts only when clinicians use it. You own the path from definition to adoption: requirements, a migration plan per use case, and retiring fragmented, duplicate versions of the same data. What success looks like • The record gets more complete, accurate, and timel