Pith. sign in

REVIEW 3 major objections 6 minor 9 references

AZT1D: A Real-World Dataset for Type 1 Diabetes

T0 review · 3 major / 6 minor · reviewed 2026-08-07 · deepseek-v4-flash

Pith's one-line read The paper introduces AZT1D, a public real-world dataset of 25 people with type 1 diabetes using automated insulin delivery, with continuous glucose, insulin, carb, and device-mode data, and claims it is the only public dataset with such…

desk verdict AZT1D's bolus-level detail is genuinely useful, but the unvalidated OCR pipeline and internally inconsistent duration figures need to be fixed before the derived columns can be trusted. read the letter →

arxiv 2506.14789 v1 pith:GQWVOCF7 submitted 2025-05-27 cs.LG q-bio.QM

classification cs.LGq-bio.QM
keywords type1diabetesautomatedinsulindeliverycontinuousglucosemonitoringbolusreal-worlddatasetmachinelearningopticalcharacterrecognitiondevicemode
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

The paper introduces AZT1D, a publicly released dataset of 25 people with type 1 diabetes who use automated insulin delivery systems. It unifies continuous glucose readings, insulin administration logs, carbohydrate entries, and device modes into a single timestamped timeseries spanning several weeks per patient. The authors' central claim is that AZT1D is the only public dataset with granular bolus insulin detail—total dose, bolus type, and the correction-specific portion of each event. That matters because such linked, real-world data is what machine-learning models need for personalized dosing advice and glucose prediction.

What carries the argument

The central object is the AZT1D dataset itself, a structured timeseries in which each row carries an event timestamp, device mode, basal insulin rate, bolus type, correction-delivered portion, total bolus insulin, food-delivered portion, carbohydrate size, and CGM glucose value. Two mechanisms build it: timestamp alignment that merges the pump's five-minute glucose readings with the pump's event logs and carb entries, and an OCR-with-coordinate-cropping pipeline that extracts hourly basal rates and device modes from clinic PDF reports. The granular bolus fields are what the paper argues no other public dataset provides.

What would settle it

Re-extract the hourly basal rates and device modes from a random sample of the original clinic PDF reports using independent manual transcription or a second OCR tool, then compare against the published dataset; a mismatch rate above a few percent would show the dataset is not as cleanly structured as claimed.

Watch

Extended reading notes

Core claim

On its own terms, the contribution is a new resource rather than a new finding about diabetes. AZT1D contains 320,488 continuous glucose monitoring entries collected over a combined 26,707 hours, alongside insulin delivery events, carbohydrate sizes, and a device-mode label for each record. The paper's distinctive assertion is that this is the only publicly available dataset with this level of detail on bolus insulin events, separating standard, correction, and automatic boluses and reporting the correction and food portions of each dose. To create the dataset, the authors aligned timestamps across data sources and used optical character recognition on clinic-generated PDF reports to recover hourly basal rates and device modes. Their aggregate analysis of patients 65 and older shows hyperglycemia rising through the day to peak in the evening and hypoglycemia most frequent in the early morning.

Load-bearing premise

The dataset's basal rates and device-mode labels come from an OCR and cropping pipeline on clinic PDF reports, so any systematic OCR error or timestamp misalignment would propagate into every field derived from those PDFs.

Editorial extensions

If this is right

  • Machine-learning models for glucose prediction and insulin dosing can now be trained on naturalistic multi-week data instead of simulated or small-cohort datasets.
  • The correction/food split of bolus events enables counterfactual recommendation systems that tell patients how to change dosing or meals to avoid hyperglycemia.
  • The temporal pattern seen in elderly patients—evening hyperglycemia and early-morning hypoglycemia—points toward time-specific monitoring and management strategies.
  • The dataset's temporal structure is suitable for offline reinforcement learning to learn personalized insulin policies from historical records.
  • Expanding the cohort to about 100 patients is planned, which would strengthen the generalizability of conclusions drawn from AZT1D.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • Because the two cited validation studies were run on this same dataset, their reported gains (76.6 percent valid counterfactual explanations and a 23 percent RMSE reduction in glucose prediction) inherit any errors in the OCR extraction and timestamp alignment.
  • The uniqueness claim is time-limited: new public datasets with equally detailed bolus fields would undo it, so the claim should be understood as a statement about the current landscape.
  • A directly testable extension would be an ablation study that trains glucose-prediction models with and without the device-mode and correction-delivered fields to quantify how much these novel fields actually improve accuracy.
  • If the OCR pipeline ever fails on a subgroup of patients, analyses restricted to the CSV-derived fields (CGM, bolus logs, carb sizes) would remain reliable, making it worth reporting which fields depend on the PDF extraction.
