When Your CT Worklist Hangs Mid-Afternoon—A 7-Step Checklist for Modality Techs

It's 2:30 PM. Your CT worklist is frozen—no new orders appearing, no status updates, and the patient in the waiting room is getting restless. You've rebooted the console once already, and the list is still stuck. Before you escalate to IT or call the PACS admin, there are seven concrete checks you can run yourself. Most hangs have a common root cause, and you can fix it in under 10 minutes without losing the afternoon's schedule.

This checklist is written for modality techs who work across GE, Siemens, Canon, and Philips scanners—the steps are vendor-agnostic, but we'll call out vendor-specific quirks where they matter. We assume you have basic access to the scanner console, the local RIS workstation, and a phone to call the PACS team if needed. Let's start with why this happens and who needs this guide.

1. Why Worklists Hang—And Why You Need This Checklist Before It Happens

A CT worklist hang isn't random. In almost every case, the root cause falls into one of four categories: a network timeout between the scanner and the RIS, a PACS archive that's rejecting images (blocking the next order), a queue conflict inside the scanner software, or a data mismatch in the order itself. According to field reports from imaging IT teams, roughly 60% of mid-afternoon hangs are caused by the PACS rejecting a single study—often due to a duplicate accession number or a mismatched patient ID—which then blocks the entire worklist update cycle.

Without a structured approach, techs tend to react in one of two ways: reboot everything (which loses time and sometimes the cached worklist) or call IT immediately (which creates a ticket that may take 30 minutes to answer). Both responses are inefficient. A 7-step checklist lets you resolve the hang yourself, or at least give the IT team a precise diagnosis when you do call.

Who needs this guide? Any CT modality tech working in a hospital or imaging center with a 5+ scanner fleet, a shared RIS, and a PACS that's older than three years. Also techs at new sites where the integration between scanner and RIS was never fully validated. If you've ever felt the stomach-drop when the worklist stops moving, this checklist is for you.

We'll walk through the steps in order—from the quickest check to the most involved—so you can start fixing the problem immediately.

What a hang looks like vs. a slow network

A true hang means the worklist column is frozen—no new rows appear, no status icons change, and clicking "refresh" does nothing. A slow network, by contrast, eventually updates after 30–60 seconds. If you see partial updates or intermittent timeouts, that's likely a bandwidth issue, not a hang. The checklist below assumes you've already confirmed it's a full freeze.

2. Prerequisites: What to Check Before You Start the 7-Step List

Before you begin the steps, make sure your environment is stable enough to run a diagnostic. You'll need:

• Access to the scanner console with admin-level login (or at least a service account that can view system logs)
• A phone or chat line to the PACS/RIS help desk—have the number ready
• The patient's accession number and MRN from the paper order or the RIS front desk
• A screenshot or photo of the frozen worklist (useful if you do need to escalate)

Also check whether other scanners in the department are experiencing the same issue. If every scanner's worklist is frozen, the problem is likely at the RIS or network level—skip directly to step 6 (network test) and step 7 (call PACS admin). If only one scanner is affected, the issue is local to that scanner's connection or software.

One more thing: verify that the scanner clock and the RIS clock are within 5 minutes of each other. A time drift of more than 15 minutes can cause HL7 messages to be rejected, which silently freezes the worklist. This is more common than most techs realize, especially after daylight saving time changes.

Once you've confirmed these prerequisites, you're ready for the 7-step sequence.

When to skip the checklist and call IT immediately

If the entire department's worklist is down, or if you see a system-wide error message (e.g., "RIS connection lost" on every scanner), don't waste time on local diagnostics. Call IT and tell them: "All CT scanners are unable to retrieve worklist—likely RIS or network outage."

3. The 7-Step Checklist: Step-by-Step Recovery

Perform these steps in order. Each step takes less than 2 minutes. If a step resolves the issue, you can stop—no need to continue.

Step 1: Refresh the worklist manually (not a reboot)

On most scanners, there's a "Refresh" or "Query" button in the worklist view. Click it once. Wait 15 seconds. If nothing changes, click it a second time after 30 seconds. Some scanners (notably Siemens syngo.via) require a double-click on the refresh icon to force a new query. If the list updates, the hang was a transient network hiccup—document it and move on.

Step 2: Check the PACS rejection log

