mirror of
https://github.com/agdamsbo/REDCapCAST.git
synced 2026-06-19 05:07:30 +02:00
Improving SAS code.
This commit is contained in:
parent
cbc39e288e
commit
3488ff0a7a
2 changed files with 140 additions and 118 deletions
59
README.md
59
README.md
|
|
@ -22,32 +22,49 @@ possible fields; this has the effect of nesting the output table in a
|
|||
way that is not useful in most analysis software. Therefore, I have made
|
||||
a solution to handle the problem in both SAS and R.
|
||||
|
||||
## Supported Platforms
|
||||
|
||||
- R
|
||||
- SAS
|
||||
|
||||
### Coming Soon
|
||||
|
||||
- Python
|
||||
- VBA
|
||||
|
||||
## Instructions
|
||||
|
||||
### SAS
|
||||
|
||||
1. Run the macro definition in the source editor or using `%include`.
|
||||
2. Run the SAS code provided by REDCap to import the data BUT COMMENT
|
||||
THIS LINE:
|
||||
```format redcap_repeat_instrument redcap_repeat_instrument_.;```
|
||||
3. Open the data dictionary in MS Excel. We will need to do some pre-
|
||||
processing to the data dictionary file before reading it in because
|
||||
some of the user entry points (such as **Field Label**) allows for newline
|
||||
characters, which can break our data ingestion. MS Excel will read in
|
||||
the newline characters correctly.
|
||||
- Copy the first four columns and paste into a new sheet.
|
||||
- Save the new sheet as a .csv file.
|
||||
- Close the file.
|
||||
4. Call the macro, adjusting parameters as needed.
|
||||
|
||||
### R
|
||||
|
||||
The function definition file contains an example to assist you.
|
||||
The function definition file contains [roxygen2](https://cran.r-project.org/package=roxygen2) comments to assist you.
|
||||
|
||||
1. Run the function definition in the source editor or using `source()`.
|
||||
2. Download the record dataset and metadata and import them. This can
|
||||
1. Download the record dataset and metadata. This can
|
||||
be accomplished either by traditional methods or using the API. The
|
||||
`read.csv()` function should be able to handle newline characters within
|
||||
records, so no pre-processing of metadata csv is needed.
|
||||
3. Call the function, pointing it to your record dataset and metadata
|
||||
`data.frame`s.
|
||||
1. Call the function, pointing it to your record dataset and metadata
|
||||
`data.frame`s.
|
||||
|
||||
### SAS
|
||||
|
||||
1. Download the data, SAS code to load the data, and the data dictionary from REDCap
|
||||
1. Run the SAS code provided by REDCap to import the data BUT COMMENT
|
||||
THIS LINE:
|
||||
```format redcap_repeat_instrument redcap_repeat_instrument_.;```
|
||||
1. Run the RECapRITS macro definitions in the source editor or using `%include`.
|
||||
1. Run the macro call `%REDCAP_READ_DATA_DICT()` to load the data dictionry into your SAS session, pointing to the file location of your REDCap data dictionary.
|
||||
1. Run the macro call `%REDCAP_SPLIT()`. You will have an output dataset for
|
||||
your main table as well as for each repeating instrument.
|
||||
|
||||
|
||||
## Issues
|
||||
|
||||
Suggestions and contributions are more than welcome! Please feel free to create an issue or pull request.
|
||||
|
||||
## About REDCap
|
||||
|
||||
This code was written for [REDCap electronic data capture tools](https://projectredcap.org/).^1^ Code for this project was tested on the REDCap instance hosted at Spectrum Health, Grand Rapids, MI. REDCap (Research Electronic Data Capture) is a secure, web-based application designed to support data capture for research studies, providing 1) an intuitive interface for validated data entry; 2) audit trails for tracking data manipulation and export procedures; 3) automated export procedures for seamless data downloads to common statistical packages; and 4) procedures for importing data from external sources.
|
||||
|
||||
## References
|
||||
|
||||
^1^Paul A. Harris, Robert Taylor, Robert Thielke, Jonathon Payne, Nathaniel Gonzalez, Jose G. Conde, Research electronic data capture (REDCap) – A metadata-driven methodology and workflow process for providing translational research informatics support, J Biomed Inform. 2009 Apr;42(2):377-81.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue