search

lzim / teampsd

Team PSD is using GitHub, R and RMarkdown as part of our free and open science workflow.
GNU General Public License v3.0
9 stars 23 forks source link

1.7.9 Team PSD Web Page #324

Closed jamesmrollins closed 5 years ago

jamesmrollins commented 5 years ago

Here are some ideas regarding the team web page. Thank you @dlkibbe for the paragraph describing Team PSD. All other words are just placeholders. Same with pictures. Like MTL, the idea is to make it easy to update for the webmaster using an admin page. So it is a relatively uncomplicated layout consistent style-wise with MTL. The map is problematic with respect to future edits, but perhaps a google maps solution might work. Certainly, I will need a listing of everyone who is going to have a bio, the bio, and portraits other than the ones you see on the page.

image image image image

lzim commented 5 years ago

@staceypark will you work with me to:

  1. Complete the photo edits from the list above (posted by me 12 days ago).
  2. Coordinate with either me or the workgroup leads to draft What we Do text for the following workgroups and key partners?
branscombj commented 5 years ago
  1. Coordinate with either me or the workgroup leads to draft What we Do text for the following workgroups and key partners?
    • [ ] ees

Coordinates with VA’s Employee Education System (EES) to secure accreditation for continuing education units for staff members who complete MTL Live, MTL Video, or MTL Facilitate.

staceypark commented 5 years ago

@lzim @jamesmrollins and I are working on updating the photos. Looks like I'll probably need to grab some folks in person and snap pictures for better headshots.

Also the bios needed to be edited to >150 words - James showed me how to do this and I'll take a stab at this on the facilitator dashboard for the website.

@staceypark will you work with me to:

  1. Complete the photo edits from the list above (posted by me 12 days ago).
  2. Coordinate with either me or the workgroup leads to draft What we Do text for the following workgroups and key partners?
  • [ ] hq
  • [ ] facilitate @branscombj thanks for taking a stab at the ees one! can you draft one for this as well?
  • [ ] model @TomRust can you draft one before the launch meeting tomorrow?
  • [ ] sim_ui @jamesmrollins can you draft one before the launch meeting tomorrow?
  • [ ] qual @teampsdkathryn can you draft one to review at the qual meeting next Tues?
  • [ ] quant @saveth @holbrooa let's spend 5min on this at the quant meeting tomorrow
  • [ ] cois
  • [ ] vapor
  • [ ] ees
jamesmrollins commented 5 years ago

@lzim I will do my best.

branscombj commented 5 years ago

facilitate workgroup develops, tests and refines the approach, scripts and supporting materials for conducting MTL with learners; also develops, tests and refines the approach, scripts and supporting materials for conducting MTL Facilitate training for new co-facilitators

Is it others' understanding that this workgroup does both? I wasn't sure.

TomRust commented 5 years ago

@jamesmrollins The modeling work group logo: Modelng Worgroup Logo

branscombj commented 5 years ago

facilitate workgroup logo: image

teampsdkathryn commented 5 years ago

Draft Qualitative Workgroup What We Do Text: Kathryn Version 1

The qualitative workgroup strives to understand what clinical providers are experiencing in the clinic and how Modeling to Learn (MTL) can create transformative change. We use a participatory epistemology by engaging with partners and stakeholders to gain a new awareness of the dynamics related to the delivery of evidence-based practices (EBP). We have a theory of change and well as a model to explain the mechanism of change. These models offer unique qualitative categories and verbal construct mapping. Our team analyzes narrative text to grasp how MTL might work to create change. We analyze causal feedbacks, time, rates, and states of accumulation using RQDA, an R package for computer assisted qualitative data analysis. We strive to develop seminal practices from group modeling to understand determinants (facilitators, barriers) for improved EBP reach. Should I embed this in the Lucid agenda as well for further discussion at the next qual workgroup meeting? Best Regards, Kathryn

