A PHP Error was encountered

Severity: Warning

Message: fopen(/var/lib/php/sessions/ci_sessionb9jkgc0hugkchd8g1lnvj2anej1bjf59): Failed to open stream: No space left on device

Filename: drivers/Session_files_driver.php

Line Number: 177

Backtrace:

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Failed to read session data: user (path: /var/lib/php/sessions)

Filename: Session/Session.php

Line Number: 137

Backtrace:

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated

Filename: models/Detail_model.php

Line Number: 71

Backtrace:

File: /var/www/html/application/models/Detail_model.php
Line: 71
Function: strpos

File: /var/www/html/application/controllers/Detail.php
Line: 252
Function: insertAPISummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated

Filename: helpers/my_audit_helper.php

Line Number: 8919

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 8919
Function: str_replace

File: /var/www/html/application/controllers/Detail.php
Line: 255
Function: formatAIDetailSummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

Efficacy and Safety of Insulin Glargine 300 U/mL Versus Insulin Glargine 100 U/mL in High-Risk and Low-Risk Patients with Type 2 Diabetes Stratified Using Common Clinical Performance Measures. | LitMetric

AI Article Synopsis

Article Abstract

Background: To determine whether previously reported reductions in hypoglycemia associated with insulin glargine 300 U/mL (Gla-300) compared with insulin glargine 100 U/mL (Gla-100) are impacted by patient risk category in type 2 diabetes (T2D), clinical performance measures based on the Healthcare Effectiveness Data and Information Set (HEDIS) were applied to patient-level data from the EDITION 2 and EDITION 3 clinical trials that compared Gla-300 and Gla-100.

Methods: In this post hoc analysis, patients were stratified as low risk (LR) if patients were <65 years old with no comorbidities derived from HEDIS (HbA1c target <7.0% [53 mmol/mol]), or as high risk (HR) if patients were either ≥65 years old or had one or more HEDIS-defined comorbidities (HbA1c target <8.0% [64 mmol/mol]). Primary endpoint was a composite of patients achieving HbA1c target without confirmed or severe hypoglycemia over 6 months in the different treatment groups in each of the EDITION trials.

Results: There was a statistically nonsignificant trend of more patients treated with Gla-300 achieving the composite endpoint compared with Gla-100 in both the LR and HR patient cohorts, regardless of prior insulin experience. A similar trend was observed for the composite endpoint of HbA1c target without nocturnal hypoglycemia.

Conclusions: There is a consistent, nonsignificant trend suggesting that Gla-300 might reduce the burden of hypoglycemia compared with Gla-100 in patients with T2D irrespective of whether they are classed as LR or HR based on age- and National Committee for Quality Assurance Healthcare Effectiveness Data and Information Set-derived comorbidities.

Download full-text PDF

Source
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC5444481PMC
http://dx.doi.org/10.1089/dia.2016.0454DOI Listing

Publication Analysis

Top Keywords

insulin glargine
16
type diabetes
8
clinical performance
8
performance measures
8
efficacy safety
4
insulin
4
safety insulin
4
glargine
4
glargine 300
4
300 u/ml
4

Similar Publications

Cell-Based Assays to Detect Innate Immune Response Modulating Impurities: Application to Biosimilar Insulin.

AAPS J

December 2024

Laboratory of Immunology, Office of Pharmaceutical Quality Research Division-IV, Office of Pharmaceutical Quality, Center for Drug Evaluation and Research, Food and Drug Administration, Silver Spring, MD, 20993, USA.

Characterizing and mitigating factors that impact product immunogenicity can aid in risk assessment and/or managing risk following manufacturing changes. For follow-on products that have the same indication, patient population, and active product ingredient, the residual immunogenicity risk resides predominantly on differences in product and process related impurities. Characterizing differences in innate immune modulating impurities (IIRMI), which could act as adjuvants by activating local antigen presenting cells (APCs), can inform the immunogenicity risk assessment potentially reducing the need for clinical trials.

View Article and Find Full Text PDF

Introduction: ONWARDS 5 evaluated the effectiveness and safety of insulin icodec (icodec) titrated with a dosing guide app (icodec with app) versus once-daily insulin analogs in insulin-naive adults with type 2 diabetes. The insulin glargine U300 (glargine U300) stratum was too small to enable a robust post hoc efficacy comparison. Augmentation methodology was applied to increase the glargine U300 group size using real-world data (RWD), to facilitate efficacy comparisons of icodec with app versus glargine U300, and to demonstrate the potential of the augmentation methodology to strengthen underpowered treatment comparisons (AUGMENT study).

View Article and Find Full Text PDF

Aims: To evaluate the efficacy and safety of insulin glargine 300 U/mL (Gla-300) in people with uncontrolled type 2 diabetes (T2D) switching from another basal insulin (BI).

Materials And Methods: INITIATION was an interventional, single-arm, phase IV study conducted in China. In this post hoc subpopulation analysis, the efficacy and safety of switching to Gla-300 was investigated in individuals with uncontrolled T2D (HbA1c 7.

View Article and Find Full Text PDF

Objective: No meta-analysis has been published comparing the efficacy and safety of tirzepatide versus once-daily basal insulins in subjects with type 2 diabetes (T2D) inadequately controlled with oral anti-hyperglycemic drugs (OADs). This meta-analysis was conducted to address this knowledge gap.

Methods: Randomized controlled trials (RCTs) involving subjects with T2D inadequately controlled with OADs and receiving tirzepatide in intervention arm and basal insulins in control arm as add-on therapy were searched throughout the electronic databases.

View Article and Find Full Text PDF

Introduction: Insulin icodec is a basal insulin designed for once-weekly administration. This study assessed the pharmacological properties of icodec in Japanese individuals with type 1 diabetes (T1D).

Materials And Methods: In a randomized, open-label, crossover study, 24 Japanese individuals with T1D (20-64 years; glycated hemoglobin ≤9.

View Article and Find Full Text PDF

Want AI Summaries of new PubMed Abstracts delivered to your In-box?

Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!