Congratulations! You've managed to setup your PACS. However, after a day or two, you realize that the ride is not as smooth as you had imagined. For instance, the modality successfully sends a study belonging to "Ndaziona Munthune" to storage archive but the doctor can't retrieve it on the viewing station. The study can't be traced on the archive.
Before we tackle the above problem, here's a quick reminder: PACS is just one of the many systems found in a hospital. In an ideal paperless hospital environment, you'd have an EHR/EMR, LIMS, HRMS, RIS (sometimes embedded in EHR), PACS, etc. Together, these systems form an integrated Hospital Information System (HIS). The EHR is usually the entry-point and is responsible for assigning unique patient IDs. All the other patient systems get the IDs from this system. In a hybrid hospital environment, however, it is not uncommon for patients to be assigned IDs randomly. In certain instances, patients get IDs which were previously assigned to other patients.
Back to our scenario where the doctor can't find patient named "Ndaziona Munthune" in the system despite the radiographer testifying that the transfer was successful, it is possible that the patient was assigned someone else's ID. If the storage archive already has another patient with that ID, then Ndaziona's images will be filed under the previous patient. The DICOM standard prioritizes patient ID than names. Try to edit the patient on the modality then resend the study to archive.
Second scenario. There was prolonged power outage and modalities can't send images to the archive after power recovery. Check if the storage server is powered on. If not, check UPS (battery backup). Some UPS units do not recover properly after prolonged power loss. REMEDY: Press and hold UPS power button for at least 10 seconds until it shuts down completely. Power on the UPS again by momentarily pressing the power button. The server should turn on automatically (storage servers are configured to automatically power on after power loss). Check network activity on network switches (blinking green or amber lights). Check at the back of modality console computer, is there network activity where the cable is attached? Try to restart all the workstations in radiology (modality consoles, storage server). These issues may also occur in the absence of power loss. Nothing seems to work? This is where the ICT/Networking/PACS_Admin guy comes in.
Unsuccessful ping, host unreachable
Do you remember the fixed/static IP we talked about on Application Entities? This is where it comes in handy. Normally you'd have a diary with a list of all computers/modalities (AEs) on the network with their respective AETs, static IP addresses, Port Numbers, and location.
Ping sucsessful
A network ping test transmits packets of data to a specific IP address and either confirms or denies presence of connectivity between IP-networked devices. Say you want to check workstation A's availability, whose IP is 172.30.2.35. You'd do this by opening CMD (on windows computer) or Terminal (on mac/linux computer) then type "ping 172.30.2.35" and hit return (press enter key). The 1st image shows a failed ping. The second image shows a successful ping for a different IP (just an example).
BEWARE: Most modality consoles do not accept ping requests, for security purposes. They have firewall rules to block incoming network traffic unless requested by the modality itself. In this case, try to initiate the ping test from the modality to storage server or to another workstation on the network.
NB: Sometimes computers may lose their static IP after power loss or some "wise" colleagues may change the network settings from static IP to DHCP ("Obtain IP automatically) for reasons best known to themselves. In this case, make sure you replace with the exact IP you recorded in your diary of PACS computers. Do not do guesswork, you'll cause IP address conflicts. USB-to-Ethernet adapters are more susceptible to this problem (I wouldn't recommend them in a PACS environment).