... | ... | @@ -18,17 +18,15 @@ PEP can import (several types of) data from the Castor system. The import stores |
|
|
|
|
|
PEP can import several types of data from Castor, depending on what is stored in the Castor study. PEP can import data from multiple Castor studies, and it can import multiple types of data from individual studies.
|
|
|
|
|
|
### CRFs
|
|
|
- *Clinical research forms (CRFs)* are filled out by assessors during a study's data gathering stage. Entered data can then be imported into PEP. Imported data will include any reports generated due to CRFs containing repeated measure fields.
|
|
|
- *Reports* can also be created in Castor by hand. PEP offers the option to import such standalone reports.
|
|
|
- *Surveys* can be filled out by participants, the data then being stored in Castor. PEP can import data from completed surveys.
|
|
|
|
|
|
@@@ more here @@@
|
|
|
|
|
|
### Reports
|
|
|
## Steps imported individually
|
|
|
|
|
|
@@@ more here @@@
|
|
|
|
|
|
### Surveys
|
|
|
PEP imports data for individual Castor (CRF) [steps](https://helpdesk.castoredc.com/article/18-create-edit-and-delete-phases-and-steps) into separate PEP columns. Since [access to PEP is controlled](Access-control) at the level of columns, the implication is that PEP can distribute Castor data with a granularity of CRF steps. In other words: PEP users can be granted access to (answers to) individual Castor steps, but not to smaller units (e.g. individual questions). This should be taken into account when configuring a Castor study meant for PEP integration. Questions should only be put together into a single step if their answers should always be distributed (or withheld) together by PEP.
|
|
|
|
|
|
@@@ more here @@@
|
|
|
An equivalent principle applies to the import of Castor survey data: answers to a single survey step end up in a single PEP column. Surveys should therefore also be configured in such a way that their data are chunked appropriately.
|
|
|
|
|
|
## Data format
|
|
|
|
... | ... | @@ -76,11 +74,9 @@ In the sample data: |
|
|
- the `WalkingAid` node (apparently) contains the answers to a [checkbox](https://helpdesk.castoredc.com/article/185-create-a-field-with-option-groups-radio-button-checkbox-and-dropdown)-type question.
|
|
|
- the `reports` node contains no entries, indicating that no repeated measurements are associated with these Castor data. Perhaps the Castor configuration contained no questions of that type, or zero repeated measurements were taken.
|
|
|
|
|
|
## Castor steps as a unit
|
|
|
If report data are imported, they are placed into the `reports` node. Keys of sub-nodes indicate the *type* of report having been imported. The value will be a JSON array containing the answer sets for individual reports.
|
|
|
|
|
|
PEP imports data for individual Castor (CRF) [steps](https://helpdesk.castoredc.com/article/18-create-edit-and-delete-phases-and-steps) into separate PEP columns. Since [access to PEP is controlled](Access-control) at the level of columns, the implication is that PEP can distribute Castor data with a granularity of CRF steps. In other words: PEP users can be granted access to (answers to) individual Castor steps, but not to smaller units (e.g. individual questions). This should be taken into account when configuring a Castor study meant for PEP integration. Questions should only be put together into a single step if their answers should always be distributed (or withheld) together by PEP.
|
|
|
|
|
|
An equivalent principle applies to the import of Castor survey data: answers to a single survey step end up in a single PEP column. Surveys should therefore also be configured in such a way that their data are chunked appropriately.
|
|
|
The import of standalone reports produces an equivalent JSON structure to keep things consistent across PEP columns. But note that the `crf` node will always be empty in these cases.
|
|
|
|
|
|
## Column naming
|
|
|
|
... | ... | |