Share X Bluesky LinkedIn Reddit HN

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

3 major / 6 minor

Summary. AZT1D is presented as a publicly available real-world dataset from 25 individuals with type 1 diabetes using automated insulin delivery (Tandem t:slim X2 with Control IQ and Dexcom G6 Pro CGM). The dataset contains CGM readings, bolus insulin logs with detailed type and correction-specific amounts, carbohydrate entries, basal rates, and device mode classifications. The paper describes the study design, the OCR-based preprocessing pipeline for extracting basal rates and device modes from clinic PDFs, the dataset schema, and a basic statistical analysis of glycemic events in elderly patients. Two prior studies by the authors are cited as use cases of the dataset. The abstract and introduction claim that this is the only publicly available dataset with this level of bolus-event detail.

Significance. If the dataset is properly validated, it is a useful contribution to the T1D machine-learning community. The granular bolus fields (total dose, bolus type, correction-specific amounts) are indeed rare in public datasets, and the multi-week real-world collection with device-mode context supports a range of ML tasks. The authors also share demographic and clinical data and state an intention to release daily and monthly visualizations, which aids reproducibility. The paper's main value, however, depends on the reliability of the derived basal-rate and device-mode columns and on the accuracy of the reported dataset statistics. Those points are not yet established, so the contribution is currently conditional on additional validation.

major comments (3)
  1. [Section II / Abstract] The reported duration is internally inconsistent. The abstract says data were obtained over 6 to 8 weeks per patient, Section II says participants contributed data over an average duration of 26 days, and the reported 320,488 CGM entries at 5-minute intervals total 26,707 hours, which implies about 44.5 days per patient on average. Please reconcile these numbers, clarify what the 26-day figure refers to, and report the exact per-patient minimum, maximum, and median observation windows. The multi-week coverage is a central selling point and must be accurately described.
  2. [Section III-A] The OCR-based extraction of basal rates and device modes from clinic PDFs is not validated. The paper states that these fields are obtained by cropping informative regions and applying OCR, but it provides no manual audit, OCR error rate, or comparison against original pump exports. This is load-bearing because device mode in Tandem t:slim X2 reports is rendered graphically as shaded intervals, so character recognition alone may not reliably assign regular/sleep/exercise labels, and an error in an hourly basal value propagates to 12 five-minute records. Please add a validation subsection that reports error rates, describes how the graphical device-mode regions were segmented and verified, and shows agreement against a ground-truth subset.
  3. [Section IV] The statistical analysis reports durations and percentages of hyperglycemia and hypoglycemia without defining the glucose thresholds used to classify these events. For example, the statement that hyperglycemia accounted for 28.6% of evening time is not interpretable unless the reader knows whether the threshold is, say, >180 mg/dL or another value. Please state explicit thresholds for hypo- and hyperglycemia (e.g., <70 mg/dL and >180 mg/dL, following standard CGM consensus) and cite the relevant clinical definitions. The same definitions must be applied consistently in Figure 3 and in any released per-patient summaries.
minor comments (6)
  1. [Abstract] There is a missing space in 'we presentAZT1D' in the abstract.
  2. [Section III-A] The phrase 'O pticalC haracterR ecognition' has unintended spacing; please write 'OCR' or 'Optical Character Recognition' with normal spacing.
  3. [Table I] The demographic table lacks a caption and a definition of the A1c column; please add a caption and state that A1c is measured in percentage (DCCT units).
  4. [Section IV] The 'monthly report' mentioned in the text is not shown or referenced to a repository location; please indicate where these materials are available or remove the claim.
  5. [Figure 3] Figure 3 has no axis labels; please add a y-axis label such as 'Total duration (minutes)' and clarify in the caption that 'elderly' is defined as age ≥65 years and how many patients are included.
  6. [Section V] References [7] and [8] are prior works by the same group that used this dataset; please state explicitly that these are applications of AZT1D rather than independent validations, so readers can calibrate the reported 76.6%/86% and RMSE/MAE improvements.

