safe_exportRecords

A safe wrapper around redcapAPI::exportRecords that does not fail when records
are requested from an empty REDCap project. In the event of an empty project,
field names are used to create an empty data structure.

internal

A portable Shiny tool to explore patient-level electronic health record data
and perform chart review in a single integrated framework. This tool supports
browsing clinical data in many different formats including multiple versions
of the 'OMOP' common data model as well as the 'MIMIC-III' data model. In
addition, chart review information is captured and stored securely via the
Shiny interface in a 'REDCap' (Research Electronic Data Capture) project
using the 'REDCap' API. See the 'ReviewR' website for additional information,
documentation, and examples.

David Mayer

ReviewR

A Light-Weight, Portable Tool for Reviewing Individual Patient
Records

Laura Wiley

Luke Rasmussen

The Wiley Lab 

safe_exportRecords function

<dl><dt>rc_con</dt>
<dd>A REDCap API Connection Object</dd>
<dt>rc_field_names</dt>
<dd>The field names for a REDCap instrument</dd></dl>

Arguments

REDCap Safe Export Records — safe_exportRecords

<dl>

<dt>rc_con</dt>
<dd>A REDCap API Connection Object</dd>


<dt>rc_field_names</dt>
<dd>The field names for a REDCap instrument</dd>

</dl>

safe_exportRecords: REDCap Safe Export Records

Description

Usage

Value

Arguments