Skip to content

Proposal for Adding MRIRadiofrequencyCoilType to Control Term (needed for Neuroimaging Extension) #365

@Peyman-N

Description

@Peyman-N

There is a final control term missing from the Neurimaging extension.
We need a control term for Coil Type used in MRI image acquisition. Currently, this is named: MRIRadiofrequencyCoilType
In DICOM, it is available for both receiver -tag (0018,9043)- and transmit -tag (0018,9051)- coils.
They have folwing types:

  1. BODY
  2. VOLUME
    head, extremity, etc.
  3. SURFACE
  4. MULTICOIL

I suggest adding the control term with follwing types:

Category Examples / Typical Terms Description
Body coil Built-in body Tx coil, Body Tx/Rx Integrated into the magnet bore; typically used as the default transmit coil, sometimes for both Tx/Rx (esp. at low field). Provides uniform excitation but lower SNR for reception compared to surface/array coils.
Volume coils Birdcage, TEM, Quadrature Encloses the imaging volume; can be transmit-only, receive-only, or both (Tx/Rx). Often used for head or torso scans.
Surface coils Single-loop, Flexible pad Placed near the region of interest; usually receive-only; high SNR in shallow depth.
Array coils 8-channel head coil, 32-channel torso array Multiple small coil elements combined for parallel imaging and high SNR.
Dedicated coils Knee coil, Wrist coil, Breast coil Optimized shape for specific anatomy; can be volume or array types.
Phased-array coils 8-ch spine array, 16-ch neurovascular Multiple receive elements covering large areas while maintaining high SNR.
Transmit–receive (Tx/Rx) coils Body Tx/Rx coil, Surface Tx/Rx loop Coil handles both RF transmission and reception; often used in low-field or interventional MRI.
Endocavitary coils Endorectal coil, Endovaginal coil Very small coils placed internally for ultra-high SNR near target tissue.

The problem is that transmit–receive is orthogonal to the others, so deciphering it is a little tricky.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions