Deprecated: Return type of DrupalCacheArray::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/rprlib/prod72/www/includes/bootstrap.inc on line 362

Deprecated: Return type of DrupalCacheArray::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/rprlib/prod72/www/includes/bootstrap.inc on line 369

Deprecated: Return type of DrupalCacheArray::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/rprlib/prod72/www/includes/bootstrap.inc on line 381

Deprecated: Return type of DrupalCacheArray::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/rprlib/prod72/www/includes/bootstrap.inc on line 388
University of Oklahoma Health Sciences Center

Longitudinal Studies

×

Error message

  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_environment_initialize() (line 695 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_environment_initialize() (line 696 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_environment_initialize() (line 697 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_environment_initialize() (line 700 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_environment_initialize() (line 702 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in include_once() (line 328 of /home/rprlib/prod72/www/sites/default/settings.php).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in include_once() (line 329 of /home/rprlib/prod72/www/sites/default/settings.php).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in include_once() (line 337 of /home/rprlib/prod72/www/sites/default/settings.php).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in include_once() (line 344 of /home/rprlib/prod72/www/sites/default/settings.php).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_settings_initialize() (line 819 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in drupal_settings_initialize() (line 828 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Warning: session_name(): Session name cannot be changed after headers have already been sent in drupal_settings_initialize() (line 831 of /home/rprlib/prod72/www/includes/bootstrap.inc).
  • Deprecated function: Return type of DatabaseStatementBase::execute($args = [], $options = []) should either be compatible with PDOStatement::execute(?array $params = null): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2244 of /home/rprlib/prod72/www/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/rprlib/prod72/www/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/rprlib/prod72/www/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/rprlib/prod72/www/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/rprlib/prod72/www/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/rprlib/prod72/www/includes/database/database.inc).

Building a Group-Based Opioid Treatment (GBOT) blueprint: a qualitative study delineating GBOT implementation

Author/s: 
Sokol, R, Albanese, M, Chew, A, Early, J, Grossman, E, Roll, D, Sawin, G, Wu, DJ, Schuman-Olivier, Z

BACKGROUND:

Group-Based Opioid Treatment (GBOT) has recently emerged as a mechanism for treating patients with opioid use disorder (OUD) in the outpatient setting. However, the more practical "how to" components of successfully delivering GBOT has received little attention in the medical literature, potentially limiting its widespread implementation and utilization. Building on a previous case series, this paper delineates the key components to implementing GBOT by asking: (a) What are the core components to GBOT implementation, and how are they defined? (b) What are the malleable components to GBOT implementation, and what conceptual framework should providers use in determining how to apply these components for effective delivery in their unique clinical environment?

METHODS:

To create a blueprint delineating GBOT implementation, we integrated findings from a previously conducted and separately published systematic review of existing GBOT studies, conducted additional literature review, reviewed best practice recommendations and policies related to GBOT and organizational frameworks for implementing health systems change. We triangulated this data with a qualitative thematic analysis from 5 individual interviews and 2 focus groups representing leaders from 5 different GBOT programs across our institution to identify the key components to GBOT implementation, distinguish "core" and "malleable" components, and provide a conceptual framework for considering various options for implementing the malleable components.

RESULTS:

We identified 6 core components to GBOT implementation that optimize clinical outcomes, comply with mandatory policies and regulations, ensure patient and staff safety, and promote sustainability in delivery. These included consistent group expectations, team-based approach to care, safe and confidential space, billing compliance, regular monitoring, and regular patient participation. We identified 14 malleable components and developed a novel conceptual framework that providers can apply when deciding how to employ each malleable component that considers empirical, theoretical and practical dimensions.

CONCLUSION:

While further research on the effectiveness of GBOT and its individual implementation components is needed, the blueprint outlined here provides an initial framework to help office-based opioid treatment sites implement a successful GBOT approach and hence potentially serve as future study sites to establish efficacy of the model. This blueprint can also be used to continuously monitor how components of GBOT influence treatment outcomes, providing an empirical framework for the ongoing process of refining implementation strategies.

Estimates of all cause mortality and cause specific mortality associated with proton pump inhibitors among US veterans: cohort study

Author/s: 
Xie, Y, Bowe, B, Yan, Y, Xian, H, Li, T, Al-Aly, Z

OBJECTIVE:

To estimate all cause mortality and cause specific mortality among patients taking proton pump inhibitors (PPIs).

DESIGN:

Longitudinal observational cohort study.

SETTING:

US Department of Veterans Affairs.

PARTICIPANTS:

New users of PPIs (n=157 625) or H2 blockers (n=56 842).

MAIN OUTCOME MEASURES:

All cause mortality and cause specific mortality associated with taking PPIs (values reported as number of attributable deaths per 1000 patients taking PPIs).

RESULTS:

There were 45.20 excess deaths (95% confidence interval 28.20 to 61.40) per 1000 patients taking PPIs. Circulatory system diseases (number of attributable deaths per 1000 patients taking PPIs 17.47, 95% confidence interval 5.47 to 28.80), neoplasms (12.94, 1.24 to 24.28), infectious and parasitic diseases (4.20, 1.57 to 7.02), and genitourinary system diseases (6.25, 3.22 to 9.24) were associated with taking PPIs. There was a graded relation between cumulative duration of PPI exposure and the risk of all cause mortality and death due to circulatory system diseases, neoplasms, and genitourinary system diseases. Analyses of subcauses of death suggested that taking PPIs was associated with an excess mortality due to cardiovascular disease (15.48, 5.02 to 25.19) and chronic kidney disease (4.19, 1.56 to 6.58). Among patients without documented indication for acid suppression drugs (n=116 377), taking PPIs was associated with an excess mortality due to cardiovascular disease (22.91, 11.89 to 33.57), chronic kidney disease (4.74, 1.53 to 8.05), and upper gastrointestinal cancer (3.12, 0.91 to 5.44). Formal interaction analyses suggested that the risk of death due to these subcauses was not modified by a history of cardiovascular disease, chronic kidney disease, or upper gastrointestinal cancer. Taking PPIs was not associated with an excess burden of transportation related mortality and death due to peptic ulcer disease (as negative outcome controls).

CONCLUSIONS:

Taking PPIs is associated with a small excess of cause specific mortality including death due to cardiovascular disease, chronic kidney disease, and upper gastrointestinal cancer. The burden was also observed in patients without an indication for PPI use. Heightened vigilance in the use of PPI may be warranted.

Subscribe to Longitudinal Studies