...
What are the resilience features built into your system?
Infrastructure Resilience
Our system has been built in a robust and resilient way and the using scalable cloud infrastructure is scalable that adapts according to demand , as well as having redundant machines so that if one machine fails, another can take its placegeographically separated redundancies.
In our application, in the event of a communication failure with the cloud, the application mobile app temporarily stores the monitoring data and sends it to the cloud as soon as the failure is resolved.
Communication between the sensor and the application is checked for packet validation and packet loss.
How is the system designed to be resilient to potential noise interference?Noise interference resilience
Our system is meticulously engineered to ensure high resilience and reliable performance , even in the presence of noise and environmental interferences that could affect electronic components and data communication. Here is how we address noise mitigation across different parts of our systemNoise mitigation resilience points are:
Sensor Resilience: Sensors are critical to our system's operation and are rigorously tested to ensure their resilience to noise. They have undergone comprehensive Comprehensive Electromagnetic Compatibility (EMC) testing in accordance with the IEC 60601-1-2 standard, demonstrating that they are not susceptible to noise interference from other devices, nor do they generate noise that could affect other systems. These tests ensure that the sensors maintain their functionality and accuracy, even in environments with high levels of electronic noise.
Communication with Mobile Devices: Communication between the sensors and mobile devices is established using Bluetooth 5.0, chosen for its advanced noise mitigation capabilities. In dense environments, where many devices operate on the 2.4 GHz frequency, both Bluetooth and Wi-Fi connections can be impacted. However, Bluetooth 5.0 and Wi-Fi incorporates robust techniques such as channel hopping and other mitigation strategies to maintain stable and reliable communication. These techniques are detailed in our wireless coexistence document, which describes how our system minimizes interference and maintains the integrity of transmitted data.
...
YES. All PHI (protected health information) is encrypted at rest. This data is encrypted at source using the public key from a client-specific public-private encryption key schema. Only our clients, in an active user session, can access PHI data that is served via a dedicated client AWS infrastructure that brain4care does not have access to.
...
For US customers, all servers are located in the US territory.
How
...
do you backup data?
All data is stored in our HIPAA-certified cloud infra-structure infrastructure with daily backups.
Do you support Single Sign-On (SSO)?
Yes. The B4C System has SSO capabilities to integrate with customers customer's AD (Active Directories) to allow for seamless and secure system login. This functionality is included via joint brain4care and client IT team project.
...
Yes. The B4C System has secure APIs to integrate with customers the customer's EMR (Electronic Medical Record) to allow for seamless and secure clinical information flow. This functionality is included via joint brain4care and client IT team project.
...
Yes. Such requests should be sent to security@brain4.care or via requests using our help.brain4.care portal.
How do I recover the device configuration?
Only brain4care authorized representatives have access to and are allowed to view, manage, and change device configurations. In the B4C System’s case, the above-mentioned configuration is for the sensor itself.
...