Skip to content

Destination groups

A group combines several destinations, and a route can send to a group as to any destination. Configuration › Destinations › Add destination, kind Group.

Everything goes to the first reachable member, in the order listed: a primary PACS, then its standby. When the primary is back, traffic returns to it.

Studies are spread over the reachable members, and all instances of a study go to the same member, so each member holds whole studies. Use it for several AI servers, or archive nodes that share the work.

  • A member that cannot be reached for the group’s failover delay (default 60 s) is skipped.
  • Instances already queued for it through the group move to another member, keeping their priority.
  • Idle unreachable members are checked with C-ECHO every 30 s, so traffic returns once they recover.
  • Idle members that are reachable are checked too, every 5 minutes by default (see idle checks): one that went down overnight is skipped from the first study of the morning.
  • The history records instances moved this way as Rerouted.

Members are ordinary destinations with their own settings (transfer syntaxes, tag edits, schedules). A member can be used on its own by other routes too.