wk3 sep_epic story_13: DEV QA PowerBI Architecture MVP

[jamesmrollins]

@lzim @staceypark @lijenn

FYI: @dkngenda

Resource Link

Lucidcharts/VA/operations/PowerBI Architecture

Please Evaluate and Comment

• User workflow
• PowerBI Architecture. Illustrates how dataset will be brought in from SQL and a PowerBI report provided based on the row level permissioning based on the user's login.
  • We know who the user is by their login
  • We know their VISN and Facility from the CRM setup
• PowerBI Architecture shows a multipage report which uses a tab structure similar to Excel to represent data/viz/params elements.
  • Filters for clinic and SP Params are provided on the data page
  • Slicers are provided on the viz tab to adjust visuals as required.
  • Params tab contains Team Data Table (model parameters) with respective definitions.
  • There is a visual mockup of the report page.
  • All representations of data on the pages are linked. As data is transformed by the user, it will update all the pages in the report.
• Single dataset model. Describes a method to establish and carry the main 24 month data set in PowerBi, and then provide a daily update. This may provide data that is current without a huge data processing burden.
• User-Access Data Model. Describes how row level permissioning will allow the user to immediately access the data that is relevant to their facility without needing to navigate to that information. May affect session 2 and 3. Discusses the potential (though likely not the first step) for integrating with CRM.

Constraints

• James does not have the ability to work with PowerBI desktop within the VA domain (a limitation of CITRIX). He will investigate getting PowerBI desktop added to the session, since it is free, by putting in a ticket.
• We may need to reinvestigate putting in a ticket to emulate a machine inside Menlo Park. Last attempt failed.
• James will also investigate accessing a VA machine through the CIDMO contract.
• David and James are dividing their work. David will focus on getting the data to PowerBI and James will focus on permissioning and setting up the report in the workspace.

[dkngenda]

Jeff updates:
Was able to get all the data into PTSD_OMHO that will be consumed by Power BI for 7 GB.
#1 Challenge this week
Coming up with some way to do ClinicSelection

Use Case:
Can set up your team with all of these from Data UI:

Sta3n
Division Name
Physical Location
Primary Stop Code
Secondary Stop Code
Clinics

• Only change is the "ProviderName" column from Clinic Selection

Power BI Data Model

Couldn't find a way to set up the relationships to keep this Provider widget on the Clinic Selection dashboard.

When you use slicers, don't have search box options, but our teams do search for specific things.

Examples:

"PCT"
"PCMHI"
"Provider Name"

"TMH"

[mnallajerla]

Discussed at 10/25 WorkGroup Leads - good to close

Reference #2262 for current Power BI documentation tasks and info