| Account | One wawa customer: a clinic or a clinic group. Integrations, API clients and webhook endpoints belong to one account. |
| Clinic | A physical location within an account. Many integrations can be assigned per clinic. |
| Server | One configured connection from wawa to an external system, for example a DICOM server, an EmbryoScope instrument or an RI Witness web service. Some screens call it a station. An account can have several; one can be the default. |
| Test Connection | The action on a server that checks wawa can reach the system and sign in. It must pass before go-live. |
| Managed integration | A connection to a clinical or business system that wawa configures and operates with you, as opposed to your own code calling the API. |
| Integration target | A system in your clinic that wawa connects to, identified by a private IP and port or a public URL. |
| Private integration | A managed integration that reaches its targets over a Site-to-Site VPN. |
| Egress IPs | The fixed addresses wawa connects to your public targets from. See Egress IPs. |
| wawa patient ID | The patient's identity-management ID in wawa. Integrations use it to match records in other systems. |
| DICOMweb | The HTTP-based DICOM standard (QIDO-RS to query, WADO-RS to retrieve) wawa uses to read imaging. |
| Structured Report (SR) | The DICOM object ultrasound machines use to carry measurements. wawa imports measurements from SR. |
| AE Title | The DICOM name of a device. Scanners query worklists for their AE Title. |
| Worklist group | A scan room or group in wawa whose AE Title worklist entries are addressed to. |
| Canonical Data Model (CDM) | wawa's stable, versioned representation of clinical and operational records, used by the API and webhooks. |
| API client | A machine credential created under Settings → Connect for the REST API. |