DICOM / DICOMweb
- Status
- Available
- Region
- Global
- Data flow
- Studies: your PACS → wawa. Worklists (Orthanc): wawa → your PACS
- Connectivity
- DICOMweb over HTTPS; Site-to-Site VPN or customer-managed public URL
- Set up by
- Clinic account administrator, values from your IT team
wawa does not run a DICOM server. It connects to yours over DICOMweb to:
- Import ultrasound studies. Follicle-tracking and pregnancy scan measurements, from DICOM Structured Reports (SR), and images appear on the patient record without re-keying.
- Push worklists (optional, Orthanc). Scheduled appointments become DICOM Modality Worklist entries, so scanners pull the day's patients instead of operators typing details in.
We recommend Orthanc as the server; any PACS with a standards-compliant DICOMweb interface works for study import.
- Clinic setup guide: settings in wawa, scanner setup (GE Voluson P8 worked example), go-live test and troubleshooting, in plain language.
- Scanner quick reference: a printable everyday card for sonographers.
Requirements
- DICOMweb (QIDO-RS and WADO-RS) served over HTTPS, with a public CA certificate, or an internal or self-signed
certificate added in wawa (see TLS certificates). Orthanc serves it under
/dicom-web/; other servers may use a different path. - Standard DICOM tags for SR reports and measurements. If your devices use custom tags, send documentation or sample data.
- Structured Reports. Image-only studies are imported without measurements; scanners must export SR.
- A secure service account for wawa (HTTP Basic):
- Unique: used only by wawa, never by people or other systems. Don't share admin credentials.
- Least privilege: read-only access to the DICOMweb endpoints and nothing administrative. Write access is
needed only on
/worklistsif you use worklists. - Strong: a randomly generated password of at least 20 characters, not a memorable word.
- Rotated at least annually, and immediately if you suspect compromise.
- A network path: a Site-to-Site VPN, or a customer-managed public URL restricted to wawa's egress IPs.
- Patient IDs on the scanners must carry the wawa patient identifier (a fixed suffix per site is supported).
- For worklists: the Orthanc REST Worklists plugin, and each scanner's AE Title and static IP.
What we need from you
Everything below is entered in wawa when the server is set up. Your IT team supplies the values; a clinic account administrator (or wawa, on your behalf) enters them.
Per DICOM server
| Input | What to give us | Example |
|---|---|---|
| Name | A label for the server, usually the site name | Main clinic PACS |
| URL | The root of the server over HTTPS, without the DICOMweb path. Worklists and Orthanc's change feed are served from the root. | https://dicom.clinic.example |
| Hostname the server answers to | Optional. Only if your server answers to a hostname that is not the one in the URL: on shared hosting that routes by name, or reached by its private IP over a VPN with a certificate issued for a name. wawa connects to the URL's address but sends this name for TLS (SNI) and the HTTP Host header. A hostname or IPv4 address on its own, without https://, a port or a path; use an IP address when the certificate lists only IP addresses. | pacs.example.azurecontainerapps.io |
| Username and password | The service account wawa uses (HTTP Basic) | |
| DICOM time zone | The time zone of the server and its scanners. Used to read study times and to write worklist dates and times. Defaults to UTC. | Europe/London |
| Strip from Patient ID | Optional. Text your scanners append to the wawa patient ID, which wawa removes before matching (every occurrence) | -SITE2 |
| DICOMweb path | Where DICOMweb is served, relative to the root. Leave the default for Orthanc; blank if DICOMweb is at the root. | dicom-web |
| Studies, series, instances, metadata and image paths | QIDO-RS and WADO-RS paths relative to the DICOMweb path. Pre-filled with the standard values; change them only for a non-standard PACS. No leading /. | studies/%{study_uid}/series |
| Orthanc server | Tick if the server is Orthanc. Required for automatic synchronisation and worklists. | |
| Automatic synchronisation | Orthanc only. wawa follows the server's change feed every 5 minutes. This setting applies to the whole account. | |
| CA root | Optional. Only if the server's certificate is not from a public CA: your internal root CA, or the server's certificate itself if it is self-signed. Your account admin adds it in wawa and selects it on the Certificates tab (see TLS certificates). wawa trusts it alongside the public CAs, for every DICOM server on the account. | |
| Default DICOM server | The server used for clinics without their own assignment |
Per clinic (if you have several sites)
- Which DICOM server serves each clinic, or "Use default".
For worklists (Orthanc only)
| Input | What to give us |
|---|---|
| Group name | A label for the scan room or group, for example Scan room 1 |
| Worklist AE title | The AE Title that room's scanner queries its worklist for, usually the scanner's own AE Title. Up to 16 printable ASCII characters, no backslash, not *, unique within the clinic. |
| Clinic | The clinic the group belongs to |
| Appointment types | Optional. Appointments of these types at the clinic go to this group with Send to Scanner Worklist ticked, even if they are not ultrasounds, for example egg collections and embryo transfers for a theatre scanner. Each type can go to one group per clinic. |
| Default for the clinic | The group used when an appointment doesn't pick one and its type is not listed on another group. The first group of a clinic becomes its default. |
Also tell us which appointment types are ultrasound scans: their appointments are sent to the worklist automatically. Staff can send any other appointment by ticking Send to Scanner Worklist on it.
Before go-live
- The validation checks pass against your server.
- Your scanners' patient IDs carry the wawa patient ID (after the optional strip).
Before the on-site test
wawa can check its own connection to your server remotely, but not the connection from your scanners to the server, which runs inside your network. That second connection is the one that most often stops a site going live, so have these ready:
- Every scanner has a static IP or DHCP reservation. Plain DHCP is not enough: when an address changes, the server stops recognising the scanner and its worklist is empty.
- Every scanner can reach the server's local IP on TCP
4242. Scanners start the connection, so the rule is needed in one direction only. Never open4242to the internet. - Each scanner uses the server as both its store destination and its worklist server, is registered on the server, and has its own unique AE Title.
- The worklist AE Title above and each scanner's own AE Title are different settings. Scanners that share one worklist
keep their own unique AE Titles and all search the worklist for the shared group's title. The server's own AE Title is
ORTHANCunless your IT team changed it, so confirm it. - Each scanner sends Structured Reports. Without them, no measurements arrive.
- Someone who can change the scanner's network and DICOM settings (often the vendor's engineer) is available on the day.
Send us one row per scanner: room, make and model, AE Title, fixed IP, and which worklist group it should see. With all of this in place, testing takes roughly half a day per site, using test patients only.
Setting it up
- Go to Settings → Integrations → DICOM and click Enable DICOM Integration.
- On DICOM Servers, add each server with the inputs above.
- On Clinic Assignments, choose the server for each clinic.
- Once a server is marked as Orthanc, add groups on Worklist Groups.
- Run Test Connection on each server.
How it works
Test Connection
Each server has Test Connection, which reports how many studies it found.
| Result | Meaning |
|---|---|
| Studies found | Connected |
| "Plain study IDs instead of DICOM+JSON" | The DICOMweb path is wrong, so wawa is not calling the DICOMweb API |
| Warning about Structured Reports | Studies without SR data are imported with their images only and show Measurements pending |
How worklists behave
- When an ultrasound appointment is booked, wawa sends a worklist entry addressed to the AE Title of the appointment's worklist group. An appointment without one goes to the group that lists its type at that clinic, otherwise the clinic's default group. The booking panel shows Send to Scanner Worklist ticked and the group, preselected with the group that lists the appointment type, otherwise the clinic's default group or its only group.
- A worklist group can list Appointment types. Booking one of those types at the group's clinic ticks Send to Scanner Worklist and selects that group, even for a type that is not an ultrasound. Staff can still change both. Each type can go to one group per clinic. Adding a type also sends its upcoming appointments at that clinic to the group if they are not on a worklist yet; appointments already on a worklist keep their group.
- Any other appointment can be sent too: tick Send to Scanner Worklist when booking it, or choose it from the appointment's More menu during the visit, then pick the group. Unticking it, or Remove From Scanner Worklist, removes the entry.
- The entry goes to the server assigned to the appointment's clinic on Clinic Assignments (or the default server), even if the patient is also registered at another clinic.
- If the clinic has no worklist group, no entry is sent, so set a default group for every clinic that uses worklists.
- Re-sending an appointment updates its entry; cancelling removes it.
- Changing an appointment type's system category to Ultrasound sends entries for its appointments straight away; changing it away from Ultrasound removes them, except for appointments ticked Send to Scanner Worklist. The three-day window below still applies.
- Only appointments starting no more than three days ago, or later, are sent.
- Editing a group does not re-send entries already on the server.
- A generic (non-Orthanc) PACS supports study import only: no worklists and no automatic synchronisation.
Synchronisation
- Studies can be fetched on demand from the patient record for any DICOMweb server.
- With Orthanc, wawa also syncs changes automatically every few minutes from Orthanc's change feed. It starts from the moment it is switched on and does not import the server's existing history.
- A study without an SR that wawa recognises is imported with its images only and shows Measurements pending until a recognised SR arrives.
- wawa never deletes studies from your server.
Debug tab
When a scan has not appeared in wawa, administrators can open the Debug tab in the DICOM settings (shown for Orthanc servers only). Choose the server, the study date and, optionally, an institution name, then click Run Debug Check. wawa reads that day's studies from Orthanc, compares them with what it has imported and shows, for each study, what is on the server, what is in wawa and the likely reason it is incomplete:
| Result | What to do |
|---|---|
| Complete | Nothing: the measurements and images are both in wawa |
| Measurements only | On the scanner, press P1 or send the images |
| Images only | On the scanner, choose Measurements, then Transfer Data |
| Not yet synced | Wait for the next synchronisation, or click Fetch Scanner Reports on the patient record |
| Images not in wawa | The report is in wawa but the images are still being imported |
| Patient not matched | Check the patient ID that was entered on the scanner |
The check only reads from your server and never changes it. It covers up to 100 studies per run and says when it has been cut short; enter an institution name to narrow it.
Everyday use
At the end of every scan the sonographer sends two things from the scanner, and both are needed:
| Send | If it is skipped |
|---|---|
| The images | The scan appears with measurements but no images |
| The measurements (Structured Report) | The scan appears with its images and a Measurements pending badge, but no measurements |
The button for each differs by scanner. On a GE Voluson, the programmable P1 key sends the images and Measurements → Transfer Data sends the measurements; P1 must be mapped to the server's STORE destination under System Setup → Connectivity → Button Configuration. The patient must be chosen from the worklist, so the scan carries the wawa patient ID. Scans appear on the patient record under Records → Ultrasound: automatically within a few minutes with Orthanc synchronisation, or straight away by clicking Fetch Scanner Reports. Measurements are imported for follicle-tracking and early-pregnancy scans only. Any other scan appears with its images and stays Measurements pending.
Measurements arrive but images do not
Wawa downloads a scan's images in the background, so allow up to an hour before treating them as missing. If they still do not appear, the cause is almost always on the scanner. The Debug tab shows which scans are affected:
| Pattern | Likely cause | What to do |
|---|---|---|
| No scan from that scanner ever has images | The send-images key (P1 on a Voluson) is not mapped to the server, or the STORE service is missing or inactive | Fix the scanner's configuration, then run a test scan: send images, then send measurements |
| Some scans have images, some do not | The send-images step is being skipped | Show sonographers that both sends are needed at the end of every scan |
A scanner that is misconfigured fails every time; one that works on some scans is being used inconsistently. Use the scanner's Verify button, not Ping: Ping is often blocked on clinic networks, so a failed Ping does not mean the service is broken. A scanner moved over from another system often still has P1 pointing at the old destination; see Point the image key at the imaging server. If a correctly configured scanner still shows scans without images, contact support.
The clinic's IT team owns the imaging server: availability, security, patching and backups. wawa supports the integration, not the server itself.