Tech Specs
Which mobile platforms support Bells?
Bells is available on a variety of platforms:
Bells app takes an average of 500 MB of storage on your Android or Apple device.
For more details, refer to the Bells recommended devices.
Which devices can use Bells?
Bells Recommended Devices
These are the recommended devices for Bells based on Operating System. Remember, these are recommendations; they do not mean other devices are not supported.
Laptop Device (Apple or Windows 10)
- 8+ GB of RAM
- Intel Core i5 or greater CPU
-
Internet Speeds
- 3 Mbps Download
- 1 Mbps Upload
Browser
-
You must use either the most recent version of the browser or one version prior. Earlier versions of the browser may still work, but full functionality is only supported on the most recent two versions of the browser.
- Along with the above requirement, your browser must support TLS 1.3. You can refer to this table to find out if your browser supports TLS 1.3.
- Note: Internet Explorer 11 is not supported for Bells.
Apple/iOS
-
iPhone
- 8 or 8 Plus
- X, XS or XS Max
- XR
-
Tablet Device
- iPad: must support a minimum resolution of 1280 X 800
- iPad Pro: must support a minimum resolution of 1280 X 800
- iPad Air: must support a minimum resolution of 1280 X 800
-
Operating System
- iOS version 12 and higher
Android
-
Mobile Device
- Samsung Galaxy: Note 10 S9/Plus or greater
- Google Pixel: 4 or greater
- Devices with similar specifications
-
Tablet Device
- Must support a minimum resolution of 1280 X 800
-
Operating System
- Android version 9 and higher
Does Bells work on both Apple and Android phones?
Yes. Bells is compatible with both iOS and Android OS devices. This also means that Bells may work on iPads and Android tablets, but tablets are not officially supported.
How does Bells keep client information safe on the phone/tablet?
We have several safety precautions in place. First, there’s encryption. Data stored on the mobile device is encrypted using AES, which uses an encryption key called an App PIN that only the user of the device will know. Encrypted data, when required, is fetched from the device storage and is decrypted back into the original format using the encryption key. Because we use a random PIN set by the end user, if the user forgets their PIN one must uninstall the application and reinstall it to set a new pin. By uninstalling the application all PHI data is removed from the device.
Second, each user must have a login for their EHR and be enabled for Bells by their agency administrator or EHR manager. Downloading the app is useless to someone that has not gone through the registration process.
Each user must have internet connectivity to log in and be authenticated. The next time the user signs in with internet connectivity, their data will sync to CT|One and pull new data back to the device.
Also, there is an organization preference to control the timeframe for your timeout on the app. The first time you log in and open the Bells mobile app, you will be asked to create a personal app PIN number for security. Anytime you are inactive on your app for more than the allotted time, the app will require that security PIN for re-entry. This works even offline where you have no connectivity. A user also has the ability to use biometrics in lieu of your app PIN, both Fingerprint/ Touch ID and Face ID are available.
Which sites should be Whitelisted for Bells?
The domains that should be Whitelisted for Bells are:
- bells.ai
- remarkable.ai
- rhoneapp.com
- unpkg.com
- cdnjs.cloudflare.com
- windows.net
- pndsn.com
- fonts.googleapi.com
- fonts.gstatic.com
- sentry.io
- mixpanel.com
- walkme.com
The displays in Bells are zoomed too far for me to scroll...
The default Windows settings on your device could potentially be causing some not-so-fun visuals in Bells. Bells already has some built in capabilities to automatically help based on the zoom/resolution settings on your device. I've got some other ideas/things to adjust to help!
- There is a preference in your Personal Settings in Bells for normal font vs. large font.
- Check your browser zoom using the ctrl key on your keyboard and scrolling wheel on your mouse.
- You can reset your browser zoom to 100% with ctrl and 0.
- If your browser zoom is not set to 100%, an indicator will show near the address bar. This is different depending on what browser you use.
- Here is an example from Chrome
- Here is an example from Chrome
- Check your Scale setting, this is in your computer's visual settings and can be adjusted to change the size of text on your device.
Tell me how Bells protects security and HIPAA compliance...
Security and HIPAA compliance are always top of mind for Bells. The Bells application follows all the Netsmart security policies and protocols as well as adds additional layers of security when warranted. For example, we have biometric encryption of all data in the mobile app.
Netsmart has routine security audits conducted by independent auditors and those audit reports can be made available upon request.
What is Bells' disaster recovery plan?
Bells' data is stored in Azure and is replicated automatically to a different region and can be restored from point-in-time backups.
Netsmart has routine security audits conducted by independent auditors and those audit reports can be made available upon request.
I can't access Bells when I work from home. What do I do now?
Since Bells is web-based, you should be able to access it from any network. Some network configuration can limit connectivity for a variety of reasons. If you're able to access Bells from some locations, but not others, your network is probably limiting the connection. Your first point of contact for suspected networking issues should be your organization's IT Help Desk. They can work with you to troubleshoot your connection more effectively than Bells support can, and provide guidance or solutions compatible with your company's security and acceptable use policies.
The Bells team is aware that the "Amazon Eero Secure" firewall/router may be blocking access to Bells. If you're using this firewall/router, we recommend using a full-tunnel VPN to work around the block.
I'm an IT Administrator with a user who can't access Bells from home. What do I do now?
As an IT admin, if you have users reporting issues with accessing Bells from home, it's crucial to ensure that Bells's web-based SaaS software has access to all necessary URL endpoints for proper functionality. If users are unable to connect to certain endpoints, it may result in limited or unavailable functionality. For users on corporate networks, it's advisable to check DNS filters and firewall rules to confirm that the required sites are allowed for HTTPS egress. If users are outside the corporate network, issues may arise from local network or ISP security filtering, such as parental controls or endpoint security solutions. If adjusting the user's local network security policy isn't feasible, providing a full-tunnel VPN could be a workaround. If you've configured IP filtering with NetSmart and verified the user's originating IP address, but issues persist, please reach out to Bells Support for further assistance.