DICOM
Category: Healthcare Standards
Node id: dicom
Standards: HIPAA, GDPR, SOC2
Performs DICOM medical imaging operations including parsing, validation, metadata extraction, anonymization, and format conversion
What it does
- DICOM file parsing with tag extraction and transfer syntax detection
- Structural and required-tag validation
- Clinical metadata extraction: patient, study, series, and image info
- PHI anonymization with remove, replace, or hash methods
- Format conversion to JPEG, PNG, NIfTI, JPEG2000
- Configurable image quality for conversion output
Use cases
- Extract clinical metadata from DICOM files for radiology analytics
- Anonymize DICOM images before sharing for research
- Convert DICOM to standard image formats for AI model training
- Validate DICOM files against required tag lists before archiving
Runtime
- Performance tier:
medium
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
dicom_data | text | Yes | DICOM file data (base64 or raw) — single instance; may also be an array for batch processing |
instances | json | No | Array of DICOM instances for batch processing — each element has inline bytes (dicom_b64/dicom_data) and/or a file_path (e.g. from a dicomweb retrieve). When present, the node processes every instance and returns result.instances[]. |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Main result data from the DICOM operation |
metadata | json | No | DICOM metadata including patient, study, and image information |
success | boolean | No | Whether the operation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | Yes | parse, validate, extract_metadata, anonymize, convert | DICOM operation to perform |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Required Tags | required_tags | json | No | Array of required DICOM tag names for validation | ||
| Include Pixel Data | include_pixel_data | boolean | No | false | Include pixel data info in metadata extraction | |
| Anonymization Method | method | enum | No | remove | remove, replace, hash | Method for anonymizing DICOM data |
| Keep UIDs | keep_uids | boolean | No | false | Preserve study/series/SOP UIDs during anonymization | |
| Output Format | output_format | enum | No | jpeg, png, nifti, jpeg2000 | Target format for conversion | |
| Quality | quality | number | No | 90 | min 1; max 100 | Output quality for image conversion (1-100) |
Errors
| Code | Description |
|---|---|
DICOM_DATA_REQUIRED | dicom_data input is missing or empty |
INVALID_OPERATION | Specified operation is not supported |
MISSING_PREAMBLE | DICOM file is missing the required preamble |
MISSING_REQUIRED_TAGS | Required DICOM tags are not present in the file |
UNSUPPORTED_FORMAT | Output format is not supported for conversion |
Runtime notes
- Output shape under 'result' varies by operation: parse has tags/tag_count, validate has is_valid/errors/warnings, convert has converted_data/output_format, etc.
- For extract_metadata, the detailed data goes into 'metadata' output (patient_info, study_info, image_info) — 'result' only contains operation name
- Anonymize returns modified DICOM data in result.anonymized_data — UIDs are regenerated unless keep_uids is true
- Convert renders the first pixel-data frame to result.converted_data (base64); requires PixelData in the input
- Array mode: if the input carries a LIST of instances (the
instancesport, adicom_dataarray, or an upstream dicomweb retrieve result.instances[] with file_path/inline bytes), the node processes each and returns result.instances[] (an array) plus result.instance_count/success_count/is_array. file_path instances are read from disk. Per-instance shapes: anonymize → {study_instance_uid, series_instance_uid, sop_instance_uid, file_path} (anonymized DICOM written to a new temp file, no inline bytes); convert → {sop_instance_uid, converted_data (base64), output_format, ...UIDs}; extract_metadata/parse/validate → the same record the single-item path returns, per instance. A single dicom_data string still returns the legacy single-item shape.
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.