Meeting: | SPARC OS Technical Committee |
|---|---|
Date: | 08/17/22 |
Time: | 3:00 pm |
MUSC | |
Iowa | |
LA CaTS | |
Children’s National | |
Case Western | |
OHSU | |
Stony Brook Medicine |
Agenda:
Standup Round for institutional updates
Louisiana Clinical & Translational Science Center:
08/03/22
Ying unable to attend & provided this update: A PR for https://www.pivotaltracker.com/n/projects/1918597/stories/182491420 was submitted.
08/17/22
(SPARC Security) High Security Vulnerability in Active Record (https://www.pivotaltracker.com/story/show/182882509) status
MUSC:
08/17/22
Team | |
|---|---|
Sherly | |
Ito | |
Matthew | |
Greg | |
James | |
Andrew | |
Jason |
Oregon Health & Science University:
08/03/22
Continued report refinements/clean up, data migration and confusion with user new account setups.
RMID issue resolved where configuration done to not force some of the required data fields
Inquired about the status of PT story SPARCRequest Step 2 and SPARCDashboard: Add Associated Organizations on Protocol Information Form. It is scheduled for the next SPARC release 3.10.0, however hasn’t been picked up yet for development work. MUSC is in the process of reviewing and prioritizing SPARC stories in planning its next release and will be sure to include this one in a status update.
08/17/22
Iowa
08/03/22
Chris unable to attend
08/17/22
Case Western
08/03/22
Jeremy unable to attend this week
08/17/22
Children’s National
08/03/22
not on this week
08/17/22
Stony Brook:
08/03/22
Implemented the delayed email fix discussed with MUSC and jobs have been running successfully so far.
Working to have clean data in dev site with goal to copy database over and use in production to avoid rebuilds. Discussed it may be best to export tables you want vs the whole database. It will be a manual process but may get the best dataset and be an easier clean up. Can reach out to MUSC to take a look when they are at this clean-up point.
Asked how to contribute Stonybrook’s feedback into PT stories. Andrew described the process of adding their name to the task (with priority ranking in parentheses) and then checking the box after saving. Can also include comments within the story. Send new story ideas to MUSC, where it can be reviewed, discussed in Operations governance and story entered for prioritization. Brigette also shared there are SOPs being drafted describing some of these processes that will be shared when finalized.
08/17/22
Update:
MUSC - status of PT story SPARCRequest Step 2 and SPARCDashboard: Add Associated Organizations on Protocol Information Form
MUSC SPARC team email sparcrequest@musc.edu. Also included on the OS Wiki page https://sparcrequest.atlassian.net/l/cp/WPoAaKP3.