You wrote that your direct team does not have much experience
with the tool Dexcom uses heavily, that you wanted anywhere from creating dashboards, data visualization, reports, analytics
, and hands‑on help with the Data Pipeline that feeds data from our third‑party rebate processor
. This is that training, expressed as the finished artefact: every tile, chart and callout below maps to a module of the 1–2 day on‑site.
Rebates accrued in the model vs. rebates actually invoiced by the third‑party processor, $M. The gap is what Payer Ops chases.
Where the rows go, where they fall out, and how fresh the extract is. This is the Day 2 lab: you trace one rebate claim from the processor file to the tile it lands in.
Ranked by accrued rebate in the selected period. Rate = rebate ÷ gross. Formulary status is the Day 1 afternoon “conditional formatting” exercise.
Net revenue share by product for the current filters.
Built around your February‑style annual on‑site in San Diego. Every module ends with a piece of this page existing in your own workbook, on your own rebate extract.
The "ask the data" ideas on this board are designed to run on a GPU server inside your own network — an open-weight model over your own documents, cited answers, no per-seat licence, nothing leaving the building. The short deck below explains how it works. Scroll through, or download it as a PDF.














Questions? Book 30 minutes: calendly.com/powerbiconsultingservices/30min