The communication failure dashboard provides a centralized view of all communication failures, enabling you to quickly identify and address issues as they arise.
As shown in the image below, it displays critical information regarding which sensors or receivers are experiencing issues and their impact on your overall data integrity.
Note: If you can not see the Communication Failure tab please check the article Manage dashboard tabs.
The two upper cards display the information related to the number of active sensores and receivers that are online and offline.
In this example, there are 410 active sensors with two of them being offline and 49 receivers of which one is offline.
By clicking on each of the cards you will be able to filter the communication failures in order to only see sensors or receivers.
Note: the sensors communication failures displayed are linked to the sensors associated with the dashboard's location. For example, if the dashboard is set to the location "Pharmacy", you will only see communication failures for the Pharmacy's sensors. If you are using the default dashboard, the communication failures will be related to all the sensors that your user has permission to see. On the other hand, the receivers communication failures are related to the sub-organization of the dashboard's location. For example, the organization "Hospital" has two sub-orgs "Pharmacy" and "Cardiology" and the Pharmacy has two locations "Room 1" and "Room 2". If your dashboard is associated with the Room 1 location then you will be able to see the communication failures linked to all the receivers from the Pharmacy sub-org.
All communication failure cards are clickable, and clicking on one will open a menu where you can see the strength of sinal graphic and other important information about this specific communication failure. To know more about this menu please check the Communication Failure Menu article.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article