2024_12: update More Info sections to reflect 3.7 pivot to consult

[ljmoody]

The current More Info section in PROD does not reflect pivot to consult/3.7 release.

Current State

MTL Guides:

• ℹ️ Will need @matthewtomo or Dev team's help in updating this section (not changeable via the Admin Dashboard)
• Is there a "guide" for MTL 3.7?
• Should this section be removed or updated?
• Desired state of MTL Guides section needs to be defined.
  

MTL Links

• ℹ️ @ljmoody is able to make edit to this section, but cannot delete fields or add new ones
• Identify what links to keep
• Identify what links to remove
• Identify what links to add
  

MTL Navigation

• ℹ️ Will need @matthewtomo or Dev team's help in updating this section (not changeable via the Admin Dashboard)
• Highlighted portions are what I've flagged as areas needing updates
• @jamesmrollins will develop new drawings to explain navigation and give to @ljmoody and @matthewtomo for implementation and editing.
• Change "Navigating the Home Screen" to "Navigating the Home Page" to be consistent with manual terminology
  

MTL Modules

• ℹ️ @ljmoody is able to make updates to this section
• Change Aggregate and AGG to Team Care
• Change Measurement Based Stepped Care and Suicide Prevention to Team Flow
• Review module descriptions, complexity reveals, and experiment variables with @lzim to develop a list of changes to make
  

MTL Sections

• ℹ️ Will need @matthewtomo or Dev team's help in updating this section (not changeable via the Admin Dashboard)
• @jamesmrollins will provide updated drawings of MM without the X-Waiver dynamics, experiments and Team Data table references.
• @jamesmrollins will provide drawings that present the DDD.
  

MTL References

• ℹ️ @ljmoody is able to make updates to this section
• Did not include a screenshot here as it's rather long and small font.
• Are there additional resources to add? @lzim

AC:

• all revisions / updates are identified and documented
• all revisions made
• all revisions live in PROD

[ljmoody]

Discussed at wk2 2024_11 #sim_ui_workflow
@matthewtomo @ljmoody @jamesmrollins

• High priority, as this is outward facing to users
• @ljmoody & @matthewtomo will workshop as needed to make updates identified in this card
• @jamesmrollins will find, update, and post Illustrator files to Laura (+Matthew?) via Praxis Teams
• Is it possible to add more sections (to MTL Sections blue bar content)? And can one change the order of them?
  A: Pretty sure it's possible to add more sections, unsure about ability to change order. @matthewtomo & @jamesmrollins will check & add discovery here for tracking purposes

[lzim]

Thanks for identifying this @ljmoody

I think this is well-documented on the card.

To sum up what I see above with a couple other edits:

• Retitle MTL Guides section "Modeling to Learn Guides & Manuals"

  • @matthewtomo Include icon/link https://mtl.how/ with description: "MTL 3.7 Consult GitHub Repository"
  • @matthewtomo Include icon/link to https://mtl.how/manual with description: "MTL 3.7 Consult Manual"
  • @matthewtomo Include icon/link to https://mtl.how/facilitation with description: "MTL 3.0 Facilitation GitHub Repository"
  • @matthewtomo Include icon/link to https://mtl.how/facilitation_manual with description: "MTL 3.0 Facilitation Manual"

• MTL Links should keep https://mtl.how https://mtl.how/data and https://mtl.how/menu

  • Remove mtl.how icon to put in the Manual section above.
  • @matthewtomo Make sure https://mtl.how/menu is linked to MTL 3.7 self-registration for users who may want to access the menu.
    • @matthewtomo If possible to remove all the testing worlds from the https://mtl.how/menu drop down and leave only PROD teams, let's clean that up for menu as we are doing for Sim UI PROD (we want to keep DEV & TEST accounts from being listed in PROD for non-admin users).
  • Have the icon for mtl.how/videos point to https://mtl.how/why_how videos enduring videos made w/ILEAD last year.

• Keep MTL Navigation section and update to reflect current MTL 3.7 release as you've noted above, including DDD , updated navigation, MM with X-waiver removed, Team Care, Team Flow, etc.

Please also reflect the story points estimate, so we can keep a close eye on our budget guardrails as Bugs and other tasks come in.

