Overview
This node processes DICOM (Digital Imaging and Communications in Medicine) files, which are standard formats for medical imaging data. It supports multiple operations on DICOM files such as extracting metadata, anonymizing patient information, converting images to common formats, and validating the file against standards.
Common scenarios where this node is useful include:
- Extracting key patient and study metadata from medical images for reporting or integration.
- Removing or masking sensitive patient information to comply with privacy regulations before sharing images.
- Converting DICOM images into widely supported image formats like PNG or JPEG for visualization or web use.
- Validating DICOM files to ensure they conform to expected standards and are not corrupted.
For example, a radiology workflow could use this node to convert DICOM scans to JPEG images for quick review, while also anonymizing patient details before sending them to external specialists.
Properties
| Name | Meaning |
|---|---|
| File Property Name | Name of the binary property containing the DICOM file to process (default: "data"). |
| Output Format | Format to convert the DICOM file to. Options: PNG, JPEG, JSON, XML. |
| Quality | Quality of output image (1-100), applicable when output format is PNG or JPEG (default: 90). |
| Window Center | Window Center value for image rendering; -1 means automatic adjustment (for PNG/JPEG). |
| Window Width | Window Width value for image rendering; -1 means automatic adjustment (for PNG/JPEG). |
Output
The node outputs an array of items corresponding to each input item processed. Each output item contains:
- A
jsonobject with operation-specific fields:- For Convert operation:
success: Boolean indicating if conversion succeeded.format: The output format used (e.g., "png", "jpeg").sourceFile: The name of the binary property holding the original DICOM file.
- For Convert operation:
- A
binaryproperty containing the converted file under the keyconverted. This binary data includes:data: The raw bytes of the converted file.mimeType: The MIME type matching the output format (e.g.,image/png).fileName: The filename with appropriate extension (e.g.,converted.png).
If errors occur and the node is configured to continue on failure, the output will contain a JSON object with an error message instead.
Dependencies
- The node relies on internal asynchronous functions (
u,y,f,g) to perform the actual processing of DICOM files:- Metadata extraction
- Anonymization
- Conversion
- Validation
These functions presumably depend on underlying DICOM processing libraries or services, but these dependencies are abstracted away in the provided code.
- No explicit external API keys or credentials are required based on the static analysis.
Troubleshooting
Missing Binary Data Property: If the specified binary property name does not exist on an input item, the node throws an error indicating the missing property. Ensure the input data contains the correct binary field.
Unsupported Output Format: Only PNG, JPEG, JSON, and XML are supported for conversion. Using other formats may cause unexpected behavior.
Quality and Window Parameters: Quality, window center, and window width parameters only apply to PNG and JPEG conversions. Setting them for other formats has no effect.
Error Handling: If the node is set to continue on failure, errors during processing will be returned as JSON error messages per item rather than stopping execution.
Links and References
Note: This summary is based solely on static analysis of the provided source code and property definitions.