Closed jamesmrollins closed 5 years ago
@jamesmrollins : About the Data switch label in MM and CC:
Thanks for working on this! The switch definitely needed a title, Can we say: "Prioritize Data" instead of "Prioritize Patients"?
Also, about the model diagram: I don't think we need the switch in the model diagram at all anymore. It doesn't interfere with any feedback loop, so it doesn't need to overlap any arrows like it did before. As long as the switch is at the top of the experiment section, I think it's clear. We will need a "BC" button, so users can see what value for RVI is used if they select "Use Team Data for New Patient Starting Rate" -- you can grab the value from the Vensim variable "fRVI"
Psy Model Requested Changes Below
@jamesmrollins While reviewing the systems stories in PSY during the qual_workgroup, we realized it would make sense to have the model diagram labelled with "Starters" "Initiators" and "Completers".
This language is the most relevant and clear to our clinicians/learners.
@staceypark are you talking about the labels I highlighted below? If not, please provide a screenshot - thanks, James
@jamesrollins We were imagining additional labels next to those rather than replacing them
@staceypark like so?
Hmm maybe it could be bolded? @lzim what do you think?
@jamesmrollins , @staceypark , @lzim -- If you're adding to those stock labels, how making a similar change to the outflows to "continue after 3 months" (circled in purple)?
Instead of "Continue Treatment Rate (after 3 Months) from Patients In First Visit" the labels could be shortened to: "Starters Continuing Treatment (after 3 Months) Rate" "Initiators Continuing Treatment (after 3 Months) Rate" "Completers Continuing Treatment (after 3 Months) Rate"
Hi @jamesmrollins and @lzim : I was reviewing AGG in test, and everything looks good! I did have one question, though: Did we intend to change the default switch setting for the service proportions? I thought our default was going to be team data, not "balanced."
Hi @TomRust below are the instructions in the master_crosswalk.xlsx. Easy enough to change, just give me the word . . .
0-1 range (this is a binary switch). Default is 1. If set to 0, then model refers to "(Service) User-defined Service Proportions from Team Data", else model refers to "(Service) Service Proportions Balanced Across Team Variables." "BC" values are returned from "(Service) Service Proportions Balanced Across Team Variables" at time 0. "i" information will be mapped to "Adjuctive User-defined Service Proportions from Team Data."
I agree with @TomRust that I thought default was "Service Proportions from Team Data." I'm not sure what the "i" quote means @jamesmrollins
"Adjuctive User-defined Service Proportions from Team Data."
Is that a typo?
@TomRust and @lzim I have already remapped the variables and reset the default to based on Tom's observations. Since the variables are no longer arrayed, I needed to map the "i" information to just one of the 6 variables that share the "Service Proportions from Team Data" experiment slider tile. The "Balanced" "i" information mapped to the "Use Team Data on New Pt Referrals" variable. By the way @TomRust , I need "i" text for the "Balanced" selection on the Select Mode switch.
@jamesmrollins and @lzim How about this itext explaining the "balanced" side of the switch:
"Balanced" mode continually adjusts the service proportions to both minimize new patient wait time and maximize the likelihood that an existing patient will receive care at the desired Return-to-Clinic Visit Interval, i.e., the team in the model will always decide to start just the right number of patients in each service, given the team's quality goals, supply, and patients' characteristics. In this mode, the service proportions automatically re-balance to accommodate any experiment. The base-case values for these parameters may differ from the estimates calculated from team data.
Below at request of @staceypark
Yes, thanks @jamesrollins and @staceypark!
2 nit-picky tweaks, please?
@branscombj request:
Yes, thank you @jamesmrollins ! @lzim @staceypark
FYI @jamesmrollins @TomRust @branscombj @dlkibbe @dlounsbu @staceypark @holbrooa @saveth @lkdolan
FRIDAY CELEBRATION: 🎈 🎈 🎈 🎈
I believe that with the Sim UI for MTL DEMO/TEAM and PROD now at MTL 1.8
We completed 26 items of a 30 item release schedule within ~1 week of the 4/23 deadline
A 90 day sprint to go from MTL 1.7 release to MTL 1.8 release. IMPRESSIVE 🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥
Original Post from James with HQ Checklist Below
Below are the development scheme and instructions to support more "agile" development. This means that we will take smaller development, test and deployment steps as we make our way to version 1.8. This scheme will enable us to take on smaller chunks of work, with respect to reviewing the changes as it relates to our given functional areas.
A typical sprint consists of five steps:
- Model modifications are completed and passed to Takouba (if required)
- Takouba designs or modifies design of SIM UI, and communicates design spec with DEV.
- DEV completes work and puts new version into TEST environment.
- Everyone who is a "To" addressee, reviews the sprint checklist (to be published) and signs off on their area.
- Sprint is moved from TEST to PROD.
Below is a listing of upcoming Sprints. DEV to TEST schedule to be published. BOLD indicates completed or documented for completion as of 4/23. 1.7.1 | Global Changes to model:
THE FOUR REMAINING ITEMS include @jamesmrollins @lkdolan @dlkibbe @branscombj @staceypark With the exception of 508 we are almost done with many of these too.
GREAT WORK EVERYONE - WHAT A GREAT TEAM 🏆🏆 🏆 🏆 🏆 🏆 🏆 🏆 🏆 🏆 🏆 🏆 🏆 🏆 🏆 🏆 🏆
@jamesmrollins and @staceypark
Can we get the new expand icon in HELP in PROD? Thanks!
@lzim - right here?
@jamesmrollins yep!
@jamesmrollins Can this issue be closed?
I'm looking at all the issues under the 1.8 Sprint Milestone and hoping that they can be closed. Thanks! 🏃♀
FYI: @staceypark
@lzim @TomRust @saveth @staceypark @holbrooa @branscombj @dlkibbe @dlounsbu @lkdolan
Below are the development scheme and instructions to support more "agile" development. This means that we will take smaller development, test and deployment steps as we make our way to version 1.8. This scheme will enable us to take on smaller chunks of work, with respect to reviewing the changes as it relates to our given functional areas.
A typical sprint consists of five steps:
Below is a listing of upcoming Sprints. DEV to TEST schedule to be published. BOLD indicates completed or documented for completion as of 4/23.
1.7.1 | Global Changes to model:
a. Change slider label to “Use Team Data for Patient Start Rate or RVI” and add “bc” 2x2 table
b. Change Experiments section to include this slider under Engagement Pattern sub-header
c. Range on the slider in weeks up to 5 years (260 weeks) - actual designed was 208 weeks 3.Change CC/MM Model Diagram to say “Appointments for New Patients” for green variable (stays the same “Add Appointments for New Patients” in Experiments Section) - actual designed was "Appointment Slots Reserved for New Patients" slider, same with icon in diagram.
3.Check for MTL 1.8 edits in MTL SEE/SAY scripts (Jane & Debbie are point)