Search
K
< Back

Implementation Overview

ADT Notifications are enabled through a phased implementation process that establishes delivery readiness, enables patient enrollment, and activates message routing. Several prerequisites must be completed before HL7 v2 ADT messages can be delivered to your system.

Implementation focuses on three core dimensions:

  • Delivery readiness: How ADT messages are transported and where they are delivered.
  • Patient enrollment: Which patients are eligible to generate notifications.
  • Activation and validation: Confirming that messages flow end to end as expected.

ADT Notifications are event driven. Messages are generated only when encounters occur after enrollment is active and delivery is enabled. Historical encounters and retroactive notifications are not supported.

High-Level Implementation Flow

ADT implementation follows a predictable sequence that establishes readiness before live delivery begins.

  • Planning and scoping: Confirm delivery method, consumption model, and enrollment approach.
  • Secure access and endpoint setup: Establish connectivity and delivery endpoints.
  • Patient enrollment: Submit rosters that define notification eligibility.
  • Licensing and activation: Enable ADT functionality for your tenant.
  • Routing and validation: Verify message delivery before production go-live.

Some stages can proceed in parallel, but all prerequisites must be satisfied before ADT messages are delivered in production.

What to Expect During Implementation

During onboarding, Health Gorilla works with your organization to:

  • Confirm implementation decisions that affect scope and sequencing.
  • Validate delivery endpoints and security requirements.
  • Ensure enrollment workflows are understood and operating correctly.
  • Confirm that routing and delivery behave as expected before go-live.

Once ADT Notifications are live, ongoing behavior depends on upstream feed activity, enrollment timing, and routing configuration. Differences in event volume or timing do not necessarily indicate delivery failures and should be interpreted within these constraints.