Creating and Managing Monitoring Protocols
Monitoring protocols enable your team to take action when specific conditions are met, such as when vital signs exceed set thresholds, the automated ECG analysis detects significant events, or sensors fail to capture data. Your Program Manager can create and manage these protocols by defining detailed alert and notification rules.
- Alert and Notification Triggers:
- Monitoring protocols determine the specific incidents and events that generate alerts and notifications, which can be configured to appear on the dashboard or as email/SMS notifications.
- Customizable Parameters:
- Duration: Set the duration for which a condition must be met before triggering an alert (e.g., heart rate above 150 BPM for more than 5 minutes).
- Hour/Min/Sec: Specify the exact time frames for monitoring specific conditions.
- Number: Set numerical thresholds (e.g., a specific heart rate or number of missed data points) that must be reached to trigger an alert.
- Communication Templates:
- Email Template: Customize the content and structure of email notifications sent to the team when an alert is triggered.
- SMS Template: Set up SMS notifications with customized messages for mobile alerts.
- Escalation Workflow Logic:
- Define and customize how the escalation process unfolds, ensuring that alerts are directed to the right individuals or teams based on the detected severity or type of incident.
- This can involve creating a tiered notification system to escalate more critical alerts to higher-level staff or more immediate communication channels.
For example, you can create a monitoring protocol that triggers an email notification if a patient’s heart rate exceeds 150 BPM for more than 5 minutes or send an SMS notification to a Technician if Atrial Fibrillation is detected, ensuring timely and appropriate responses.
These protocols allow for granular control over monitoring and ensure that critical health data is promptly and efficiently addressed.