Subscribing to Alerts

To begin receiving Patient360 Clinical Alerts, you must enroll patients for monitoring and configure a delivery method. Alerts are triggered only for patients who are actively enrolled at the time of the network query and associated with a practice that is licensed for Clinical Alerts.

Activation and Access

While Health Gorilla Support must enable Clinical Alerts for your tenant, you need to define the preferred delivery method—FHIR webhook, HL7 v2 A08 message, or FHIR Subscription—and confirm that your delivery endpoint is ready to receive notifications.

After activation, you can begin enrolling patients and preparing to process alerts.

Enrolling Patients

Clinical Alerts are only triggered for patients who are enrolled at the time of the network query. Enrollment ensures that alerts are generated for the appropriate patient cohort.

You can enroll patients using either the FHIR Group API or a static roster upload.

FHIR Group API Enrollment

Managing enrollment through the FHIR Group API allows you to add and remove patients dynamically.

Use the following Group operations to manage enrollment:

@add to enroll patients
@remove to unenroll patients
@lookup to check whether a patient is enrolled
@members to retrieve the list of enrolled patients

Note: All enrolled patients must have valid FHIR IDs.

Roster Upload

For stable patient cohorts provided by attribution partners such as Experian or HSX, you can submit a static roster for enrollment.

Prepare the roster file according to Health Gorilla specifications:

Format the file as fixed-width for Experian or CSV for HSX.
Upload the file using SFTP.
After the upload, request confirmation from Health Gorilla Support that the roster was ingested successfully.

Configuring Delivery Methods

You select the delivery method when Clinical Alerts is activated for your tenant. The selected method applies to all alerts for your tenant.

You can choose from the following options:

FHIR Webhook: The system delivers a FHIR Parameters resource referencing a new Encounter to the webhook endpoint that you provide. Automatic retries occur for failed deliveries.
HL7 v2 A08 Message: The system generates a synthetic HL7 v2 A08 message from the retrieved document and routes it to your HL7 integration engine. You are responsible for implementing retry handling for this method.
FHIR Subscription: You can configure a FHIR Subscription to receive synthetic ADT notifications based on Clinical Alerts. Use the following criteria for the Subscription resource: Bundle?message.event=admin-notify&clinicalAlerts=true

Note: Without the clinicalAlerts=true parameter, you will not receive Clinical Alerts.

Next Steps

After you enroll patients and configure the delivery method, you may want to:

Monitor the delivery endpoint to verify that alerts are being delivered successfully.
Go to Clinical Alerts > Receiving and Retrieving Alerts to review the alert payload structure and retrieval steps.
Go to Clinical Alerts > Best Practices for Clinical Alerts for recommendations on monitoring enrollment and optimizing alert delivery.