< Back

Overview

Clinical Alerts notify your system when enrolled patients experience significant clinical encounters across national health information networks, such as hospital admissions, emergency department visits, or other care events. These notifications help you stay aware of patient activity across diverse care settings.

Clinical Alerts complement traditional HL7-based alerting by expanding detection to external networks. Alerts are triggered by document queries and retrievals, not by hospital ADT feeds, giving you visibility into patient activity beyond your core EHR system.

Use Cases

  • Coordinate timely follow-up after hospital discharges or emergency visits
  • Monitor high-risk or chronic populations for unexpected care encounters
  • Track patients during referrals and care transitions across external networks
  • Detect inpatient and emergency encounters for enrolled patients nationwide

Benefits

  • Broader visibility into encounters that may occur outside your core EHR system
  • Timely notifications that support faster interventions and follow-up
  • More complete continuity of care by identifying encounters missed by ADT-only feeds
  • Stronger support for population health and value-based care programs

How Clinical Alerts Detect Events

When an external healthcare organization queries an enrolled patient through a national network using an ITI-55 or ITI-38 transaction in Carequality, CommonWell, TEFCA QHIN exchange, or eHealth Exchange, Clinical Alerts initiate background monitoring for new clinical documents related to that patient.

If a qualifying document is retrieved, Health Gorilla parses it to generate either a FHIR Encounter resource or a synthetic HL7 v2 A08 message, depending on your delivery configuration. The alert is then sent to the configured endpoint.

This document-driven process allows Clinical Alerts to capture care events that may not be visible through traditional HL7 ADT feeds.

Types of Events Detected

Clinical Alerts detect significant clinical encounters based on document activity, such as:

  • Hospital admissions
  • Emergency department visits
  • Inpatient discharges
  • Other care transitions documented through national network activity

Where Clinical Alerts Fit in Your Workflow

Clinical Alerts can deliver notifications through:

  • FHIR webhook (recommended)
  • HL7 v2 A08 message
  • FHIR Subscription (optional)

You choose the delivery method that best matches your system architecture. Clinical Alerts support delivery at scale for up to one million enrolled patients per tenant.