Stop Boiling the Ocean: An Iterative Data Strategy
summary
Mississippi replaces a stalled three‑year RFP with an incremental, standards‑based stack: MarkLogic operational data store as the hub, Mesa claims engine kept, Verato for MPI, Onyx for 9115 APIs and AWS as cloud provider, Cloverleaf ESB, Okta/ID.me for identity, GDIT as system integrator. A 6‑week proof of value (2.5 FTE) builds provider‑ownership graphs and mastering that found hidden mergers; a 3‑FTE/4‑week RAG LLM workflow surfaces policy gaps in state plans. Total contracted cost runs about one‑third of the original RFP.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 1:10Background on Medicaid and CMS rules
- 4:40Mississippi's failed RFP and challenges
- 8:14New data strategy and vendor selection
- 16:45Gary Katz on identity resolution and proof of value
- 22:57Disclosure of ownership compliance demo
- 29:38Generative AI for policy analysis
- 34:58Closing thoughts and Q&A
related talks
44mBreaking a Monolithic Devops
11mBreaking Data Silos: Enterprise Data Management
41mFrictionless Compliant Data & Analytics Environments
52mScaling Data Teams: Three Pitfalls and How To Avoid Them
41mModern Data Stack: Optimising and Scaling Data in a Tech Company
19mPrescriptive approach to cloud: From on-premises to cloud in 9 months
39mRethinking RDBMS Data Migration
43mSponsored Session: Operational Data Stores for Financial Risk Mitigation