Purpose
This channel is the demo’s Orthanc-specific inbound adapter. It polls Orthanc’s changes feed, detectsStableStudy, retrieves the study metadata, and emits one normalized event to the generic PACS study events relay.
Source configuration
Use this complete reader script:
Destination
Add a JavaScript source transformer:
Because this call originates inside the OIE container,
127.0.0.1 reaches the other OIE listener directly.
Java 17 compatibility
Do not implement the HTTP request withnew java.net.URL(url).openConnection() in this OIE/JRE combination. Rhino can receive an IllegalAccessException for the internal sun.net.www.protocol.http.HttpURLConnection class. The tested script uses OIE’s bundled Apache Commons HttpClient.
Cursor and replay behavior
The last Orthanc change sequence is stored inglobalChannelMap. Redeploying or recreating the channel can reset this cursor and replay older changes. HMIS idempotency makes identical messages safe, but a production PACS adapter should persist its cursor durably and monitor replay volume.