2024_11: remove AGG and SP from outward-facing Sim, Demo, & Team projects + Documentation

[ljmoody]

Decision at wk3 2024_09 #sim_ui_workflow:

• ALL instances of "AGGREGATE" or "AGG" should now be only "Team Care"
• ALL instances of "SUICIDE PREVENTION" or "SP" should not only be "Team Flow" (keeping the setting predecessor GMH/SMH/PC PCMHI as appropriate)
• But, Data UI, Power BI still says "Team (AGG) Care" and "Team (SP) Flow" -- behind the scenes, things users don't see

AC:

• [ ] While developing, testing, & documenting, identify locations in Sim, Demo, Team and Documentation where these terms are used/found
• [ ] As they're identified, post a picture, highlight usage, specify what it should be changed to, and tag @ljmoody, @matthewtomo
• [ ] All instances of Aggregate / AGG removed
• [ ] All instances of Suicide Prevention / SP removed

[ljmoody]

Previously identified before tracking via this card:

• [x] AGG in Outputs and Text section of Sim UI Play page: ✅ resolved:

• [x] Aggregate in Save Experiment pop-up: ✅ resolved:

• [ ] SP in blue bar header - change to "GMH Team Flow":

[ljmoody]

Tejas would like to know if the entire name is desired or an acronym could be used in this case. The whole name adds more visual clutter, yet the acronyms aren't widely used (not yet, anyway) for these.

@lzim, what is your preference?

• [x] Team Care experiment code:

  • [x] use entire name
  • [ ] use acronym

• [x] Team Flow experiment code:

  • [x] use entire name
  • [ ] use acronym

[ljmoody]

