Supported File Types

Datature Nexus currently supports DICOM and NIfTI file types for 3D medical imaging projects. Each file type has specific requirements that must be met for successful upload and processing.

NIfTI File Upload Requirements

To upload a NIfTI file into a 3D medical project as an asset in Nexus, ensure that the file meets the following criteria:

• File size must not exceed 1 GiB
• File format must be uncompressed (.nii) or compressed using gzip (.nii.gz)
• File must be in NIfTI-1 or NIfTI-2 format
• File must define only dimensions x, y, z, and optionally t
  • If the time dimension t is defined, it must contain exactly one frame
• The datatype must be one of the following:
  • DT_UNSIGNED_CHAR (2)
  • DT_SIGNED_SHORT (4)
  • DT_SIGNED_INT (8)
  • DT_FLOAT (16)
  • DT_DOUBLE (64)
  • DT_INT8 (256)
  • DT_UINT16 (512)
  • DT_UINT32 (768)
  • DT_INT64 (1024)
  • DT_UINT64 (1280)
  • DT_FLOAT128 (1536)

📘

Note:

RGB, RGBA, and complex datatypes are not supported.

DICOM File Upload Requirements

To upload or sync a 3D DICOM image into a 3D medical project as an asset in Nexus:

1. Create a ZIP file containing the DICOM files that define the series
2. Ensure the ZIP file meets the following requirements:
   • File size must not exceed 1 GiB
   • Must not contain any folders (all DICOM files must be located in the root of the ZIP file)
   • Compressed file names must:
     • Contain only alphanumeric characters, hyphens, underscores, spaces, and periods
     • End with the extension .dcm or .dicom
     • Be between 1 and 256 characters in length
   • Must contain only DICOM files (files without image data will be ignored)
   • All DICOM images must belong to the same study and series
3. DICOM images comprising a 3D series must satisfy the following:
   • The (0020, 0010) Transfer Syntax UID must be one of the supported syntaxes below:
     • Explicit VR Little Endian
     • Implicit VR Little Endian
     • Explicit VR Big Endian
     • Deflated Explicit VR Little Endian
     • RLE Lossless
     • JPEG Basline (Process 1)
     • JPEG Extended (Processes 2 & 4)
     • JPEG Lossless, Non-Hierarchical (Process 14)
     • JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14[Selection Value 1])
     • JPEG-LS Lossless
     • JPEG-LS Lossy (Near-Lossless)
     • JPEG 2000 (Lossless Only)
     • JPEG 2000

• The (0028, 0004) Photometric Interpretation must be either MONOCHROME1 or MONOCHROME2
• The (0020, 0037) Image Orientation must be identical across all image slices
• If defined, the (0028, 1050) Window Center and (0028, 1051) Window Width attributes should define only a single view (only the first view will be used if multiple views are defined)

📘

Note:

Associated data, like RT Structure Sets, should be imported via Annotation Upload after the ZIP file is uploaded or synced into the project.