<HashMap><database>biostudies-literature</database><scores/><additional><omics_type>Unknown</omics_type><volume>97(4)</volume><submitter>Bom MJ</submitter><pubmed_abstract>&lt;h4>Objectives&lt;/h4>This study aimed to investigate the performance of computed tomography derived fractional flow reserve based interactive planner (FFR&lt;sub>CT&lt;/sub> planner) to predict the physiological benefits of percutaneous coronary intervention (PCI) as defined by invasive post-PCI FFR.&lt;h4>Background&lt;/h4>Advances in FFR&lt;sub>CT&lt;/sub> technology have enabled the simulation of hyperemic pressure changes after virtual removal of stenoses.&lt;h4>Methods&lt;/h4>In 56 patients (63 vessels) invasive FFR measurements before and after PCI were obtained and FFR&lt;sub>CT&lt;/sub> was calculated using pre-PCI coronary CT angiography. Subsequently, FFR&lt;sub>CT&lt;/sub> and invasive coronary angiography models were aligned allowing virtual removal of coronary stenoses on pre-PCI FFR&lt;sub>CT&lt;/sub> models in the same locations as PCI was performed. Relationships between invasive FFR and FFR&lt;sub>CT&lt;/sub> , between post-PCI FFR and FFR&lt;sub>CT&lt;/sub> planner, and between delta FFR and delta FFR&lt;sub>CT&lt;/sub> were evaluated.&lt;h4>Results&lt;/h4>Pre PCI, invasive FFR was 0.65 ± 0.12 and FFR&lt;sub>CT&lt;/sub> was 0.64 ± 0.13 (p = .34) with a mean difference of 0.015 (95% CI: -0.23-0.26). Post-PCI invasive FFR was 0.89 ± 0.07 and FFR&lt;sub>CT&lt;/sub> planner was 0.85 ± 0.07 (p &lt; .001) with a mean difference of 0.040 (95% CI: -0.10-0.18). Delta invasive FFR and delta FFR&lt;sub>CT&lt;/sub> were 0.23 ± 0.12 and 0.21 ± 0.12 (p = .09) with a mean difference of 0.025 (95% CI: -0.20-0.25). Significant correlations were found between pre-PCI FFR and FFR&lt;sub>CT&lt;/sub> (r = 0.53, p &lt; .001), between post-PCI FFR and FFR&lt;sub>CT&lt;/sub> planner (r = 0.41, p = .001), and between delta FFR and delta FFR&lt;sub>CT&lt;/sub> (r = 0.57, p &lt; .001).&lt;h4>Conclusions&lt;/h4>The non-invasive FFR&lt;sub>CT&lt;/sub> planner tool demonstrated significant albeit modest agreement with post-PCI FFR and change in FFR values after PCI. The FFR&lt;sub>CT&lt;/sub> planner tool may hold promise for PCI procedural planning; however, improvement in technology is warranted before clinical application.</pubmed_abstract><journal>Catheterization and cardiovascular interventions : official journal of the Society for Cardiac Angiography &amp; Interventions</journal><pagination>614-622</pagination><full_dataset_link>https://www.ebi.ac.uk/biostudies/studies/S-EPMC7984343</full_dataset_link><repository>biostudies-literature</repository><pubmed_title>Non-invasive procedural planning using computed tomography-derived fractional flow reserve.</pubmed_title><pmcid>PMC7984343</pmcid><pubmed_authors>Everaars H</pubmed_authors><pubmed_authors>van de Ven PM</pubmed_authors><pubmed_authors>Nap A</pubmed_authors><pubmed_authors>Verouden NJW</pubmed_authors><pubmed_authors>Driessen RS</pubmed_authors><pubmed_authors>de Winter RW</pubmed_authors><pubmed_authors>Knaapen P</pubmed_authors><pubmed_authors>Taylor CA</pubmed_authors><pubmed_authors>van Rossum AC</pubmed_authors><pubmed_authors>Bom MJ</pubmed_authors><pubmed_authors>Danad I</pubmed_authors><pubmed_authors>van Diemen PA</pubmed_authors><pubmed_authors>Sprengers RW</pubmed_authors><pubmed_authors>Schumacher SP</pubmed_authors><pubmed_authors>Opolski MP</pubmed_authors><pubmed_authors>Leipsic JA</pubmed_authors></additional><is_claimable>false</is_claimable><name>Non-invasive procedural planning using computed tomography-derived fractional flow reserve.</name><description>&lt;h4>Objectives&lt;/h4>This study aimed to investigate the performance of computed tomography derived fractional flow reserve based interactive planner (FFR&lt;sub>CT&lt;/sub> planner) to predict the physiological benefits of percutaneous coronary intervention (PCI) as defined by invasive post-PCI FFR.&lt;h4>Background&lt;/h4>Advances in FFR&lt;sub>CT&lt;/sub> technology have enabled the simulation of hyperemic pressure changes after virtual removal of stenoses.&lt;h4>Methods&lt;/h4>In 56 patients (63 vessels) invasive FFR measurements before and after PCI were obtained and FFR&lt;sub>CT&lt;/sub> was calculated using pre-PCI coronary CT angiography. Subsequently, FFR&lt;sub>CT&lt;/sub> and invasive coronary angiography models were aligned allowing virtual removal of coronary stenoses on pre-PCI FFR&lt;sub>CT&lt;/sub> models in the same locations as PCI was performed. Relationships between invasive FFR and FFR&lt;sub>CT&lt;/sub> , between post-PCI FFR and FFR&lt;sub>CT&lt;/sub> planner, and between delta FFR and delta FFR&lt;sub>CT&lt;/sub> were evaluated.&lt;h4>Results&lt;/h4>Pre PCI, invasive FFR was 0.65 ± 0.12 and FFR&lt;sub>CT&lt;/sub> was 0.64 ± 0.13 (p = .34) with a mean difference of 0.015 (95% CI: -0.23-0.26). Post-PCI invasive FFR was 0.89 ± 0.07 and FFR&lt;sub>CT&lt;/sub> planner was 0.85 ± 0.07 (p &lt; .001) with a mean difference of 0.040 (95% CI: -0.10-0.18). Delta invasive FFR and delta FFR&lt;sub>CT&lt;/sub> were 0.23 ± 0.12 and 0.21 ± 0.12 (p = .09) with a mean difference of 0.025 (95% CI: -0.20-0.25). Significant correlations were found between pre-PCI FFR and FFR&lt;sub>CT&lt;/sub> (r = 0.53, p &lt; .001), between post-PCI FFR and FFR&lt;sub>CT&lt;/sub> planner (r = 0.41, p = .001), and between delta FFR and delta FFR&lt;sub>CT&lt;/sub> (r = 0.57, p &lt; .001).&lt;h4>Conclusions&lt;/h4>The non-invasive FFR&lt;sub>CT&lt;/sub> planner tool demonstrated significant albeit modest agreement with post-PCI FFR and change in FFR values after PCI. The FFR&lt;sub>CT&lt;/sub> planner tool may hold promise for PCI procedural planning; however, improvement in technology is warranted before clinical application.</description><dates><release>2021-01-01T00:00:00Z</release><publication>2021 Mar</publication><modification>2026-06-02T16:18:32.661Z</modification><creation>2025-04-03T21:34:19.206Z</creation></dates><accession>S-EPMC7984343</accession><cross_references><pubmed>32845067</pubmed><doi>10.1002/ccd.29210</doi></cross_references></HashMap>