PACOM VigilCore (REST)
PACOM Systems·AE_HSc_PACOMVIGILCORE_RestConnectorGuide
Overview
The PACOM VigilCore connector integrates AlertEnterprise Guardian with PACOM VigilCore — PACOM Systems' modern cloud-native PACS platform, succeeding the legacy GMS line. VigilCore is positioned for enterprises wanting a REST-native PACS without the Windows / .NET intermediary required by pacom-gms.
The architecture is direct: AE → PACOM VigilCore Connector → VigilCore RESTful API → VigilCore System. The connector uses AE's generic REST connector framework with per-operation endpoint URLs configured as System Parameters. Authentication is OAuth 2.0 password grant — the connector posts the configured username + password to the Token URL (e.g., https://demo.vigilcore.dev/api/login/v1) and receives a bearer token used on subsequent calls.
The connector is actively developed — the guide carries 5 revision-history entries through 2026-03-05, indicating PACOM and AE are iterating on field mappings and parameter sets. Customers on VigilCore 8.4+ should plan to track these revisions during initial deployment.
Architecture
Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.
Authentication
1 method supported
The VigilCore REST API authenticates via OAuth 2.0. The connector posts username + password + grant_type system parameters to the configured Token URL (example: https://demo.vigilcore.dev/api/login/v1) and receives an access token. The token is sent on subsequent REST calls.
Endpoints
10 endpoints exercised by the connector
| Method | Path | Description | Category |
|---|---|---|---|
| POST | {tokenURL} | OAuth 2.0 token endpoint (example demo URL https://demo.vigilcore.dev/api/login/v1). | auth |
| POST | {CREATE_USER0 endpoint} | Create User Account with badge. | provisioning |
| GET | {SEARCH_USER0 endpoint} | Search / lookup users. | query |
| PUT | {UPDATE_USER0 endpoint} | Update User information. | provisioning |
| DELETE | {DELETE_USER0 endpoint} | Delete User account. | deprovisioning |
| POST | {ASSIGN_BADGE0 endpoint} | Assign Credential to a user. | provisioning |
| GET | {SEARCH_BADGE0 endpoint} | Search / lookup badges. | query |
| POST | {ACTIVATE_BADGE0 endpoint} | Activate Credential. | lifecycle |
| POST | {DEACTIVATE_BADGE0 endpoint} | De-activate Credential. | lifecycle |
| DELETE | {REMOVE_BADGE0 endpoint} | Remove Credential from user. | deprovisioning |
Prerequisites
Everything that must be in place for this connector to work, with the owner who's responsible.
PACOM VigilCore 8.4+ with REST API enabled
customerAn operational PACOM VigilCore deployment (8.4 or later) with the REST API reachable from the AE application server. The Instance URL system parameter must point to the API base.
OAuth 2.0 credentials provisioned in VigilCore
customerVigilCore admin must provision a dedicated API user with username + password and provide the OAuth Token URL. Configure these as System Parameters along with grant_type.
Per-operation endpoint URLs configured
aeEach REST operation (CREATE_USER0, UPDATE_USER0, DELETE_USER0, SEARCH_USER0, ASSIGN_BADGE0, SEARCH_BADGE0, ACTIVATE_BADGE0, DEACTIVATE_BADGE0, REMOVE_BADGE0) must be configured as a System Parameter pointing to the appropriate VigilCore endpoint URL. The connector also needs userIdentifierKey and per-operation identifier-key variants (SEARCH_USER_userIdentifierKey, ASSIGN_BADGE_userIdentifierKey, etc.).
Track guide revisions during deployment
aeThe VigilCore connector guide has been revised 5+ times between January 2025 and March 2026, with active field-mapping and parameter changes. Verify the deployment matches the latest revision and re-validate after VigilCore version upgrades.
Known limitations
Documented constraints to set customer expectations before deployment.
Active iteration — field mappings change between revisions
informationalBecause the connector guide has been revised 5+ times in 14 months with field-mapping and parameter updates, customers locked to a frozen revision risk drift from VigilCore's current API surface. Recommend revalidating against the latest connector guide before each VigilCore version upgrade.
PACS specifics
VigilCore exposes Users with associated Credentials (badges) via REST resources. Credential lifecycle (assign / activate / deactivate / remove) is modeled as discrete API operations rather than status-field toggles.
Roles / access levels in VigilCore are managed through the REST API; specific access-group semantics (GAG / FAG analogs from GMS) are not exhaustively documented in the connector guide and require verification against the customer's VigilCore admin configuration.
VigilCore tenants are isolated at the API layer. One AE→VigilCore connector per tenant.
- Topology
- cloud
- Event model
- polling
- Anti-passback
- unknown
- Holiday schedules
- unknown
- src/connectors/pacom-vigilcore-rest/source.pdf — Full connector guide — 35 pages, revision 5.0 dated 2026-03-05
- src/connectors/pacom-vigilcore-rest/source.pdf — p6 — Supported Version
- src/connectors/pacom-vigilcore-rest/source.pdf — p7 — Connector Architecture