<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">79571</controlfield>
  <controlfield tag="005">20210820090344.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.1109/JBHI.2018.2851299</subfield>
  </datafield>
  <datafield tag="024" ind1="8" ind2=" ">
    <subfield code="2">sideral</subfield>
    <subfield code="a">107422</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">ART-2018-107422</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Martín Yebra, Alba</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0003-0226-4950</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Quantification of Ventricular Repolarization Variation for Sudden Cardiac Death Risk Stratification in Atrial Fibrillation</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2018</subfield>
  </datafield>
  <datafield tag="506" ind1="0" ind2=" ">
    <subfield code="a">Access copy available to the general public</subfield>
    <subfield code="f">Unrestricted</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">Objective: Atrial fibrillation (AF) rhythm gives rise to an irregular response in ventricular activity, preventing the use of standard ECG-derived risk markers based on ventricular repolarization heterogeneity under this particular condition. In this study we proposed new indices to quantify repolarization variations in AF patients, assessing their stratification performance in a chronic heart failure (CHF) population with AF. Methods: We developed a method based on a selective bin averaging technique. Consecutive beats preceded by a similar RR interval were selected, from which the average variation within the ST-T complex for each RR range was computed.We proposed two sets of indices: (i) the 2-beat index of ventricular repolarization variation, (I_V2), computed from pairs of stable consecutive beats; and (ii) the 3-beat indices of ventricular repolarization variation, computed in triplets of stable consecutive beats (I_V3). Results: These indices showed a significant association with sudden cardiac death (SCD) outcome in the study population. In addition, risk assessment based on the combination of the proposed indices improved stratification performance compared to their individual potential. Conclusion: Patients with enhanced ventricular repolarization variation computed in terms of the proposed indices were successfully associated to a higher SCD incidence in our study population, evidencing their prognostic value. Significance: using a simple ambulatory ECG recording, it is possible to stratify AF patients at risk of SCD, which may help cardiologists in adopting most effective therapeutic strategies, with a positive impact in both the patient and healthcare systems.</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/grantAgreement/ES/DGA-FEDER/T39-17R-BSICoS</subfield>
    <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO/DPI2016-75458-R</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
    <subfield code="a">by</subfield>
    <subfield code="u">http://creativecommons.org/licenses/by/3.0/es/</subfield>
  </datafield>
  <datafield tag="590" ind1=" " ind2=" ">
    <subfield code="a">4.217</subfield>
    <subfield code="b">2018</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">COMPUTER SCIENCE, INFORMATION SYSTEMS</subfield>
    <subfield code="b">19 / 155 = 0.123</subfield>
    <subfield code="c">2018</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">MATHEMATICAL &amp; COMPUTATIONAL BIOLOGY</subfield>
    <subfield code="b">5 / 59 = 0.085</subfield>
    <subfield code="c">2018</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">MEDICAL INFORMATICS</subfield>
    <subfield code="b">4 / 26 = 0.154</subfield>
    <subfield code="c">2018</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">COMPUTER SCIENCE, INTERDISCIPLINARY APPLICATIONS</subfield>
    <subfield code="b">16 / 106 = 0.151</subfield>
    <subfield code="c">2018</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="592" ind1=" " ind2=" ">
    <subfield code="a">1.122</subfield>
    <subfield code="b">2018</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Biotechnology</subfield>
    <subfield code="c">2018</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Health Information Management</subfield>
    <subfield code="c">2018</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Electrical and Electronic Engineering</subfield>
    <subfield code="c">2018</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Computer Science Applications</subfield>
    <subfield code="c">2018</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="655" ind1=" " ind2="4">
    <subfield code="a">info:eu-repo/semantics/article</subfield>
    <subfield code="v">info:eu-repo/semantics/submittedVersion</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Laguna, Pablo</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0003-3434-9254</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Cygankiewicz, Iwona</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Bayés-de-Luna, Antoni</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Caiani, Enrico G.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Martínez, Juan Pablo</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0002-7503-3339</subfield>
  </datafield>
  <datafield tag="710" ind1="2" ind2=" ">
    <subfield code="1">5008</subfield>
    <subfield code="2">800</subfield>
    <subfield code="a">Universidad de Zaragoza</subfield>
    <subfield code="b">Dpto. Ingeniería Electrón.Com.</subfield>
    <subfield code="c">Área Teoría Señal y Comunicac.</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="g">23, 3 (2018), 1049 - 1057</subfield>
    <subfield code="p">IEEE j. biomed. health inform.</subfield>
    <subfield code="t">IEEE journal of biomedical and health informatics</subfield>
    <subfield code="x">2168-2194</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">398866</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/79571/files/texto_completo.pdf</subfield>
    <subfield code="y">Preprint</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">147385</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/79571/files/texto_completo.jpg?subformat=icon</subfield>
    <subfield code="x">icon</subfield>
    <subfield code="y">Preprint</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="o">oai:zaguan.unizar.es:79571</subfield>
    <subfield code="p">articulos</subfield>
    <subfield code="p">driver</subfield>
  </datafield>
  <datafield tag="951" ind1=" " ind2=" ">
    <subfield code="a">2021-08-20-08:37:06</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">ARTICLE</subfield>
  </datafield>
</record>
</collection>