Route a second site's studies over the WAN at night

Goal: a clinic connected by a slow WAN link keeps its own studies flowing locally all day, and sends them to the main hospital’s PACS without saturating the link during office hours. Urgent studies still go at once.

Steps

1. A node at the clinic: install a node there, enrolled with the same central service as the main site’s nodes. The clinic’s modalities send to it; their source matches them by the clinic’s network.
2. The main PACS as a destination, with a schedule:
   • Standing limit: none (full speed outside the windows);
   • window: Mon–Fri 07:00–19:00, Limit 5 Mbit/s (or Pause);
   • Send high-priority instances even while paused: on.
3. Urgent studies: a source for the clinic’s emergency room modality (or a header condition, say RequestedProcedurePriority Equals STAT) with a route of Queue priority High above the general clinic route.
4. A local copy (optional): a local destination, such as a clinic workstation or mini-PACS, on the same route, so local reading never waits for the WAN.

How it behaves

The schedule applies on each node by its local time, so the clinic’s node follows the clinic’s clock. Studies wait on the clinic node’s disk during the day and drain in the evening; Nodes shows the queue and its oldest instance, and a paused destination does not raise the oldest instance alert.

Size the clinic node’s disk for a day’s studies plus the time the link may be down: see Plan and size.