Nedap AEOS
Nedap Identification Systems·AE_HSc_NedapConnectorGuide
Overview
The Nedap connector integrates AlertEnterprise Guardian with Nedap AEOS — Nedap Identification Systems' enterprise PACS, widely deployed in EMEA enterprises (banking, healthcare, transportation, energy). AEOS is one of the more sophisticated PACS in terms of multi-site federation and policy-based access management.
Architecture: AE → ACF → Alert Nedap Connector → Nedap SOAP API → Nedap Application. The connector uses SOAP over HTTPS — a deliberate choice on Nedap's part to maintain compatibility with their existing integration ecosystem.
Architecture
Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.
Authentication
1 method supported
Basic auth credentials in WSSE-style SOAP headers, sent over HTTPS to the Nedap SOAP API endpoint.
Prerequisites
Everything that must be in place for this connector to work, with the owner who's responsible.
Nedap AEOS with SOAP API enabled
customerAn operational Nedap AEOS deployment (2020.X, 2021.X, 2023.X, or 2024.X) with the SOAP API enabled and reachable from the AE application server.
AEOS API user with provisioning + reconciliation privileges
customerDedicated AEOS API user account.
PACS specifics
AEOS cardholder model with associated tokens (Nedap's term for credentials) and access entitlements.
AEOS uses a policy-based access model — Authorisations grant access through Roles and Areas. Specific mapping conventions are AEOS-deployment specific.
AEOS supports multi-site federation natively. Single connector instance per AEOS deployment.
- Topology
- on-prem
- Event model
- polling
- Anti-passback
- unknown
- Holiday schedules
- unknown
- src/connectors/nedap/source.pdf — Full connector guide, updated 2025-09-08
- src/connectors/nedap/source.pdf — p6 — Supported Version