Current Release: SPARCRequest Version 3.12.0

MUSC Release Date: 12/14/2023 OS Release Date: TBD

RELEASED

Page Index:

SPARCRequest Version 3.12.0 New Features

(SPARCRequest) - Add Unsubmitted Notice for Draft Requests (LA CaTS Contribution)

A new feature is available to assist research teams in identifying their protocols with drafted service requests, and for resuming requests within those protocols.

A collapsible box will appear above the SPARCRequest steps arrows that lists these studies with hyperlinks to the study in SPARCDashbaord. From there, users should choose the green Add/Modify Requests button to return to the SPARCRequest shopping cart to complete requests for services.
A "Task" list with a checkmark symbol is also available in the upper navigation bar, and will include a red dot as notice if there are protocols with draft service requests. Selecting the task list will present a pop-up box, displaying the protocols with hyperlinks as described above.

(SPARCRequest Step 3) Edit Visit Bug Caused by Default Billing Function

Previously, there was a bug associated with using ‘Set Default Billing Designation' in the SPARCRequest Step 3 Quantity/Billings’ Tab where, subsequently the Edit Visit pop-up appeared in the top left corner, limiting the ability to edit. In this release, we have fixed this bug so that the Edit Visit pop-up appears next to the visit being edited.

Previous	Current

(SPARCRequest & SPARCDashboard) Add option to include additional funding sources

Teams now have the option to include additional funding sources on studies/projects within SPARCRequest Step 2 and SPARCDashboard ‘Financial Information’ section. These additional sources may represent secondary or previous funding sources. The (primary) Funding Source and Additional Funding source labels have updated help text to assist with this distinction.

(SPARCRequest & SPARCDashboard) Prices not consistently displaying

Due to accounting calculations at different time points, prices in Catalog Pricing Maps in SPARCCatalog were displaying differently from those in the frontend user interfaces (SPARCRequest Step 1, SPARCDashboard, Admin Edit). In this release, prices are consistently calculated and displayed in Catalog, Cart, Service Rate and Your Cost amounts across SPARC application. For accurate pricing, calendar calculations for ‘Total per Patient/Study’ amounts continue rounding based on original (full or discounted) cost.

(SPARCRequest & SPARCDashboard) Update Milestone 'Site Level' Field Names

To best reflect intended information, the Milestones field names in SPARCRequest Step 2 and SPARCDashboard have been changed from ‘Initial Site Level Amount Offered’ and ‘Negotiated Site Level Amount’ to ‘Initial Start-up Amount Offered’ and ‘Negotiated Start-up Amount’.

Previous	Current

(SPARCRequest & SPARCDashboard) EPIC notes and questions display

In this release, we have fixed the issues where EPIC study notes were displaying for non-Epic indicated studies and subsequent ‘Publish to Epic’ questions were not consistently displaying when editing the study.

Previous	Current

(SPARCRequest & SPARCDashboard) Performance Improvements

As part of a push to improve the functioning of the site, we have been performing various optimizations to increase load times. This release includes additional tasks towards this effort to improve loading and navigation times within the SPARCRequest & SPARCDashboard Service Details calendar and within service providers’ SPARCDashboard Admin Edit workspace.

(SPARCRequest, SPARCDashboard, SPARCForm) Form Data is not Rendering within Studies

Previously, SPARC Forms were requiring teams complete the latest form version whenever there was a new form version released. As a result, previously completed form data was not viewable on the study, appearing as though the form had not been completed and requiring a new form submission.

In this release, SPARC will now only require new form version completion when a previous version was not submitted. The currently completed version will correctly display on the study ‘Forms’ section in SPARCRequest Step 4 and ‘Form Submissions’ Dashboard section. All form versions remain available for service administrator’s view within SPARCForms.

(SPARCDashboard) - Add study Archive/Unarchive prompt

In this release, we have added a prompt that will describe what the Archive/Unarchive action does to confirm a desire to proceed.

(SPARCDashboard) Make Protocol Merge Fields Searchable

In this release, we have added a study search feature for Administrators performing protocol merges to assist with merging the intended studies. When entering the SPARC ID in the merge fields, information the SPARC ID, Study Title, Short Title, RMID and Primary PI Name will display.

(SPARCDashboard) Original Requester not being set for Related Services

Previously, when requesting services that have related services attached to them, the system was not recording the related service’s original requester. This has been fixed with this release so that the requester is displayed in the SPARCDashboard Correspondence button and applicable SPARCReports.

(SPARCDashboard and SPARCReport) Backend Merges not showing up in Merged Protocol Column and Protocol Merges Report

Protocol merges performed outside of the SPARC Protocol Merge feature available to Site Administrators will now be included in the SPARCReport Protocol Merges report and SPARCDashboard Merged Protocol ID(s) column.

(SPARCForm, SPARCCatalog, & SPARCDashboard) Add Ability to Send Surveys to Specific Recipients

In this release, we have enabled the new feature released in SPARC version 3.11.0 that added new functionality to surveys, allowing administrators to select specific recipient study roles to receive surveys and completion reminders. Within SPARCCatalog Forms, administrators are able to select the role(s) that will receive new surveys and completion notices for an active survey. Administrators retain the ability to resend survey completion reminders that will now be associated with the established recipient list. This feature will be enabled for forms in a future SPARC release.

(SPARCForms) SRID Column Sorting Bug

Previously, a bug was located in the Surveys Service Request ID (SRID) Column sort where instead of sorting in ascending and descending order by the SRID, it sorted based on the number of characters in the SRID. In this release, the SRID Column sort in SPARCForms will sort by protocol order, arranged by service requests.

(SPARCCatalog & SPARCRequest) Remove the email submission data when the split/notify is disabled.

This release fixes a bug that sent notices to team shared (submission) emails that were deleted from SPARCCatalog. Now when the split/notify is removed at an organizational level in SPARCCatalog, these submission emails will also be removed instead of requiring the user to delete the email before changing the split/notify.

(SPARC Admin) Add option to edit user SPARC Login ID

In this release, we have added the ability within SPARCAdmin for SPARC System Administrators to update a user’s SPARC Login ID.

(SPARC Database, SPARC Notifier) Add new 'Recent Submitter'

In order to accurately record a service request’s original submitter from someone who’s submitted an edited request, in this release recent submitter' information has been added. The requester displays on service request amendment notices and within SPARCReports Service Requests report ‘Submitted By’ column. To distinguish between these requesters, the report’s previous column titled ‘Requester’ has been updated to read ‘Original Requester’.

(SPARC-RMID API) eIRB data not saving and is editable in SPARC

A bug existed where IRB data for RMID validated eIRB studies was being imported into SPARC, but was no longer being recorded, and the imported data was editable on study applications. These bugs have been fixed with this release, and users should see validated IRB data on studies and in applicable SPARC Reports after the daily, overnight data refresh.

(SPARCRequest-RMID API) Add Server Down MSTeams Notification to the Status Check Method

When the SPARC-RMID API is down, a notice will be logged within the SPARC MSTeams channels.