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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Background: When performing transcatheter left atrial appendage (LAA) closure, peridevice leaks and device-related thrombus (DRT) have been associated with worse clinical outcomes-hence, their risk should be mitigated.
Objectives: The authors sought to assess whether use of preprocedural computational modeling impacts procedural efficiency and outcomes of transcatheter LAA closure.
Methods: The PREDICT-LAA trial (NCT04180605) is a prospective, multicenter, randomized trial in which 200 patients were 1:1 randomized to standard planning vs cardiac computed tomography (CT) simulation-based planning of LAA closure with Amplatzer Amulet. The artificial intelligence-enabled CT-based anatomical analyses and computer simulations were provided by FEops (Belgium).
Results: All patients had a preprocedural cardiac CT, 197 patients underwent LAA closure, and 181 of these patients had a postprocedural CT scan (standard, n = 91; CT + simulation, n = 90). The composite primary endpoint, defined as contrast leakage distal of the Amulet lobe and/or presence of DRT, was observed in 41.8% in the standard group vs 28.9% in the CT + simulation group (relative risk [RR]: 0.69; 95% CI: 0.46-1.04; P = 0.08). Complete LAA closure with no residual leak and no disc retraction into the LAA was observed in 44.0% vs 61.1%, respectively (RR: 1.44; 95% CI: 1.05-1.98; P = 0.03). In addition, use of computer simulations resulted in improved procedural efficiency with use of fewer Amulet devices (103 vs 118; P < 0.001) and fewer device repositionings (104 vs 195; P < 0.001) in the CT + simulation group.
Conclusions: The PREDICT-LAA trial demonstrates the possible added value of artificial intelligence-enabled, CT-based computational modeling when planning for transcatheter LAA closure, leading to improved procedural efficiency and a trend toward better procedural outcomes.
Download full-text PDF |
Source |
---|---|
http://dx.doi.org/10.1016/j.jcin.2023.01.008 | DOI Listing |
Eur Heart J Case Rep
December 2024
Department of Cardiology, Klinik Floridsdorf, Brünner Straße 68, 1210 Vienna, Austria.
Tex Heart Inst J
December 2024
Electrophysiology Clinical Research & Innovations, The Texas Heart Institute, Houston, Texas.
Clin Case Rep
December 2024
Department of Cardiothoracic Surgery HonorHealth Scottsdale Arizona USA.
Patent foramen ovale (PFO) closure using percutaneous devices, such as the Amplatzer occluder, is a common treatment for patients with a history of cryptogenic stroke or transient ischemic attack (TIA). Although generally well-tolerated, some patients may develop adverse reactions to the device materials, particularly in the presence of a nickel allergy. Symptoms can include chest pain, rashes, and migraines, which may necessitate surgical removal of the device.
View Article and Find Full Text PDFJ Clin Med
December 2024
Department of Cardiovascular Surgery and Transplantology, Institute of Cardiology, Jagiellonian University Medical College, St. John Paul II Hospital, 31-202 Krakow, Poland.
In patients with atrial fibrillation and contraindications for oral anticoagulation, in which an increased risk of stroke remains, a left atrial appendage exclusion should be considered for elimination, because the left atrial appendage is the most common site of thrombus. The aim of this study is to present the first-in-human study results of the Sierra Aegis Left Atrial Appendage Ligation System, a new epicardial-only left atrial appendage closure system. This study was a prospective, first-in-human, single-center study evaluating the effectiveness and safety of the Sierra Aegis Left Atrial Appendage Ligation System device for epicardial left atrial appendage closure.
View Article and Find Full Text PDFKyobu Geka
October 2024
Department of Cardiovascular Surgery, Nakadori General Hospital, Akita, Japan.
Left atrial appendage closure is widely performed in cardiac surgery to prevent intracardiac thrombus in patients with atrial fibrillation. Herein, we report the surgical case of an 80-year-old man whose left atrial appendage became aneurysmic long after undergoing suture exclusion. At the age of 67, he underwent mitral valve annuloplasty and left atrial appendage suture exclusion for mitral regurgitation and chronic atrial fibrillation at our institution.
View Article and Find Full Text PDFEnter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!