Delivery Method

ADT messages can be delivered using one of the following methods:

• FHIR subscriptions: Event-driven delivery to an endpoint defined by your organization.
• Secure File Transfer Protocol (SFTP): File-based delivery to a designated drop location.
• Health Gorilla UI: Operational visibility for confirmation and review, not primary delivery.

The selected delivery method affects endpoint configuration, security requirements, and validation steps but does not change which ADT events are generated.

Notification Consumption Model

Confirm how ADT notifications will be consumed after delivery:

• Client-owned application: Your system receives and processes ADT messages directly.
• Third-party system: ADT messages are delivered to an external platform, such as an EHR or care-management system.
• Health Gorilla UI: Used for secondary visibility or confirmation, not as a primary processing system.

If notifications are delivered to a third-party system, coordination with that system’s technical team may be required.

Delivery Destinations

Determine how many delivery destinations are required:

• Single destination: All eligible ADT messages are delivered to one endpoint.
• Multiple destinations: Messages are routed to different endpoints based on tenant or subtenant configuration.

Delivery destinations are defined during configuration and apply consistently once routing is active.

Patient Enrollment Approach

ADT Notifications are generated only for patients who are actively enrolled at the time an encounter occurs. Confirm the following enrollment details:

• Roster ownership: Who prepares and maintains patient rosters.
• Submission method: How rosters are submitted.
• Update cadence: How often rosters are refreshed.

Each roster submission replaces prior enrollment state. Patients not included in the most recent roster are no longer eligible for notifications.

Operational Responsibilities

Confirm how ongoing operations will be handled after go-live:

• Who monitors delivery success.
• How enrollment updates are managed.
• How changes to delivery endpoints or routing are requested.
• How issues are escalated when behavior appears unexpected.

Clear ownership helps distinguish expected ADT behavior from issues that require investigation.