Sherlock designs Meridian's AI operating model in three artifacts a CEO can act on: the target org chart with named roles, the RACI-backed decision rights, and the capability heatmap that decides what to build, what to buy, and what to partner for.
| Decision | Single owner | Consulted / Informed |
|---|---|---|
| Annual AI investment envelope | CEO | Steering Cmte, CFO, Board Finance |
| Which initiatives get funded this quarter | AI Steering (majority) | CAIO recommends · CMO/COO consulted |
| Approve model for production release | Model Risk Committee | CAIO accountable · Domain owner informed |
| Build vs. buy vs. partner | CAIO | Domain owner, CFO, CIO consulted |
| Tier assignment (risk classification) | Head of Model Risk | Compliance consulted · CAIO informed |
| Domain roadmap sequencing | Domain Pod Lead | CAIO consulted for cross-pod dependencies |
| AI incident containment | CAIO | Compliance accountable to Board · CMO/COO informed |
| Board attestation content | CAIO | Compliance consulted · CEO informed |
“Meridian will operate AI in a federated hub-and-spoke model: a central AI Center of Excellence (hub) owns standards, tooling, model risk, and the PHI data platform; four domain pods (Clinical, Ops & Rev-Cycle, MA Plan, Member Experience) execute against them. The Chief AI Officer reports to the CEO with a dotted line to the COO. Steady-state headcount is 38 AI FTE at Year 2, hired in four hiring waves starting with the CAIO in Q3-2026 and reaching pod-lead coverage by Q1-2027. The capability heatmap identifies 6 build, 4 partner, and 2 buy priorities — the differentiators (STARS gap-closure, PHI platform, model risk) are built in-house; commodities (ambient scribe, contact-center summarization) are bought; regulated clinical workflows are partnered with EHR-native vendors.”