2024_06 - Determine status and scope remaining in June Roadmap - Create a reports generator to support site reports

[emilymetcalf114]

Discussed wk2 jan_epic during MTL blue session 12 prep with QIICs. Feature requests include:

• [ ] Default 6 result dashboard views up in each module are the default in the tt_report Select Reports menu.
• [ ] Another useful feature would be to have the user selected views in the Results Dashboard be the defaults tt_reports.
• [ ] Select pages in the tt_report "Build the report you want."
• [ ] Select the text boxes across other worlds if when needed (shared world; team world) for the Alternative Experiments that have been run in multiple world

[jamesmrollins]

Go to Traffic Light Prototype for wireframes.

[jamesmrollins]

Benefits Hypothesis

Often, the end user does not need all the details contained within the legacy tt1, tt2 or tt3 report. The current reports generator supports customization by allowing the user to select experiments and charts for the given report, but also includes QHFD, Team Data Tables and Definitions of Terms that may not be required for the user's needs. These reports serve the capacity building function of MTL but are not conducive to the consultation type of service. Furthermore, the current reports do not include a way to include the Traffic Light infographic. The "Site Report" would include the Traffic Light info-graphic, have the ability to capture System SME observations in a text field (with editing tools) and present experiments and chart exhibits in the report.

Requirements

• [ ] Create a means for the end user to select each element of the site report (i.e., team data table, definitions of terms and others).
• [ ] Create a means for the user to add in text information directly to the report and provide common editing tools for formatting text.
• [ ] Create a means for the user to be able to upload document text from word, notepad and related word processing or text files.
• [ ] Create a means for the user to copy and paste text and graphics into the text window using the system clipboard.
• [ ] Provide a spell checker for the text information.
• [ ] Create a means for the end user to select the order in which the reports items are presented.
• [ ] Support a PDF download or print.
• [ ] Maintain the ability to export charts only.

Wireframe

tt Reports WIreframe.pdf

[lzim]

@jamesmrollins

@epearman @jamesmrollins Is there a status update from support_workflow on this one?

Recommended Next Steps:

• [ ] @emilymetcalf114 - Produce for review the final tt3 report to teams that just wrapped up MTL with @lzim & @jamesmrollins
• [ ] @jamesmrollins & @lzim use review to refine the tt_reports wireframe MVP>
• [ ] @emilymetcalf114 & @epearman (see wk2 feb_epic 8AM_workflow agenda) - Evaluate data on tt reports, co-planning documents and surveys are being sent now using Dynamics.

[lzim]

wk3 mar_epic

Responses on sim_ui_workflow

Excellent @jamesmrollins 🚀 Thank you so much!

Apologies we were short on time at 8am_workflow today to cover these. We are working on improving that as fast as we can!

Re: #2835 - We'll review the tt_report wireframe w/#systems_smes tomorrow.

• [ ] I'll check to see if I have any questions to finalize call about review with #qiics too or not.

I would also like to review w/#systems_smes the TEST decision meter prototype at https://mtl.how/test

• [ ] @emilymetcalf114 and @lzim @dlkibbe @dlounsbu We'll record so you have #user_acceptance_testing

@jamesmrollins asked and @lzim answered

What is the desired point-of-entry for the tt report (i.e., the Dynamic Decision Dashboard, Facilitator Panel, both)?

@lzim Answer: First Screen for all users no matter login type. Yes, Facilitator Panel. Yes, Dynamic Decision Dashboard.

Return Question from @lzim I think we may need to add/replace another icon on the main navigation to get to it from anywhere in the Sim UI. Recommendations?

Will the consultative approach use the QHFD structure for comments, or do we need to add a more general "comments" or "observations" field?

• tt_report needs to be 1-2 pages without the PARTNER or BUILD phases that the Q/H/F/D support, which will be in our MTL external implementation facilitation approach.

For "modeling consultation services:" we need to be able to create "decision support" "recommendations" in the tt_report

• [x] open-ended list of recommendations
• [x] open text recommendations

Feature Request: the tt_report includes static images for key insights drawn from the

• [ ] "dynamic decision dashboard" - Key high volume states, and inflow <> outflow imbalances.
• [ ] "decision meters" - Key recommended decision heuristics in pts/wk or appts wk for the site.

Feature Request: The "dynamic decision dashboard" creates a zoom in/out interactivity to track the scaling from

Zoom in

• Common team care problems: CC, MM, PSY, Team (AGG) Care (pts/wk or appts/wk)

Zoom out

• Team (SP) Flow - episodes of care (pts/wk)
• Desired state Team (SP) Flow - facility/mo or visn/quarter aligned with MHOC
• Desired state Health Equity Sankey in Power BI (facility/mo or visn/quarter)

DECISION: Remove "AGG" and "SP" in our 2024 MTL 4.0 release that includes all these modeling consultation and decision support features and health equity.

