20230412-Technical Committee Meeting Minutes

Agenda:

Standup Round for institutional updates

Louisiana Clinical & Translational Science Center: 

3/29/2023

• SPARC v3.10.1 is live now.

4/12/2023

• Follow up from last meeting- Q: When will MUSC update to rails 6? A:No timeline yet

• No update

MUSC:

3/29/23

• 3.4.0 SPARC Fulfillment - release pushed out, tentatively another 2 weeks

• SPARCRelease 3.11.0 - Summer 2023

Oregon Health & Science University:

3/29/23

• Has SPARC v3.10.1 to dev environment to begin testing its application.

• Still interested in Your Cost reporting, which will be considered.

• (SPARCDashboard) Ability to Restore Modified Rates Back to Price on Pricing Map

  • Follow up from OS Ops call 3/17/23 is for Tech group to discuss dev approaches to accomplish this. Will be an ongoing discussion.

  • During Tech call Erik emailed Brigette their current script for routinely removing modified rates (admin_rates)

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

  • Instead of submitting a PR, will add coding info to story for consideration of its applicability within SPARC.

  • Looking to migrate mass amounts of catalog services between programs and cores. Is there a best practice, script, etc. to do this? Past issue experienced with this story would be resolved with their fix but want to make sure their plan for a rake task to do this is acceptable. MUSC usually makes archives services and enters as a new service, but Brigette will also check internally for other process and get back to OHSU.

4/12/23

• Follow up from last meeting:

  • Q: Looking to migrate mass amounts of catalog services between programs and cores. Is there a best practice, script, etc. to do this? A:

    • No established best practice for mass updates.

      • MUSC did a large # of service updates for a program, years ago and it was a complex process (also had to consider Fulfillment data) that needed to have several check points for data integrity.

      • As OHSU mentioned, their script fix on ⁠this story may handle the Admin Edits orphaned services. However, still consider split/notify hierarchy to make sure the correct provider gets those service req submission emails.

    • Recommendation is to use what’s supported in SPARC currently:

      1. Inactive old service and create a new service under new program/core (is manual per service)

      2. Use the Catalog feature to move services to a diff program or core (is manual per service)

    • If still desiring to use script for mass changes (e.g, for bigger priority to preserve all history with a service with the change), do incrementally for migration & data checks along the way, as well as report checks that request #s and data appears correctly.

    •  

• Still looking for ‘your_cost’ field, how it gets calculated

  • Will follow up with Imogen with code

• OHSU is working on testing 3.10.1

  • Having users test in dev environment

Iowa

3/29/23

• not in attendance

4/12/23

Case Western

3/29/23

• No new SPARC updates

4/12/23

Children’s National

3/29/23

• not in attendance

4/12/23

Stony Brook:

3/29/23

• not in attendance

4/12/23