Escalation and De-escalation of Temporary Mechanical Circulatory Support: Joint Consensus Report of the PeriOperative Quality Initiative and the Enhanced Recovery After Surgery Cardiac Society.

BACKGROUND

Temporary mechanical circulatory support (tMCS) for cardiogenic shock (CS) is increasing despite knowledge gaps and variations in management practices. This document was created to provide clinicians with guidance regarding initiation, escalation, and de-escalation of tMCS in patients with CS.

METHODS

An interdisciplinary, international expert panel using a structured literature appraisal and modified Delphi method derived consensus statements regarding triggers for prompt patient assessment and initiating tMCS in CS, assessing adequacy of support, readiness for tMCS weaning, and next steps in nonrecovery. Individual statements were graded on the basis of the quality of available evidence.

RESULTS

The panel addressed 4 main questions aimed at initiation, escalation, and de-escalation of tMCS. On the basis of available literature review and expert consensus, 11 recommendations were formulated. Key principles included recognition of the need for patients with CS who have ongoing hemodynamic compromise, tissue hypoperfusion, and metabolic derangements to be considered for early tMCS initiation. An interdisciplinary shock team should be involved in management, with early referral when patient conditions require care beyond center capabilities. Discussions providing anticipatory guidance should be performed with patients and decision makers before initiating tMCS. Management of tMCS involves frequent, timely hemodynamic and tissue perfusion reassessments to determine the need for escalation or weaning. For patients unable to be weaned from tMCS, evaluation should include interdisciplinary assessment for advanced therapies, with palliation included as a consideration in care discussions.

CONCLUSIONS

A practical guide to initiation, escalation, and de-escalation of tMCS is provided. Center-specific approaches that are based on local capabilities should be implemented.