Power Platform Specialist

Power Platform Specialist Start: 2-3 weeks from date of offer Location: Remote - EST working hours Length of Contract: 3-6 months Hours Per Week: 10-30 pending on consultant availability • W2 Contract Only • • No 3rd Party Applicants • • Background Check Required • My client, a hospital, is in need of a Power Platform Specialist. The initial project is to migrate their current Excel (+ Power Query w/ some VBA) workflow planning system to a Power BI w/ Power Automate and Dataverse dashboard solution. The existing Excel file is highly functional but limited in that the macro-enabled files stored cannot accommodate multi-user access / editing. All data is patient information. Musts: Power Platform Specialist Migration experience from Excel to Power BI Healthcare / Hospital data experience Plus: Experience with MS Access Experience with Redcap From the Client: Business outcome • A reliable Power BI dashboard that shows: • Current census, MD/CTM caseloads, and team totals. • A 15-business-day admissions forecast grid (excludes weekends and MGB holidays), driven by a reference date and “what-if” capability. • Upcoming discharges and scheduled intakes incorporated into projected caseloads. • Automatic handling of default MD–CTM pairings with the ability to override, including a split-assignment edge case for one CTM. • Optional toggles to include/exclude covering staff when providers are OOO, plus display of coverage notes. • Power Automate flows that: • Refresh the data pipeline on a schedule. • Push concise AM snapshots and threshold alerts (e.g., caseload limits) to the intake/assignments leads. • Clean handoff: documentation, a light admin guide, and structured source control of M/DAX. Environment & constraints • Microsoft 365 tenant. Storage is OneDrive/SharePoint; target backend is Dataverse. • Power BI Premium is available. • No PHI leaves Microsoft 365. Row-level security and access separation required. • We already have well-defined logic and de-identified exemplars in Excel/Power Query, plus a working macro that mirrors the needed behaviors. Data model • Core entities: Patients (MRN as unique id), Admissions/Discharges (inclusive counting on admit and discharge days), Scheduled Intakes (pre-admission), Staff (CTM/MD with default pairings and overrides), Absences, Coverage (OOO with covering provider + notes), and a Workday/Holiday calendar. • Measures that calculate: daily census, caseload by CTM/MD/team, and projected caseload for each of the next 15 workdays from a selected reference date. Deliverables & milestones 1. Discovery & read-in (2–3 business days): Review existing Excel PQ, M code, and the few VBA routines. Confirm scope, edge cases, and acceptance tests. 1. Data ingestion (≈1 week): Stand up Dataflows or equivalent PQ pipelines; stage curated tables in Dataverse; set refresh cadence. 1. Model & DAX (≈1 week): Build semantic model, business-day logic (holiday-aware), reference-date “what-if,” caseload/forecast measures, coverage overlays. 1. Reports & interactions (3–5 days): Admissions Forecast Grid, census and caseload panels, discharge/intake lists, coverage/OOO notes, include/exclude coverage toggle. 1. Automations (2–3 days): Scheduled refresh + targeted alerting/summaries via Power Automate. 1. UAT, hardening, handoff (≈3 days): Performance tuning, RLS, documentation, and admin training. Candidate requirements (must-haves) • Deep Power BI (Dataflows, M, DAX), Dataverse schema design, and Power Automate (cloud flows). • Strong Excel Power Query background for porting logic. • Proven experience with operational dashboards, holiday-aware business-day calculations, and parameterized/what-if scenarios. • Comfortable implementing RLS and working within healthcare privacy constraints (no PHI outside M365). • Communicates clearly with non-technical stakeholders; writes maintainable M/DAX and leaves usable docs.