Patient experience & onboarding
Onboarding and activation funnels, async and sync care models (messaging-first care, video visits, triage), retention and engagement loops.
Form Health · Sana · Collective Health
Most healthcare builds are not new problems. They are known projects with known shapes: an EHR that fits the practice, records that arrive before the visit, prescribing that works, billing that gets paid. I have run each of these before, as the product and technology executive accountable for the outcome.
Onboarding and activation funnels, async and sync care models (messaging-first care, video visits, triage), retention and engagement loops.
EHR selection, implementation, or custom build: Medplum, Elation, custom. Operational workflows designed around how the clinic actually runs, not around the vendor. Credentialing, provider data and directories.
AI before, during, and after the visit: record review, ambient scribing, summaries, inbox and call deflection. Hosted with Anthropic (Claude), on AWS, or third party (Nabla, Zoom), deployed in regulated settings. Context-walled, verify-not-promise multi-agent AI, run daily in my own practice..
Record retrieval and aggregation via Metriport or Zus, normalization, and records placed inside the clinical workflow where they get used.
E-prescribing via Photon, DoseSpot, Surescripts: pharmacy routing, prior authorization, and the prescribing workflow inside the visit. Lab ordering and results via Junction, Quest.
Custom and insurance billing, revenue cycle management (RCM), claims adjudication in house and third party, and the TPA operations and workflows underneath: eligibility, enrollment, payments.
GLP-1 and weight management, coaching, dietitian services: longitudinal programs with clinical protocols, staffing models, and unit economics that hold.
Population health programs, engagement at payer scale, and the path to value-based care: measurement, contracting readiness, care navigation.
Self-funded and level-funded plans, single and multi-payer setups, tiered networks, plan design, and the ben-admin integrations around them.
The stack changes; the method does not. New vendor, new modality, new line of business: same problem framing, same project discipline.