A PHP Error was encountered

Severity: Warning

Message: fopen(/var/lib/php/sessions/ci_session1k6fc0vvqgg8kpafgpthjolslsc9ete9): 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

Pharmacotherapy for primary biliary cholangitis: an assessment of medication candidacy and rates of treatment. | LitMetric

Pharmacotherapy for primary biliary cholangitis: an assessment of medication candidacy and rates of treatment.

BMC Gastroenterol

Department of Medicine, Division of Gastroenterology and Hepatology, Thomas Jefferson University Hospital, 132 South 10th Street, Suite 480, 19107, Philadelphia, PA, USA.

Published: January 2024

AI Article Synopsis

Article Abstract

Background: Ursodeoxycholic acid is the preferred first-line therapy for primary biliary cholangitis. Alternative therapies, such as obeticholic acid, are recommended for patients who cannot tolerate ursodeoxycholic acid or who have an inadequate response to ursodeoxycholic acid monotherapy. Prior investigations have suggested that as many as 30% of patients with primary biliary cholangitis may have never received treatment with ursodeoxycholic acid. No prior investigations have examined usage rates of obeticholic acid in the treatment of primary biliary cholangitis.

Methods: All patients with an ICD-10 diagnosis of primary biliary cholangitis who had any records within the health system were included. A review of medical records was performed to confirm the diagnosis of primary biliary cholangitis and determine which medications had been prescribed for treatment, as well as candidacy for second-line therapies.

Results: A total of 495 patients met inclusion criteria. Notably, 95% of patients were taking ursodeoxycholic acid for treatment of their primary biliary cholangitis, with 67% of patients having disease that was well-controlled on ursodeoxycholic acid monotherapy. In total, 8% of patients were taking obeticholic acid (either as combination or monotherapy). Only 3% would benefit from the addition of a second line therapy but had not yet been offered medication. Only 3% of patients were not on any medication for management of their primary biliary cholangitis.

Conclusions: Ursodeoxycholic acid is a readily available and generally well-tolerated medication that should be offered to all patients with primary biliary cholangitis as first-line therapy. While prior investigations have suggested that up to 30% of patients with primary biliary cholangitis may never have received treatment for the disorder, the present study suggests that patients are generally being managed according to guidelines. Moreover, a significant proportion of patients with primary biliary cholangitis will qualify for second line therapies and prescribers should be aware of the indications to use these medications.

Download full-text PDF

Source
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC10768361PMC
http://dx.doi.org/10.1186/s12876-023-03108-4DOI Listing

Publication Analysis

Top Keywords

primary biliary
44
biliary cholangitis
36
ursodeoxycholic acid
28
patients primary
16
obeticholic acid
12
patients
12
prior investigations
12
biliary
11
acid
10
primary
10

Similar Publications

Background & Aims: Approximately 40% of patients with Primary Biliary Cholangitis (PBC) show incomplete response to ursodeoxycholic acid, thus needing second-line treatment to prevent disease progression. As no head-to-head comparison study is available, we used a network meta-analysis (NMA) to compare efficacy and safety of available second-line therapies.

Methods: We performed a systematic literature review including randomised, placebo-controlled trials of patients with PBC and incomplete response, or intolerance, to ursodeoxycholic acid, and compared relative risks (RRs) for primary (biochemical response at 52-week) and secondary outcomes [incidence of new-onset pruritus and serious adverse events (SAEs)].

View Article and Find Full Text PDF

Introduction: Biliary tract cancer (BTC) originates from the biliary epithelium of the small ducts within the liver (intrahepatic cholangiocarcinoma, IHCC), the main ducts of the hilum (extrahepatic cholangiocarcinoma, EHCC), or in the gallbladder (gallbladder cancer, GC). Due to presentation with nonspecific symptoms as well as absence of screening, most patients present with advanced disease and unfavorable prognosis.

Areas Covered: The ABC-02 trial established the current first-line chemotherapy with gemcitabine/platinum for advanced BTC in 2010.

View Article and Find Full Text PDF

Biliary sepsis, characterized by contamination and infection of the biliary tract, poses a serious medical issue with detrimental effects on the patients. While cholecystectomy is the usual treatment for symptomatic gallstones, the most desirable management approach for biliary sepsis remains debated, prompting a scientific evaluation of the long-term effects of cholecystectomy. To compare the long-term outcomes of biliary sepsis in patients undergoing cholecystectomy versus conservative management (CM), this study will systematically review the existing literature to clarify differences in recurrence rates, complication rates, and overall survival.

View Article and Find Full Text PDF

Background And Aims: Malignant biliary strictures (MBS) pose diagnostic and therapeutic challenges due to the frequent indeterminate results after initial sampling. Next generation sequencing (NGS) panel (BiliSeq) offers promise in MBS detection, but real-world performance remains uncertain. This study aimed to assess standard sampling techniques alone and with BiliSeq for malignancy detection in biliary strictures, and to evaluate management changes based on NGS.

View Article and Find Full Text PDF

Background/purpose: The Japanese public health insurance system has recently covered robotic pancreaticoduodenectomy (RPD). This study aimed to review the results of RPD during the introductory period and elucidate its safety and feasibility in Japan.

Methods: Consecutive data of 425 patients who underwent RPD were retrospectively collected from 10 high-volume centers in Japan between April 2020 and September 2022.

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!