Search
K
< Back

Message Processing

When a participating hospital transmits an HL7 ADT message to Health Gorilla, the message is evaluated in real time to determine whether it should generate an ADT Notification. Notifications are created only for enrolled patients and delivered immediately to your configured endpoint.

Notification Processing Flow

ADT Notifications are processed and delivered as follows:

  1. A hospital encounter event occurs, such as an admission, discharge, transfer, or emergency department visit
  2. The hospital generates and transmits an HL7 ADT message to Health Gorilla through a secure interface
  3. Health Gorilla receives and parses the message
  4. The message is evaluated against your current enrollment list
  5. If the message references an actively enrolled patient, an ADT Notification is generated
  6. The ADT Notification is delivered to your configured endpoint

Enrollment Matching

ADT Notifications are generated only for patients who are actively enrolled at the time the notification is processed.

  • If a patient is not enrolled, no ADT Notification is generated
  • If a patient is enrolled after the original message was sent, no retroactive notification is generated

You should maintain accurate and timely enrollment lists to ensure that ADT Notifications are generated as expected.

Delivery Behavior

ADT Notifications are delivered in real time after processing.

  • Notifications are delivered as HL7 ADT messages to your configured endpoint
  • Health Gorilla does not queue or delay notifications unless required by downstream delivery constraints
  • ADT Notifications are not retried if delivery fails. You are responsible for implementing retry or reconciliation logic if required
  • Delivery timing depends on hospital feed latency and HL7 message generation patterns at the source hospital

Processing Considerations

  • ADT Notifications are generated only from supported HL7 message types. See ADT Notifications > Supported HL7 Message Types
  • Hospital feeds may vary in completeness and consistency. Some feeds may not provide all message types for every patient encounter
  • Duplicate or update notifications (such as A08) are delivered as provided by the source hospital. You should implement deduplication in your workflows
  • Notifications are typically delivered within seconds of receiving the corresponding HL7 message