class: center, middle .logo[] # QueryBuilder Product Tour Swipe to switch between slides on mobile devices. Use the arrow keys and home/end on devices with a keyboard. © MGRID 2019. All rights reserved --- class: middle ### Introduction This product tour shows responsible self-service data selection for research. In the next slides we show how: * a researcher can easily adjust a query on a hospital data source for a running study * a data steward can inspect and approve the adjusted query before it is executed --- class: center, middle ### Projects  A researcher logs in and lands on the available projects page. The researcher selects the "Study" project. --- class: center, middle ### Query - Overview  The researcher uses the query definition screen to adjust the query. --- class: center, middle ### Query - Source Tables  The "Source Tables" section shows the tables and attributes in the hospital data source(s) that are available for selection. --- class: center, middle ### Query - Output Columns  Add columns to the query output by dragging attributes from the "Source Tables" section to the "Output Columns" section. Attributes can be renamed and aggregated if needed. --- class: center, middle ### Query - Filter Conditions  Drag attributes from the "Source Tables" section to the "Filter Conditions" section and use powerful filter operations to restrict the query output. --- class: center, middle ### Query - Preview Results  The effect of changes in the query are visible in the "Preview Results" pane, showing sample data output, without disclosing any personally identifying information, and population sizes (distinct number of patients, admissions) --- class: middle ### Intermezzo: query stacking A powerful feature of the QueryBuilder is the ability to stack queries. This means using the output of one query as a starting point for the next. For example: * A query "patients" selects all patients with a particular diagnosis and age * A query "prescriptions" uses "patients" as a starting point and selects all drug prescriptions for those patients * A query "bed movements" uses both "patients" and "prescriptions" to list the bed movements of all patients x days prior to a particular drug prescription --- class: center, middle ### Query Stacking  The "Heparin administration" query uses the "Male Patients" query as a starting point. --- class: center, middle ### Request Approval  After adjusting the query, the researcher requests approval to execute the query. --- class: center, middle ### Dataset Authorisation Service  The data steward is notified of the researcher's approval requests and logs in. --- class: center, middle ### Approve Request  The data steward selects the pending approval request and authorises execution. --- class: center, middle ### Schedule Execution  With the query now approved by the data steward, the researcher can run the query or schedule recurring execution. --- class: middle ### Query Execution and Transport Query execution is asynchronous from the UI, to enable queries on large datawarehouses. The results of the query can be transported to a (per project) pre-configured target, e.g.: * an Aridhia Workspace * a cloud bucket (Google, Azure) * a file system within the hospital --- class: center, middle ### Questions or Demo Requests info@mgrid.net