DICOM

Process and analyze DICOM medical imaging files
Join our community

Actions4

Overview

This node processes and analyzes DICOM (Digital Imaging and Communications in Medicine) medical imaging files. It supports four main operations:

  • Extract Metadata: Retrieves DICOM tags and metadata from the file, useful for obtaining patient or study information without handling image data.
  • Anonymize: Removes or replaces patient-identifiable information to protect privacy before sharing or analysis.
  • Convert: Converts DICOM files into other formats such as PNG, JPEG, JSON, or XML, enabling easier viewing or integration with other systems.
  • Validate: Checks the DICOM file against various levels of compliance with the DICOM standard to ensure file integrity and correctness.

Typical use cases include preparing medical images for research by anonymizing sensitive data, converting images for reports or presentations, extracting metadata for cataloging, and validating files received from different sources to ensure they meet standards.

Properties

Name Meaning
Operation The action to perform on the DICOM file: Extract Metadata, Anonymize, Convert, or Validate.
File Property Name Name of the binary property containing the DICOM file (default is "data").
Validation Level How strictly to validate the DICOM file (Basic, Standard, Strict). Only shown for Validate.

Additional properties relevant only to specific operations (not requested here) include fields to include in metadata extraction, anonymization profiles and custom rules, output format and quality for conversion, etc.

Output

The node outputs an array of items corresponding to each input item processed. Each output item contains:

  • A json object with operation-specific results:

    • For Validate:
      • valid: Boolean indicating if the file passed validation.
      • errors: Array of error messages found during validation.
      • warnings: Array of warning messages.
      • level: The validation level used.
      • sourceFile: The name of the binary property holding the original file.

  • No binary output is produced for the Validate operation.

For other operations (not detailed here), binary outputs may contain modified or converted DICOM files.

Dependencies

  • Requires access to the binary data of the DICOM file within the specified binary property.
  • Uses internal asynchronous helper functions to perform each operation (extractMetadata, anonymize, convert, validate).
  • No external API keys or services are required based on the provided code.

Troubleshooting

  • Missing Binary Data: If the specified binary property does not exist on an input item, the node throws an error indicating the missing property.
  • Validation Errors: If the DICOM file fails validation, errors and warnings will be listed in the output JSON. Users should review these to correct file issues.
  • Incorrect Property Names: Ensure the "File Property Name" matches exactly the binary property containing the DICOM file.
  • Operation Mismatch: Selecting an operation but providing incompatible parameters may cause unexpected results; verify that properties correspond to the chosen operation.

Links and References

Discussion