Working with ECG
We have created a FHIR based profile for the CRUD operation for 12 lead ECG.
Check the Swagger API's:
The documentation can be found at "Medical Service" section of Admin panel. It is a POST endpoint, and it adds on to the base URL with:
/patient/{userId}/observation/ecg
Provide the necessary object
Mandatory attribute of the object is "leads". It represents an array of objects, where each object is an ECG lead. For ECG lead, there are several important attributes:
data - an array of number values (in microvolts)
period - single number representing milliseconds between each of the data value
lead - name of the lead
origin - number value (in microvolts) which defines vertical center of the data (y axis zero)
Visualize the ECG stream
Inside the patient portal you will be able to visualize the ECG stream by using either our ECG viewer or implement your own. Therefore you have to navigate inside the Patient portal to measurements section and find ECG. In case you cannot find it please check the settings.
Pre-processing of ECG data
In the past we have done quite some research on the pre-processing of ECG, but also prediction models for for instance AF (atrial fibrillation).
We would be glad to collaborate with you on this.
Normally for the pre-processing you would have a script (Python or else) on the device sending the right data to the backend. Then on backend side there would be an additional script for prediction models.
