Overview
Clinical Alerts is a Health Gorilla–designed, document-driven notification service that provides network-based awareness of patient clinical activity across national health information networks. Clinical Alerts detects patient activity by observing document exchange on those networks rather than relying on facility-generated event feeds.
By monitoring document exchange activity across networks, Clinical Alerts expands visibility beyond hospital-centric sources. You gain awareness of patient activity across inpatient, outpatient, emergency, post-acute, and specialty care settings based on where clinical documents are exchanged.
Clinical Alerts provides notification that qualifying activity occurred. Alerts do not include clinical documents. When the an alert indicates actionable activity, you can use Patient360 to retrieve and review the documents as part of downstream clinical, operational, or care-management workflows.
How Clinical Alerts Works
Clinical Alerts monitors document query and retrieval activity on national health information networks for enrolled patients. When an organization retrieves clinical documents for a patient, Health Gorilla evaluates that activity against alerting criteria.
If Health Gorilla identifies qualifying activity, it generates an alert and delivers it to your system using the configured delivery method. Alerts reference related encounters and documents but do not include clinical document content.
When an alert indicates activity that requires follow-up, your organization uses Patient360 to retrieve and review the associated documents.
Key Capabilities
Clinical Alerts supports event-driven awareness across networks and care settings through the following capabilities:
- Detecting patient activity inferred from document exchange across national health information networks
- Providing cross-setting visibility into inpatient, outpatient, emergency, post-acute, and specialty care activity
- Delivering event notifications at scale using FHIR subscriptions or Secure File Transfer Protocol (SFTP), depending on configuration
- Supporting downstream workflows by signaling when Patient360 retrieval is appropriate
Use Cases
Clinical Alerts supports workflows that benefit from early awareness of patient activity across organizations and care settings. Common use cases include the following scenarios:
- Care coordination and case-management workflows that require timely awareness of new clinical activity without point-to-point hospital integrations
- Emergency department, outpatient, and inpatient visit awareness inferred from network document exchange
- Transition-of-care and post-acute follow-up workflows
- High-risk patient monitoring and outreach programs that require earlier visibility than retrospective record retrieval
- Population health and utilization monitoring programs that require scalable, network-based event visibility
Event coverage is document-driven and depends on where and when participating organizations exchange clinical information on the network. Clinical Alerts does not assert that observed activity represents a complete or definitive clinical encounter.
Relationship To Patient360
Clinical Alerts and Patient360 support complementary workflows within your organization.
Clinical Alerts notifies your system when qualifying patient activity is observed through network document exchange. When an alert indicates activity that requires review or follow-up, your organization uses Patient360 to retrieve the associated clinical documents.
Alerts do not automatically retrieve records and do not include clinical document content. Your organization initiates document retrieval through Patient360 on demand, based on alert-driven workflows.