Direct Qlik access is limited to known users at this time. As we move toward release of the Test and Production environments we will update this with additional information.


SMPH is providing 3 Qlik environments:

  1. Production: This is where applications that are tested and ready to use will live. Most end users will only see the Production environment.
  2. Test: This is where power users help test Qlik applications that are being prepared for moving to Production. 
  3. Development: This is where development of new Qlik Sense apps and work to update existing apps will take place. Only Qlik developers will have access to the development environment. 

Learn more about roles in each environment in SMPH Qlik Sense.

Learn more about how Qlik dashboards move through the environments.


If you're a new User of Qlik, here’s a nice introductory document for Interacting with Qlik dashboards.


To get started as a developer:

  • You must have completed your HIPAA security training (usually handled within your first days of employment and updated annually). Learn more about HIPAA at SMPH
  • Send an email to data@med.wisc.edu 
    • This will be a relatively simple process if you are working with a unit that already has at least one developer established.
    • If you are the first developer for a new unit that would like to would like to start development, we will discuss the right person to fill the role of Stream Admin for your unit. Learn more about roles in SMPH Qlik Sense.
  • We will take you through steps to review a data agreement, and provide materials to start getting up to speed in Qlik Sense.


We are preparing a fillable form to initiate a conversation for something you'd like to see in Qlik. In the meantime, please send an email to data@med.wisc.edu to get started. If your idea has SMPH-wide appeal, we will discuss collaborative development options.

Learn more about what it takes to get an idea to production.


SMPH IT will be creating a default UW Qlik Theme. In the meantime, review the recommendations provided by Qlik on how to create apps that meet accessibility standards.




The core data to be used in Qlik enterprise reporting will be stored in files called QVDs. A QVD (QlikView Data) file is a file containing a table of data exported from Qlik Sense. QVD is a native Qlik format and can only be written to and read by Qlik Sense. If you're a Developer and would like to see a sample of how this works you can look here -  Qlik Data Overview.docx for more information.


Each department will have their own area (Stream) for their data. You will be given access as needed by requesting  access from the Stream Administrators. There will also be some shared central data available. Finance Data will be coming from the SFS (WISDM) data warehouse, and HR data from the HRS (EPM) data warehouse.


As a developer, you have access to the Finance data by using the FINANCE_QVDs_WISDM or the FINANCE_QVDs_AADW  folders found in the right-hand side Connections panel in the data load editor. At this time, the WISDM data is coming directly from the SFS - SFMRT(WISDM) warehouse. If you have worked with the SFMRT data in the past, the current QVDs are a direct match for what you would normally see in the database. Currently we have General Ledger, Period Summary, and Payroll Star sample data in the Development Environment. For more detailed information please see the SFS documentation. The AADW data is being added as needed. Currently there is a basic customized version of the GL Star, and some QVDs requested specifically for the finance group.


As a developer, you have access to the Human Resources data by using the HR_QVDs_EPM or the HR_QVDs_AADW folders found in the right-hand side Connections panel in the data load editor. The EPM folder contains data coming directly from the HRS - EPM data warehouse. If you have worked with the HRS/EPM data in the past, the current QVDs are a direct match for what you would normally see in the EPM database. The AADW folder will contain data that has been grouped into categories such as demographics, compensation, contact info, etc. For more detailed information on the EPM (HRS) source data please see the EPM data warehouse documentation.