MUSC Release Date: TBD OS Release Date: TBD
IN PROCESS
Page Index:
SPARCRequest Version 3.12.0 New Features
(SPARCRequest & SPARCDashboard) Add optional fields to projects and studies to house additional funding information
Currently projects and studies only have the ability to associate information about one funding award (see below). For many studies there are multiple funding sources, either at one time or as the study continues and new funding is obtained. To facilitate tracking these funding developments/changes, we have added the ability to add additional funding sources to a protocol in the study information section on SPARCRequest Step 2 and on SPARCDashboard.
 |
(SPARCRequest) Remove the email submission data when the split/notify is disabled.
Validation needed that all submission emails have been disabled if the Split notify is disabled. This was related to a bug that left emails duplicating or going out when email was removed.
Testing showed the email is remaining from when first put in there when there was a split/notify established at the (program) level. Whereas, the current split/notify is at the core level.
SPARC is requiring a certain sequence of events to remove the emails so it disassociates from the split/notify. Current story will add the feature for submission emails to follow the same action that removes the split/notify.
Previous | Current |
|---|---|
 | |
(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 2 & SPARCDashboard) EPIC Study Type Questions not Consistently Displaying
When testing, it was observed that the Confidentiality and Epic Questions section question 'Do you want to have your Study Published in Epic?' is not showing subsequent Study Type questions & its responses when returning to page for edits.
When the section is completed at one time for first entry, it provides all the response options and saves the content. However, when returning back to the page, the screen load does not display those answered questions unless you toggle between the Yes/No 'Epic Publish' question.
In this release, we corrected this bug and now the questions appear correctly in both the Study Information section and Study Details section in SPARCDashboard.
Previous | Current |
|---|---|
 | |
(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 display
In this release, we have fixed the issue where EPIC study notes were displaying for non-Epic indicated studies.
Previous | Current |
|---|---|
 |  |
(SPARCRequest Step 3) Edit Visit Bug Caused by Default Billing Function
Previously, there was a bug that occurred after using the Default Billing Function in the Quantity/Billings Tab on SPARCRequest Step 3. After using the Default Billing Function in the Quantity/Billings Tab, when the user goes back to the Template Tab and clicks on a Visit, the Edit Visit pop-up appears in the top left corner while the title of the pop-up appears next to the visit select. In this release, we have fixed this bug so that the Edit Visit pop-up appears next to the visit that was clicked on.
Previous | Current |
|---|---|
 |  |
(SPARCRequest and SPARCCatalog) Submission Email Bug
Previously, service providers were reporting that they were continuing to receive submission requests to emails that had been removed from their services in SPARCCatalog. In this release, we have fixed this bug.
Previous | Current |
|---|---|
(SPARCRequest & SPARCDashboard) Site Optimization
As part of a push to improve the functioning of the site, we have been performing various optimizations to increase load times. Here are the three stories addressing the load times
(SPARCRequest & SPARCDashboard) Service Calendar Performance Improvement
Current work is being done remove extra eager loading that was causing slowdowns. Initial dev testing showed improvement in load time for template tab on large studies.
(SPARCRequest & Dashboard) Calendar Visit Quantity Performance Refactor
Ongoing effort to optimize calendar load times.
(SPARCDashboard) Improve Admin Edit Loading
Efforts continue to increase the load time for navigating SPARCDashboard Admin edits.
Investigative work of slowdowns includes "push to fulfillment" and "push to epic" buttons. Protocols/requests are checked to see if they are "valid" before rendering the buttons, so that if it isn't, the buttons can be disabled with a user message.
This causes slow down and its worth considering only checking when someone pushes either button. The study validation here seems to only be used for these buttons, and it's a huge performance hit.
(SPARCRequest, SPARCDashboard, SPARCForm) Form Data is not Rendering within Studies
Previously, service providers reported that completed form data was not rendering within their studies. In this release, we fixed this bug to allow form data to render within studies.
Previous | Current |
|---|---|
 |    |
(SPARCDashboard) Make Protocol Merge Modal Fields Searchable
In this release, we have added the new Modal field pop up when Administrators enter a protocol in the merge fields when protocol merging to assist with merging the intended studies. The search identifies information about a protocol, including Protocol ID, RMID, Short Title, and PI Name.
(SPARCDashboard) Performance Enhancement When Accessing Admin Edit
SPARC administrators and service providers should experience a quicker load time when accessing Admin Edit to track work on their service requests. This update is a part of ongoing efforts to improve load times within the SPARC Application.
(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) 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 original requester in the database. Additionally, the system was not recording the original requester in the Correspondance button, in the Action column on Dashboard.
Previous | Current |
|---|---|
 |
(SPARCDashboard and SPARCReport) Backend Merges not showing up in Merged Protocol Column and Protocol Merges Report
When we initially added the Protocol Merges Column in SPARCDashboard and the Protocol Merges Report in SPARCReport, we didn't consider backend merges and focused on the frontend overlord "Merge Protocol" functionality. Because of that, when a developer would perform a protocol merge on the backend, the newly merged protocol would not show up in the Merged Protocol column in SPARCDashboard. Subsequently, the merge would not appear in the Protocol Merges Report in SPARCReport. In this release, we have fixed this issue and now backend protocol merges appear in both the Protocol Merges Report in SPARCReport and the Protocol Merges Column in SPARCDashboard.
Previous | Current |
|---|---|
(SPARCForm, SPARCCatalog, & SPARCDashboard) Add Ability to Send Surveys to Specific Recipients
In this release, we have added new functionality to surveys allowing administrators to select specific recipients to receive surveys. A user will be able to decide the recipients who will receive the form in SPARCCatalog.
     |
(SPARCForms) SRID Column Sorting Bug
Previously, a bug was located in the 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, and arrange by service requests.
Previous | Current |
|---|---|
 |  |
(SPARC Admin) Add option to edit user SPARC Login ID
In this release, we have added the ability to updated the SPARC Login ID for users from the SPARCAdmin module.
  |
(SPARC Database, SPARC Notifier) Add new 'Recent Submitter' field
In this release we are adding a ‘Submitted By’ column and updating the ‘Requester’ column to ‘Original Requester’. The rationale for this was to maintain current information on study protocols and help track services that have been submitted or resubmitted by different requesters from the original requester
  |
|---|
(SPARC-RMID API) Issues with RMID API eIRB data saving into SPARC
Previously, service providers were reporting that IRB information missing on the Service Requests report for a large # of studies. After reviewing SPARC, the eIRB verified study data (Pro#, initial approval date, current approval date, expiration date) are on these studies, but the content is not appearing in reports, is not stored in the database irb_records table, is not displaying in Study Details read-only view, and content edits are not being saved.
Previous | Current |
|---|---|
 | |
 |