20220817 - Technical Committee Meeting Minutes

Agenda:

Standup Round for institutional updates

Louisiana Clinical & Translational Science Center: 

08/03/22

• Ying unable to attend & provided this update: A PR for Add Demographics Attributes to Identities https://www.pivotaltracker.com/n/projects/1918597/stories/182491420 was submitted.

08/17/22

• Submitted PR for (SPARC Security) High Security Vulnerability in Active Record (https://www.pivotaltracker.com/story/show/182882509). Accepted Story.

• Updated PR for Add Demographics Attributes to Identities https://www.pivotaltracker.com/n/projects/1918597/stories/182491420 to add back unintentionally removed line.

• Asked if services can be copied & modified or if there are any scripts to import services. Andrew noted MUSC has used a script for hospital & patient billing services if Ying wanted to take a look at that in live task for comparison. There’s also an import service task she may want to check out, keeping in mind it may be outdated so make sure it has the fields needed.

MUSC:

08/17/22

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

• Need clarification on required design for SPARCRequest Step 2 and SPARCDashboard: Add Associated Organizations on Protocol Information Form. The story describes a feature Case has built that’s similar to this one, potentially to make Case’s Project/Study Scope field optional and contribute that to the main repository. The next steps for this design will be determined. This is important for OHSU, but not urgent so may be ok to fit within a SPARC release timeline without OHSU taking on the development.

Iowa

08/03/22

• Chris unable to attend

08/17/22

• not on this week

Case Western

08/03/22

• Jeremy unable to attend this week

08/17/22

• Jeremy unable to attend this week

Children’s National

08/03/22

• not on this week

08/17/22

• not on this week

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:

• Status of PT story SPARCRequest Step 2 and SPARCDashboard: Add Associated Organizations on Protocol Information Form - is OHSU interest in working on this one?

• MUSC SPARC team email sparcrequest@musc.edu. Also included on the OS Wiki page https://sparcrequest.atlassian.net/l/cp/WPoAaKP3.

• Began looking in using MSTeams for group communication

Discussion:

Action Items: