<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<rss version="2.0">
  <channel>
    <title>Lotze, U.</title>
    <link>http://repub.eur.nl/res/aut/7503/</link>
    <description>List of Publications</description>
    <language>en</language>
    <image>
      <url>http://repub.eur.nl/static-eur/img/logo.png</url>
      <title>RePub, Erasmus University Rotterdam</title>
      <link>http://repub.eur.nl</link>
    </image>
    <item>
      <title>Vectorcardiographic monitoring to assess early vessel patency after reperfusion therapy for acute myocardial infarction (Article)</title>
      <link>http://repub.eur.nl/res/pub/5491/</link>
      <pubDate>1995-01-01T00:00:00Z</pubDate>
      <description>Reperfusion therapy has lowered mortality in patients suffering from acute myocardial infarction. Failure to reperfuse is associated with an increased short- and long-term mortality. In a prospective study we used dynamic vectorcardiography to monitor 96 patients with acute myocardial infarction treated with reperfusion therapy to non-invasively assess coronary patency. The results from continuous monitoring were compared to those obtained from angiography. By using trend-analysis of QRS vector difference and ST vector magnitude, we were able to correctly identify 58 of the 70 patients (83%) with a reperfused infarct-related artery, and 19 of the 26 patients (73%) with a persistently occluded artery demonstrated at an early angiogram (diagnostic accuracy 80%). In patients with high-grade collateral flow to the infarct-related area, the results of the vectorcardiographic monitoring and of angiography showed the largest disagreement, whereas the accuracy of vectorcardiographic monitoring was high: 88% among patients without collaterals. The present results suggest that QRS complex and ST segment vectorcardiographic monitoring is a useful tool for assessing early coronary artery patency, and that dynamic vectorcardiography may help in identifying candidates for emergency coronary angiography.</description>
    </item>
  </channel>
</rss>