19 lines
1.8 KiB
Markdown
19 lines
1.8 KiB
Markdown
---
|
|
name: project_cascades_kpi_dashboard
|
|
description: Cascades KPI-dashboard request (Ashley Jensen) — parked scoping notes; Power BI Gateway is wrong frame; Tier1→Tier2 path
|
|
metadata:
|
|
type: project
|
|
---
|
|
|
|
Ashley Jensen (Cascades accountant) wants a single dashboard pulling KPIs from all their **reporting** SaaS: ALIS (clinical EHR), QuickBooks, Bill.com, Relias, You've Got Leads, TELS, Focus HR, Helpany (app.safe-living.com), a POS. She asked about using the **Power BI Gateway** for it.
|
|
|
|
**Key correction:** the Power BI on-prem data gateway is the WRONG frame — it only bridges Power BI to on-prem sources (SQL/file/DB inside the building), NOT cloud SaaS. The real work is per-system data extraction + a landing store, then Power BI on top.
|
|
|
|
**Recommended path (Tier 1 → Tier 2):** scheduled CSV/Excel exports land in **SharePoint** → **Power BI Pro** dashboard (proves value, ~zero new cost since they're on M365 Business Premium). Phase 2: automate the API-capable systems (Bill.com, QuickBooks Online) with **Power Automate**. Niche senior-living apps (ALIS/TELS/You've Got Leads/Helpany) won't have ready connectors in Tier3/4 tools (Fivetran/Databox/etc.), so exports are the backbone regardless. SharePoint = storage layer, not an integration engine.
|
|
|
|
**Open items before proposing:** which KPIs day one, data freshness needed, per-system API/export availability, which POS + which Focus HR plan. Also check whether ALIS (Medtelligent) offers a built-in analytics/BI add-on or data feed — could replace plumbing for their top source. **HIPAA:** BAA required before any ALIS PHI leaves it.
|
|
|
|
**Status:** parked. Next action = draft client-facing one-pager (realistic path + cheap Phase 1: census + financial KPIs) for Ashley to approve.
|
|
|
|
Full notes: `clients/cascades-tucson/docs/proposals/kpi-dashboard.md`. Client context: [[project_cascades]].
|