The DICOM server is the part of AuraPACS your modalities talk to. It listens on an AE title and port, accepts studies as they are sent, files them, and answers worklist queries from the scanners. This page explains what it does and what the centre's IT configures, in plain terms.
A DICOM server is a program that waits on the network for imaging machines to send it studies. Each CT, MR, X-ray or ultrasound is configured with the server's address, port and Application Entity title, and at the end of a scan it transmits the images using the DICOM protocol. The server accepts them, checks the patient and study identifiers inside the files, and stores them.
In AuraPACS the DICOM server runs on the on-premise node. The same node also provides the modality worklist service, which the scanners query to get the day's scheduled patients, and serves the stored studies to the browser viewer. There is no separate product to buy or a second server to run.
The protocol is old and dependable. What fails is a wrong port, a mistyped AE title or a firewall nobody mentioned.
The scanner is told to send to one AE title and the server is listening under another. The send fails with no useful message on the console.
The node's DICOM port is closed by a Windows firewall rule or a router, so the association never opens.
The node gets a new address from DHCP and every modality is now sending into nothing.
The scanner can send studies but was never set up to query the worklist, so patient details are still retyped.
The modality's DICOM settings are behind a service menu the centre has never opened.
Six months later nobody remembers which AE title the ultrasound uses.
Run the AuraPACS installer on a Windows machine on the centre's network.
Give the node a static IP so modalities always find it.
The node listens under one AE title on one port; write both down.
Allow inbound connections on that port from the modalities' addresses.
In the scanner's DICOM settings add the node as a storage destination: IP, port, AE title.
Point the scanner's worklist query at the same node, then test with one scheduled patient.
A verification and a test send from each machine confirm the study lands and opens in the browser.
Workflow: Both are given the node's IP, port and AE title as a storage destination; a test send from each arrives and opens in the browser.
Result: Two modalities live in an afternoon, guided over WhatsApp.
Workflow: The machine cannot send DICOM; the centre plans a replacement or an export route and the rest of the modalities go live.
Result: An honest answer rather than a broken promise.
Workflow: The CT's worklist query is pointed at the node; front desk schedules a patient and it appears on the console.
Result: Patient names stop being retyped.
Workflow: Sends fail; the static address is restored and the modalities reconnect.
Result: A five-minute fix once the cause is known.
One capable person who can install Windows software and set a static IP.
Comfortable following steps over a screen share.
Who add the storage destination and worklist on the scanner side.
Everything on this page is done remotely with guidance.
Where the node install and modality connection can be done in person.
The Application Entity title is the name a DICOM device uses on the network. The node has one, each modality has one, and they must match what is configured on each side for a send or a worklist query to succeed. See What is DICOM.
The node listens on a single configurable port for DICOM connections. The exact value is set at installation and given to you to enter on each modality, along with the node's IP and AE title.
Yes, with remote guidance from Elevate Aura over WhatsApp and screen share. The scanner-side settings may need the modality's service engineer if they sit behind a service menu. In Chennai the setup can be done in person.
Yes. The modality worklist service is part of the AuraPACS node, so the scanner sends studies to and queries scheduled patients from the same address. See DICOM worklist software.
Very old units sometimes cannot send over the network. That is confirmed on a call before setup, so you know which modalities will connect and which need a workaround or replacement.
No. Receiving, the worklist and local viewing run on the centre's network. The internet is used for the encrypted offsite copy, remote reading and WhatsApp links.
Tell us how you work today. We will show you what the platform would look like for you, and give you a clear scope and timeline.
Founder-led · Chennai, India · Built and supported by the person who wrote it