| Contributors | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
A fully integrated interface between SPARCRequest and OnCore has been developed under the promotion of the Medical University of South Carolina. Roll-out with OnCore enterprise went live in September 2020.
SPARCDashboard → OnCore Minimal Footprint API
The purpose of SPARCRequest having a minimum footprint Interface (7 fields) with OnCore:
...
Figure 4. Record Shows in OnCore
Minimal Footprint API Configurations:
To turn on and utilize the minimal footprint API, the following settings have to be configured:
...
7. oncore_endpoint_access
OnCore → SPARC RPE and CRPC Endpoint Interface
In OnCore, SPARCRequest can be configured as an RPE Endpoint destination once the endpoint address is added into OnCore.
...
If a study does not have an existing calendar, OnCore can push a RPE and then CRPC push into SPARCRequest to initiate a study calendar with arms and visits.
SPARCDashboard OnCore Log Page
In SPARCDashboard, users with the oncore_endpoint_access are able to see the “OnCore Log” button (Figure 6), which lists which protocols have received CRPC pushes from OnCore.
...
OnCore Log UI | OnCore Log History Window |
|---|---|
 |  |
Figure 7
Technical Specs
Format: Health Level Seven (HL7) messaging, based on an XML encoding
Protocol: Simple Object Access Protocol (SOAP)
The API can be used for other Clinical Trial Management Systems as a template
For more details about the minimal footprint API, please check the links below to the GitHub codes: https://github.com/sparc-request/sparc-request/blob/36113d1c28e5ef6f7cc8118fb741ef515a8d8bf0/app/lib/oncore_protocol.rb
For more details about the RPE/CRPC endpoint API, please check the link to the GitHub codes: https://github.com/sparc-request/sparc-request/blob/36113d1c28e5ef6f7cc8118fb741ef515a8d8bf0/app/controllers/oncore_endpoint_controller.rb
...