stanford-tide-dashboard
importedsoftware/stanford-tide-dashboard
Continuous glucose monitoring dashboard for algorithm-enabled prioritizations of patients with type 1 diabetes.
Machine-generated from the listed sources and not yet reviewed by a human.
- Category
- Software & Systems
- Subcategory
- unknown
- License
- GPL-3.0(osi)
- Status
- dormant
- Maturity
- deployed
- Organization
- unknown
- Country
- unknown
- Documentation
- unknown
- Tags
- continuous-glucose-monitoring · diabetes · health-informatics · plotly · plotly-dash · python
- Regulatory
- unknown
Top contributors by commit count, from the project’s public repository. Avatars are served by their origin, not stored here. To be removed from this list, open an issue.
Computed from shared tags, weighted so a rare tag counts for more than a common one. These are suggestions, not curated relationships.
- stanford-hypoglycemia-forecastingcontinuous-glucose-monitoring · diabetes · health-informatics
A machine learning model for week-ahead hypoglycemia prediction from continuous glucose monitoring data.
- agp_toolcontinuous-glucose-monitoring · diabetes
Ambulatory glucose profile analysis tool
- Glucodashdiabetes · plotly
A Blood Glucose data visualization tool.
- molplotlyplotly-dash
add-on to plotly which show molecule images on mouseover!
- CGMIconcontinuous-glucose-monitoring
Show blood sugar and trend arrow (pulled from Nightscout) as icon in the windows system tray
- dexta-intelligencecontinuous-glucose-monitoring
Self-hosted agentic harness for diabetic patients. Connect CGM, pump & wearables; discover why patterns happen with AI agents. Your data stays on your machine.
- api.github.com/repos/flaviagiammarino/stanford-tide-dashboardretrieved 2026-08-05 · via github-api
Machine-imported from GitHub search. Last push 2023-11-12, 5 stars, license reported as GPL-3.0. Category and schematic were assigned by keyword heuristics and are unreviewed.
Not yet verified by a human. Correct this record →
/v1/entries/38.json→ .entries["stanford-tide-dashboard"]
Entries are sharded 64 ways by a stable hash of the id, so a consumer can find any record without an index.