• Reposted from the Microsoft Healthcare & Life Sciences Blog at this link: https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/planning-for-a-secure-and-scalable-power-bi-enterprise-architecture-with-sensiti/2492766

    Leveraging data for Analytics, Reporting, and self-service Business Intelligence can provide great value to an organization. Most large organizations (especially those in Regulated Industries) also need to ensure that Sensitive Data such as PHI, PII, PIFI, Company IP, and Company Financials are properly managed and controlled. With Microsoft Power BI and some thoughtful planning, organizations can scale out an Analytics, Reporting and self-service Business Intelligence platform that ensures Security and Compliance for Sensitive Data.

    Below is a recorded version of a presentation reviewing considerations and best practices for planning a secure and scalable Power BI Enterprise Architecture with Sensitive Data at the core. Topics include:

    • Securing Power BI Tools such as Power BI Desktop and Gateways
    • Planning Azure Active Directory (AAD) based authentication and Workspace Architectures
    • Row Level Security (RLS) and Object Level Security (OLS)
    • Microsoft Information Protection (MIP)
    • Microsoft Cloud App Security (MCAS)
    • vNets / Private Links
    • Azure Data Lake integration
  • Reposted from the Microsoft Healthcare & Life Sciences Blog at this link: https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/ingest-healthcare-open-data-into-azure-and-power-bi-using-new-github-repository/2278523

    Numerous Government agencies make Healthcare Open Data available to the public at no cost. Data from the CDC, CMS, FDA, World Bank, US Census, USDA and many others provide rich sources of valuable data. These vast sources of robust and useful data are free to use but can have different file formats, different table structures, different context, and different data granularities. Ingesting all of this data into a common place where it can be used and shared is often time-consuming and challenging. I’ve put together a repository in GitHub called Power Pop Health to help with these challenges.

    Power Pop Health is a collection of content intended to simplify the process of ingesting and prepping Healthcare Open Data for Analytics, Business Intelligence, Data Science, and more. Power Pop Health has a simple mission: Make it easy for you to ingest, transform and format Healthcare Open Data and common reference tables so that you can achieve more. The GitHub repository can be viewed at this link.

    How does Power Pop Health work? I’ve tried to make it simple with low code/no code/no PowerShell deployment so that anyone can use it with nothing more than an Azure subscription and Power BI. Where code is necessary, there are cut-and-paste scripts with tutorial videos for the deployment:

    • Step 1 – Ingest Raw Data into an Azure Data Lake
    • Step 2 – Make the Data usable in Azure and/or Power BI
    • Step 3 – You take it from here! The data is ready to blend with your Organizational data, use for training, create demos, analyze to find trends, etc.

    What data is currently available in the first release of Power Pop Health?

    Over the last few years I have accumulated examples and tutorials that leverage public Healthcare data. This first release is a repository to share those examples in a unified format, and in one place. Future additions to this repository will be based on feedback from the community, with an initial plan to focus primarily on Population Health data such as Social Determinants of Health. Below is a chart of the data available in this first release:

    Here’s a quick summary of each data set in the initial release. Before using these data sources, I’d also recommend reading the licensing terms from the data providers to ensure that you are using the data appropriately:

    1. CDC Daily PM 2.5 Concentrations – Air Quality measurements at the level of States and Counties for 2001-2016.
    2. CDC Population Weighted UV Irradiance – Ultraviolet Radiation measurements at the level of States and Counties for 2004-2015.
    3. CMS DRG /MDC / Surgical Class v38.1 – Diagnoses Related Groups (DRGs), Major Diagnostic Categories, and Surgical Class version 38.1.
    4. CMS ICD10 CM 2021 – 2021 ICD10 CM Diagnosis codes for the US.
    5. CMS ICD10 PCS 2021 – 2021 ICD10 PCS Procedural codes for the US.
    6. Date Table (DataFlows) – A custom Date Table that can be deployed to Power BI DataFlows.
    7. Date Table (Power Query) – A custom Date Table that can be deployed to Power BI Power Query.
    8. Time Table – (DataFlows) – A custom Time Table that can be deployed to Power BI DataFlows.
    9. Time Table (Power Query) – A custom Time Table that can be deployed to Power BI Power Query.
    10. FCC State & County FIPS – A reference table for State and County FIPS geographical mapping codes provided by the FCC.
    11. FDA Food Recall Enforcement Reports – Foods that have been recalled.
    12. FDA CAERS Reports (Food Events) – Adverse events attributed to Foods.

    13. Medicare Part D Provider Utilization and Payment Data 2013-2018 – I’ll have this data available in the next release, but for now it is available in an end-to-end Azure Synapse and Power BI solution at this link: https://github.com/kunal333/E2ESynapseDemo 

  • A quick tutorial for deploying Azure Data Lake Storage Gen2.

  • A tutorial walking through the process to deploy an Azure Data Factory to a Resource Group.

  • This tutorial review the process to add existing M scripts (could be from Power BI or Excel Power Query) to DataFlows.

  • A tutorial for deploying a simple Azure ARM Template to Azure Data Factory:

  • This video walks through a quick demo of Power BI Q&A for Natural Language Queries running over Azure Synapse.

  • This video walks through a quick demo of the Power BI Decomposition Tree running over Azure Synapse.

  • This video walks through a quick demo of Power BI Small Multiples (Trellis Chart) running over Azure Synapse:

  • Reposted from the Microsoft Healthcare & Life Sciences Blog at this link: https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/updated-end-to-end-azure-synapse-and-power-bi-cms-medicare-part-d-solution/2145136

    Back in December I worked with a colleague from the Azure team, Kunal Jain, to release an end-to-end Azure Synapse and Power BI solution using real CMS Medicare Part D data. The solution can be deployed with a few clicks in Azure and runs in less than an hour. Here is a link to the December article: https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/deploy-an-end-to-end-azure-synapse-analytics-and-power-bi/ba-p/1940720 . Here’s a link to the GitHub site: https://github.com/kunal333/E2ESynapseDemo .

    Based upon feedback from users and our own to-do list, we have released new updates to the solution:

    • New 2018 Data is now added to the solution. The solution now has about 148 million rows of real CMS Medicare Part D Healthcare data.
    • Design of the Dimensions in Synapse was simplified to improve query performance. The column [Year] in each dimension used to represent every time a granular value existed, and now it represents to most recent year that it existed. See the Azure Update video below for a detailed explanation.
    • Logic in Azure Data Factory was consolidated to simplify the data flows and improve performance.
    • ‘Smart Narrative’ Power BI AI visual was added to the Summary page of the Power BI report (see video below).
    • ‘Q & A’ Power BI AI visual was added to a new page called “Q & A” of the Power BI report (see video below).
    • ‘Decomposition Tree’ Power BI AI visual was added to a new page called “Decomp Tree” of the Power BI report (see video below).
    • ‘Key Influencers’ Power BI AI visual was added to a new page called “Key Influencers” of the Power BI report (see video below).
    • Small Multiples were also added on a new page (see video below).

    The video below summarizes some of the changes in Azure:

    The video below summarizes some of the changes in Power BI: