q01/phantom-mri-dicoms
28
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
This dataset tracks all phantom MRI acquisitions done for the TRR379 for the purpose of validating the Q01 protocol at all sites.
21 commits 4 branches 0 tags 156 KiB
  • Python 100%
Find a file
Exact
Michał Szczepanik d4b97c3519 Switch field map labelling to use acq instead of run 
It is now clear that the intention was to use each field map
acquisition just once. To make this more apparent in the BIDS layout,
and enable Heudiconv's "CustomAcquisitionLabel" strategy for matching
IntendedFor, we switch from using run- labels to acq- labels. The
label will be either the corresponding task label (if intended for
func) or the corresponding acquisition label (for dwi).

We still keep the ImagingVolume and Shims options: we'd rather not
assign IntendedFor than assign a mismatched one.

It seems that the conditional which handles protocol name with no
explicit field map numbering was left over from the initial draft (it
seems that protocols from Aachen, Frankfurt, and Mannheim always use
run-(1/2/3) while Mannheim has a naming strategy altogether
incompatible with this heuristic), but the conditional is kept (and
updated) just in case.
2026-06-03 20:53:56 +02:00
.datalad [DATALAD] new dataset 2025-08-29 16:36:13 +02:00
code Switch field map labelling to use acq instead of run 2026-06-03 20:53:56 +02:00
sessions [DATALAD] Save updated subdatasets 2025-11-09 10:10:32 +01:00
.gitattributes Generalize pseudonymization to multi-context ID mapping 2025-08-31 15:52:14 +02:00
.gitmodules Adopt new session naming nomenclature 2025-11-09 07:50:46 +01:00
id_map.tsv Adjust layout to mimic Q01 pseudonymization 2025-10-31 11:05:59 +01:00
README.md Update pseudonymization example 2025-10-31 12:18:29 +01:00

README.md

Phantom MRI study dataset

This dataset tracks all phantom MRI acquisitions done for the TRR379 for the purpose of validating the Q01 protocol at all sites.

Key aspects of this setup

Session labels are pseudonymized identifiers

This first layer of personal data protection reduces the chances of participant identifiers appearing as part of file/path names.

Each session or acquisition is placed into a directory/dataset
in sessions/ that is given a project-internal pseudonymous identifier as its directory name.

Multi-project ID mapping

The top-level id_map.tsv is a tab-separated table, which maps session source identifiers to any number of contexts. The source identifier corresponds to the directory name for a DICOM dataset in the sessions/ directory. This is the value in the first column of each table row. Every subsequent column define the ID mapping to a different context. The context label is defined in the header row.

A script to perform "re-identification" from a particular context is provided at code/reidentify.py. It can be used like this

python3 code/reidentify.py id_map.tsv q01 AP001

The script returns the source identifier linked to the q01 identifier AP001.

The file id_map.tsv is an annexed file. Once the last copy of this file is destroyed, identifier-based re-identification is no longer possible (a precondition for data anonymization).