wk2 dec_epic PBI Documentation Session 3 DEV

[mnallajerla]

• [x] Session 3 SEE Guide
• [x] Session 3 SAY Guide
• [x] Session 3 SAY Checklist

1. Link to the document and add relevant team members to the card.

• [ ] Add the link the current draft of the documentation for the issue:

2. Link to issues that must be edited in the document in the issue_tracker and feature_tracker. (use the # for the link to the issue)

• [ ] Issue
• [ ] Issue

3. Team Review

• [ ] Fidelity - check with Lindsey
• [ ] Data UI - check quant_workgroup
• [ ] Sim UI - check with model_workgroup and/or sim_workgroup

4. Review and Open Pull Requests (use the # for the link to the pull request)

• [ ] Check the draft for typos
• [ ] Check or open a pull request for the document edits

5. Review and/or Update Graphics

• [ ] Screenshots
• [ ] Gifs
• [ ] Logos/Icons
• [ ] Links

6. Dependencies

• [ ] Make sure that any edits you make that need to be added to depend_product are tracked (e.g., MTL Video)

7. Close Pull Requests

• [ ] Request review and/or close open pull requests for the document

[lijenn]

Discussed 8am WG 12/13:

• [ ] Agg is aggregate mix of services in a team
• [ ] Removed "Params" - 3 left hand tabs
• [ ] EDIT: in bold "Psychotherapy Patient Cohort"
  • [ ] Sankey Scalar (row 1) New Patient Start Rate (pts/wk) (row 2)
• [ ] DOCUMENTATION:

Due to the large amount of data in each report, we have to make ClinicSelections twice.

Learner - Facing "SEE" First, we make ClinicSelections to zoom in on a particular Veteran's care in the data tabs, then we can zoom out see what our care decisions are adding up to over time by reviewing team trends over the last two years in the viz tabs.

In the next session, we make ClinicSelections to review team data estimates related to common care problems: Care Coordination, Medication Management, Psychotherapy, Team (Aggregate) Care, and the Mental Health Continuum of Care for Suicide Prevention.

Facilitator - Facing - "SAY" The selections should be the same, so that Data viz and patient reports correspond to Sim UI.

MTL Blue - ClinicSelection for the session 2 report and ClinicSelection made for the session 3 report. MTL Red - ClinicSelection for the part 1 report and ClinicSelection for the part 2 report.

Making the same ClinicSelections for each report enables clinicians to zoom in on each Veteran's care in the data tabs and zoom out to review their team trends over timein the viz tabs. And, ensures that decisions they review in the Sim UI align with the Data UI team data.

MTL Red: Teams can use team meetings to regularly review data tabs to zoom in make better decisions for individual Veterans, and regularly review viz tabs to zoom out and see whether team trends are trending in a helpful direction.

MTL Blue: Once the team's upgrade their mental models via participatory learning from simulation (MTL Blue), Teams can use team meetings to regularly review data tabs to zoom in make better decisions for individual Veterans, and regularly review viz tabs to zoom out and see whether team trends are trending in a helpful direction.

• [ ] Note: How the Data UI works to create and define a team's local data

Key Use Case and "value-add" of the Modeling to Learn Data UI: Teams need to define themselves using Clinics.

Local self-definition is the only valid way to define a team over time. Providers can be cross-mapped to different sta6a.

e.g., Altoona PCT (PTSD Clinical Team) covered up to 6 sta6a.

LocationSID not all clinics (sta6a) level map VISTA scheduling "clinics" to specific provider names.

KEY IDEA: The Data UI exists to standardize the process by which a team defines itself, since there is not data-based standard that could apply everywhere over time.

Team is the unit at which care decisions are coordinate and made. Team is defined by the Green Box "Vista Clinics"

[mnallajerla]

Moving these notes above to the card tracking all theory and consistency review on documentation - #2423.