9/19/24 comment from Tejas (copied from issue #3158, before tracking this effort in a unique card):

Hello @ljmoody , As per notes from Teams:

DECISION: ALL instances of "AGGREGATE" or "AGG" should now be only "Team Care" in any Sim UI, Demo, Team, Documentation. ALL instances of "SP" should now be only "Team Flow" (keeping the setting predecessor GMH/SMH/PC PCMHI as appropriate)

These changes are available on Dev environment.

• [ ] SIM UI
• [ ] MTL Demo

Team Care

Experiment

Team Flow

Note: For this development, it is recommended to avoid manual deployment & get support using Git CI-CD to facilitate the deployment of code into TEST & Prod environment as it involves changes at multiple locations.

[matthewtomo]

Discussed Friday Dev Standup wk_3 2024_09 @matthewtomo @tejaspesquare

• Clarified that the Dev team only really needs to keep an eye out for "agg" or "sp" in the Sim, Demo, Team projects
• Clarified that if they do find "agg" or "sp" they should document that in this card, and then replace it with the correct terminology
• @matthewtomo and @ljmoody will check in with @lzim to verify whether or not "TC" and "TF" are adequate abbreviations for "Team Care" and "Team Flow", and will report back to @tejaspesquare. (This is only currently planned to be used for the experiments section as discussed above)

[matthewtomo]

Discussed Monday Dev Standup wk_4 2024_09 @matthewtomo @tejaspesquare

• @tejaspesquare identified this section of text in the Demo site:
• @ljmoody any thoughts on corrections for this paragraph?

[matthewtomo]

• Additional instances located when verifying that SDM-DOCs are up to date:
• This is the name of the actual file used by our system, changing this would require editing either:
  • Changing our file names and changing all of the locations in our code where those file names are used, OR
  • Changing our currently working automation (that generates the SDM-DOCs) in some way

[ljmoody]

Discussed at wk4 2024_09 #9am_workflow @lzim @ljmoody @matthewtomo @dlkibbe

• [x] change "a team's mix of aggregate services" to "team care across a mix of services"
• [x] change "suicide prevention" to "team flow"
• [x] additional change: please hyphenate "measurement based" (green edit in screenshot)
• fyi: these updates are relevant to #3158.

• @ljmoody any thoughts on corrections for this paragraph?

[tejaspesquare]

Hello Matthew,

• Additional instances located when verifying that SDM-DOCs are up to date:

This has been manually updated at one location for the time being, as we have identified a static definition; however, it is essential to confirm whether this operates correctly with the CI-CD.

Furthermore, we identified similar occurrences throughout the document in various locations (count surpassing one thousand). We have not yet investigated the necessary actions required to replace each of them.

[matthewtomo]

Hi @tejaspesquare, I think for now we decided that it was okay to leave the sp and agg in those SDM-DOCs, since we want them to be accurate to the "behind the scenes" filename. The above comment was more focused on documenting them and providing potential solutions to discuss in the #9am_workflow_meeting.

[ljmoody]

@ljmoody needs to remove from MTL 3.7 Consult Manual:

• [x] 1. from Make, View, and Export Team Clinic Selections for Import to Sim UI section:

[tejaspesquare]

Hello Matthew,

• Additional instances located when verifying that SDM-DOCs are up to date:

The document header name has been modified for following and is now accessible on the TEST environment.

Team Flow

Team Care

[matthewtomo]

@tejaspesquare I think that based on previous discussion we decided to keep the original filenames in the SDM-DOCs, since we want to make sure that it matches the name of the file we are actually using in our system.

Would we be able to revert that change?

Hi @tejaspesquare, I think for now we decided that it was okay to leave the sp and agg in those SDM-DOCs, since we want them to be accurate to the "behind the scenes" filename. The above comment was more focused on documenting them and providing potential solutions to discuss in the #9am_workflow_meeting.

[matthewtomo]

Discussed Friday Dev Standup wk_4 2024_09 @matthewtomo @tejaspesquare

• The above issue has been resolved

@tejaspesquare I think that based on previous discussion we decided to keep the original filenames in the SDM-DOCs, since we want to make sure that it matches the name of the file we are actually using in our system.

Would we be able to revert that change?

Hi @tejaspesquare, I think for now we decided that it was okay to leave the sp and agg in those SDM-DOCs, since we want them to be accurate to the "behind the scenes" filename. The above comment was more focused on documenting them and providing potential solutions to discuss in the #9am_workflow_meeting.

• Additionally, the Demo site now is up to date feature-wise with Demo-test, but we encountered a bug during our trial this morning
• [x] @matthewtomo will document related bugs to the Demo site in new cards later today.

fyi: @ljmoody

[matthewtomo]

Discussed Dev Standup wk_1 2024_10 @matthewtomo @tejaspesquare

• Tutor prompt 4 for team care and team flow positioning has been resolved

fyi: @ljmoody

---

ℹ️: added this comment + link to #3202, dev/test flow tutor prompts

[ljmoody]

UPDATE 11/22/24: We will make these changes at a later date. A new card was created for Admin-facing AGG & SP changes to make - #3321

---

@matthewtomo, is it relevant to also change the following for what Admin users view in the Tutor Admin Dash? (I don't remember if we discussed this already.)

And another level down (example):

[ljmoody]

@matthewtomo, following up on unchecked items on this card.

• [ ] Change needed. Observed in TEST and PROD, fyi:

• Are the MTL Module save names listed correct (i.e., no need to specify service choice for the modules with those)? Want to be sure before crossing off the last item in my Sept 19 comment above. Team Flow examples:

[ljmoody]

@lzim, looking for your direction in this comment above regarding changing Team Care to "TC" and Team Flow to "TF" within the Experiment maintenance sidebar.

If you approve, I'd also like to propose the same change occur within the Tutor Administrative Dashboard:

fyi @matthewtomo

[lzim]

If there is room I'd rather keep "Team Care" and "Team Flow" not use TC or TF.

The reason, beyond the fact that they have more characters than the 9 character (incl. space) "Team Care" and "Team Flow" do, is that many clinicians will more readily grasp the CC is short for "Care Coordination" and that MM is short for "Medication Management" and PSY is short for "Psychotherapy." Those are more likely to be abbreviations they may already use in clinical care.

In contrast, "Team Care" and "Team Flow" are short hands that have really more developed with MTL development, and are therefore less familiar and not as readily grasped without being spelled out.

[ljmoody]

@lzim, your explanation helps my understanding of your response - thank you!

@matthewtomo. revised my comment above for renaming within the Tutor Admin Dashboard.

[matthewtomo]

is it relevant to also change the following for what Admin users view in the Tutor Admin Dash? (I don't remember if we discussed this already.)

Yes, but I'm thinking that this might be a good change to make later due to current scoping and how it will not be seen by outside users (only admins)

[matthewtomo]

Discussed Dev Standup wk_1 2024_10 @matthewtomo @tejaspesquare

@matthewtomo, following up on unchecked items on this card.

• [ ] Change needed. Observed in TEST and PROD, fyi:

• [ ] @lzim @ljmoody are we certain we wish to remove the description of Team Flow from the above graphic? I thought we had already changed the label to be Team Flow + the description.

• Are the MTL Module save names listed correct (i.e., no need to specify service choice for the modules with those)? Want to be sure before crossing off the last item in my Sept 19 comment above. Team Flow examples:

• @ljmoody experiments for Team Flow save all three of those services at the same time (because the Team Flow model uses all three). The labels for the diagrams are used to only show one at a time to the user and reduce complexity.

[ljmoody]

Yes, but I'm thinking that this might be a good change to make later due to current scoping and how it will not be seen by outside users (only admins)

Absolutely agree. I bundled it here because it's the same subject matter, but do agree it can/should be at a later date. I'll create a card (#3321) for those changes and update my comment above to include+link to that.