Treatment patterns in patients with type 2 diabetes mellitus treated with glucagon‐like peptide‐1 receptor agonists: <scp>H</scp> igher adherence and persistence with dulaglutide compared with once‐weekly exenatide and liraglutide
Bibliographic record
Abstract
AIMS: To compare adherence (proportion of days covered [PDC]), persistence, and treatment patterns among patients with type 2 diabetes mellitus (T2DM) newly initiating glucagon-like peptide-1 receptor agonists (GLP-1RAs). More specifically, the main objectives were to compare dulaglutide vs exenatide once weekly and dulaglutide vs liraglutide. METHODS: Patients with T2DM newly initiating dulaglutide, albiglutide, exenatide once weekly, exenatide twice daily and liraglutide between November 2014 and April 2015 were hierarchically selected from Truven Health's MarketScan Research Databases. Propensity score matching was used to account for selection bias. Adherence to and persistence with the index GLP-1RA, and switching and augmentation patterns were assessed during the 6-month post-index period. RESULTS: Mean adherence for the matched cohorts was significantly higher for dulaglutide than for exenatide once weekly (0.72 vs 0.61; P < .0001) and liraglutide (0.71 vs 0.67; P < .0001). The percentage of patients achieving PDC ≥ 0.80 was significantly higher for dulaglutide compared with exenatide once weekly (54.2% vs 37.9%; P < .0001) and liraglutide (53.5% vs 44.3%; P < .0001). The mean (standard deviation) days on treatment for all matched patients was significantly higher for patients in the dulaglutide cohort compared with those in the exenatide once-weekly (148.4 [55.4] vs 123.6 [61.6]; P < .0001) and liraglutide cohorts (146.0 [56.9] vs 137.4 [60.1]; P < .0001). A significantly lower proportion of patients on dulaglutide discontinued treatment compared with those on exenatide once weekly (26.2% vs 48.4%; P < .0001) and those on liraglutide (28.0% vs 35.6%; P < .0001). CONCLUSIONS: Dulaglutide initiators had significantly higher adherence, were more persistent, and had lower discontinuation rates compared with initiators of exenatide once weekly or liraglutide during the 6-month follow-up period.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".