Skip to content

REDCap Interoperability

REDCap integration is a configured capability. A study can declare REDCap as an external authority while Metricis provides participant delivery, cognitive tasks, scoring, scheduling support, or other governed workflows.

Operating model

Integration mode is explicit per study. In a REDCap-managed mode, event, instrument, field, participant, and site mappings define how data crosses the boundary. Metricis does not silently switch to a local system of record when REDCap is unavailable or misconfigured.

Supported integration patterns

  • import or reconcile configured study metadata and participants;
  • map Metricis releases and results to REDCap instruments, fields, events, and repeating instances;
  • receive Data Entry Trigger webhooks where configured;
  • enqueue outbound writes with idempotency and retry state;
  • route site-specific projects or credentials; and
  • expose reconciliation and terminal failures for operator review.

The exact pattern depends on the REDCap version, enabled APIs/modules, institutional policy, project design, and study configuration.

Safety rules

  • API tokens and webhook secrets stay server-side.
  • Credentials, project identifiers, and base URLs are deployment configuration.
  • Stable mappings are validated before a study is enabled.
  • Webhook and queued-job replay must be idempotent.
  • Direction and ownership are defined per data family to avoid sync loops.
  • Failed writes are visible and recoverable; success is not assumed from queue acceptance.
  • Imported and exported records retain source and mapping provenance.

Before production

Validate with a non-production REDCap project, representative longitudinal/repeating events, all sites, unusual identifiers, missing values, corrected records, duplicate webhooks, timeouts, rate limits, and credential rotation. Document which system is authoritative for each field family and how discrepancies are resolved.

See Integration overview, REST API, and Trust and governance.