20230426-Technical Committee Meeting Minutes

Meeting:	SPARC OS Technical Committee
Date:	04/26/2023
Time:	3:00 pm
MUSC
Iowa
LA CaTS
Children’s National
Case Western
OHSU
Stony Brook Medicine

Agenda:

Standup Round for institutional updates

Louisiana Clinical & Translational Science Center:

4/12/23

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

4/26/23

MUSC:

4/26/23

Oregon Health & Science University:

4/12/23

Follow up from 3/29/23 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

4/26/23

Iowa

4/12/23

4/26/23

Case Western

4/12/23

4/26/23

Children’s National

4/12/23

4/26/23

Stony Brook:

4/12/23

4/26/23