Search
K
< Back

Product Examples

Subscriptions deliver event-driven notifications that power multiple Health Gorilla products. Each product defines its own event types, payload formats, and configuration options, but all share the same reliable delivery framework. Reviewing these examples helps your organization understand how subscriptions are applied in practice and what to expect during implementation.

Clinical Alerts

Clinical Alerts use subscriptions to notify your organization when enrolled patients experience new encounters across connected networks. Instead of requiring repeated queries, subscriptions send alerts as soon as new encounter data is detected.

  • Events delivered: Encounter creation or update based on retrieved external documents
  • Delivery methods: FHIR subscription (Encounter) HL7 v2 A08 message
  • Configuration: Requires patient enrollment in Clinical Alerts and registration of a delivery endpoint

Patient360

Patient360 subscriptions enable ongoing monitoring of patient activity once a record has been retrieved. After the initial query, Health Gorilla monitors for new documents or updates and notifies your organization automatically.

  • Events delivered: Newly available clinical documents, updated records, or inferred encounters
  • Delivery methods: FHIR subscription (DocumentReference or Encounter)
  • Configuration: Linked to the patient roster maintained by your organization

Lab Network

Lab Network subscriptions deliver laboratory results directly to your application as soon as they are available from participating laboratories. This eliminates polling and ensures timely result delivery.

  • Events delivered: New or corrected test results
  • Delivery methods: FHIR subscription (DiagnosticReport) or HL7 v2 ORU R01 result message
  • Configuration: Created automatically when an order is placed and associated with the accession number or patient ID

ADT Notifications

ADT Notifications use subscriptions to broadcast admission, discharge, and transfer events from hospitals and connected networks.

  • Events delivered: Admission, discharge, and transfer events (ADT family)
  • Delivery methods: FHIR subscription (Encounter) or HL7 v2 ADT message
  • Configuration: Requires ADT feature licensing and registration of a delivery endpoint