<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DashPoint Analytics Insights</title>
    <link>https://www.dashpointanalytics.com/insights/</link>
    <description>Practical answers on data, reporting, Microsoft Fabric and AI.</description>
    <language>en-us</language>
    <item>
      <title>What should a skilled nursing facility dashboard track between star rating updates?</title>
      <link>https://www.dashpointanalytics.com/insights/skilled-nursing-facility-dashboards-star-ratings/</link>
      <guid>https://www.dashpointanalytics.com/insights/skilled-nursing-facility-dashboards-star-ratings/</guid>
      <pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Keith Hoover</dc:creator>
      <description>A useful SNF dashboard tracks the inputs to your CMS star rating every day from your own systems: nursing hours per resident day, the MDS items behind quality measures, census, and whether charting is current. That way you see problems before Care Compare does.</description>
    </item>
    <item>
      <title>What does moving from Power BI Pro to Microsoft Fabric actually involve?</title>
      <link>https://www.dashpointanalytics.com/insights/moving-from-power-bi-pro-to-fabric/</link>
      <guid>https://www.dashpointanalytics.com/insights/moving-from-power-bi-pro-to-fabric/</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Keith Hoover</dc:creator>
      <description>Moving from Power BI Pro to Fabric is mostly data engineering: pull the logic out of each report's dataflows, agree on one definition per metric, rebuild it once in shared lakehouse tables with Git and dev/prod, and reconcile against the old numbers before cutover.</description>
    </item>
  </channel>
</rss>