Key result
3D heart models outperform 2D cultures for cardiovascular disease modeling and drug screening.
Answers are grounded in this paper and cite their sources.
In vitro modelling the complex (patho-) physiological conditions of the heart is a major challenge in cardiovascular research. In recent years, methods based on three-dimensional (3D) cultivation approaches have steadily evolved to overcome the major limitations of conventional adherent two-dimensional (2D) monolayer cultivation. These 3D approaches aim to study, reproduce or modify fundamental native features of the heart such as tissue organization and cardiovascular microenvironment. Therefore, these systems have great potential for (patient-specific) disease research, for the development of new drug screening platforms, and for the use in regenerative and replacement therapy applications. Consequently, continuous improvement and adaptation is required with respect to fundamental limitations such as cardiomyocyte maturation, scalability, heterogeneity, vascularization, and reproduction of native properties. In this review, 2D monolayer culturing and the 3D in vitro systems of cardiac spheroids, organoids, engineered cardiac microtissue and bioprinting as well as the ex vivo technique of myocardial slicing are introduced with their basic concepts, advantages, and limitations. Furthermore, recent advances of various new approaches aiming to extend as well as to optimize these in vitro and ex vivo systems are presented.
No takes yet. Share an insight, caveat, or question.
Mohr et al. (2022) conducted a review in Cardiovascular disease. 3D in vitro and ex vivo heart models (cardiac spheroids, organoids, engineered cardiac microtissue, bioprinting, myocardial slicing) vs. 2D monolayer culturing was evaluated. 3D heart models and myocardial slicing advance over 2D monolayer cultures for disease research and drug screening, though this review reports no quantitative clinical outcomes.
Synapse has enriched 10 related papers. Consider them for comparative context: