What is the hypometrics package?
The hypometrics package aims to bring together analysis of continuous glucose monitor (CGM) data, physical activity and sleep data from wearable devices (e.g. Fitbit) and person-reported hypoglycaemia data from smartphone applications (e.g. The Hypo-METRICS app). The package offers the ability to clean, link, visualise and analyse data from those devices and provide key metrics from each.
Why the hypometrics package?
The building blocks of what is now the hypometrics package were developed in an effort to support and facilitate the analysis of data from the Hypo-METRICS (Hypoglycaemia - MEasurement, ThResholds and ImpaCtS) study. Hypo-METRICS was a multinational, multicentre, observational study conducted between 2020 and 2022 as part of the Hypo-RESOLVE project to investigate hypoglycaemia and its impact in diabetes. Over 600 participants with type 1 or insulin-treated type 2 diabetes were recruited across 9 UK and EU sites. For 10 weeks, participants wore a CGM and Fitbit and recorded episodes of hypoglycaemia using the Hypo-METRICS smartphone app. You can find more information in the protocols for the Hypo-METRICS study and Hypo-METRICS app.
What data can I analyse using the hypometrics package?
The hypometrics package offers tools to clean, check, analyse and visualise the following types of data:
1. Continuous Glucose Monitoring Data: more detail can be found here.
2. Physical Activity Data: more detail can be found here.
3. Sleep Data: more detail can be found here.
4. Person-Reported Hypoglycaemia Data: more detail can be found here.
Importantly, the package also allows the linkage and integration of the above described data, as shown here.
Installation
The package is available on GitHub and can be installed and downloaded by running:
install.packages("remotes")
remotes::install_github("leicester-cdag/hypometrics")Load the package every time you start R:
library(hypometrics)Documentation
The package documentation can be found here.
Contributing
We are happy to receive bug reports, suggestions and questions to fix problems and add features.
Here are some simple ways in which you can contribute (in the increasing order of commitment):
- Read and correct any inconsistencies in the documentation
- Raise issues about bugs or wanted features
- Review code