[
  {
    "id": "verified-caller-id",
    "title": "Identity verification that made telehealth answering possible",
    "organization": "Doximity",
    "timeframe": "2013–2017",
    "role": "Early product lead on Doximity Dialer",
    "summary": "Patients ignored calls from unknown numbers, blocking telehealth adoption. Dialer showed the doctor's office number — verified and HIPAA-safe.",
    "relevanceToAI": "When a system decides what identity to present, that decision has to be traceable and correctable — the same constraint that applies to clinical AI at scale.",
    "keyTakeaways": [
      "Identity is a product decision, not just a feature — who the system says you are shapes whether anyone picks up",
      "Audit-ready logs and escalation playbooks matter as much as the happy path",
      "Carrier rules, privacy constraints, and clinician adoption shape the product from the start"
    ],
    "outcomes": [
      "Pickup rates improved enough that clinics stopped raising it as a top concern",
      "iOS app reviews climbed from 3.7 to 4.8 stars",
      "Spoofing reports dropped below the carrier review threshold",
      "Clinician adoption accelerated — answering stopped being the bottleneck"
    ],
    "evidenceLevel": "mixed",
    "url": "https://kanav.net/work/case-studies/verified-caller-id/"
  },
  {
    "id": "care-navigation",
    "title": "Routing rules that made care navigation accountable",
    "organization": "Transcarent",
    "timeframe": "2021–2022",
    "role": "Director of Product, Care Experiences",
    "summary": "Led product across value-based specialty-care and care-navigation programs (Surgery, Urgent Care, Behavioral Health, Oncology Care).",
    "relevanceToAI": "AI-generated care recommendations only work if the system makes ownership visible — who owns the next step, how to escalate, and what happens when the recommendation conflicts with clinical judgment.",
    "keyTakeaways": [
      "Routing rules have to make ownership visible — algorithm output without a workflow owner is just a suggestion",
      "Completion dashboards become operational tools when they surface exceptions and accountability",
      "Unified records are the prerequisite for any downstream intelligence"
    ],
    "outcomes": [
      "Routing and escalation rules cut the exception queue by making ownership visible",
      "Care plan completion rates converged — the gap between highest and lowest programs shrank",
      "Frontline teams stopped flagging routing as a top reason for delayed resolutions"
    ],
    "evidenceLevel": "directional",
    "url": "https://kanav.net/work/case-studies/care-navigation/"
  },
  {
    "id": "fiduciary-planning",
    "title": "Review routing and escalation for physician-facing financial guidance",
    "organization": "Andwise",
    "timeframe": "2022–2024",
    "role": "Co-Founder and CEO",
    "summary": "Co-founded Andwise. Built the medical advisory board, review routing, escalation clocks, and accountable sign-off workflows for physician-facing financial guidance.",
    "relevanceToAI": "Advice systems in regulated domains need human review checkpoints, provenance records, and escalation paths — the same product architecture that applies to clinical AI recommendations.",
    "keyTakeaways": [
      "Sensitive recommendations need accountable sign-off, not just confidence scores",
      "Advisory boards are operational infrastructure when their authority is encoded into workflow",
      "Review records become inspectable evidence when something goes wrong"
    ],
    "outcomes": [
      "Recommendation turnaround dropped from days to hours for standard reviews",
      "Grew to 1,200+ physician users and a 700-member physician community",
      "Review records linked decision context to outcomes",
      "Physician trust scores rose as recommendation provenance became visible"
    ],
    "evidenceLevel": "mixed",
    "url": "https://kanav.net/work/case-studies/fiduciary-planning/"
  }
]