A PHP Error was encountered

Severity: Warning

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

Management of Penetrating Cardiac Injuries With Pericardial Window and Drainage in Select Patients. | LitMetric

AI Article Synopsis

Article Abstract

Background: Management of penetrating chest injuries with a positive pericardial window (PW) are presumed cardiac injuries and traditionally result in sternotomy. However, there is some evidence in the literature that select patients can be managed with PW, lavage, and drainage (PWLD).

Methods: All patients with penetrating chest trauma who underwent PW and/or sternotomy over a 5-year period were identified. Patients were stratified by operative intervention [PW + sternotomy vs PWLD] and compared. Multivariable logistic regression (MLR) analysis was performed to determine independent predictors of therapeutic sternotomy.

Results: Of the 146 patients who underwent PW and/or sternotomy included in the study, 126 patients underwent PW, 39 underwent sternotomy, and 10 underwent PWLD. There was no difference in demographics, LOS, ICU LOS, vent days, or mortality in patients who underwent PW + sternotomy, compared to patients who underwent PWLD. In the PWLD group, one patient returned to the OR for recurrent pericardial effusion and no patients required sternotomy. Multivariable logistic regression identified ISS as an independent predictor of therapeutic sternotomy (OR 1.160; 95% CI 1.006-1.338, P = .0616). Interestingly, positive FAST, significant CT findings, and trajectory were not predictors of therapeutic sternotomy. There were 7 patients with a left hemothorax and negative FAST found to have a positive PW and cardiac injury mandating sternotomy and repair.

Conclusion: Penetrating cardiac injury can be managed with PWLD in select patients. Positive FAST, significant findings on CT, and trajectory do not mandate sternotomy. A negative FAST in the setting of a hemothorax does not rule out a cardiac injury.

Download full-text PDF

Source
http://dx.doi.org/10.1177/00031348231157815DOI Listing

Publication Analysis

Top Keywords

patients underwent
16
select patients
12
cardiac injury
12
patients
11
sternotomy
11
management penetrating
8
penetrating cardiac
8
cardiac injuries
8
pericardial window
8
penetrating chest
8

Similar Publications

Background: The current guidelines recommend patient stratification based on transthoracic echocardiography (TTE) to identify individuals with potential pulmonary hypertension (PH). We validated the relationship between PH and the pulmonary artery diameter (PAD) on computed tomography (CT) with peak tricuspid regurgitant velocity (TRV) measured by TTE for referral of patients with suspected PH for TTE screening.

Methods: We performed a retrospective analysis of CT-based PAD of 2356 patients who underwent TTE from February 2, 2013 to December 25, 2019 at our institution.

View Article and Find Full Text PDF

Background: Laparoscopic sleeve gastrectomy (LSG) specimens are histologically analyzed to identify incidental pathologies. However, no guidelines recommend routine histology. This study evaluates the clinical utility of LSG sample analysis and if incidental diagnoses have a significant clinical impact.

View Article and Find Full Text PDF

To evaluate dual-layer dual-energy computed tomography (dlDECT)-based characterization of thrombus composition for differentiation of acute pulmonary embolism (PE) and chronic thromboembolic pulmonary hypertension (CTEPH). This retrospective single center cohort study included 49 patients with acute PE and 33 patients with CTEPH who underwent CT pulmonary angiography on a dlDECT from 06/2016 to 06/2022. Conventional images), material specific images (virtual non-contrast [VNC], iodine density overlay [IDO], electron density [ED]), and virtual monoenergetic images (VMI) were analyzed.

View Article and Find Full Text PDF

Purpose: Sulcus-deepening trochleoplasty (TP) effectively treats patellofemoral (PF) instability (PFI) caused by high-grade trochlear dysplasia (TD), but current evidence is based on small case series. We hypothesised, that TP would result in significant functional improvements and a low re-dislocation rate but would not accelerate the progression of PF cartilage deterioration.

Methods: We retrospectively reviewed all TP cases performed by a single surgeon between 2015 and 2021.

View Article and Find Full Text PDF

Leukaemia stem cells (LSCs) are major contributors to chemoresistance in acute myeloid leukaemia (AML). Identifying potential biomarkers within LSCs that can predict chemosensitivity in AML is key. This prospective study involved 20 consecutive de novo AML patients who underwent '7 + 3' induction therapy.

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!