DINGO Flow logo

Documentation

DINGO Flow Public Docs

DINGO Flow helps imaging teams receive DICOM studies, evaluate routing rules, apply metadata transformations, deliver objects to destinations, monitor delivery work, and clean up temporary data after the workflow is settled.

Product Overview

What DINGO Flow Does

DINGO Flow is an operations workspace for DICOM routing. It is designed for teams that need visibility and control over where incoming studies go, how metadata should be adjusted before delivery, and which deliveries need attention.

01

Receive

Imaging systems send DICOM studies into Flow through the receiving endpoint configured for the environment.

02

Route

Enabled rules inspect DICOM metadata and decide which destinations should receive each matching object.

03

Transform

Optional profiles can adjust metadata before delivery, including cleanup, replacement, added values, prefixes, suffixes, or anonymization.

04

Deliver

Flow creates delivery work for each destination and tracks status, attempts, errors, and evidence.

05

Monitor

Operators use Dashboard, Incoming Studies, Delivery Queue, and Activity Log to follow work and resolve exceptions.

06

Clean Up

Temporary retained studies are removed after configured timing once required deliveries are settled.

Receiving

Receiving DICOM From Imaging Systems

Use DINGO Flow as the receiving point for studies that need rule-based routing. Configure the sending imaging system with the receiving details shown in Flow Setup, then send a small test study before enabling production traffic.

Start with a controlled test Before routing live volume, send a known test study and confirm it appears in Incoming Studies, matches the expected rules, and creates the expected delivery work.
  • Use Setup to review the active receiving details for the environment.
  • Confirm that sending systems are authorized by the local network and security policy.
  • Use Incoming Studies to verify patient, accession, modality, date, status, and received timing.
  • Use the Activity Log to inspect receive and routing events when troubleshooting.

Delivery Targets

Creating Destinations

Destinations define where DINGO Flow sends routed DICOM objects. Each destination can be enabled or disabled, tuned for delivery behavior, and tested before it is used in active routing rules.

Destination Details

  • Name each destination clearly for operators.
  • Keep inactive destinations disabled until they are ready.
  • Use delivery limits conservatively at first, then increase only when the destination can handle the load.

Delivery Preferences

  • Choose whether to preserve original data handling or request a specific transfer preference.
  • Review destination health and recent success or failure history from the Dashboard.
  • Use the Delivery Queue to filter work by destination when investigating issues.

Routing Logic

Building Routing Rules

Routing rules decide which destinations receive incoming DICOM. Rules can match on simplified DICOM tag names, such as modality, patient ID, accession number, study date, description, institution, or UID fields.

1. Name The Rule

Use a name that explains the business intent, such as CT to Research Archive or XR Emergency Copies.

2. Choose Priority

Set priorities so operators understand the expected evaluation order.

3. Add Conditions

Use equals, contains, exists, absent, or pattern conditions to match the desired DICOM metadata.

4. Bind Destinations

Select one or more destinations, optionally with a transformation profile for each route.

Metadata Handling

Applying Transformations

Transformation profiles are reusable sets of metadata actions. Apply them when a destination requires adjusted values, cleaned fields, consistent prefixes or suffixes, or anonymized data for non-clinical workflows.

  • Remove: delete a selected tag before delivery.
  • Replace: overwrite a tag with a configured value.
  • Add: add a tag value where appropriate.
  • Prefix or suffix: preserve the existing value while adding controlled text around it.
  • Empty: keep the tag but clear its value.
  • Anonymize: apply a broader privacy-focused profile where the workflow calls for it.

Daily Use

Monitoring Delivery Status And Retries

Operators normally work from Dashboard, Incoming Studies, Delivery Queue, and Activity Log. These views show whether studies are still routing, complete, retained, deleted, or waiting for attention.

Dashboard

Use the Dashboard for current totals, active queue counts, destination health, delivery outcomes, and recent routing performance.

Incoming Studies

Search studies by patient, ID, accession, modality, date, receive time, and status. Open retained studies for operational visual review when needed.

Delivery Queue

Filter delivery work by status and destination. Retry failed or cancelled work, cancel selected scopes, or resend a study when the workflow requires it.

Activity Log

Inspect events, delivery attempts, error details, and evidence. Use this view when explaining what happened during routing or delivery.

Viewer access is for operational review The included viewing path is intended for operations, QA, research, education, and general visualization. It is not intended for diagnostic or therapeutic decisions.

Retention

Retention And Cleanup Behavior

DINGO Flow keeps temporary studies only while they are useful to the active workflow. Once required deliveries are settled and the configured timing has passed, Flow can mark studies retained and then clean them up.

  • Settlement timing: gives recently received studies a quiet period before cleanup decisions.
  • Temporary retention: controls how long settled studies remain available for operational review.
  • Deleted record history: controls how long deleted study records remain visible for operational traceability.
  • Log retention: keeps audit and delivery-attempt history according to configured operational needs.

Notifications

Alerts And Scheduled Summaries

DINGO Flow can send operational notifications when selected thresholds are met. This helps teams notice delivery problems, queue buildup, availability interruptions, storage pressure, and recurring destination issues.

Delivery Failure Threshold

Notify the team when recent failed or retrying attempts exceed the configured threshold.

Destination Failure Rate

Flag destinations whose failure rate crosses an operational limit.

Queue Backlog

Send an alert when pending work stays above a threshold for the configured duration.

Scheduled Summary

Send periodic counts for pending deliveries, failed deliveries, completed work, retained studies, and items needing attention.

Configuration

Configuration Backup And Import

Use Import / Export to save and restore routing configuration. Exports can include destinations, transformations, routing rules, route bindings, and selected Setup settings.

Treat configuration exports as sensitive Configuration files may contain credentials, endpoint details, and operational policy. Store them securely and share them only through approved channels.
  • Export before significant routing or destination changes.
  • Validate imported configuration before sending production studies.
  • Use clear naming and change records so operators understand what changed.

Security

Access Control And Operational Responsibility

DINGO Flow is intended to be operated in a trusted imaging environment with appropriate access controls. Do not expose the control panel, receiving endpoints, or configuration surfaces to untrusted networks.

  • Place DINGO Flow behind organization-approved access controls when users connect remotely.
  • Limit access to operators and administrators who are responsible for routing configuration.
  • Protect credentials, notification tokens, configuration exports, screenshots, and logs.
  • Test routing rules and transformations with known studies before enabling production traffic.
  • Document operational ownership for changes to destinations, rules, transformations, alerts, and retention.