Capability Status¶
Metricis evolves quickly. This page separates implemented capability from deployment enablement and study-specific validation so that product copy does not become an accidental operational promise.
Last verified: 2026-07-18
Machine-readable source: docs/capabilities.json
Status definitions¶
| Status | Meaning |
|---|---|
| Available | Implemented and available without a feature-specific enablement flag |
| Configured | Implemented but requires deployment credentials, infrastructure, or study configuration |
| Feature-gated | Implemented and tested but intentionally disabled until enabled for a deployment or study |
| Validation stage | Implemented research capability whose scientific or operational validation remains study-specific |
Current inventory¶
| Capability | Status | Scope |
|---|---|---|
| Studies and longitudinal registries | Available | Workspaces, participants, cohorts, schedules, sites, arms, and lifecycle workflows |
| Governed electronic data capture | Available | FormSpec authoring, versioned releases, edit checks, queries, SDV, signatures, locks, and audit history |
| Participant and caregiver delivery | Available | Magic links, onboarding, tasks, diaries, consent, schedules, accessibility, and offline-capable capture |
| Cognitive assessment and ePRO | Available | jsPsych batteries, questionnaires, recurring check-ins, scoring, and version-pinned delivery |
| Wearable and device data | Configured | HealthKit and Health Connect ingestion plus derived signal families |
| eConsent and participant rights | Available | Versioned consent, signatures, assent, re-consent, purposes, withdrawal, and provenance |
| Data quality and monitoring | Available | Validation, missing-data review, queries, risk-based SDV, change classification, and audit reconstruction |
| REDCap interoperability | Configured | REDCap-managed studies, mappings, webhooks, retryable sync, and fail-safe controls |
| Governed exports and analysis APIs | Feature-gated | Policy-controlled exports, de-identification, snapshots, manifests, tokens, and analysis bundles |
| Governed AI-assisted authoring | Feature-gated | Protocol ingestion and draft ChangeSets with human review and release |
| Public study and registry sites | Configured | Published information, interest/join pathways, bilingual content, and edge metadata |
| Multimodal research measures | Validation stage | Registry-specific measures, phenotype proposals, active-stand workflows, and non-diagnostic trends |
Reading the table responsibly¶
- A status applies to the platform implementation, not automatically to every hosted deployment.
- “Available” does not replace installation qualification, validation, standard operating procedures, training, or protocol approval.
- “Configured” means external systems or credentials materially affect the result.
- “Feature-gated” means a team must make a deliberate enablement decision; documentation should not imply universal availability.
- “Validation stage” capabilities must not be described as diagnostic or clinically validated unless evidence for that intended use is separately established.
The roadmap may describe work newer than this verification date. If roadmap language and this page differ, treat the capability manifest as the current public claim and open a documentation issue to reconcile them.