Exports and Analysis

Metricis is designed to produce governed, interpretable data products rather than anonymous file downloads. Export and analysis APIs are feature-gated and should be enabled only with deployment-specific authorization and policy.

Export workflow

1. An authorized user selects a study or registry context, dataset, purpose, and output profile.
2. Policy evaluates role, consent, data classification, and de-identification requirements.
3. Metricis creates an immutable snapshot of the selected source and derived records.
4. A manifest records schema, versions, filters, mappings, transformations, timestamps, and checksums.
5. The resulting bundle is made available through an audited, time-bounded path.

Output families

Configured bundles can target tabular analysis and common statistics-package workflows. Source values, coded values, derived scores, and transformation metadata remain distinguishable. ODM-related metadata and REDCap mappings support interoperability, but each downstream analysis still needs a protocol-specific data-management and statistical plan.

De-identification and minimization

Export profiles can remove or transform direct identifiers, constrain dates or sites, and limit fields to the approved purpose. De-identification is a policy and risk decision, not a single universal transform; small cohorts and linked datasets may still be re-identifiable.

Reproducibility

Use the snapshot identifier and manifest as the stable reference for analysis. If the operational database changes, an earlier snapshot remains interpretable through its pinned form/task versions, algorithms, mappings, and filters.

See REST API, Data quality and monitoring, and Trust and governance.