Thanks so much!
FYI: @matthewtomo & @jamesmrollins

[ljmoody]

@lzim I understand what you're saying and can easily shift work focus—without exceeding budget targets.

[jamesmrollins]

@ljmoody @matthewtomo Here are the revamped page scrolls. I will rely on you two to provide instructions with respect to links related to icon/link combinations Lindsey specified above. I will email the EPS files in case a designer is needed to redo the non user-edited parts of the scroll.

more_info_page_3.7.pdf

[ljmoody]

11/18/24 DECISION: We'll make changes in TEST instance, then migrate to PROD.

---

@jamesmrollins, some changes needed to your pdf file, please:

• top navbar:
  

• MTL Guides & Manuals section:
  

• MTL Links section: FYI: I wasn't able to get the asterisk text to bump to the next line as shown in your mockup.
  

• MTL Navigation section:
  

• MTL Modules section: @ljmoody will make these changes & double-check experiment variables.
  

• MTL Sections section:
  

[ljmoody]

Please see above comments for tracking progress on this card.
@jamesmrollins, could you please make the changes in the above comment that are not checked off?
@matthewtomo, I tagged you in Lindsey's comment on tasks you have access to that I don't from the Admin Dashboard.

[ljmoody]

@lzim, please review italicization of the following terms and let me/us know if anything is amiss. We'd like to ensure we get it right the first time.

From your comment above:

Include icon/link to https://mtl.how/manual with description: "MTL 3.7 Consult Manual"

->Should this instead be: MTL 3.7 Consult Manual?

• yes
• no

Include icon/link to https://mtl.how/facilitation_manual with description: "MTL 3.0 Facilitation Manual"

-> Should this instead be: MTL 3.0 Facilitation Manual?

• yes
• no

Globals I've captured from your scribing, edits, etc:

• MTL 3.7
• Modeling to Learn 3.7
• MTL 3.7 Consult Manual
• MTL 2.0-3.0 External Implementation Facilitation Manual
• Modeling to Learn 3.7
• MTL Red (color: red)
• MTL Blue (color: blue)
• MTL 3.7 Red Live Consult (color: red)
• MTL 3.7 Blue Live Consult (color: blue)
• MTL 3.0 Facilitation
• MTL 3.0 Facilitation Manual

fyi @matthewtomo

[lzim]

Thanks for checking @ljmoody

• If it's the title of something and it's a specific release, then yes as you've shown above, please do put the entirety of that name/title/version/release, etc. in italics. Thanks!

FYI: @matthewtomo

[jamesmrollins]

@ljmoody I should be able to get the PDF update done before the end of the week.

[ljmoody]

11/26/24 update:

• more_info wireframes (pdf & eps files) are updated and located here.
• I'm reviewing against suggested edits above.

fyi @matthewtomo

[ljmoody]

@lzim, your clarification is needed on these points:

1. How Team Flow is expressed throughout the Sim.

This ask is also related to #3261 and this comment. (My apologies if I missed this was decided and addressed before.) Could you please specify how Team Flow should present in the Sim UI / More Info / Outputs and Text? See examples below.

• Team Flow
• Team Flow: Measurement Based Stepped Care
• Team Flow: Measurement-Based Stepped Care
• Team Flow: Measurement Based Stepped Care and Suicide Prevention
• Team Flow: Measurement-Based Stepped Care and Suicide Prevention

• use: "Team Flow: Measurement-based Stepped Care, Symptoms, and Suicide Prevention"

2. The label for Team Flow>Specialty Mental Health radio button.

The radio button is currently "SPC"; however, when clicked, you can see all stocks are referring to "SMH". The Data UI also refers to SMH. Please specify what this radio button label should be:

• SMH
• SPC

3. MTL Guides & Manuals section of More Info page.

Should this diagram be removed completely? I believe we removed it entirely from another location with the 3.7 release (the manual, perhaps?). If not, what changes would you like to see?

• Remove
• Modify as follows:

fyi @jamesmrollins @matthewtomo

[ljmoody]

@jamesmrollins, thanks for the updated PDF! I've reviewed and have further changes; however, you may want to wait to post an updated PDF until Lindsey has responded to the questions above. Also, some changes are because I missed them the first time around-oops! 😬

