221021 SPARC OS Ops Agenda

Date

Oct 21, 2022

Participants

Discussion Topics

• SPARCRequest version 3.10.0 Production Release planned for 10/27/2022. Will update group if date changes. Reviewed draft of release notes.

• (SPARCDashboard) Send Correspondence to Service Provider Function UX Improvement - Confirm requirements

  • Everyone should review this story to confirm the requirements before development work can begin.

• (SPARCDashboard) Include Notes for Non-Clinical Services in Fee Agreement - OHSU Contribution

  • OHSU will work on the development for this story, planning to go in the 3.10.0 production release

  • This story will be sent out for everyone today for priority review to include in this release.

• SPARC Catalog And SPARC Admin - service appears in program in UI after being moved to Core in Catalog

  • Setup a meeting with Andrew, OHSU Developer, Imogen, and Ops Team to address the issue occurring with when a service is moved from a Program is moved to a Core

• (SPARCDashboard) Add New 'Submitted On' Column to Request Table LA CaTS Contribution

  • Determining if column name in this story should change to reflect the data presented, such as Most Recent Submission or Initial Submission. MUSC will review the story and current content displaying when a service is resubmitted.

• (SPARCRequest Step 4 and SPARCDashboard) Able to multi-select documents and download into Zip

  • Currently working on an error with the column selections

  • Brian reported they didn’t include batch downloading in the Funding Module. He will check with Ying on this exclusion rationale.

• (SPARCDashboard) Protocol Merge Should keep the Non-Master Protocol Pro# when there is no eIRB record on the Master Protocol

  • Along with describing this story, Brian reported they are experiencing errors when merging protocols for when there is a same service in different statuses (beyond submission) on both studies. They have to administratively delete one of the services in order to merge the studies. This is a function of SPARC that doesn’t allow two active services for the same provider. However, discussion included possibly allowing an override or ‘select which service to keep’ with merges as a 2nd step if there are duplicate services for the same providers that would otherwise produce this error.

• Story entry and development work processes:

  • Confirmed process for institutions to enter in stories for work requests - enter Brigette as owner so we are aware of the story, enter in details, including whether they will do the development, and tag ‘for review’. It will be looked at to see if committee meeting agenda discussion or committee review is the next step and then follow resulting process.

  • SOPs describing this full process are being drafted.

  • Traditionally, labels for ‘contribution’ were included to give credit for which institution identified the story. This can be revisited if the label should instead be used to indicate when an institution will do the development work on the story.

Action Items

• (MUSC) Keep group informed of SPARC release status

• (All) Document review of stories referenced above

• (MUSC) Confirm data populating in Dashboard Requests ‘Submitted On’ column

• (OHSU + MUSC) Schedule meeting to discuss Core/Program service displays

• (OHSU) Development work on Fee Agreement story for potential inclusion in upcoming release