220916 SPARC OS Ops Agenda

Date

Sep 16, 2022

Participants

Institution Updates

• Stony Brook - consulting with Leila for Go Live question; finishing up resources

• OHSU - question on whether this is a bug or system function: a service moved from a Core Program to a service level is still showing up at the Core level. Advised to enter in a story so we can take a look to fully understand the issue and advise.

• Iowa - meeting with Leila to demo Oncore

• LACaTS - no major updates

• MUSC

  • Research Master ID release 8/25/2022.

  • Working on SPARCRequest Release, tentatively planned for end of October.

Discussion Topics

• (SPARCRequest) Change New Request Question

  • Introduced at 8/19/22 meeting. Current meeting’s discussion of below proposed update included:

    • Primary purpose of guiding new users to the correct response

    • Continued consideration of system design of ‘Yes’ and ‘No’ buttons and existing user actions

    • Preserving workflow of adding a service to the cart and then asking this question, as well as the public service browsing experience

    • Potentially removing the question and adding instruction within the buttons (e.g., ‘Add to new study’ and ‘Add to existing study’)

• (SPARCRequest Step 2 and SPARCDashboard) Add Associated Organizations on Protocol Information Form - Originally discussed at the 2/18/2022 meeting. Current meeting discussed below details and requirements updates, in light of similar functions at Case & LACaTS and key goal of data capture best aligned with CTSA metrics reporting.

  • Original nomenclature and options - new External Orgs option in Other Details Study/Project section with Collab Org Name and Collab Org Type - not required to use, customizable

  • Design similar to current IRB Records question’s function (see video below)

  • Standardization in considering important metrics for CTSA reporting

    • Previous metrics & evaluation committees attempt to define & standardize collaborations terms, with little resolution. MUSC evaluation offered to keep us informed of any relevant developments.

    • Research Performance Progress Report (RPPR) fields include: "Relationship" (Subaward, MOU, Reliance etc); "Type" (University, VA, Other, etc.); "Funding Category" (State, Non Profit, Private etc)

    • What information may already be in other systems and any current or future plans to integrate the data

Open

New Design Features

Design Image	Description

Design Image	Description
Open Originally Proposed Design	To identify institutions/organizations involved with a project/study, add section to SPARCRequest Step 2 and SPARCDashboard Protocol Information form, "Other Details”. Collaborating Organization Name = multiple-choice dropdown list that allows institution organization name entries Collaborating Organization Type = checkbox selection using standard options (Academic collaborator, CTSA collaborator, Community collaborator, Hub partner, Healthcare enterprise partner, Other, None) that allows institution configuration
	Included for ‘Project’ vs Study (only Project is used). In Project Scope, with different options for single or multiple collaborators Required entry
	Included for Study vs. Project  “Type of Collaboration" = Case’s "Project Scope”  Required entry