Monitoring and Operations

Operational monitoring of Clinical Alerts helps your organization confirm delivery health, detect anomalies in alert volume, and troubleshoot when expected alerts do not arrive.

Delivery Monitoring

Monitoring requirements depend on the configured delivery method.

FHIR Subscription

Your system should:

• Log inbound HTTP requests and response status codes.
• Verify that responses are consistent 2xx acknowledgments.
• Alert on rising error rates or sustained non-2xx responses.

SFTP

Your system should:

• Monitor file arrival patterns at the configured SFTP location.
• Validate downstream ingestion and processing.
• Alert on missing or delayed file delivery.

Volume Expectations

Alert frequency varies with:

• The number of enrolled patients.
• Query frequency on participating networks.
• Document availability across the networks where your patients receive care.
• Successful encounter inference from retrieved content.

Alert volume may fluctuate over time as enrollment, care activity, or network participation changes. Establish a baseline for expected volume and investigate sustained deviations.

Investigating Unexpected Behavior

The absence of an alert does not necessarily indicate the absence of care. Alerts are generated only when qualifying document exchange activity is observed and processed successfully.

If expected alerts are not received:

• Confirm patient enrollment status.
• Confirm delivery configuration and endpoint availability.
• Confirm that qualifying document-driven activity occurred within an active observation window.

If unexpected alert volume or timing patterns occur, contact Health Gorilla for investigation.

Operational Considerations

Alert-driven workflows should account for variability in timing, document availability, enrollment scope, and network participation.