nov_2021

[lijenn]

11/4 HQ Workgroup Notes:

ORD Databases

• R01: We believed this was already VINCI provisioned.
• IIR: We believed we needed to have VINCI provision this.

Documentation:

• Always use the official project site, which is tracking the trail of communication/documentation rather than email.
• If email is used, make sure to always cc Lindsey on compliance-related items.

[mnallajerla]

11/8 Workgroup Leads

Top Things this Week

• NIH Annual Report due today - @lzim coordinating with Marisela; watch out for updates from Debbie for progress report
• IIR/R01 VINCI provisioning issue - @dkngenda and @mnallajerla working on it. Reviewed materials, will share provisioning request language when it is ready for review
• CI2I Forms (sp?)

Calendar Review

• Manuscript Monday - no one signed up as of yet. might use this time and then have presentations at Team Time
• Veteran's Day on Thursday - Quant Operations and HQ CANCELLED

Discussion Review of Manuscript Progress and Needs

• What are the needs?
• Defining Dev, Operations, Research etc streams; remembering they are rooted in a research tradition
• Next step is getting papers written, but in a way that conveys principles.

[lzim]

wk 3 8AM Workgroup Leads 11/15/21

@lzim to touch base briefly at team_temp - then at 8AM Workgroup Leads @mnallajerla @dkngenda @lijenn @jamesmrollins please attend to the following 2 primary tasks:

1. Review the wk3 sprint 11/15/21 and reduce down from > 200 pts due this week to approximately 40-50 pts due this week & ~40-50 during wl4 and wk5 of _novepic and determine what can be done in dec_epic - Note we are finishing about 50 pts/sprint, yet this has not been reduced. Questions need to be asked, discussed, decisions made.
2. Reflect on the functions most needed at 8AM workgroup leads in our new hires when there is no PI and no Research Program Manager at workgroup leads :smile_cat:

11/15/2021 Schedule

• 7AM NIH Progress Report - Our work to PAVIR was due last week. Lindsey is coordinating w/PAVIR this AM and will need to miss 8AM Workgroup Leads.
• 10AM Data Review w/Andrew rescheduled to 11/22 so that we can draft cohort requests for Ryan to be reviewed on Wed 11/17 call.
• 10AM @lzim has IRI meeting
• 11AM @lzim & @lijenn meet w/PTEMS about Dynamics
• 12noon @lzim teaches Stanford class
• 12:30PM - #manuscriptmonday - Review & work to finalize a) Figures, b) Methods templates, d) Take home message for discussion section for manuscripts
• Note: @lijenn & @dkngenda leave early today due to SAFe on Thurs/Fri

Some Top Priorities for the Day @lijenn

• Gracelyn is confirmed for SAFe; Need to determine between Tom, Libby and Swap who gets the last seat.
• Co-planning! Touch base with QIICs this AM.
• Coordinate w/John & David about Power BI testing with their team.
• Can you see the IRB feedback we got for R01? Need to respond today.

@dkngenda & @mnallajerla

• Finalize draft for R01 and IIR VINCI cohort requests

[mnallajerla]

8 AM WG Leads 11/15

Calendar Review

• SAfe Training this week

• Review discussion from Team Time (see above for comments from Lindsey.)

• See above for Monday schedule

• Manuscript Monday - no one signed up yet but assume folks are working on figure

• Tuesday Facilitate WorkGroup: CoPlanning

• TeamTime: No one signed up but same as Manuscript Monday

• Wednesday Quant Research: Meet with Ryan about VINCI data request

• Wednesday Support:

• Wednesday SIM UI: Hawaii contract, Save feature issue, @dkngenda to attend SIM UI unless this is addressed during Support

• Thursday/Friday - SAFe training.

• Thursday Hawaii meeting: @lzim and @jamesmrollins to meet with Hawaii team @ 1 PM PST

• Thursday HQ: end the day with this

[dkngenda]

Meetings:

• 10 AM meeting with Andrew

• MM: Introduction/Lit review discussion

  • Setting the context for the manuscripts we are working on.

  • What you want your take away message to be.

  • mm timeline:

_novepic wk3 - Finalize - Participatory Take Away Message, Methods Template, Co-authors, Participatory Synthesis Figure wk4 - Finalize - Introduction/Literature review _decepic wk1 - Edit - revisit the "who" the agents of actions, the voice/POV centered. wk2 - Submit any manuscripts that are ready.

Key ideas for MM:

