No products in the cart.
10-24-19-RCM-Policies-3.2.0.pdf (0 downloads)
|
RCM 3.2 Policies
|
|
ABSTRACT:
RCare Mobile (RCM) version 3.2.0 was released on 10/15/19. This version of RCM addresses all known issues in addition to solidifying the platform and adding new functionality. There is one potential issue that remains in the software. This issue can be avoided by following existing RCM polices.
TECH SUMMARY:
RCM 3.2.0 contains a known path to a state where RCM phones will not receive alerts. If the policies below are followed this path can easily be avoided.
Path to error:
If an RCM phone loses Wi-Fi connection while the phone is in Do Not Disturb Mode and an alert is triggered during that outage the phone will not receive the alert until the phone is manually activated.
Related Policies:
Do Not Disturb Mode: Do Not Disturb Mode should not be used at any time. Please train staff to never lower the volume below the “Vibrate” setting. [Do Not Disturb is the lowest level in the volume settings accessible via the “rocker” switch on the side of the phones.] Note: If the phone is in Do Not Disturb Mode and on Wi-Fi an alert will pull the phone out of Do Not Disturb and “wakes up” the device. Log-in/Log-Out:
The Log-in and Log-Out features of RCM not only allow for efficient management and reporting of staffing hours but also drive back-end functionality. For both reasons staff need to be trained to log out of RCM when leaving Wi-Fi for planned breaks, meals etc. If the building has known Wi-Fi “dead spots” staff need to be trained to manually activate the phone and confirm connection to Wi-Fi.
Wi-Fi Connectivity:
RCM functions on a dedicated Wi-Fi network. Clinical staff need to be made aware of any deficiencies in coverage, strength etc. that may affect the phones connection to said dedicated Wi-Fi. Although 3.2.0 has added an audible notification when Wi-Fi is lost, if staff plan to leave Wi-Fi for extended periods they should be following the log in/out policy above. Note: If the RCM app is unlocked users can select other networks. An RCM phone on the wrong network is the same as that phone not being on Wi-Fi at all. Phones should be locked after install and the RCM phones should only “know” the appropriate nurse call Wi-Fi SSIDs.
|
|
|
Log-in/Log-Out:
The Log-in and Log-Out features of RCM not only allow for efficient management and reporting of staffing hours but also drive back-end functionality. For both reasons staff need to be trained to log out of RCM when leaving Wi-Fi for planned breaks, meals etc. If the building has known Wi-Fi “dead spots” staff need to be trained to manually activate the phone and confirm connection to Wi-Fi.
Wi-Fi Connectivity:
RCM functions on a dedicated Wi-Fi network. Clinical staff need to be made aware of any deficiencies in coverage, strength etc. that may affect the phones connection to said dedicated Wi-Fi. Although 3.2.0 has added an audible notification when Wi-Fi is lost, if staff plan to leave Wi-Fi for extended periods they should be following the log in/out policy above. Note: If the RCM app is unlocked users can select other networks. An RCM phone on the wrong network is the same as that phone not being on Wi-Fi at all. Phones should be locked after install and the RCM phones should only “know” the appropriate nurse call Wi-Fi SSIDs.
|
|
CONCLUSION:
If any or all of the above policies are followed the path to not receiving alerts can easily be avoided. The primary solutions/takeaways are:
● Do Not Disturb Mode: Train staff on how Do Not Disturb Mode is activated and ensure they don’t enter or use that mode.
● Checking the Phone when reentering Wi-Fi: In situations where temporary Wi-Fi outages can’t be avoided (e.g. elevators, stairwells etc.) train staff to manually check their phone for alerts when reentering good Wi-Fi.
|