Biometrics
The biometrics modality is a PRISM extension designed for physiological assessments that do not fit into standard BIDS beh or physio categories. Examples include VO2max tests, plank tests, balance assessments, or anthropometric measurements.
[!TIP] Starting a new biometric assessment? Use the Biometrics Import Template to define your variables in Excel. It includes a Help sheet explaining all options.
File Name Structure
Biometric data files MUST follow this naming convention:
sub-<label>[_ses-<label>]_task-<label>_biometrics.<extension>
Entity |
Description |
|---|---|
|
Required. The subject identifier. |
|
Optional. The session identifier. |
|
Required. The name of the biometric task (e.g., |
|
Required. The suffix indicating the modality. |
|
Required. Typically |
Example:
sub-001_ses-01_task-ukk_biometrics.tsv
Sidecar JSON (*_biometrics.json)
Each biometric data file MUST be associated with metadata in a JSON sidecar. This file contains metadata about the assessment protocol.
PRISM follows the BIDS inheritance principle for biometrics sidecars:
Preferred (inherited): one dataset-level sidecar per task, named
task-<task>_biometrics.jsonin the dataset root.Override (if metadata truly differs): a subject/session-specific sidecar next to the TSV (e.g.,
sub-01_ses-01_task-<task>_biometrics.json).
Top-Level Objects
The JSON structure is divided into three main objects to organize metadata logically.
Object |
Requirement |
Description |
|---|---|---|
|
REQUIRED |
Technical details about the data acquisition. |
|
REQUIRED |
Scientific context, protocol details, and references. |
|
REQUIRED |
Administrative metadata about the file itself. |
Technical Object Fields
Key |
Requirement |
Type |
Description |
|---|---|---|---|
|
REQUIRED |
|
Type of assessment ( |
|
REQUIRED |
|
The format of the data file (e.g., |
|
OPTIONAL |
|
Software used (e.g., |
|
OPTIONAL |
|
Version of the software platform. |
|
OPTIONAL |
|
Primary language (e.g., |
|
OPTIONAL |
|
Who performed the test ( |
|
REQUIRED |
|
The device or equipment used (e.g., “Stopwatch”, “Cycle Ergometer”). |
|
OPTIONAL |
|
Manufacturer of the equipment. |
|
OPTIONAL |
|
Model name/number. |
|
OPTIONAL |
|
Date of last calibration ( |
|
OPTIONAL |
|
Who supervised the test. Allowed: |
|
OPTIONAL |
|
Where it took place ( |
Study Object Fields
Key |
Requirement |
Type |
Description |
|---|---|---|---|
|
REQUIRED |
|
Short alphanumeric identifier (e.g., |
|
REQUIRED |
|
Full human-readable name (e.g., |
|
OPTIONAL |
|
Common abbreviation. |
|
OPTIONAL |
|
Instrument version. |
|
OPTIONAL |
|
Instrument authors. |
|
OPTIONAL |
|
Reference citation. |
|
OPTIONAL |
|
DOI for the instrument. |
|
OPTIONAL |
|
Rights and license information. |
|
OPTIONAL |
|
High-level access classification. |
|
OPTIONAL |
|
Rights holder. |
|
OPTIONAL |
|
Psychological/physical construct measured. |
|
OPTIONAL |
|
Keywords describing the instrument. |
|
REQUIRED |
|
Detailed description of the procedure. |
|
RECOMMENDED |
|
Instructions given to the participant. |
|
OPTIONAL |
|
Psychometric properties. |
|
OPTIONAL |
|
Estimated time to complete. |
|
OPTIONAL |
|
Structured list of references. |
|
OPTIONAL |
|
Translation/adaptation provenance. |
Metadata Object Fields
Key |
Requirement |
Type |
Description |
|---|---|---|---|
|
REQUIRED |
|
Version of the schema used (e.g., |
|
REQUIRED |
|
Date of file creation in |
|
OPTIONAL |
|
Tool or person who created the file. |
Metric (Column) Definitions
In addition to the three top-level objects, a biometrics sidecar typically contains one object per TSV column (the column name is the JSON key). These entries document how to interpret and validate each metric.
Common fields for each metric:
Key |
Requirement |
Type |
Description |
|---|---|---|---|
|
REQUIRED |
|
Human-readable description of the metric/column. |
|
REQUIRED |
|
Unit of measurement (e.g., |
|
OPTIONAL |
|
Expected type: |
|
OPTIONAL |
|
Hard bounds for valid values. |
|
OPTIONAL |
|
Enumerated allowed values (numbers/strings). |
|
OPTIONAL |
|
Mapping of coded values to labels (e.g., Likert scale). |
|
OPTIONAL |
|
Optional session hint for repeated assessments (e.g., |
|
OPTIONAL |
|
Optional run hint for repeated assessments (e.g., |
Example metric with labeled levels:
"rpe_scale": {
"Description": "Rate of perceived exertion",
"Units": "score",
"DataType": "integer",
"AllowedValues": [0, 1, 2, 3],
"Levels": {
"0": "selten oder überhaupt nicht",
"1": "manchmal",
"2": "öfter",
"3": "meistens"
}
}
Generating Templates from Excel
You can generate biometrics JSON templates from a single-sheet Excel codebook (no data required) using prism_tools.py biometrics import-excel. See docs/PRISM_TOOLS.rst for the full column list and an example.
Example Sidecar
{
"Technical": {
"StimulusType": "Biometrics",
"FileFormat": "tsv",
"Equipment": "Stopwatch, Heart Rate Monitor"
},
"Study": {
"BiometricName": "ukk",
"OriginalName": "UKK 2km Walk Test",
"Description": "Participants walk 2km as fast as possible. HR and time are recorded.",
"Instructions": "Walk 2km at a steady, fast pace. Do not run.",
"Reference": "Oja et al. (1991)",
"EstimatedDuration": "15-20 min"
},
"Metadata": {
"SchemaVersion": "1.1.1",
"CreationDate": "2025-11-27"
}
}