Circularity Check

0 steps flagged · score 2.0 of 10

No significant circularity: AZT1D is a dataset artifact, and the only self-citations in the Use Cases section are applications of the dataset, not inputs to its construction.

full rationale

The paper's central contribution is a dataset artifact, not a derived prediction, so the standard circularity patterns do not apply. The construction chain in Section III-A converts raw CGM CSV records and pump PDF records into a unified time series via timestamp alignment and OCR; these preprocessing steps are not fitted to, or defined in terms of, any downstream result. The statistical analyses in Section IV are descriptive summaries of the same data, and the paper does not claim to predict those summaries from independent variables. The Use Cases section cites two prior papers by the same authors ([7] and [8]) that used this dataset; those self-citations are illustrative applications and are not load-bearing for the dataset's existence, structure, or claims of completeness. The statement that AZT1D is the only publicly available dataset with this level of bolus detail is a novelty claim based on the authors' knowledge, not a result derived from the dataset, so it cannot reduce to its own input. Separately, the unvalidated OCR extraction of basal rates and device modes, and the apparent inconsistency between the stated 26-day average duration and the total hours/CGM entries, are correctness and validation concerns rather than circularity concerns. Accordingly, the appropriate circularity score is low, reflecting only the minor non-load-bearing self-citation in the use-case demonstration.

Assumptions & free parameters 1 free parameters · 4 assumptions · 0 invented entities

The dataset release rests primarily on the assumption that the data extraction and recording pipeline is error-free. No free parameters are fitted, but the unstated glucose thresholds in the statistical analyses are the only hand-chosen numerical inputs. The paper introduces no new theoretical entities.

free parameters (1)
  • Glucose thresholds for hyper/hypoglycemia = not stated
    Section IV reports durations of hyperglycemia and hypoglycemia but never specifies the glucose cutoffs (e.g., 70 mg/dL and 180 mg/dL). The reported percentages depend on these unstated values.
assumptions (4)
  • domain assumption OCR of pump PDFs captures basal rates and device modes accurately
    Section III-A relies on OCR after cropping PDF regions; no validation is provided, so any OCR error becomes data error.
  • domain assumption CGM readings are reliable and sampled every 5 minutes
    The total number of CGM entries is used to compute monitoring hours; this assumes regular 5-minute sampling with no data loss.
  • domain assumption Insulin pump logs and carbohydrate entries reflect actual patient behavior
    The dataset treats recorded boluses, carb sizes, and device modes as ground truth for real-world behavior, with no verification against other sources.
  • domain assumption The eligibility criteria define a representative AID-user population
    Section II limits inclusion to T1D patients using a Tandem pump in Control IQ; this restricts generalizability to the broader T1D population.

how reviews work

0 comments
Cite this review

Pith. "Pith review of AZT1D: A Real-World Dataset for Type 1 Diabetes." pith.science (2026). https://pith.science/paper/GQWVOCF7

@misc{pith2026250614789,
  author       = {Pith},
  title        = {Pith review of: AZT1D: A Real-World Dataset for Type 1 Diabetes},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/GQWVOCF7}},
  note         = {Machine review of arXiv:2506.14789}
}
read the original abstract

High quality real world datasets are essential for advancing data driven approaches in type 1 diabetes (T1D) management, including personalized therapy design, digital twin systems, and glucose prediction models. However, progress in this area has been limited by the scarcity of publicly available datasets that offer detailed and comprehensive patient data. To address this gap, we present AZT1D, a dataset containing data collected from 25 individuals with T1D on automated insulin delivery (AID) systems. AZT1D includes continuous glucose monitoring (CGM) data, insulin pump and insulin administration data, carbohydrate intake, and device mode (regular, sleep, and exercise) obtained over 6 to 8 weeks for each patient. Notably, the dataset provides granular details on bolus insulin delivery (i.e., total dose, bolus type, correction specific amounts) features that are rarely found in existing datasets. By offering rich, naturalistic data, AZT1D supports a wide range of artificial intelligence and machine learning applications aimed at improving clinical decision making and individualized care in T1D.

