[Feature Request] Import from GadgetBridge

[MaxGitHubAccount]

As a user of a smart watch I want to import my steps into Kailona in order to not having to move those steps manually to Kailona.

Background
With the use of smart watches steps are counted automatically all days. Gadgetbridge is an open source app which tracks health data of various smart watches without the need to use propietary servers. The goals of both projects are well aligned as it gives the user the possibility to keep data safe and allowing to self measure own health.

Why this feature?
Currently I have to type in the steps of every day manually from Gadgetbridge to Kailona.

Gadgetbridge Export
Gadgetbridge already implements an export for all data collected. One can also upload those exports to Nextcloud. Apart from steps additionally also other data could be imported like heart rate.

Acceptance Criteria

• Kailona can import GadgetBridge export files
• A directory in the Nextcloud can be defined for automatic import of updating files
• A new import will not add another entry for already imported data
• Imported files are shown in the Kailona dashboard

Link to GadgetBridge https://gadgetbridge.org/
Data Export at GadgetBridge https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Data-Export-Import-Merging-Processing

[makuser]

I'm also a user of Gadgetbridge and thought about the same usage scenario a few months ago.

I would however to keep it clean and where it belongs, rather implement the FHIR protocol into gadgetbridge and 'stream' the data to the server that way, rather than perform a regular import of the data into ehr.

I generally do not see data aquisition adapters themselves to be useful to have in the core ehr app, rather either as external services that you might spin up, or as plugins/features in the data mining applications like Gadgetbridge.
In the case of for example Apple Health or Google Fit, an adapter service could be responsible to aquire data from these services and inject them into the FHIR server periodically, as this feature was something that's been asked several times before.

It'd be interesting to see what the project members think about the general data aquisition architecture from external health hardware or software though.