• MTL Navigation
  

• Navigating the Home Page
  

• MTL Modules - TEST instance updated with corrected Team Flow wording; ready for your screenshot, James
  

• Model Diagram
  

• Outputs and Text
  

fyi @matthewtomo

[lzim]

@ljmoody Re: your question:

This can work across uses:
"Team Flow: Measurement-based Stepped Care, Symptoms, and Suicide Prevention"

• Due to the re-organization of Office of Mental Health (OMH) and Office of Suicide Prevention (OSP) earlier this year it would be nice to reflect both "symptoms" and "suicide risk" just like the first sentence of the Team Flow description does.
• There is both high-risk for suicide-flag stock and flow structure and a symptom based stock and flow structure, which is more accurately reflected with the full title.
  ...whether you have enough characters for this across response web design formats...well let me know how that goes 😅

Let me know if that raises more questions. Thanks for all you're doing on this!

[ljmoody]

@lzim thank you for the response to question 1 - there are two others that followed it within the same comment. Please respond or I'll add to an agenda for next week.

[ljmoody]

Discussed at 12/9/24 Team Praxis meeting:

• @jamesmrollins to revise PDF this week with above edits, will contact @ljmoody if clarifications are needed
• Once PDF changes are made, @matthewtomo will be able to make backend changes
• @matthewtomo, a reminder to change within the Sim UI (you or Dev team):
  • Lindsey confirmed wanting "SPC" to change to "SMH"

[lzim]

Thanks @ljmoody I have no idea how introduced "SPC" it has never been that in any iteration ??

[matthewtomo]

@ljmoody @lzim

• SPC has been corrected to SMH on both the home page and on the team flow play page.
  

[jamesmrollins]

FYI @lzim
FOR: @ljmoody @matthewtomo

more_info_page_3.7.pdf

The Wireframe embedded here has been completed IAW with instructions above. EPS available for DEV designers as required. Let me know if you have any questions. Thanks ALL!

[matthewtomo]

Discussed Dev Standup wk3 2024_12
@matthewtomo @tejaspesquare

• Dev team has access to the new wireframes and will review them before implementation
• Dev team and @tejaspesquare will reach out on this card if they have any questions, or if they require any graphics for development

[ljmoody]

Discussed at ad hoc sync up wk3 2024_12
@matthewtomo @ljmoody @jamesmrollins
fyi @tejaspesquare

• @ljmoody reviewed the latest wireframe; 4 revisions needed
• @ljmoody and @matthewtomo met to discuss the latest wireframe
  • request last 2 pages of PDF/EPS are not included in next version (not related to this task)
• feedback given to @jamesmrollins, who is making adjustments and will re-post PDF and EPS files for Dev to use

[jamesmrollins]

@matthewtomo @ljmoody @tejaspesquare

Here is the latest and greatest PDF.

more_info_page_3.7.pdf

[ljmoody]

fyi @matthewtomo - reviewed the latest+greatest and it's ready to be worked with now.

[tejaspesquare]

Hello @jamesmrollins

Here is the latest and greatest PDF.

more_info_page_3.7.pdf

Could you please provide me with the EPS files for further processing?

[matthewtomo]

Hello @jamesmrollins

Here is the latest and greatest PDF.
more_info_page_3.7.pdf

Could you please provide me with the EPS files for further processing?

Discussed Dev Standup wk4 2024_12
@matthewtomo @tejaspesquare

• Discussed that no work is currently needed for admin page
• @jamesmrollins, @tejaspesquare would still like to have the .eps files to allow designer to extract any needed graphics at a higher fidelity

.eps files:
OneDrive_1_1-2-2025.zip

[matthewtomo]

Discussed Dev Standup wk2 2024_01
@matthewtomo @tejaspesquare

• Development on the changes for this page are still ongoing.

[matthewtomo]

Discussed Dev Standup wk4 2024_01
@matthewtomo @tejaspesquare

• Development for this task is still ongoing (expected to be completed this week)

fyi: @ljmoody

[tejaspesquare]

@ljmoody , @matthewtomo ,

• More Info page development is completed & can be verified on DEV instance.

Thank You!