Skip to content

Studies and Longitudinal Registries

Metricis supports studies and registries as peer research contexts. They share platform services—identity, forms, consent, participant delivery, quality, integrations, and exports—without forcing a longitudinal registry into a study-shaped lifecycle.

Studies

A study can define sites, arms, cohorts, events, visits, schedules, participant identifiers, forms, task batteries, consent requirements, notifications, and integration settings. Configuration is versioned so collected data can be traced to the release in effect at the time.

Typical study workflows include:

  • protocol-driven setup and reusable templates;
  • site- and role-scoped researcher access;
  • participant enrollment and scheduling;
  • staff-entered and participant-entered data;
  • cognitive assessment delivery;
  • review, queries, verification, signatures, and locks; and
  • governed analysis snapshots and exports.

Registries

A registry represents an ongoing population and can collect recurring measures, diaries, phenotypes, device signals, and consent over a longer horizon. Registry participants can later join linked sub-studies while their registry membership and history remain distinct.

Registry workflows include participant-initiated interest or joining, registry-specific consent, recurring delivery, public information, and context-aware participant access. A linked sub-study adds its own membership, consent, instruments, and authority rather than inheriting everything implicitly.

Shared identity, explicit context

One account may give a person access to work from linked contexts, but every task and response retains the study or registry that authorized it. The API enforces context and consent at the service layer; navigation alone is not an authority boundary.

Configuration lifecycle

  1. Define or import research configuration as a draft.
  2. Validate stable identifiers, rules, mappings, and dependencies.
  3. Review the proposed change and its provenance.
  4. Release a version for use.
  5. Pin the release to a study/registry schedule or workflow.
  6. Preserve the version with collected data and downstream exports.

Continue to forms and governed data capture, participant experience, or core concepts.