We haven't determined how experimentation will work from the Dynamic Decision Dashboard, thus we don't have an algorithm for how we save experiments for all models, how the experiments are conducted once we drill down to a particular module, or how these might be assigned to a working group. So we could use ideas on how the interaction would look with a facility or VISN decision-maker and how their decisions would affect or relate to follow on work.

REMINDER: Team PSD determine with #systems_smes because no other user group is modeling any more. No capacity building (BUILD) phase, just consultation.

Next Steps - Finalize for Slide Deck/Guides

• Site leadership in the consultation model will ONLY see the items below
  1. Sharepoint & "Site Studies" (Story J)
  2. Slide Decks of "Use Cases"
  3. Decision Meters of new local decision heuristics
  4. Dynamic Decision Dashboard - Review volume of pts and appts & inflow/outflow imbalances
  5. tt_report - see above
  6. In power_bi - sankey with facility/mo and visn/quarter

So, these are all #systems_sme and #support_workflow answers we will review wk3 mar_epic (tomorrow)

• [ ] #systems_sme - How we experiment
• [ ] #systems_sme - How we save experiments
• [ ] #support_workflow @emilymetcalf114 @epearman - How to assign users to groups in Forio Epicenter Sim UI

FYI #adjudicate_memo @lzim 3 story points to be added. @epearman @emilymetcalf114 @hthrmarsh

[jamesmrollins]

FYI

• [ ] @emilymetcalf114
• [ ] @epearman
• [ ] @hirenp-waferwire
• [ ] @lzim

Below is a fresh drawing for the tt report:

1. User would click tt Admin from either the Decision Dashboard or the Facilitator Panel to access a menu of experiments, modules and so forth to include in their report rendering. Note this entire menu will likely be replaced by the target report builder.
2. When the user has aligned all resources, they click on "Preview" to render the webpage.
3. The "Recommendations" section has a set of editing tools and an unlimited word count.
4. The user can incrementally save and return to this page later.
5. The user can upload a text file such as a Word document.
6. Care Decision Meters as from first wireframe.
7. Patient Flows might come from the Team (SP) Flow module, updated with MHOC variables to play forward.
8. The user can add more charts from the module using this icon.
9. Team Care would come from Team (AGG) Care module.
10. Health Equity Patient Flows indicating our future model that might help decision-makers to play forward.

I've also included a PDF attachment for your closer examination and use.

tt_reportsgenerator v2.pdf

[lzim]

Discussed at wk3 mar_epic sim_ui_workflow

@lzim @jamesmrollins @emilymetcalf114 @epearman @hthrmarsh

Based on conversation at consult_facilitate_workflow with #qiic

• [x] Determined 2 types of site visit reports are required.

DECISION Site Report not the Team Time Report.

Next Steps:

• [ ] @emilymetcalf114 Brief "heads up" report - get template from QIICs.
• [ ] @lzim Email Cliff & Claire about the still to be finalized overall template. #2924

[ghost]

ajudicate_memo march efforts for this issue will be tracked on #2937.

Dispositioning this issue to the backlog until blocker #crossref #2924 is removed - Need the template that the QIICs use with the site.

[jamesmrollins]

Cross Reference: #2785

From the 6/1 F2F

DECISION: tt Reports are now called mtl red report and mtl blue report. (supports non-functional requirements for maintaining parallel development between studies)

Benefits Hypothesis

Simplified reporting will support SMEs, QIICs and Facility Managers by providing needed information in a simplified format including PPT and PDF formats. The reporting will provide a means for experts to input text suggestions and maximum flexibility for adding charts and other illustrations such as Care Decision meters. The report builder will be easy to use, offering reduced clicks, more intuitive selection of experiments and charts and a text field with editing tools.

Requirements

• [ ] Investigate reporting via PDF and PPT for specific mtl Report uses.
• [ ] The tt report builder is onerous - investigate ways to simplify.
• [ ] Investigate why we are collecting research arm data in the "Team Setup"
• [ ] Executive Leadership Team (ELT), Primary Care Services (PCS) and Government Accountability Office (GAO).
• [ ] The report will be used to support the facilitator, System SME and "Facility Team."
• [ ] At the top of the report, "Summary of Recommendations" field with full edit capability.
• [ ] Include Decision meters, see #2804 .

[lzim]

wk1 2024_06 - Not 100% what this card is tracking compared to other MTL 3.7 cards

Can you advise for our June Roadmap Event @ljmoody by chance?

[ljmoody]

Hi @lzim, Some of the tasks on this card are already in place or in the works. Others seem outdated (and predate my time on the team). MTL reports generator is being tracked in the following open cards (and multiple closed ones, too). It's likely we may revisit the functionality and design aspects of the reports generator via these cards. As such, I'm closing this one. FYI: @jamesmrollins, @lijenn - any issue with this action?

• 3028, test

• 3033, train

• 2987, doc