Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENH] Add explicit wording on DICOM terms correspondence #1450

Merged
merged 4 commits into from
Jun 17, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions src/common-principles.md
Original file line number Diff line number Diff line change
Expand Up @@ -422,6 +422,11 @@ possible. Since the NIfTI standard offers limited support for the various image
acquisition parameters available in DICOM files, we RECOMMEND that users provide
additional meta information extracted from DICOM files in a sidecar JSON file
(with the same filename as the `.nii[.gz]` file, but with a `.json` extension).
Currently defined metadata fields are listed in the [Glossary](./glossary.md).
Where possible, DICOM Tags are adopted directly as BIDS metadata terms and
indicated with "**Corresponds to** DICOM Tag ID1, ID2 `DICOM Tag Name`.".
When harmonization has been deemed necessary, this is indicated in the
BIDS term description with "**Based on** DICOM Tag ID1, ID2 `DICOM Tag Name`.".
Extraction of BIDS compatible metadata can be performed using [dcm2niix](https://github.com/rordenlab/dcm2niix)
and [dicm2nii](https://www.mathworks.com/matlabcentral/fileexchange/42997-xiangruili-dicm2nii)
DICOM to NIfTI converters. The [BIDS-validator](https://github.com/bids-standard/bids-validator)
Expand Down