Sawan Ruparel

Sawan Ruparel is the chief technology officer of Oncera Health, where he leads the engineering and data work behind the survivorship platform.

He is also the co-founder and chief executive of Web Mavens, and has spent years building healthcare IT and compliance systems, including 340B and clinical platforms, alongside scalable, secure web applications. That background is the reason Oncera's architecture starts from a different place than most consumer health products: the assumption is not that data can be collected and figured out later, but that a survivor's record belongs to the survivor and everything else is designed around that.

In practice, that shapes several decisions the product is built on. Participants enroll themselves rather than being enrolled by an employer or a clinic. What they record is theirs, and organizations that sponsor the program receive aggregate reach and engagement only, never individual health information. There is no clinician dashboard streaming patient data for someone to monitor, because a survivorship platform that creates a new monitoring obligation for a busy clinic will not survive contact with one.

He owns the data intelligence layer: the work of turning short, ordinary daily check-ins across the seven domains of survivorship into patterns a person can actually see, and then into a summary short enough to be useful in a ten minute follow-up appointment. The hard part is not the collection, it is the compression, and doing it without implying more certainty than the underlying signal supports.

He also holds the line on what the platform is not. Oncera is educational and non-diagnostic. It does not diagnose, treat, or predict recurrence, and no amount of pattern detection changes that boundary. Where the product could be built to imply a clinical judgement it deliberately is not, and that constraint is enforced in the engineering rather than only in the copy.

Alongside the platform he is responsible for the security and privacy posture Oncera brings to evaluation conversations with clinical partners, health systems, and employer benefits teams, and for the technical review that happens before any new domain, measure, or integration ships. That review is deliberately unglamorous work: checking that a new measure is one a survivor can answer honestly on a bad day, that a new integration does not quietly widen who can see what, and that nothing shipped this month has started to sound more certain than the evidence behind it.