From: Stacey Park notifications@github.com Sent: Wednesday, May 15, 2019 4:25 PM To: lzim/teampsd teampsd@noreply.github.com Cc: Azevedo, Kathryn J. Kathryn.Azevedo@va.gov; Mention mention@noreply.github.com Subject: [EXTERNAL] Re: [lzim/teampsd] 1.7.9 Team PSD Web Page (#324)

@lzimhttps://github.com/lzim @jamesmrollinshttps://github.com/jamesmrollins and I are working on updating the photos. Looks like I'll probably need to grab some folks in person and snap pictures for better headshots.

@staceyparkhttps://github.com/staceypark will you work with me to:

  1. Complete the photo edits from the list above (posted by me 12 days ago).

  2. Coordinate with either me or the workgroup leads to draft What we Do text for the following workgroups and key partners?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/lzim/teampsd/issues/324?email_source=notifications&email_token=AG5Y22LEHVPADIK64VC5BNLPVSLWHA5CNFSM4HCMTOE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQHFUI#issuecomment-492860113, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG5Y22KIAVIBMOHTHN2FXR3PVSLWHANCNFSM4HCMTOEQ.

branscombj commented 5 years ago

@staceypark Some guidance on level of detail and tone/audience for the workgroup descriptions? I see that my approach and Kathryn's are very different. Let me know if you want me to write more. Thanks!

lzim commented 5 years ago

@branscombj

I think we are going for it being okay to have diversity right now, and are open to not being overly directive about tone/detail. But, I do think the participatory principles should be emphasized more in our facilitate workgroup, as that is key! Do you want to take a crack at it?

lzim commented 5 years ago

@jamesmrollins @TomRust @staceypark

I didn't have time to say this yesterday, but I don't think we will have logos for each Team PSD workgroup and it would be weird if we did...case in point @TomRust 😆

But, our key partners do have logos.

RECOMMEND:

  1. Separate Workgroups from Key Partners.

WORKGROUPS

KEY PARTNERS

  1. Omit an image on the left for Workgroups, but retain it for Key Partners.

Thanks!

TomRust commented 5 years ago

@jamesmrollins -- Here is the Modeling Workgroup blurb:

The Modeling Workgroup builds virtual worlds. These worlds allow provider teams to quickly, easily, and safely experiment with their wildest improvement ideas. In seconds, they can see outcomes and unintended consequences that would otherwise remain hidden for months or years. Unlike in their actual clinics, they have complete freedom to make as many mistakes as they need to learn, allowing them to develop intuition about how to optimize trade-offs specific to their own combination of patients, partners, and resources. We are perpetually learning from teams to improve these virtual worlds, to find the right balance between realism and usefulness.

lzim commented 5 years ago

Thanks @TomRust!

branscombj commented 5 years ago

@lzim

KEY PARTNERS

  • [ ] vapor
  • [ ] ees

Just wondering if TAS = key partner

lzim commented 5 years ago

@branscombj

I think the TAS see themselves as Facilitators and members of Team PSD. They do not have their own logo and we (myself and the TAS) are all part of Office of Mental Health and Suicide Prevention (OMHSP)

However, we do list Drs. Wiechers and Trafton as key partners on the maps above, and they are also OMHSP.

For these resasons, we could list OMHSP as a key partner, if we did that we would also want to list @TomRust's office: Office of Healthcare Transformation (OHT).

WORKGROUPS

KEY PARTNERS

FYI: @jamesmrollins and @staceypark

TomRust commented 5 years ago

Hey @staceypark and @jamesmrollins -- The links to the SEE files from the demo site (https://github.com/lzim/teampsd/tree/master/mtl_facilitate_workgroup/mtl_live_guide) don't work.

It looks like we lost the "mtl_live_guide" folder, which is part of the old link, and now have all the SEE files in the "learner_see" folder. I can re-do the links to point at the "learner_see" folder, if that's right. Just let me know.

lzim commented 5 years ago

Great catch 🎣 @TomRust

But I didn't notice this before: It should NOT go to the Team PSD repo. It should definitely to to https://mtl.how where the "BEST" "CURRENT" SEE guides (and soon SAY guides) live.

FYI: @jamesmrollins and @staceypark

saveth commented 5 years ago

@jamesmrollins says this is done and needs to be close. Any new issues or request requires a new ticket.