20251008-Technical Committee Meeting Minutes

SPARCRequest Wiki

20251008-Technical Committee Meeting Minutes

Meeting:

SPARC OS Technical Committee

Meeting:

SPARC OS Technical Committee

Date:

Oct 8, 2025

Time:

11:00 am - 11:28 am

MUSC

Brigette, Greg

Iowa

 

LaCATS

Ying

Children’s National

 

Case Western

 

OHSU

Imogen

Stony Brook Medicine

 

Morehouse

Ruvina, Helen

Agenda

Last Meeting’s Minutes

Institutional Updates:

 

Louisiana Clinical & Translational Science Center: 

9/10/2025

  • Working on Ruby on Rails upgrade to v7.2.

  • Encountering “mime negotiation invalid type” exceptions post Ruby 7.0 upgrade with SPARC v3.13.0.

    • Suspected misconfiguration; MUSC has also received - Greg suggested it may be due to security scanners, suggested handling via configuration or middleware. Ying noted frequent batch errors and traced IPs to Amazon/Microsoft.

10/8/2025

  • Upgraded rails to 7.1.5.2

    • exceptions from capistrano version requiring upgrades

    • deprecation warnings

      7.0 > 7.1.5.2 getting warnings - had to fix - will send PR for the changes she made

    • Next working on upgrading to 7.2

  • SPARCRequest reporting date filter bug - if you only select start or end, it auto runs all dates

  • deprecation warnings - they don’t receive these warmings from production log. Does MUSC have system that sends notifications for deprecation warnings? Greg will check.


MUSC:

Links are accessible by Open-Source Members

10/8/2025


Oregon Health & Science University:

9/10/2025

  • Not in attendance

10/8/2025

  • Have not determined a SPARC upgrade timeline due to other development priorities. No major issues reported by users.


Iowa

9/10/2025

  • Not in attendance

10/8/2025

  • Not in attendance


Case Western

9/10/2025

  • The topic ‘adding admin services to the cart’ was discussed at their August 21 meeting, but there are not detailed notes. Jeremy will revisit it in the next team meeting.

  • Upgrading to SPARC v3.12.1 is underwayWorking on Ruby on Rails upgrade to v3.13.

  • Encountering “mime negotiation invalid type” exceptions post-upgrade.

  • Suspected misconfiguration; Greg suggested it may be due to security scanners and offered potential solutions.

    • Customizations merged; minor fixes ongoing.

    • Target production deployment by end of September.

    • Upgrade will support updated training materials and videos.

10/8/2025

  • Not in attendance


Children’s National

9/10/2025

  • Not in attendance

10/8/2025

  • Not in attendance


Stony Brook:

9/10/2025

  • Not in attendance

10/8/2025

  • Not in attendance


Morehouse:

9/10/2025

  • Ruvina reported continued issues with delayed job scripts not populating the data table. Brigette advised checking the previous emails from Andrew and replying for further guidance.

10/8/2025

  • Getting close to going live.  Have a few questions from group testing.

    • Can “Funding Source Status” and “Funding Source” be non-required fields? They have instances where “No Funding” status and “N/A” source apply.

      • Ying noted that another “Funding Source” option can be added via permissible values, but “Funding Status” requires custom code changes to avoid breaking the application.

      • Imogen shared that their system has “Unfunded” status option that hides the funding source dropdown when “Unfunded” is selected, using a default value of unfunded in the database. Believes may have been implemented a while ago, so the change effort is not presently known.

    • Can bulk patient lists can be uploaded into Fulfillment?

      • Brigette noted there’s no built-in functionality, but you may be able to do a script import. She will check with Andrew if there’s an existing script.

    • Is there a script to delete test data from production, while retaining metadata?

      • Brigette is not aware of one but will also check with Andrew on this.

    • PI names not found during study creation due to lack of SPARC account.

      • Brigette explained MUSC’s system pulls from LDAP and auto-creates SPARC accounts. If they don’t have something similar, then it would only pull from SPARC created accounts.

      • They will discuss whether to engage their IT dept to set up their system similarly.

 

Copyright © 2011-2026 MUSC Foundation for Research Development