This is the most common cause. Open the PACS worklist viewer on the scanner console (often under "Sent Studies" or "Archive Status"). Look for any study that shows a status of "Rejected" or "Failed" in the past 15 minutes. If you find one, note the rejection reason—usually it's "Duplicate Accession Number" or "Patient ID Mismatch." Call the RIS team to correct the order, then resend the study. Once the rejected study is cleared, the worklist will almost always unfreeze within 60 seconds.

Pro tip: On GE Revolution scanners, the rejection log is under the "Service" tab → "Archive Manager." On Canon Aquilion, it's under "Utility" → "Network Status" → "Failed Studies."

Step 3: Verify the scanner-RIS HL7 connection

Navigate to the scanner's network configuration screen. Look for the "HL7 Connection Status" or "RIS Link" indicator. It should show a green checkmark or "Connected." If it shows red or "Disconnected," the scanner has lost its link to the RIS. Try toggling the connection off and on (not a full reboot). On Philips iCT scanners, this is under "System Settings" → "Interfaces" → "RIS Connection" → "Reconnect." Siemens scanners often have a "Restart HL7 Service" button in the service menu.

If the connection re-establishes but the worklist remains frozen, proceed to step 4.

Step 4: Restart the scanner worklist service (not the OS)

Instead of rebooting the entire console, restart only the worklist service. This is a much faster recovery. On GE scanners, you can stop and restart the "Worklist Manager" service from the Windows Services panel (accessible via the service login). On Siemens scanners, use the "Stop/Start Worklist" option in the service tool. This clears any corrupted cache in the worklist queue without affecting the scanner's calibration or table position.

Wait 30 seconds after restarting. If the worklist appears, the hang was caused by a software thread deadlock. Document this for the PACS team to patch later.

Step 5: Check for a stuck exam in the scanner queue

Sometimes the worklist hang is a side effect of an exam that never finished sending to PACS. Open the "Exam Queue" or "Current Studies" list on the scanner. If you see an exam with a status of "Sending" or "Pending" that hasn't changed in 10+ minutes, that exam is blocking new orders. Cancel the send (usually there's a "Cancel" or "Abort" button) and resend it manually. This often releases the worklist.

Be careful: canceling a send may lose any unsaved images. If the exam is still in progress, wait for it to complete before canceling.

Step 6: Test network connectivity from the scanner

Open a command prompt on the scanner console (if available) and ping the RIS server IP address. If the ping times out, the network path is down. You can also try pinging the PACS server. If both fail, the issue is at the network level—call IT and report that the scanner cannot reach the RIS or PACS subnet. If the ping succeeds, the network is fine, and the hang is likely software-related (steps 1–5 should have caught it).

On scanners that don't expose a command prompt, look for a "Network Test" utility in the service menu. Most vendors include one.

Step 7: Escalate with a precise summary

If none of the above steps resolve the hang, call the PACS/RIS help desk. Give them this information: "Scanner model and software version, time the hang started, what steps you've already taken (refresh, checked rejection log, restarted HL7 connection, restarted worklist service, checked exam queue, pinged RIS), and the accession number of the last successfully received order." This saves the IT team 15 minutes of basic triage and gets you a faster resolution.

While waiting for IT, you can run a manual worklist query via the scanner's DICOM query/retrieve function (if available) to at least see pending orders—though you won't be able to update status until the hang is fixed.

4. Tools and Environment Realities: What You Should Have Ready

To make this checklist work in practice, you need a few things set up in advance. First, save the IP addresses of your RIS and PACS servers somewhere accessible (a laminated card taped to the console, or a note in the tech lounge). Second, ensure the service login credentials are stored in a secure but accessible password manager—don't wait for a hang to hunt for passwords.

Third, configure the scanner to log HL7 messages. Most scanners have a debug logging mode that records every worklist query and response. When a hang happens, these logs are gold for root-cause analysis. Ask your PACS admin to enable HL7 logging on all CT scanners, and teach techs how to export the logs after an incident.

Fourth, keep a screenshot tool on the scanner console. A simple Snipping Tool shortcut can capture the frozen worklist, the PACS rejection log, and the network status screen. These screenshots help IT diagnose faster than verbal descriptions.

Finally, consider a shared department log (paper or digital) where techs record every worklist hang, the steps taken, and the resolution. Over time, patterns emerge—like "every Tuesday at 3 PM" or "after the RIS upgrade." This log is your best tool for prevention.

Vendor-specific notes

