< Back

Alert Rules

Patient360 Clinical Alerts are generated based on document activity across national networks. Certain factors can cause alerts to be suppressed, delayed, or filtered. You should understand how these behaviors affect alert delivery and account for them when monitoring Clinical Alerts.

Document Issues

Health Gorilla parses incoming documents to generate FHIR Encounter resources or synthetic HL7 v2 A08 messages. If a document is incomplete or malformed, alert generation may be suppressed. The following types of document issues can result in alert suppression:

  • Documents that lack required Encounter elements
  • Documents with invalid or incomplete patient references
  • Unstructured document types that cannot be parsed into Encounter-based events

Source Filtering

Network queries can originate from a variety of organizations and endpoints. Certain queries and documents are filtered based on tenant-level configuration. The following source-level filtering rules may affect alert generation:

  • Queries from blocklisted sender OIDs are ignored
  • Documents from nonparticipating networks or endpoints may be excluded based on tenant settings
  • Receiver allowlists can be used to limit alert generation to documents received from specific endpoints

If required, contact Health Gorilla Support to review or adjust tenant-level filtering rules.

Patient Enrollment Changes

Clinical Alerts are triggered only for patients who are actively enrolled at the time of the network query. The following enrollment-related behaviors affect whether alerts are generated:

  • If a patient is enrolled but later removed, alerts will not be generated for subsequent queries
  • If a patient is enrolled after a document has already been retrieved, no retroactive alert is generated

You should monitor enrollment lists regularly and coordinate any enrollment updates with care teams and workflows.

Delayed Alerts

Alerts are delivered as quickly as possible based on document availability and network activity. The following factors can introduce delays in alert delivery:

  • Documents may be retrieved hours after the original network query, depending on source system behavior
  • Parsing and Encounter generation may take additional time if document content requires review
  • Alerts are typically delivered within 4 to 24 hours of the triggering network query

If you observe delays beyond this range, you should contact Health Gorilla Support to investigate potential issues.