<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">125927</controlfield>
  <controlfield tag="005">20241125101150.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.3390/s23042220</subfield>
  </datafield>
  <datafield tag="024" ind1="8" ind2=" ">
    <subfield code="2">sideral</subfield>
    <subfield code="a">133427</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">ART-2023-133427</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Rinkevicius, Mantas</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Influence of photoplethysmogram signal quality on pulse arrival time during polysomnography</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2023</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">Intervals of low-quality photoplethysmogram (PPG) signals might lead to significant inaccuracies in estimation of pulse arrival time (PAT) during polysomnography (PSG) studies. While PSG is considered to be a “gold standard” test for diagnosing obstructive sleep apnea (OSA), it also enables tracking apnea-related nocturnal blood pressure fluctuations correlated with PAT. Since the electrocardiogram (ECG) is recorded synchronously with the PPG during PSG, it makes sense to use the ECG signal for PPG signal-quality assessment. (1) Objective: to develop a PPG signal-quality assessment algorithm for robust PAT estimation, and investigate the influence of signal quality on PAT during various sleep stages and events such as OSA. (2) Approach: the proposed algorithm uses R and T waves from the ECG to determine approximate locations of PPG pulse onsets. The MESA database of 2055 PSG recordings was used for this study. (3) Results: the proportions of high-quality PPG were significantly lower in apnea-related oxygen desaturation (matched-pairs rc = 0.88 and rc = 0.97, compared to OSA and hypopnea, respectively, when p &amp;lt; 0.001) and arousal (rc = 0.93 and rc = 0.98, when p &amp;lt; 0.001) than in apnea events. The significantly large effect size of interquartile ranges of PAT distributions was between low- and high-quality PPG (p &amp;lt; 0.001, rc = 0.98), and regular and irregular pulse waves (p &amp;lt; 0.001, rc = 0.74), whereas a lower quality of the PPG signal was found to be associated with a higher interquartile range of PAT across all subjects. Suggested PPG signal quality-based PAT evaluation reduced deviations (e.g., rc = 0.97, rc = 0.97, rc = 0.99 in hypopnea, oxygen desaturation, and arousal stages, respectively, when p &amp;lt; 0.001) and allowed obtaining statistically larger differences between different sleep stages and events. (4) Significance: the implemented algorithm has the potential to increase the robustness of PAT estimation in PSG studies related to nocturnal blood pressure monitoring.</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">3.4</subfield>
    <subfield code="b">2023</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">CHEMISTRY, ANALYTICAL</subfield>
    <subfield code="b">34 / 106 = 0.321</subfield>
    <subfield code="c">2023</subfield>
    <subfield code="d">Q2</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">INSTRUMENTS &amp; INSTRUMENTATION</subfield>
    <subfield code="b">24 / 76 = 0.316</subfield>
    <subfield code="c">2023</subfield>
    <subfield code="d">Q2</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">ENGINEERING, ELECTRICAL &amp; ELECTRONIC</subfield>
    <subfield code="b">122 / 353 = 0.346</subfield>
    <subfield code="c">2023</subfield>
    <subfield code="d">Q2</subfield>
    <subfield code="e">T2</subfield>
  </datafield>
  <datafield tag="592" ind1=" " ind2=" ">
    <subfield code="a">0.786</subfield>
    <subfield code="b">2023</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Instrumentation</subfield>
    <subfield code="c">2023</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Analytical Chemistry</subfield>
    <subfield code="c">2023</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Atomic and Molecular Physics, and Optics</subfield>
    <subfield code="c">2023</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Information Systems</subfield>
    <subfield code="c">2023</subfield>
    <subfield code="d">Q2</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Medicine (miscellaneous)</subfield>
    <subfield code="c">2023</subfield>
    <subfield code="d">Q2</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Biochemistry</subfield>
    <subfield code="c">2023</subfield>
    <subfield code="d">Q2</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Electrical and Electronic Engineering</subfield>
    <subfield code="c">2023</subfield>
    <subfield code="d">Q2</subfield>
  </datafield>
  <datafield tag="594" ind1=" " ind2=" ">
    <subfield code="a">7.3</subfield>
    <subfield code="b">2023</subfield>
  </datafield>
  <datafield tag="655" ind1=" " ind2="4">
    <subfield code="a">info:eu-repo/semantics/article</subfield>
    <subfield code="v">info:eu-repo/semantics/publishedVersion</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Charlton, Peter H.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Bailón, Raquel</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0003-1272-0550</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Marozas, Vaidotas</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, 4 (2023), 2220 [20 pp.]</subfield>
    <subfield code="p">Sensors</subfield>
    <subfield code="t">Sensors</subfield>
    <subfield code="x">1424-8220</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">2098791</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/125927/files/texto_completo.pdf</subfield>
    <subfield code="y">Versión publicada</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">2687091</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/125927/files/texto_completo.jpg?subformat=icon</subfield>
    <subfield code="x">icon</subfield>
    <subfield code="y">Versión publicada</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="o">oai:zaguan.unizar.es:125927</subfield>
    <subfield code="p">articulos</subfield>
    <subfield code="p">driver</subfield>
  </datafield>
  <datafield tag="951" ind1=" " ind2=" ">
    <subfield code="a">2024-11-22-12:06:26</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">ARTICLE</subfield>
  </datafield>
</record>
</collection>