Lyniate Team

Improve Operations and Patient Care with Real-Time Data Using Corepoint Action Points

July 17, 2018

  • Improve operations and data workflows
  • Support caregivers with real-time patient data
  • Customize alert notifications based on message data

There is so much data flowing through your interfaces every day that could be driving process and workflow improvements, as well as improving patient care.

Corepoint Action Points are customizable triggers that monitor the healthcare data flowing through Corepoint Integration Engine and identify any message data that should trigger an alert notification… giving you more insight and control.

Corepoint customers are constantly innovating and discovering new ways to leverage Corepoint Action Points to improve care in their organizations. Physicians, clinicians, application analysts, technicians, and patients, all benefit by these improved workflows.
Corepoint Action Points Workflow
A common workflow is to trigger an email notification based on a specific test code, result type, or missing data in a message. Many Corepoint customers use Action Points to transmit key data in real-time to applications that are in use by caregivers.

Action Points alerts the right individual or application when specified events occur. A common example is to trigger an email notification based on a specific test code, result type, or missing data in a message. Many Corepoint customers use Action Points to transmit key data in real-time to applications that are in use by caregivers.

Common Action Points workflows used by Corepoint Health customers today:

Event   Action
Incoming STAT order from an ordering physician. Notify the physician immediately with results.
Specified disease code from a diagnosis. Notify a variety of departments, based on threat level.
Completed lab test result for a patient in the ER. Notify the nurse and physician immediately.
During the registration process, a required field is left blank by an EHR that doesn’t enforce the requirement, so the message will be rejected by other systems. Notify the registration clerk with a custom email to update the record with the required information.
Hospital requests an order to Radiology that doesn’t exist, so the RIS returns a NACK (negative acknowledgement) with a description that includes the issue. Send a custom email to the Billing Specialist to update the order number to match the RIS.
Hospital and Referring Physician use EMPI Lookup to match patient identifier. If query returns multiple patients, notify the owner of appropriate owners to either add additional parameters to the query or update the EMPI to resolve the duplication.

Examples of customers using Corepoint Action Points:

  • LHP Hospital Group uses Action Points to create logic that alerts caregivers via pager with patient information that is on their specific floor of the hospital. Read more.
  • Halifax Health transmits data from the engine to caregivers’ Vocera® Communication Badges, reducing the need to constantly check the EHR. Watch video.
  • Use Action Points to populate patient-facing apps with the engine using C-CDA. Read more.

Related Blogs

Jesse Eichhorn

Introducing Lyniate EMPI by NextGate 11.2: powerful new tools to drive identity data trust

Listen to my colleague and identity data management veteran Rico Garcia talk about what makes this new version special.

Read more
The number 1 integration engine is now available in the cloud

Shelley Wehmeyer

The Best-in-KLAS® healthcare integration engine, Lyniate Corepoint, deployed in the cloud

Rolling out now... the integration engine you know and love, Lyniate Corepoint, is deployed on AWS to provide optimal business continuity, system resiliency, and security.

Read more
Lyniate_Rapid_illustration_api_gateway_manager (1)

Lyniate Team

Lyniate introduces Rapid, a healthcare API gateway

Rapid is a healthcare API gateway and manager designed to help health teams create and safeguard APIs, including Fast Healthcare Interoperability Resources (FHIR)-based APIs like those required by the CMS Interoperability and Patient Access Rule.

Read more