Snowflake’s healthcare CTO has mapped agentic AI onto the cancer journey. In From Discovery to Remission: How Agentic AI Is Reshaping the Oncology Continuum, Murali Gandhirajan walks five stages, discovery, screening, diagnosis, treatment and survivorship, and argues that “all five bottlenecks trace back to the same root cause: There is no unified data foundation that can reason across the continuum.” The sharpest scenario is one data event: an agent “receives a sequencing result, compares it with similar patient profiles, identifies open trials, models feasibility and prepares a tumor board summary.”
The figures come in two kinds. The industry numbers are cited to outside sources: oncology drug attrition above 95% and $50 billion to $60 billion a year on failed trials, from a 2023 JAMA Network Open study, and 21.6% more breast cancers found by an AI-supported screening workflow. The customer numbers are vendor case studies: AstraZeneca cutting data product development from six months with 16 engineers to four days with two, more than 118 data products and more than $10 million in savings; Zelis ingesting from more than 40 sources through Openflow and running more than 20 production agents. Read those as Snowflake’s numbers. What survives is the governance line, which is the right one for PHI: “auditability, access controls, agent guardrails and clear rules for when to keep humans in the loop are mission critical.”
Here the catalog agrees with the post. The Snowflake provider page lists 49 API pages, and the ones the story’s agents would run on are all there: the Cortex Agents API, Snowflake Cortex Analyst API, Snowflake cortex search service API and Snowflake Cortex Inference API, with the Snowflake Grant API and Snowflake Role API carrying the access controls the post calls mission critical. The Snowflake agentic access profile counts 408 operations, 276 acting and 14 human-in-the-loop. The catalog description records an account-hosted MCP server exposing Cortex tools “under Snowflake RBAC.” Openflow, which the Zelis example depends on, has no API page of its own.
Snowflake scores 81.2 on the Kin Score, exemplar band, led by access clarity at 92.1 and developer ergonomics at 80.4, with contract governance the weakest facet at 45.5. Agent Readiness is 45.6, agent-native, with MCP server, idempotency, reversibility and agent skills lit. The unlit dimensions are consent identity, dry-run mode, protected resource metadata and dynamic client registration. For a post about agents acting on patient data, consent identity is the one to watch: the human-in-the-loop rule Snowflake describes is real in its operations, and the record does not yet show how a patient’s consent travels with an agent’s request.