On GE scanners, the worklist service is tied to the "AW Server" component. Restarting the AW Server service (not the whole AW) is usually sufficient. On Siemens syngo.via, the worklist is managed by the "Data Manager" service—restarting that service is safer than a full system reboot. Canon Aquilion scanners often require a full console restart for worklist issues, but try toggling the "RIS Link" first. Philips iCT scanners have a dedicated "Worklist Reset" button in the service menu—use it before restarting.

5. Variations for Different Constraints

Not every site has the same setup. Here's how the checklist changes based on your environment.

Single-scanner clinic vs. multi-site hospital

In a single-scanner clinic, you are the only tech, and IT support may be remote or after-hours. Steps 1–5 are your lifeline. If none work, you may need to reboot the scanner (which loses 10–15 minutes) or switch to paper-based workflow until IT can remote in. In a multi-site hospital with shared RIS, step 6 (network test) becomes critical—a campus-wide network issue can affect all scanners, and you'll want to coordinate with other techs.

Legacy RIS vs. modern cloud RIS

If your RIS is an older on-prem system (like McKesson or an ancient GE Centricity), worklist hangs are more frequent and often caused by database locks. Steps 2 and 3 are especially important—checking the PACS rejection log and the HL7 connection. For cloud-based RIS (like Cerner or Epic hosted), hangs are rarer but when they happen, the issue is usually at the cloud service level. In that case, skip to step 7 and report it to the RIS vendor's support.

After-hours or weekend scenario

When IT is off-duty, you may have no choice but to reboot the scanner if steps 1–5 fail. But before you reboot, try one more thing: unplug the network cable from the scanner console for 10 seconds, then plug it back in. This forces a DHCP renewal and can clear a stuck ARP table. It's not a fix, but it buys you time.

Scanner with no service login access

Some sites restrict service-level access to biomed or vendor engineers only. In that case, steps 4 and 6 may be unavailable. Focus on steps 1–3 and 5—they can be done from the user interface. If those fail, you must call IT and hope they can remote in quickly.

6. Pitfalls, Debugging, and What to Check When the Checklist Fails

Even with a solid checklist, things can go wrong. Here are the most common pitfalls and how to handle them.

Pitfall: Restarting the scanner too early

Rebooting the console should be a last resort, not a first response. A reboot loses the cached worklist, any unsent images, and the diagnostic clues (like error messages in the HL7 log). It also takes 5–10 minutes. We've seen techs reboot out of habit, only to have the hang recur immediately because the underlying cause (a rejected study) was never addressed. Always run steps 1–5 before rebooting.

Pitfall: Misreading the PACS rejection log

The rejection reason may be cryptic, like "AE Title Mismatch" or "Storage Commitment Failure." Don't panic. Take a screenshot and send it to IT. In the meantime, try resending the rejected study with a new accession number (if the RIS allows it). If the worklist unfreezes, you've confirmed the root cause.

Pitfall: Forgetting to check other scanners

If you're the only tech on duty and your scanner is hung, it's easy to assume the problem is local. But if you ask a colleague and discover all scanners are down, you've wasted time on local steps. Make the cross-department check a habit—it takes 30 seconds.

Pitfall: Not documenting the hang

After the hang is resolved, it's tempting to move on and catch up on patients. But without documentation, the same hang may happen again tomorrow. Log the date, time, scanner ID, steps taken, and resolution. Share the log with the PACS team weekly. Over time, this data drives preventive maintenance—like updating HL7 interface engines or increasing PACS storage capacity.

What to do when the checklist truly fails

If you've completed all 7 steps and the worklist is still frozen, there are two possibilities: either the issue is at the RIS database level (a corrupted order or a deadlock in the RIS queue) or the scanner's operating system has a deeper problem (like a disk failure). In both cases, IT will need to escalate to the RIS vendor or the scanner manufacturer. Your detailed step log will save them hours.

In the meantime, consider switching to a manual workflow: write down patient orders on paper, scan the patients, store images locally (or on a USB drive if the scanner allows), and reconcile with the RIS later. It's not ideal, but it keeps the patient moving. The key is to not let a worklist hang stop patient care entirely.

This checklist won't prevent every hang, but it will give you a repeatable process to recover quickly. The next time your CT worklist freezes mid-afternoon, you'll know exactly what to do—and you'll be back to scanning in under 10 minutes.

A spare cartridge at the nurses' station beats a heroic mid-shift scramble every time.

— A biomedical equipment technician, clinical engineering

If the log shows a gap, capture the batch ID and operator initials before you rerun the cycle.

— A hospital biomedical supervisor, device maintenance