SEND Explorer Warehouse supports connectors for direct data collection system connection and import of study data. Current collection systems supported include:
Xybion Pristima
Instem Provantis (self-hosted only)
Due to differences in data collection practices, configuration is required when implementing connections to Pristima or Provantis systems from SEND Explorer Warehouse. Connectors can also be developed for other preclinical data collection systems.
Loading and other configuration options for studies associated with direct data collection systems can be accessed through the Data Steward/Source Systems screen and selecting the gear icon next to source system (see screenshot below). SEND Explorer permission level of Data Steward or Administrator is required to view/update configuration options.
Configuration options for the direct data collection system Source Systems include:
Study Types
This function lists study types (static list pulled from data collection system) and defines if studies associated with a study type are available for loading into SEND Explorer or not. If data for studies associated with a Study Type should be included in SEND Explorer, then Include should = Y. If data for studies associated with a Study Type should not be included in SEND Explorer, then Include should = N. To update the Include field for a Study Type, click in the cell and type in Y or N and click OK. If the Include field is changed to N for a Study Type and there are already studies associated with that Study Type loaded in SEND Explorer, they will need to be deleted manually.
If new study types are added to the collection system and should be included in SEND Explorer, they need to be added to this table. Consult Certara staff if new study types need to be added. Automatic population of added study types is planned for future automation.
Domains
This is part of the initial configuration, and a static list of categories are pulled from the data collection system. It allows data collection system categories, activities, etc. to be mapped to applicable SEND domains and to determine what data types will be loaded to SEND Explorer.
If new categories/activities are added to the data collection system and need to be included in SEND Explorer, they need to be added to the Domains table manually and mapped to the appropriate SEND domain. Consult Certara staff if new categories need to be added to the Domains table. Automatic population of added categories is planned for future automation.
Study Exclusions Table
This table is used to list any studies that should not be loaded from the data collection system into SEND Explorer. To exclude a study from loading:
From the Data Steward top menu, select Source Systems
Click on the gear icon to the right of the source system name associated with the direct data collection system connection (e.g. Pristima, Provantis, etc.)
Click on the Study Exclusions button
Click on the Create Study Exclusion button
Type in the data collection system study number
Click OK
The study will be added to the Exclusions table and no future data from the study will be uploaded to SEND Explorer. If the study was already loaded into SEND Explorer, it will need to be deleted. Any data currently loaded into SEND Explorer for the study will remain unless it’s deleted. To remove the exclusion and start loading data again for a study:
Locate the study in the Study Exclusions Table
Click on the Delete link in the Delete column for the study and click on OK to confirm deletion from the Exclusion table
Loading of the study again from the data collection system will occur with the next SEND Explorer load cycle
Direct data collection systems are defined as interim sources. When final datasets (from a Source System that includes the TS domain) are loaded for a study originally loaded from an interim Source system, a record is automatically added to the Exclusions table to prevent the study from being uploaded any further from the data collection system. The data collection system source data is also added to the Load Queue for deletion as part of the overall workflow load cycles.