Figures

Figures reproduced from arXiv: 2506.14789 by the authors.

Figure 1
Figure 1. Basal rate and the device mode extraction from the PDFs using OCR and coordinate system. [PITH_FULL_IMAGE:figures/full_fig_p002_1.png] view at source ↗
Figure 2
Figure 2. Daily CGM readings with annotated insulin and food events, and providing a summary of glucose trends and variability. [PITH_FULL_IMAGE:figures/full_fig_p003_2.png] view at source ↗
Figure 3
Figure 3. Total duration of hypoglycemia and hyperglycemia events across four [PITH_FULL_IMAGE:figures/full_fig_p004_3.png] view at source ↗

Discussion (0). Sign in to comment.

Reference graph

Works this paper leans on

9 extracted references · 8 canonical work pages

  1. [1]

    11em plus .33em minus .07em 4000 4000 100 4000 4000 500 `\.=1000 = #1 \@IEEEnotcompsoconly \@IEEEcompsoconly #1 * [1] 0pt [0pt][0pt] #1 * [1] 0pt [0pt][0pt] #1 * \| ** #1 \@IEEEauthorblockNstyle \@IEEEcompsocnotconfonly \@IEEEauthorblockAstyle \@IEEEcompsocnotconfonly \@IEEEcompsocconfonly \@IEEEauthordefaulttextstyle \@IEEEcompsocnotconfonly \@IEEEauthor...

  2. [2]

    M. A. Atkinson, G. S. Eisenbarth, and A. W. Michels, ``Type 1 diabetes,'' The lancet, vol. 383, no. 9911, pp. 69--82, 2014

  3. [3]

    Control, C

    D. Control, C. T. of Diabetes Interventions, and C. D. S. R. Group, ``Intensive diabetes treatment and cardiovascular disease in patients with type 1 diabetes,'' New England Journal of Medicine, vol. 353, no. 25, pp. 2643--2653, 2005

  4. [4]

    DeSalvo and B

    D. DeSalvo and B. Buckingham, ``Continuous glucose monitoring: current use and future directions,'' Current diabetes reports, vol. 13, pp. 657--662, 2013

  5. [5]

    Limbert, A

    C. Limbert, A. J. Kowalski, and T. P. Danne, ``Automated insulin delivery: A milestone on the road to insulin independence in type 1 diabetes,'' Diabetes Care, vol. 47, no. 6, pp. 918--920, 2024

  6. [6]

    Marling and R

    C. Marling and R. Bunescu, ``The ohiot1dm dataset for blood glucose level prediction: Update 2020,'' in CEUR workshop proceedings, vol. 2675, 2020, p. 71

  7. [7]

    J. I. Hidalgo, J. Alvarado, M. Botella, A. Aramendi, J. M. Velasco, and O. Garnica, ``Hupa-ucm diabetes dataset,'' Data in Brief, vol. 55, p. 110559, 2024

  8. [8]

    Arefeen, S

    A. Arefeen, S. Khamesian, M. A. Grando, B. Thompson, and H. Ghasemzadeh, ``Glyman: Glycemic management using patient-centric counterfactuals,'' in 2024 IEEE EMBS International Conference on Biomedical and Health Informatics (BHI). 1em plus 0.5em minus 0.4em IEEE, 2024, pp. 1--5

Show all 9 references
  1. [9]

    Khamesian, A

    S. Khamesian, A. Arefeen, A. Grando, B. Thompson, and H. Ghasemzadeh, ``Type 1 diabetes management using glimmer: Glucose level indicator model with modified error rate,'' arXiv preprint arXiv:2502.14183, 2025

Pith tools

Reviewed August 7, 2026 · model on record in the stance chip above.