New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Team PSD Travel - June to December 2019 #354
Comments
Team PSD Presenters, has everyone registered for SDS? |
Is the intention to pay the registration fee ourselves and then get repaid in concur when we actually travel? Or is there some mechanism for the office to pay the registration fee up front? |
We pay and then we remit to PAVIR to get reimbursed for both SDS and the AI conference, which is also due today. I am paying for these off of my NIH grants, VA is not paying for them. |
Ah okay. I'll complete both registrations now. |
|
@lzim I registered for SDS two weeks ago. I got VA to pay for my SDS registration as an education expense. good old form 182. |
@TomRust Nice! 🤓
@staceypark can still register before the early SDS deadline as a non-presenter. BTW: Congratulations to @jamesmrollins @dlkibbe and @dlounsbu as we just learned that our panel presentation was accepted to the Society for Implementation Research Collaboration in Seattle in September. I updated it above. 🥂 |
My travel plans to India from Aug 16-30 have been cancelled. |
I filled out the travel reimbursement form and created a holbrook_stanfordAI folder in pavir_expenses. The only question mark for me is the check request for the reg fee. I believe we submitted that form already (early last month), but I dithered around and delayed getting the form in, so there's a chance it didn't get submitted to PAVIR. If that's the case, it can just be added to the overall travel form. @staceypark I sent an email asking about it - can you check and make sure that Stanford AI reg fee check request got submitted? Obviously I haven't received it, but we know they're slow so it might just be stuck in their queue. |
Thanks! I will send in the AI conference today! We'll get to the bottom of this ASAP! FYI: @staceypark |
I think this issue can be closed?? |
Well, Tom and I still have ISTSS in 3 weeks, but we can check this issue as needed to get the GSA and per diem. |
June
1. Team PSD F2F 6/13-6/18 - We need final travel projects to finalize this plan. We are looking to travel on 6/12 and 6/18, ideally with full work days Th, Fri and Mon, Tues.
Team members traveling
NOTES
2. SCRA 6/25-29 – David and Lindsey Workshop in Chicago, IL – Accepted
Web: https://www.scra27.org/event/biennial-conference/2019-biennial/
OSF Travel Wiki: https://osf.io/dxsvt/wiki/travel/
Team members traveling
NOTES
July
1. SDS 7/22-7/26 – Team PSD sessions in Albuquerque, NM – 5 of 5 Acceptances received
Web: https://www.systemdynamics.org/conference
OSF Travel Wiki: https://osf.io/rt9qz/wiki/travel/
Team members traveling
NOTES
September
1. SIRC 9/11-9/13 – Team PSD Panel in Seattle, WA – accepted!
Web: https://societyforimplementationresearchcollaboration.org/5th-biennial-society-for-implementation-research-conference-september-12-14-2019/
OSF Travel Wiki: https://osf.io/mdzxt/wiki/travel/
Team PSD members traveling
NOTES
2. Frontier AI-Assisted Care – 9/18-9/19 – Team PSD Quant Workgroup attends this Scientific Symposium at Stanford.
Web: https://med.stanford.edu/frontierofaicare.html
Team PSD members traveling
Notes
October
1. AHSR 10/15-18 – Team PSD Med Management Model Workshop in UTAH – Invited Pre-Conference Workshop
Web: https://medicine.utah.edu/internalmedicine/epidemiology/parcka/ahsr-conference/
OSF Travel Wiki: https://osf.io/rmqb8/wiki/travel/
Team PSD members traveling
NOTES
November
OMHSP 11/4-11/8 - MH Continuum of Care Meeting focused on Measurement Based Care and Stepped Care - Location and details TBD.*
Team PSD members traveling (TBD)
ISTSS 11/13-11/16 – Team PSD PSY Model Workshop in Boston – accepted!
Web: http://www.istss.org/am19/home.aspx
OSF Travel Wiki: https://osf.io/5tw29/wiki/travel/
Team PSD members traveling
NOTES
The text was updated successfully, but these errors were encountered: