Bug Sim UI Team Care: The saving dialogue is saving an RVI experiment for MM with "ED" which should be for engagement duration

[lzim]

FYI @jamesmrollins
Let's talk about this at support_workflow or sim_ui_workflow

In the MTL Blue team that I co-facilitate on Thurs (wrapping up 02/02) I see that an experiment adjusting the RVI from 9 weeks to 12 weeks is labeled with "ED."

Shouldn't that be for engagement duration?

Also at wk4 jan_epic @emilymetcalf114 @epearman @lzim

Noticed that the experiment save order does not reflect the order of the drop down menu of changes made in the save dialogue See example of intake below.

[jamesmrollins]

@lzim @epearman @emilymetcalf114 @hirenp-waferwire

Problem

When the user saves an experiment, there is an inconsistency between the saved filename string and the actual saved variable and value.

Hypothesis

If the user saves the experiment multiple times before the run, the algorithm may not be accurately recording the experiment settings. Thus, when the experiment is run and saved, the saved filename string is incorrect.

Experiment

1. Open Medication Management Module. Change the setting of an experiment variable. Then save the experiment without running the experiment.

2. Change the experiment setting of original variable and add in another experiment variable setting. Save the experiment without running the experiment.

3. Change experiment settings from original setting on ED panel to base case. Save the experiment. The "edoud" and the "edo" value calculations show negative values. Since they are on "BC," they should not be reported in the save name string.

4. Run the simulation. Change the RVI value. Click save. The Sim UI, now includes the post-run changes to the experiment variables in the save string. RVI change was not a part of the run.

Conclusions

1. In the use case above, the user may have made a post run change and then clicked save. Since the Sim UI does not lock out the experiment sliders post-run, this is a failure mode.
2. In the experimentation, the Sim UI does not appear to be gathering some experiment sliders setting properly (ED), indicating another potential failure mode.

Recommendations

1. Lock the experiment sliders after the run, so they do not get saved improperly.
2. Investigate the ED issue at the code level and determine cause.
3. Double check all the other sliders in all the modules to ensure they are gathering data correctly for the experiment name string.

Needed Decision

In which order would we like the variables to appear? Experiment variable order or dropdown order? Both were specified during the design phase.

[lzim]

@jamesmrollins

• [x] Makes sense to lock the sliders after a run.
• [x] Great to investigate the ED issue, but definitely don't want any trouble for this team's last session, which is Thurs 02/02.
• [ ] The inconsistency above in list of variables between the ? icon and the sliders isn't even the one I noticed. But, I see it's what's driving the different order in the save dialogue. Recommendation: Check align with the Team Data Table and ideally ensure that this order also aligns with the MTL 3.0 Power BI Data UI

Does that make sense to you?

[jamesmrollins]

@lzim

lol.

Looks like we have an even split (with "?" list consistent with the Data UI).

Deeper Dive

• [ ] CC, MM, Psy and SP Data UI do not line up very well with the Sim UI.
• [ ] While it would be easier to change the Sim UI for the Team (Agg) Care instance above, achieving this consistency across all the modules would be easier in the Data UI.
• [ ] Which is authoritative?

[lzim]

Add to wk1 feb_epic support_workflow agenda

@epearman @emilymetcalf114 @jamesmrollins @lzim

[emilymetcalf114]

@lzim @jamesmrollins @epearman Let's move to wk1 feb_epic sim_ui_workflow agenda tomorrow instead, since Lindsey and I will miss support_workflow. Thanks!

[ghost]

@lzim @emilymetcalf114

Discussed during support_workflow wk1 feb_epic

• Multiple places (Experiment Slider, Team Data Table, Experiment Values) will need to be changed in the sim UI to match the order of the variables in the Data UI.

  ---

• [ ] Should James proceed with changing all places in the SIM UI that do not match the order of the variable in the Data UI or should the order of the tabs in the Data UI be changed to match the SIM UI?

  • [ ] @epearman needs to look into what would be involved in changing the tabs order in the Data UI

[ghost]

Discussed at wk1 feb_epic sim_ui

DECISION Hold on this issue since we need to review and align it with UAD and bookability

crossref #2851 - ASAP Due Bug: Re-Review the Binning of Encounters for Time Assumptions

1. Discussion - Evaluate in relation to UAD - bookability and labor mapping - wk1_feb mixed_methods

• [ ] @jamesmrollins review UAD bookability
• [ ] @emilymetcalf114 review UAD bookability
• [ ] @epearman review UAD bookability
• [ ] @lzim review UAD bookability

[lzim]

@epearman @emilymetcalf114 @jamesmrollins

I'm surprised @jamesmrollins is the only one to review UAD bookability??