2023_jun_epic #story_b: Backend: GitHub/ZenHub API integration; Frontend: LEAF frontend (a new 'consult' LEAF; 6 Issue Template that could be LEAF Forms)

[ghost]

• [x] @jamesmrollins and @emilypearman to investigate if LEAF integration with GitHub is possible via API

__-

DECISION who: @lzim @hthrmarsh @emilymetcalf114 When: wk4 april_epic System_sme_support_workflow scribbed: Support_workflow

100% sure we need to be in LEAF ASAP for _Modeling to Learn_

Top priority to capture the volume of the end of trials to justify our future budget. Prioritize in next 2023_roadmap_q2 -Propose in the #health_equity_grant if we can get the partnerships and clarity in time -Set up in next quarterly roadmap Jul-Sept (q4 of FY23)

NOW if can - reported that in FY22 Team PSD squashed 200+ bugs developed 200+ features

Budget Request for FY23 & FY24 Costing Aim with HERC for HSRD grant. Planned to describe our value streams.

We should retain the GitHub/ZenHub functionality, but identify API integrations

story_j

GitHub Actions

[ghost]

@jamesmrollins, thank you for looking into this so quickly, can you add your preliminary findings on this issue to this card as well?

[jamesmrollins]

FYI: @epearman @emilymetcalf114 @hthrmarsh

• [x] LEAF Preliminary Information Regarding LEAF #LEAF_support_services contains portal entry for general and national project consultations, tech support, CoP and others.
• [x] #LEAF_community_of_practice contains the Team and channels that support the LEAF CoP.
• [x] #LEAF_GitHub contains the public LEAF repo.
• [x] No evidence of API in the support channels, nor any hits on general searches in the Team channel or their Tech Support Portal. Did put in a query on the CoP channel to see if anyone knows anything about an API.

[jamesmrollins]

FYI: @epearman @emilymetcalf114 @hthrmarsh

Results of CoP question - BOOM!!

LEAF_Using_JSON_with_Excel_Power_BI.pptx

[ghost]

EDIT: @jamesmrollins & @lzim discussed wk2 2023_may_epic support_workflow

Exports from LEAF to Power BI are not the focus and are opposite direction of the functionality needed.

Overview of LEAF_Using_JSON_with_Excel_Power_BI.pptx

• Exports LEAF reports to an excel file
• Excel file is set up based on users credentials
• Excel file can be set up to refresh LEAF report data upon opening

Next Steps:

• [x] @jamesmrollins - attending training session wk2 2023_may_epic
• [x] @jamesmrollins - Review the functional requirements for our LEAF site for MTL down below.
• [x] wk1 2023_may_epic Participated in the demo @epearman @hthrmarsh @lzim @emilymetcalf114

Resources

1. Build a new leaf site
2. Video instructions for how to create a new leaf portal
3. Sign up for a training session?

[ghost]

When setting up a site they will ask optionally for an executive sponsor.

If storing PII or PHI you will need to ensure you follow these secure steps

[ghost]

Directions to Enroll in Training: Training Dates and Times: Tuesday, May 9, 2023, 1:00 PM – Thursday, May 11, 2023, 2:30 PM

1. Go to the Leaf Launchpad
2. Select "Register for Training"

Our LEAF Test site for learning

[hthrmarsh]

@pearman - I've registered for the training.

For everyone else - if you're registering, use the test site already created by Emily P: https://leaf.va.gov/VISN21/640/teampsd_test/

[ghost]

DECISION Scribed in: system_sme_workflow during wk1 2023_may_epic LEAF demo attended by: @lzim @hthrmarsh @epearman Lindsey Notes Emily P notes

• [ ] LEAF focuses on two primary functional requirments
  • [ ] consult_workflow to kick of MTL
  • [ ] Frontend LEAF form for users; GitHub API integration on the backend

Next Steps:

• [ ] @jamesmrollins is working on scoping out user_story_maps for 2023_jun_roadmap

---

Aim 3 Implications Aim 3 is about tracking activity costs, which we've done in GitHub to date.

Next Steps: To avoid data loss and continuity. Scope API based alignment first.

---

FYI: @jamesmrollins

[lzim]

wk1 2023_may_epic @jamesmrollins

UPDATED #2972 Story Board based on wk2 2023_may_epic support_workflow @lzim @jamesmrolins

1. We will ultimately pursue LEAF.
2. Top priority for 2023_may_epic we need @emilymetcalf114 & @epearman to ensure no data loss with site set up across Teams/Sharepoint/Dynamics/Sim UI for trial sites.
3. But, because we are going to begin narrower LEAF/GitHub API integration

These are our two primary functional requirements:

• [ ] One consult (LEAF consult that kicks of the MTL consult_workflow process),
• [ ] Six GitHub Issue Templates that can be a form.

wk3 2023_may_epic

• [ ] #2973 @jamesmrollins to create two user story maps for these two functional requirements above.

4. [x] @jamesmrollins is completed the trainings this week.

LMK if you have questions. Thx!

[jamesmrollins]

Consult workflow skeleton as per wk2_may_epic support_workflow mtg.

1. Site has been identified usually a STA3N. They either self-identify or they are on the MTL site list.
2. If self-referred, review the trial list for MTL for where the site is in the study.
3. Assumption:  We will be given a fundamental entity (site=STA3N) to start the intervention.
4. Part one will start with same Data UI Review for both Red and Blue.
5. Part two starts with asking for area of focusing the Sim_UI and which clinic would be in scope.

[jamesmrollins]

FYI @epearman @hthrmarsh @lzim

Met with a collaborator from the LEAF CoP meeting today. The recording is in the Sim UI Workflow. He discussed how access JavaScript and the general structure of LEAF from a coder's perspective. So it is technically possible to use the GitHub API to move information from LEAF to GitHub. Furthermore, Michael Gao, LEAF's creator confirmed that it is possible to use the API. So good news, in terms of using LEAF as a user interface. I also received information about how to get LEAF to post to an Outlook calendar. So, we may find it is fully capable of helping us manage our consults.

Recommendations

1. Close this card - cross ref with this card with #2973 .
2. Story map the Consult workflow in Lucid.
3. Bounce it off the Consultant/System SMEs. (Probably need to schedule this)
4. Program the LEAF development, testing and implementation during the next PI.

• [ ] Sounds great - let's do it!
• [ ] Sounds great - but see my comments below
• [ ] fageddaboudit

[lzim]

@jamesmrollins to update Title of card & Data based on #sim_ui_workflow F2F wk5 2023_may_epic

Top priority to initiate a Team PSD MTL consult in LEAF. Secondary priority the API integration