• Cite your justifications for your take-away messages (e.g. AGG - What is the state of the science about policy resistance?)

• Our citations should come from our target journals, Imp Sci and Community Psychology. Search for articles (e.g. "policy resistance" AND "healthcare").

  • What similarities do we have?

  • What gaps do we cover?

• What we need to cover is already in our OSF bibliography

• People will be more invested if they are able to picture these teams and be invested in them, and why these things are important

• Think about the gaze of the audience

STORY: Characters in a world.

• • Challenges to overcome.
• Applied healthcare research:
• Characters:
• Patients
• Providers
• Policymakers
• Mentees
• Statististicians
• Engineers

How our papers should flow

1. Clarify PARTICIPATORY takeaway message for Discussion first.

2. INTRO Set it up: Applied Problem: Stakeholders in context, AND Situate unique scientific question/gap: Scientists in methods.

[lijenn]

wk5 nov_epic Overarching Top Priorities:

• [ ] 1. Power BI Data UI UAT
• [ ] 2. IIR Progress report - VINCI request
• [ ] 3. Manuscripts - Submit next month
• [ ] 4. R01 Progress Reports - Dr. Su
• [ ] 5. Co-planning

SAMHSA - DOH Hawaii

• VA Educational Project
• Not Research
• mtl.info@va.gov - Not VA Healthcare Operations (why mtl.help@va.gov).

Last Stanford QI Class 12noon-1PM - @lijenn

• SunetID info came in today - Evaluation survey
• Just need a fresh copy and link for the Fall 2021 PGY 3 group.

Facilitate WG

• [ ] Co-planning
• [ ] PBI Updates for John and David

ASAP and/or Wednesday Overflow if needed

• [ ] R01 Progress Report
  • [ ] GSU Subaward - Need to justify Jane rolling off and describe Debbie's role of support, keep an eye on updated biosketche from Debbie, need FTE percent for the budget side from Marisela. FYI @lijenn @mnallajerla to track this task to keep it moving forward.
  • [ ] Updated Power Analysis AIM 1 and AIM 2 @dkngenda
    • Cohort requests to VINCI this AM
    • Re-evaluate AIM 1A & 1B enrollment tables for initial power analysis

Progress Reports & Grant Submissions

• We have to justify any staffing changes with a scientific rationale.
• Progress reports release the next year's funds. Learning note: *Not tailoring a Biosketch to the application at hand can be the difference between having to resubmit the grant or getting it funded.

research/309 #309 - 500 Series Mental Health Stop Code

• Location two stop codes that denote TMH - 179 & 117.
• Teams > quant_workgroup > Files
• 00_Orientation_Onboarding_References
• Phone series stop codes became more important than ever.
• EBPharm.
• EBPsy.

Double-check:

• Encounters managed by phone.
• CPT Code use guidance from CMS.

PTSD_OMHO Table > listStopCodes There are 64 stop codes in that list.

2389 - Card to track these documentation tasks for Quant (ie stop codes)

• [ ] Tracking Master Documentation
• [ ] [ ] Align data resources, for example, stop code list.

research/311 - Ensure that Stopcode 179 (Veterans Video Connect-VVC) is included in all our research and operations code bases.

liststopcode used to populate the clinic lists in the Clinic Selection

• We only have 64 Outpatient MH Stop Codes of interest.
• ClinicSelection tab: If StopCode 179 is the only stop code used, we would miss those encounters.

Quant WG - Future State: Quarterly Code Review and Annotating Code

• Ideally: someone proactively on the Quant Workgroup would run these stop codes by Jodie every quarter and/or stops by BISL office hours to check them out

• What we would want: A Master Code Base on GitHub

• We could annotate any updates Track changes easily This is where the Technical Writer role could come in @mnallajerla in terms of tracking the documentation at least while we still do not have a Technical Lead

• Annotating Code: Use a # (R) or dash (SQL); Include initials, date, short description, and GH issue card

• GitHub Repos - Master Documentation

  • version control
  • code review
  • Cross-reference; dependency tracking
  • .e.g.,DatasetBuild_Viz.sql--AN: 11-17-2020 - Added the VVC and fiscalyear here GitHub Issue 1584

• Master Code Base

  • WHERE - GitHub
  • WHY: Version control, full circle - everything cross references relevant information and track dependencies
  • WHAT: We all have several places where we have Master Documentation; @dkngenda & @mnallajerla to huddle up to discuss that further to start setting this up
  • WHEN: For dec_epic