Sending Data Post Data Exchange
The sending system will take the new health data that needs to be sent to the device and send it to the Software Development Kit (SDK). This SDK plays a pivotal role in ensuring the security and integrity of the data transmission. Upon receiving the health data, the SDK will first sign the data to guarantee its authenticity and integrity. This signing process involves using a private key to create a digital signature, which can later be verified by the receiving device using the public key to confirm that the data has not been tampered with. Following the signing process, the SDK will encrypt the data to protect its confidentiality during transit. Encryption ensures that even if the data is intercepted, it cannot be read by unauthorized parties. Once the data is both signed and encrypted, the SDK will send it to the pre-registered push URL.
Upon successful receipt of the data by the server, the server will take the next step in the data delivery process. It will send a push notification to the device associated with the intended recipient. This push notification will contain the URL from which the device can download the new health data. The device, upon receiving the notification, will follow the URL to download the encrypted health data.
Once the data is downloaded to the device, it undergoes a series of crucial security checks and processes. The device will first decrypt the data to convert it back to its original, readable form. Following decryption, the device will parse the data to interpret and organize the information appropriately. Next, the device will verify the digital signature attached to the data, ensuring that the data has remained unchanged since it was signed by the SDK. This verification step confirms the data’s authenticity and integrity. After successfully decrypting, parsing, and verifying the signature, the device will save the health data securely.
Upon saving the data, the device will trigger a notification to inform the user that new health data has been received and is available for review. This notification will include a summary of the new data, providing the user with a quick overview. The user can then click on the notification to open the relevant application and view the detailed health data. This streamlined process ensures that the user is promptly informed of new health data updates and can access them easily and securely.
to SDK
data with private
signing key
push URL
to patient device
data from URL
public key
local database
on device with
data summary