In the dcm4chee-arc-light device configuration, enable the HL7 Application under the device's HL7 DeviceExtension and bind it to an MLLP listener port (default 2575)
Define an HL7 Order Scheduling rule that maps ORM^O01 message fields to DICOM Modality Worklist attributes: map PID-3 to PatientID, OBR-4 to ScheduledProcedureStepDescription, OBR-7 to ScheduledProcedureStepStartDateTime, and OBR-24 to Modality
Configure the rule to match on ORM^O01 order control code NW (new order) and to create a new Scheduled Procedure Step in the MWL when the message is received
Test by sending a sample ORM^O01 message via MLLP to the configured port using a tool such as hl7sender and then query the MWL via C-FIND with the expected PatientID to confirm the worklist entry was created
Handle order cancellation by configuring a rule for ORM^O01 with order control code CA to mark the corresponding MWL entry as cancelled or delete it
Known gotchas
HL7 v2 segment field separators and encoding characters in MSH-1 and MSH-2 must match the dcm4chee-arc HL7 configuration; mismatched delimiters cause silent parse failures where fields are mapped to wrong attributes
The dcm4chee-arc HL7 Order Scheduling rules use XSL transformations to map HL7 messages to DICOM attributes; customizing the mapping requires editing the XSLT stylesheets deployed in the WildFly application, not just the device JSON configuration
ORM^O01 messages may arrive before or after a corresponding ADT^A08 patient update; build the MWL creation rule to be idempotent so that duplicate ORM messages for the same order do not create duplicate worklist entries
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp