Delivery Methods

Clinical Alerts supports two delivery methods. Each method defines the transport used to transmit alerts. Payload format and alert semantics remain consistent regardless of delivery method. Only one delivery method can be configured per tenant.

FHIR Subscription

FHIR Subscription delivery transmits alerts to your system using a FHIR Subscription with webhook transport. Your organization provides the HTTPS endpoint that receives notifications. Health Gorilla configures and operates the FHIR Subscription used for alert delivery for your tenant and sends event-driven notifications to the endpoint you define. Delivery relies on standard HTTP response semantics for acknowledgment.

FHIR Subscription delivery works well when your system supports HTTPS endpoints and event-driven processing.

Your organization must ensure that:

• Your system accepts HTTP POST requests at the configured endpoint.
• Your system returns HTTP status codes in the 200–299 range to acknowledge receipt.
• Logging, monitoring, and acknowledgment handling are in place.

Non-2xx responses are treated as delivery failures and may result in retries based on tenant configuration.

Secure File Transfer Protocol (SFTP)

SFTP delivery writes alert files to a configured SFTP destination. Delivery is batch-oriented and file-based.

SFTP delivery works well when webhook-based delivery is not available or when downstream systems require batch file ingestion.

Your organization must:

• Provide the SFTP host, port, and authentication details (password-based or key-based).
• Ensure the destination is reachable and properly configured.
• Complete network allowlisting and TLS configuration.
• Ingest and process delivered files in downstream systems.

The delivery cadence and file grouping depend on tenant configuration and system conditions.

Delivery Behavior

Alert delivery is asynchronous and event driven. Delivery does not provide real-time guarantees because alerts may be transmitted minutes to hours after the underlying network activity, depending on processing queues, system conditions, and delivery configuration.

Delivery failures do not retroactively affect enrollment or alert generation. Retry behavior and error handling depend on the configured delivery method and tenant settings.

Delivery configuration does not support filtering, routing, or modifying alert content. Clinical Alerts does not persist alert payloads for later retrieval. Your organization is responsible for logging, acknowledgment, auditing, and downstream handling within your system.

Delivery Setup and Validation

Delivery setup establishes how Clinical Alerts notifications reach your system after alerts are generated. Your organization provides delivery details to Health Gorilla, and Health Gorilla configures and operates alert delivery for your tenant based on those details.

Delivery setup and validation focus on:

• Providing delivery details for the selected delivery method
• Confirming endpoint readiness
• Verifying that generated alerts reach your system as expected

Delivery setup does not affect which patients are monitored or whether alerts are generated.

Provide Delivery Details

To configure alert delivery, your organization must share delivery details with Health Gorilla. Provide the following information based on the delivery method.

FHIR Subscription Delivery

• HTTPS endpoint URL
• Network allowlisting requirements
• Confirmation that your system accepts HTTP POST requests
• Confirmation that your system returns HTTP 2xx responses to acknowledge receipt
• Confirmation that inbound logging or monitoring is in place

SFTP Delivery

• SFTP host and port
• Authentication method (password-based or key-based)
• Public keys or credentials required for access
• Target directory or file drop location
• Network allowlisting or TLS requirements, if applicable

Health Gorilla applies these details prospectively.

Prerequisites for Validation

Before validating alert delivery, confirm that:

• An enrollment model is configured and active
• A delivery method has been selected
• Delivery details have been provided to Health Gorilla

Validate Endpoint Readiness

Endpoint readiness depends on the selected delivery method.

For FHIR Subscription delivery, confirm that:

• The endpoint accepts HTTP POST requests.
• Responses return HTTP status codes in the 200–299 range.
• Inbound logging or monitoring is available.

For SFTP delivery, confirm that:

• Routing to the configured SFTP destination is enabled.
• TLS configuration and allowlisting are complete.
• A test delivery can be routed successfully.

Verify Alert Delivery

Delivery verification requires observed alert activity for an enrolled patient.

Confirm that:

• Alerts generated by Clinical Alerts are transmitted using the configured delivery method.
• Delivery attempts are observed at the destination.
• Referenced resources can be accessed through Patient360 record retrieval workflows, when applicable.

Client Responsibilities

After delivery is configured, your organization is responsible for:

• Monitoring delivery endpoints or file drops.
• Handling retries and idempotency in downstream systems.
• Confirming alert receipt and processing behavior.
• Auditing and logging alert activity as required.

Alerts are generated only for patients enrolled at the time qualifying document-driven activity is processed. Delivery reflects observed network activity and is not guaranteed to be immediate.