Skip to content

Commit

Permalink
Add explicit wording on DICOM terms correspondence
Browse files Browse the repository at this point in the history
  • Loading branch information
yarikoptic committed Mar 31, 2024
1 parent bd08602 commit 8ccc10d
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions src/common-principles.md
Original file line number Diff line number Diff line change
Expand Up @@ -422,6 +422,9 @@ 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).
Many of such metadata entries are explicitly formalized in BIDS and could be found listed in the [Glossary](./glossary.md).
Whenever formalizing a new metadata entry within BIDS, the name SHOULD correspond to original DICOM Tag whenever the value is taken *as is* without any further harmonization.
The description of the term in the schema SHOULD describe such correspondence as "Corresponds to 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

0 comments on commit 8ccc10d

Please sign in to comment.