Guides
  1. Guides
  2. Clinical Alerts

Implement Clinical Alerts

Implementing Clinical Alerts requires a sequence of steps, including activation, configuration, enrollment, and validation, that are performed by Health Gorilla and your organization before go-live.

Verify Activation Prerequisites

Before configuration, verify your technical readiness by making sure that:

  • Clinical Alerts is enabled for your Health Gorilla tenant.
  • Your system can receive, acknowledge, and process notifications in an idempotent manner.
  • You have selected an enrollment model and a delivery method.

Configure the Delivery Method

Choose one delivery method per tenant, either FHIR Subscription or Secure File Transfer Protocol (SFTP), and provide Health Gorilla with the corresponding endpoint or SFTP credentials. Your system captures the deduplication identifiers that will be used in downstream processing.

Delivery configuration controls transmission only. It does not influence eligibility or alert timing. Delivery failures do not prevent alert generation, and notification ordering is not guaranteed.

Enroll Patients

Choose one of the supported enrollment models:

  • Limited Enrollment: Your organization manages a FHIR R4 Group resource containing enrolled patients. Changes apply prospectively.
  • All-Tenant Enrollment: All patients associated with the tenant are enrolled automatically. New patients are included as they are added.

Enable Source Document Storage (Optional)

For organizations licensed for C-CDA storage, Clinical Alerts imports the source document associated with each alert into the patient's chart, where it is accessible through the FHIR R4 DocumentReference API. To enable, contact Health Gorilla.

Validate End-to-End Behavior

Validate that enrollment, alert generation, delivery, and document retrieval function together as expected by confirming:

  • Enrollment is active for one or more test patients.
  • A qualifying document is processed.
  • An alert is received at the configured endpoint.
  • Required identifiers are captured for deduplication.

After go-live:

  • Monitor delivery health using inbound logs or file arrival monitoring.
  • Implement deduplication using stored identifiers.
  • Establish a baseline for expected alert volume.

Confirm Operational Readiness

Before go-live, confirm the following:

  • Delivery and enrollment are active and validated.
  • Your system acknowledges FHIR deliveries or ingests SFTP files successfully.
  • Idempotent downstream handling is implemented.
  • Monitoring is in place for delivery failures or delays.

Clinical Alerts is asynchronous. Alerts are typically delivered in 4 to 24 hours, and ordering relative to other events is not guaranteed.

After go-live, monitor the response codes, SFTP ingestion, alert deduplication, and alert volume to confirm your system continues to function as expected.