A technologist walks up to the CT or ultrasound console, queries the worklist and gets nothing. Or the exam they need isn’t there. Within minutes, patients are being registered by hand at the modality, and that’s where mismatched names, wrong accession numbers and orphaned studies begin.
The DICOM Modality Worklist (MWL) is one of the quietest parts of the imaging chain until it breaks. This guide walks through how MWL works, where it usually fails, and a practical order for troubleshooting it.
How Modality Worklist works, in plain terms
- An order is placed in the EHR or RIS.
- The order is sent, usually as an HL7 ORM (or OMI/OMG) message, to the system that acts as the worklist provider. That might be the RIS, the PACS, a broker or an interface engine.
- The worklist provider turns the order into a scheduled procedure step with patient demographics, accession number, procedure code and modality.
- The modality sends a DICOM C-FIND query (MWL SCU) to the worklist provider (MWL SCP), usually filtered by modality type, AE title, station and date.
- The provider answers with matching scheduled exams, and the tech selects one.
A problem at any of these five points looks the same at the console: an empty or incomplete list.
Step 1: Is it one modality or all of them?
Start by narrowing the scope.
- One modality affected: focus on that device’s network, DICOM configuration and query filters.
- All modalities affected: look upstream at the worklist provider, the interface engine or the HL7 feed.
- Only certain exam types missing: suspect procedure code mapping or modality-type filtering.
That one question can cut your troubleshooting time in half.
Step 2: Confirm basic connectivity
For a single modality, verify:
- The device can reach the worklist server’s IP address and port.
- A DICOM C-ECHO (verification) from the modality to the MWL SCP succeeds.
- No recent firewall, VLAN, switch or IP address change affected the device.
- DNS is resolving correctly if the modality is configured by hostname.
Network changes made for unrelated projects are a frequent, overlooked cause.
Step 3: Check AE titles and DICOM configuration
DICOM is strict about identity. Confirm that:
- The modality’s calling AE title is configured on the worklist provider exactly as the device sends it (case and spacing matter).
- The called AE title, IP and port on the modality match the worklist server.
- A replacement console, software upgrade or vendor service visit didn’t reset the configuration.
A mismatched AE title often produces a rejected association that the technologist simply sees as “no results.”
Step 4: Review the query filters on the modality
Many “empty worklist” calls come down to a filter.
- Scheduled date: is the modality asking for today only, or a range? Check the device’s date, time and time zone too; a clock that’s off can push exams outside the window.
- Modality type: an order scheduled as “CT” won’t show on a query filtered for “CR.”
- Station AE or station name: if the provider schedules exams to a specific room or station, the modality must query for that value.
Try a broad query (no station filter, wider date range) to see whether exams exist at all.
Step 5: Follow the order upstream
If no modality sees the exam, trace the order itself:
- Was the order actually placed and released in the EHR or RIS?
- Did the HL7 message leave the source system and arrive at the interface engine?
- Did the interface engine route and transform it correctly, or is it sitting in an error queue?
- Did the worklist provider accept it and create a scheduled procedure step?
Check the interface engine logs and queues. A stopped interface, a full queue or a single malformed message can block everything behind it.
Step 6: Check procedure and modality mapping
Exams that consistently fail to appear may have a mapping problem: the procedure code from the EHR doesn’t map to a modality type or department in the worklist provider. New procedure codes added in the EHR without a matching update downstream are a common culprit.
Step 7: Look at worklist housekeeping
On the server side, review:
- Purge rules that remove scheduled steps too early.
- Exams already marked complete or in progress (some systems hide them).
- Duplicate or merged patient records that changed what the modality sees.
- Database or service health on the worklist provider.
Don’t forget the downstream risk
When MWL fails and technologists enter demographics manually, the result is often studies that don’t match the order: misspelled names, missing accession numbers, wrong patient IDs. Those studies may land in PACS unverified or fail to reconcile with the report. After the worklist is fixed, review the exams acquired during the outage and reconcile them so nothing is lost or attached to the wrong patient.
Prevention: keep MWL boring
- Monitor HL7 interfaces and queues with alerts, not just after complaints.
- Document every modality’s AE title, IP, port and filters in one place.
- Re-test worklist and storage after every modality upgrade or service visit.
- Include MWL testing in change-control for network and interface changes.
- Train technologists on what to do, and whom to call, when the list is empty.
Real-world troubleshooting
Workflow problems in PACS rarely announce their root cause. As one client put it:
“As a clinical administrator in PACS workflow, I collaborated with SHIS services to resolve challenging technical issues, including a recurring dictation module crash. Cesar effectively identified and addressed the root cause issue.” — Cheryl in Michigan (Sacred Heart Imaging Solutions, Our Story)
If your MWL problems trace back to the network itself, such as switches, firewalls or workstation issues at a medical practice, our partner A. Computer Doctor provides IT and network support for medical offices.
Frequently asked questions
What is a DICOM Modality Worklist? It’s a DICOM service that lets imaging devices query a scheduling system for upcoming exams, so patient and order details are loaded automatically instead of typed in by hand.
Why is my modality worklist empty? The most common causes are network or AE title problems, query filters (date, modality or station) that don’t match how exams are scheduled, and orders that never made it from the EHR or RIS through the interface engine.
What’s the difference between MWL and MPPS? MWL tells the modality what’s scheduled. Modality Performed Procedure Step (MPPS) reports back what was actually done, such as when an exam started and finished.
Can a time zone or clock issue break the worklist? Yes. If the modality’s date or time is off, its date-filtered query may miss today’s exams.
Who should own MWL troubleshooting? It usually spans PACS administrators, interface analysts, the RIS or EHR team and the modality vendor. Having one person coordinate across them speeds up the fix.
Get expert help with your worklist and PACS workflow
Sacred Heart Imaging Solutions brings 20+ years of healthcare IT experience to PACS and CPACS support, integration with EHR and RIS systems, and workflow optimization. If your worklist, interfaces or imaging workflow keep causing delays, contact us to talk through your environment.