CDL Nuclear · Anchor Notes
Anchor Note · CDL Nuclear

Call Extraction: CDL MedScout Data Discussion — Platform Evaluation

Date
Wednesday, September 10, 2025
Format
Gong · ~38 minutes
Participants
Phil Cranmer (CDL), Ronald Miller (CDL, likely data/analytics), Skylar Talley (MedScout) · Fathom Notetaker also listed

Call Extraction: CDL MedScout Data Discussion — Platform Evaluation

DDX ID: 0461 Date: 2025-09-10 Duration: ~38 minutes Participants: Phil Cranmer (CDL), Ronald Miller (CDL, likely data/analytics), Skylar Talley (MedScout) — Daniel Wheaton (MedScout). Fathom Notetaker also listed. Call type: Data reconciliation and platform evaluation. CDL comparing MedScout claims data against AcuityMD data to validate accuracy before switching platforms. Triage: Moderate-to-rich. The core conversation is about data accuracy validation, but several distinct insights emerge about CDL’s data evaluation process, Phil’s role as data gatekeeper, and the severity of the Acuity relationship breakdown.

Distinct Insights

1. Phil requires data accuracy validation before any platform rollout — the data is the gatekeeper, not the platform

What: Phil: “I love the platform like that’s not the barrier, right? It’s the platform’s only as good as the data is good.” And: “Once we check the box on data and I’m feeling good… once we get through this hurdle, we’ll be good to go.”

So what: CDL has a sequential evaluation process: platform UX first, then data accuracy. Phil already validated MedScout’s platform experience and found it satisfactory. But he’s explicitly blocking wider rollout until data accuracy meets his standard. This means CDL won’t adopt a claims data tool on platform quality alone — the data must reconcile against known account volumes before Phil gives the green light. For MedScout (or any data vendor), the implication is that the demo-to-contract pipeline includes a mandatory data validation step where CDL compares platform numbers against their ground truth. Phil personally owns this gate. The platform could be perfect, but if Flagstaff Medical Center shows 15 procedures when Phil knows it’s 6,700+, nothing moves forward.

Speaker credibility: Phil, stating his own decision criteria. Very high. Scope: Company-wide — affects both motions and all downstream adoption. Motion: Both.

2. CDL treats claims data as directional by comparing against known customer volumes

What: Phil is actively reconciling MedScout data against AcuityMD data AND against CDL’s own internal knowledge of customer procedure volumes. The Flagstaff example: MedScout showed 15 procedures vs. 6,700+ in Acuity. Phil’s approach is triangulating — platform A vs. platform B vs. what CDL knows to be true from direct customer relationships.

So what: CDL has an internal ground truth layer that neither data vendor has. Because CDL installs and manages nuclear imaging equipment for its customers, they know actual procedure volumes at their existing accounts. This gives Phil a validation dataset that most platform buyers don’t have. He’s not comparing two black boxes against each other — he’s comparing two black boxes against direct customer knowledge. This triangulation approach is why Phil catches discrepancies that other buyers might miss. It also means CDL’s data accuracy bar is unusually high: they can verify whether reported volumes are plausible because they have independent ground truth for a subset of accounts.

Speaker credibility: Phil, describing his evaluation methodology. High. Scope: Company-wide evaluation process. Motion: Both.

3. Phil personally manages quarterly board-level volume reporting via Excel exports

What: Phil: “I’m the asshole that always emails them every quarter saying where’s my update.” He exports data from Acuity to Excel for board and executive reporting on procedure volume trends.

So what: Claims data flows from the platform into Excel, then into board-level strategic planning. This reveals two things. First, Phil is the single person responsible for translating raw claims data into executive intelligence — there’s no data team or analyst layer between the platform and the boardroom. Second, the board consumes procedure volume trends quarterly, which means CDL’s strategic planning cadence is quarterly, and data accuracy directly affects board-level decision-making. If Phil doesn’t trust the data, he can’t put it in front of the board. This is why he blocks rollout on data quality — his personal credibility with the board is on the line. The quarterly cadence also suggests CDL’s platform evaluation isn’t urgent by days but operates on a quarterly planning horizon.

Speaker credibility: Phil, describing his own process. Factual. Scope: Company-wide — board reporting affects strategic direction. Motion: Both.

4. Duplicate accounts in private practice data force manual consolidation

What: Phil: “If you’re a naive sales rep and you want to call on a high volume account, obviously, I want to see the volume bucketed together.” The private practice data contains duplicates that dilute true volumes across multiple entries for what is functionally the same practice.

So what: Private practice claims data has an account attribution problem that health system data doesn’t (or has differently). A single cardiology practice might appear under multiple entries — different NPIs, different TINs, different location addresses — each showing a fraction of the true volume. A rep looking at the list might skip what appears to be a 200-procedure practice, not realizing it’s actually an 800-procedure practice split across four entries. This creates a specific data quality problem for the private practice motion: CDL needs a consolidated view where volumes from the same practice are bucketed together. Phil is doing this consolidation manually, which means he’s the bottleneck for clean private practice targeting data. Automating this consolidation (or fixing the attribution) directly unblocks the private practice team’s ability to self-serve targeting data.

Speaker credibility: Phil, describing a known data issue he manually works around. High. Scope: Primarily private practice motion — private practices have more naming/NPI fragmentation than hospitals. Motion: Private practice team.

5. The Acuity relationship has deteriorated to the point of active hostility

What: Phil: “I don’t know if I believe anything they say today because they pretty much hate me now.” The red-lined agreement from CDL’s internal counsel is already prepared for MedScout, suggesting the switch is a when-not-if decision.

So what: CDL’s previous data vendor (AcuityMD) relationship has broken down. Phil’s language (“pretty much hate me”) suggests this isn’t just commercial dissatisfaction — the interpersonal relationship between CDL and Acuity is adversarial. CDL already has legal counsel reviewing the MedScout agreement. This means CDL’s platform switch isn’t a competitive evaluation where they might stay with the incumbent — the incumbent is effectively ruled out. MedScout’s real competition is CDL’s willingness to switch at all, not AcuityMD winning them back. The data validation exercise Phil is running is the last gate before a decision that’s already been made directionally.

Speaker credibility: Phil, describing a vendor relationship. Firsthand. High. Scope: Company-wide vendor decision. Motion: Both.

Transcription Notes

  • Ronald Miller — appears in participant list but his role at CDL is unclear from this transcript. Possibly data/analytics or operations given the data-focused nature of the call.
  • Flagstaff Medical Center — used as a data reconciliation test case. The 15 vs. 6,700+ discrepancy likely reflects a data configuration or code coverage issue (similar to the King’s Daughters pattern from call 0686), not a fundamental platform data quality problem.
  • No transcription errors against the term bank detected — the SPICED summary format suggests this was processed through a different notes template than the later MDCN format.