Configure a DICOM SCU application (e.g., dcmtk findscu) with the MWL SOP class UID 1.2.840.10008.5.1.4.31 and target the Worklist SCP's host, port, and Called AE title
Build a C-FIND request dataset with matching keys: ScheduledProcedureStepSequence containing ScheduledStationAETitle, ScheduledProcedureStepStartDate, and Modality, plus PatientID as a return key
Send the C-FIND association and iterate over C-FIND responses; each response corresponds to one Scheduled Procedure Step
Extract PatientName, PatientID, AccessionNumber, RequestedProcedureDescription, and ScheduledProtocolCodeSequence from each response dataset to pre-populate the modality
On the modality, write the returned data (especially PatientID and AccessionNumber) back to acquired image headers so downstream PACS can reconcile images with the order
Known gotchas
The SCP returns one C-FIND response per matching Scheduled Procedure Step, not one per study; a single patient order can produce multiple responses if it contains several scheduled steps (e.g., multiple series protocols)
Using an empty (universal match) date range can return the entire worklist from a large SCP and overwhelm the SCU — always scope queries to a specific date range or ScheduledStationAETitle
MWL SOP Class (1.2.840.10008.5.1.4.31) uses the Worklist Information Model, not the Study Root or Patient Root models used for C-FIND against PACS; ensure the correct SOP class UID is negotiated in the Presentation Context
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