ICEBOX: PSY Results DashB - Add "i" Icon and Info Table and Validate RVI

[lzim]

Discussed at hq_workflow 09/15/2022

@lzim was prepping with @dlounsbu on Tues 08/13 for MTL Blue Session 6

Use Case: How to review these variables in the

RVI in Results Dashboard Engagement Duration in Results Dashboard

Expect to Engagement Duration & RVI here

• [ ] "i" pop-up in Control Panel in Results Dashboard
• [ ] Blue Color Table for the Definitions of Output Variables
• [ ] One table is helpful for the learner.

[jamesmrollins]

Hi @lzim , @emilymetcalf114

Regarding RVI

• [ ] Analyzed the Vensim Psy model (see first image below). The patient cohort "Supply Used *" variables are directly affected by the user inputs "User Change in RVI after 3 Months."
• [ ] These variables are present as output charts in the Sim UI (see image 2)

Image 1 - Supply Variables Affected by "User Change in RVI after 3 Months"

Image 3 - Supply Variable Outputs in Sim UI

Regarding Engagement Duration.

• [ ] From the model (see below), we see that Engagement Time rates for patient low, medium and high patient cohorts are affected by the "User Change in Engagement Duration after Three Months" variable.
• [ ] These sum to affect the "Ending Rate" and the "Patients in Care for More than 3 Months" (see orange). Both of these outputs are available in the Sim UI.
• [ ] Did you want to communicate Ending Rates (green) for each of these or patient cohort stocks (blue).

Image 4 - User Engagement Time Affects Low, Medium and High Duration Patients.

[jamesmrollins]

FYI: @emilymetcalf114 10/26 Workflow Leads meeting:

• @lzim would like to get help prioritizing this effort with current demand.
• Will work this in the hq_workflow.

[jamesmrollins]

@emilymetcalf114 and @lzim

Work that would be performed for this task (to help with planning)

1. Need to pull all the "i" information directly from variables in Vensim for the listed charts.
2. Complete this pull for all models.
3. Organize them back into a table for easier editing.
4. Put a new "i" information icon on the Results Dashboard. Attach given variables notes field to the table entry.
5. Edit "i" information (I could hire @TomRust to do the first pass edit on these).
6. Once editing complete, put the new "i" information back into the variables.
7. Troubleshoot and debug in Test-slow.
8. Repeat for each model.
9. We could split this task into 5 cards (by module) (3 story points each). Each requires a week for pull, a week for edit, a week for update and testing. Could take around 4-5 months.
10. I have capacity available to start this production line (@lrollins33).