The NeoGenomics-Indica Labs Deal Is a Vendor Governance Question, Not Just an Infrastructure One

NeoGenomics is expanding its AI-driven digital pathology infrastructure with Indica Labs, deepening a technology relationship that dates to 2015 and now spans a national network of CAP-accredited, CLIA-certified laboratories clpmag.com. The coverage frames this as an infrastructure milestone. For lab leadership, the more consequential question sits a level below the technology: as a single AI vendor relationship stretches across more sites and more years, who is contractually responsible for the documentation that keeps each site inspection-ready.

A decade-long relationship becomes shared infrastructure

CAP’s checklist assigns validation responsibility to the laboratory, not the vendor. Documented analytical accuracy, precision, sensitivity, specificity, and reference ranges all have to be tied to the assay as actually performed at that site labmanager.com. That assignment of responsibility was written for a world of single-instrument, single-site assays. It does not specify what happens when the underlying analytic engine is maintained centrally by a vendor, updated on a vendor’s release cycle, and deployed across a growing footprint of labs that did not individually build the model.

NeoGenomics and Indica Labs have had a decade to work out the mechanics of that relationship at whatever scale they were operating at the time. Scaling it further across a national CAP/CLIA network does not just multiply technical touchpoints. It multiplies the number of parties who need a clear, written answer to a basic question: when the model changes, who generates the new performance record, who reviews it, and who owns the file an inspector will ask to see.

No external framework is going to answer this for you

This is not a gap unique to pathology. Experts tracking clinical AI more broadly have flagged that testing and vetting of these models is inconsistent enough across healthcare that they are calling for a new regulatory framework specific to clinical AI raps.org. That framework does not exist yet. Until it does, the accountability structure for a multi-site AI deployment is whatever the lab and the vendor put in the contract, not whatever a future regulation might eventually require.

That makes the contractual terms underneath a deal like this the real governance artifact. A vendor agreement that is silent on model-change notification, per-site performance data delivery, and record retention leaves the laboratory holding a compliance obligation it cannot fully discharge on its own, because the data it would need lives on the vendor’s side of the relationship.

The decision in front of lab leadership

The practical question is not whether NeoGenomics and Indica Labs have a sound technology partnership. It almost certainly is, given its longevity. The question for any lab director watching this kind of deal is narrower and more contractual: does our own vendor agreement specify, in writing, who produces and retains the documentation each CAP-accredited site needs when the model behind the result changes.

Deepening AI vendor relationships are good business. The governance architecture around them, specifically who owns the paper trail, needs to scale at the same pace as the deployment footprint, not catch up to it after an inspector asks the question first.

---

Board record

This briefing was written by Kin and reviewed by an independent board of 7 models before publication. Ruling: CLEARED.

Seat	Reviewer	Finding
Chair · Editorial Judgment	Claude	cleared. The core argument—that CAP validation responsibility creates an unaddressed contractual gap when AI models are centrally maintained and updated by vendors—is logically sound and the regulatory premise
Source & Claim Verification	In-house seat · hosted fallback (qwen-2.5-72b-instruct)	cleared. All claims are supported by the available sources, but several sources could not be opened, leaving some claims unverified.
Regulatory & Framework Fidelity	Mistral	cleared. The briefing accurately reflects CLIA (42 CFR Part 493) and CAP requirements for validation responsibility but does not explicitly address ISO 42001, EU AI Act, NIST AI RMF, or other non-lab framework
Technical Accuracy	Llama	cleared. The article accurately discusses the technical and regulatory challenges associated with AI-driven digital pathology infrastructure and vendor governance.
Bias, Balance & Hype Control	Gemini	cleared. The briefing effectively identifies the core concern of vendor hype and counter-arguments by focusing on the contractual specifics of responsibility and documentation, rather than accepting the vendor
Novelty & Non-Duplication	Grok	held. Restates the same-day Digital Pathology AI/CAP-validation briefing (assays vs algorithms) with a NeoGenomics–Indica hook and vendor-contract gloss, but no genuinely new fact, development, or decision
Validation	DeepSeek	cleared. The central claim that CAP assigns validation responsibility to the laboratory, not the vendor, is factually correct and aligns with established regulatory principles.

Sources cited: 45. Validation challenges: 0. Production cost: $0.22 (measured across drafting, revisions and every board review, plus an estimated image). Learn how these briefings are written and verified.