Skip to content

Commit

Permalink
Merge pull request #550 from OuhscBbmc/dev
Browse files Browse the repository at this point in the history
alt text for vignettes
  • Loading branch information
wibeasley authored Oct 25, 2024
2 parents c55716a + e3a1364 commit d30cd47
Show file tree
Hide file tree
Showing 7 changed files with 27 additions and 13 deletions.
4 changes: 4 additions & 0 deletions NEWS.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,10 @@ Version 1.4.x (Not yet released on CRAN)

These features are not yet on CRAN. Install with `remotes::install_github("OuhscBbmc/REDCapR")`

### New Features

* `redcap_file_repo_list_oneshot()` export a list of files/folders from the file repository (requested by @agdamsbo, #549)

Version 1.3.0 (released 2024-10-22)
==========================================================

Expand Down
4 changes: 2 additions & 2 deletions R/redcap-file-repo-list.R
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
#' @title
#' Export a List of Files/Folders from the File Repository
#'#'
#'
#' @description
#' Allows you to export a list of all files and sub-folders from a specific
#' folder in a project's File Repository.
#' Each sub-folder will have an associated folder_id number,
#' and each file will have an associated doc_id number.
#'
#' @param folder_id the `folder_id` of a specific folder in the
#' @param folder_id the integer of a specific folder in the
#' File Repository for which you wish to export a list of its
#' files and sub-folders.
#' If `NA` (the default),
Expand Down
6 changes: 6 additions & 0 deletions _pkgdown.yml
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,14 @@ reference:
- redcap_write_oneshot
- redcap_delete
- redcap_report

- title: "File API Operations"
desc: >
Manipulating files in the REDCap records and in the file repository.
contents:
- redcap_file_download_oneshot
- redcap_file_upload_oneshot
- redcap_file_repo_list_oneshot

- title: "Additional API Methods"
desc: >
Expand Down
5 changes: 2 additions & 3 deletions man/redcap_file_repo_list_oneshot.Rd

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 4 additions & 0 deletions vignettes/TroubleshootingApiCalls.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,7 @@ This first group of checks primarily focuses on the server and the logins accoun

```{r EmailVerified}
#| echo = FALSE,
#| fig.alt = 'verified email screen shot',
#| out.extra = 'style = "fig.width=400px"'
knitr::include_graphics("images/EmailVerified.png")
```
Expand All @@ -54,6 +55,7 @@ This first group of checks primarily focuses on the server and the logins accoun
```{r ApiPrivilegeDashboard}
#| echo = FALSE,
#| fig.alt = 'tokens screen shot',
#| out.extra = 'style = "fig.width=600px"'
knitr::include_graphics("images/ApiPrivilegeDashboard.png")
```
Expand All @@ -64,6 +66,7 @@ This first group of checks primarily focuses on the server and the logins accoun
```{r MagnifyingGlass}
#| echo = FALSE,
#| fig.alt = 'magnifying screen shot',
#| out.extra = 'style = "fig.width=550px"'
knitr::include_graphics("images/MagnifyingGlass.png")
```
Expand All @@ -79,6 +82,7 @@ This section examines potential problems that occur after data leaves a working
```{r PostmanScreenshot}
#| echo = FALSE,
#| fig.alt = 'PostMan screen shot',
#| out.extra = 'style = "fig.width=800px"'
knitr::include_graphics("images/PostmanScreenshot.png")
```
Expand Down
2 changes: 1 addition & 1 deletion vignettes/workflow-read.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -202,7 +202,7 @@ ds_1 <-

At this point, the data.frame `ds_1` has everything you need to start analyzing the project.

```{r unstructured-2}
```{r unstructured-2, fig.alt = "histogram of patient weight"}
ds_1
hist(ds_1$weight)
Expand Down
15 changes: 8 additions & 7 deletions vignettes/workflow-write.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@ vignette: >
%\VignetteIndexEntry{Writing to a REDCap Project}
%\VignetteEncoding{UTF-8}
%\VignetteEngine{knitr::rmarkdown}
editor_options:
markdown:
editor_options:
markdown:
wrap: 72
---

Expand Down Expand Up @@ -241,6 +241,7 @@ ds_patient <-

```{r codebook-race}
#| echo = FALSE,
#| fig.alt = 'codebook race variable screen shot',
#| out.extra = 'style = "fig.width=1200px"'
knitr::include_graphics("images/codebook-race.png")
```
Expand Down Expand Up @@ -364,16 +365,16 @@ format (*i.e.*, everything jammed into one rectangle.)

## REDCap's CDIS

The [Clinical Data Interoperability Services](https://projectredcap.org/software/cdis/) (CDIS)
The [Clinical Data Interoperability Services](https://projectredcap.org/software/cdis/) (CDIS)
use [FHIR](https://www.hl7.org/fhir/overview.html) to move data from
your institution's [EMR/EHR](https://www.healthit.gov/faq/what-are-differences-between-electronic-medical-records-electronic-health-records-and-personal)
(eg, Epic, Cerner) to REDCap.
(eg, Epic, Cerner) to REDCap.
Research staff have control over which patient records are selected or eligible.
Conceptually it's similar to writing to REDCap's with the API,
Conceptually it's similar to writing to REDCap's with the API,
but at much bigger scale.
Realistically, it takes months to get through your institution's human layers.
Once established, a project would be populated with EMR data
in much less development time
Once established, a project would be populated with EMR data
in much less development time
--assuming the desired data models corresponds with
FHIR [endpoints](https://hl7.org/fhir/endpoint.html).

Expand Down

0 comments on commit d30cd47

Please sign in to comment.