<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
    <record>
        <controlfield tag="001">77127</controlfield>
        <controlfield tag="005">20200108100343.0</controlfield>
        <datafield tag="024" ind1="7" ind2=" ">
            <subfield code="2">doi</subfield>
            <subfield code="a">10.1109/JBHI.2018.2805773</subfield>
        </datafield>
        <datafield tag="024" ind1="8" ind2=" ">
            <subfield code="2">sideral</subfield>
            <subfield code="a">106144</subfield>
        </datafield>
        <datafield tag="037" ind1=" " ind2=" ">
            <subfield code="a">ART-2018-106144</subfield>
        </datafield>
        <datafield tag="041" ind1=" " ind2=" ">
            <subfield code="a">eng</subfield>
        </datafield>
        <datafield tag="100" ind1=" " ind2=" ">
            <subfield code="a">Luengo, David</subfield>
        </datafield>
        <datafield tag="245" ind1=" " ind2=" ">
            <subfield code="a">Hierarchical algorithms for causality retrieval in atrial fibrillation intracavitary electrograms</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">Multi-channel intracavitary electrograms (EGMs), are acquired at the electrophysiology laboratory to guide radio frequency catheter ablation of patients suffering from atrial fibrillation (AF). These EGMs are used by cardiologists to determine candidate areas for ablation (e.g., areas corresponding to high dominant frequencies or complex fractionated electrograms). In this paper, we introduce two hierarchical algorithms to retrieve the causal interactions among these multiple EGMs. Both algorithms are based on Granger causality, but other causality measures can be easily incorporated. In both cases, they start by selecting a root node, but they differ on the way in which they explore the set of signals to determine their cause-effect relationships: either testing the full set of unexplored signals (GS-CaRe) or performing a local search only among the set of neighbor EGMs (LS-CaRe). The ensuing causal model provides important information about the propagation of the electrical signals inside the atria, uncovering wavefronts and activation patterns that can guide cardiologists towards candidate areas for catheter ablation. Numerical experiments, on both synthetic signals and annotated real-world signals, show the good performance of the two proposed approaches.</subfield>
        </datafield>
        <datafield tag="536" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO/TEC2015-64835-C3-3-R</subfield>
            <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO/TEC2015-69868-C2-1-R</subfield>
        </datafield>
        <datafield tag="540" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
            <subfield code="a">All rights reserved</subfield>
            <subfield code="u">http://www.europeana.eu/rights/rr-f/</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/acceptedVersion</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="a">Ríos-Muñoz, Gonzalo Ricardo</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="a">Elvira, Víctor</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="a">Sánchez, Carlos</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="a">Artés-Rodríguez, Antonio</subfield>
        </datafield>
        <datafield tag="773" ind1=" " ind2=" ">
            <subfield code="g">23, 1 (2018), 143-155</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">808864</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/77127/files/texto_completo.pdf</subfield>
            <subfield code="y">Postprint</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">143836</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/77127/files/texto_completo.jpg?subformat=icon</subfield>
            <subfield code="x">icon</subfield>
            <subfield code="y">Postprint</subfield>
        </datafield>
        <datafield tag="909" ind1="C" ind2="O">
            <subfield code="o">oai:zaguan.unizar.es:77127</subfield>
            <subfield code="p">articulos</subfield>
            <subfield code="p">driver</subfield>
        </datafield>
        <datafield tag="951" ind1=" " ind2=" ">
            <subfield code="a">2020-01-08-09:29:02</subfield>
        </datafield>
        <datafield tag="980" ind1=" " ind2=" ">
            <subfield code="a">ARTICLE</subfield>
        </datafield>
    </record>

    
</collection>