Marturion is creating a ECG Wearable device.

• This device is a little wearable device which connects to either a T-shirt with embedded electrodes or simply to regular ECG electrodes on the chest to capture continuous ECG.
• This wearable device exports its signal over a BLE connection.

Original Scope of Work

Marturion offered this because when they were introduced to the project the scope of work was described as creating a BLE connection to the RPi4B from an unspecified wearable device – and we proposed that this represented a great candidate because we could be in control of the firmware at both ends of the BLE connection. What They have since agreed with Rob is that the firmware we create on the RPi4B will receive the ECG signal data and store this in a sequence of time-stamped files which Rob’s firmware can then lift and read directly for onward transmission. Naturally this implies a small lag between data capture and data transmission but this should be minimal and in any case is normal behaviour for this type of device. Our expectation is therefore that the firmware we create will not actually need to be integrated in any significant way with Rob’s firmware and will simply read the ECG data from the BLE connection and save it into a sequence of files.

Business goals:

• Create a prototype device based on RPi and Ubuntu Core (Sonador Gateway) capable of receiving data from medical imaging modalities (MRI, CT, Ultrasound, ...) and sending it to the cloud.
• Implement support for the gateway to integrate with medical sensors (EKG) over Bluetooth Low Energy (BLE) and transfer signal data to the cloud.
• Integrate with the Sonador medical cloud and retrieve a remotely managed configuration for the device.
• Push data to imaging servers (Orthanc) specified by the configuration using the DICOMweb protocol as data arrives to the device (either over BLE or DICOM/PACS).
• Once data has been pushed to the cloud by the gateway (and verified/stable), remove the local copy of the data.

Definition of done:

• Have a physical device which can be installed at a clinic site.
• Plug the device in at the clinic so it has Internet connectivity and is visible to an imaging modality.
• Push imaging data to the device and confirm that it is transferred to the cloud.
• Demonstrate the wearable EKG transferring patient data to the device which is also pushed to the cloud (and be able to view it in Sonador/OHIF).

Schedule: October 7, 2022

• ROM build of Ubuntu Core for RPi device which includes Orthanc and Python plugin (Oct 7)

Schedule: October 10-14, 2022

• Working example of Sonador/Gateway integration for pushing medical imaging data (Oct 14)

Schedule: October 17-21, 2022

• Sonador Gateway UI prototype (status, network details, ...) and working example of pushing signals data (Oct 21)

Schedule: October 24-28, 2022

• MVP: device is able to push imaging/sensor data to cloud and view in OHIF (Oct 28)

Schedule: October 31, 2022

• Test in clinical environment (Oct 31)
  • Test engineers: Rob Oakes and Derrick Givens

Collaborators:

• Smith and Nephew: Robotics advanced research, technology, and innovation
• Marturion: hardware and primary contractor
• Sonador AI: cloud and embedded firmware

Hardware:

• EKG remote sensor: provided by Marturion and able to transfer sensor data over bluetooth
  • Will be responsible for writing the device firmware for receiving the data on the gateway and encoding it in a format compatible with DICOM
• Sonador Gateway: RPi running Ubuntu core and Orthanc able to integrate with the Sonador medical cloud

Software:

• Sonador and Orthanc cloud deployments: receive data in a DICOM format pushed by the gateway
• OHIF: cloud based viewer which will be used to review and annotate the EKG data