z-logo
Premium
Ventricular Contractility and Compliance Measured During Axial Flow Blood Pump Support: In Vitro Study
Author(s) -
Jhun ChoonSik,
Cysyk Joshua P.
Publication year - 2014
Publication title -
artificial organs
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.684
H-Index - 76
eISSN - 1525-1594
pISSN - 0160-564X
DOI - 10.1111/aor.12165
Subject(s) - cardiology , contractility , ventricular assist device , ventricle , compliance (psychology) , medicine , heart failure , diastole , cardiac output , hemodynamics , blood pressure , psychology , social psychology
Abstract End‐systolic elastance and end‐diastolic compliance have been used to quantify systolic and diastolic function of the left ventricle ( LV ). In this study, the effective end‐systolic elastance, ( E ES ) eff , end‐systolic volume intercept, ( V 0 ) eff , and end‐diastolic compliance of the LV were assessed at various levels of left ventricular assist device ( LVAD ) support. We tested the hypothesis that ( E ES ) eff and ( V 0 ) eff vary as a function of LVAD speed, while compliance does not change. The Penn State in vitro cardiac simulator was used in two heart conditions (control and heart failure [ HF ]) with the H eart M ate II axial flow LVAD . The LVAD speed was linearly increased from 6000 to 11 000 rpm, with 500‐rpm increments. The end‐systolic and end‐diastolic pressure–volume relationships were estimated at each LVAD speed. Acute LVAD support itself showed pseudo‐improvement of ventricular contractility. The ( E ES ) eff and ( V 0 ) eff in HF were found to be dependent on the LVAD speed. The effective compliance for both control and HF was independent of the LVAD speed. Therefore, when examining the time‐course cardiac recovery induced by the LVAD support, LV performance should be measured immediately before and after LVAD support while keeping LVAD speed consistent to avoid potential overestimation of long‐term cardiac recovery.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here