<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">98224</controlfield>
  <controlfield tag="005">20231006143306.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.1371/journal.pone.0224409</subfield>
  </datafield>
  <datafield tag="024" ind1="8" ind2=" ">
    <subfield code="2">sideral</subfield>
    <subfield code="a">121872</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">ART-2019-121872</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Marín, J.</subfield>
    <subfield code="0">(orcid)0000-0003-4527-3267</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Integrating a gait analysis test in hospital rehabilitation: A service design approach</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2019</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">Background 
Gait analysis with motion capture (MoCap) during rehabilitation can provide objective information to facilitate treatment decision making. However, designing a test to be integrated into healthcare services requires considering multiple design factors. The difficulty of integrating a ''micro-service'' (gait test) within a ''macro-service'' (healthcare service) has received little attention in the gait analysis literature. It is a challenge that goes beyond the gait analysis case study because service design methods commonly focus on the entire service design (macro-level). 
Objective 
This study aims to extract design considerations and generate guidelines to integrate MoCap technology for gait analysis in the hospital rehabilitation setting. Specifically, the aim is to design a gait test to assess the response of the applied treatments through pre- and post-measurement sessions. Methods We focused on patients with spasticity who received botulinum toxin treatment. A qualitative research design was used to investigate the integration of a gait analysis system based on inertial measurement units in a rehabilitation service at a reference hospital. The methodological approach was based on contrasted methodologies from the service design field, which materialise through observation techniques (during system use), semi-structured interviews, and workshops with healthcare professionals (13 patients, 10 ''proxies'', and 6 doctors). 
Results 
The analysis resulted in six themes: (1) patients'' understanding, (2) guiding the gait tests, (3) which professionals guide the gait tests, (4) gait test reports, (5) requesting gait tests (doctors and test guide communication), and the (6) conceptual design of the service with the gait test. 
Conclusions 
The extracted design considerations and guidelines increase the applicability and usefulness of the gait analysis technology, improving the link between technologists and healthcare professionals. The proposed methodological approach can also be useful for service design teams that deal with the integration of one service into another.</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">2.74</subfield>
    <subfield code="b">2019</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">MULTIDISCIPLINARY SCIENCES</subfield>
    <subfield code="b">27 / 71 = 0.38</subfield>
    <subfield code="c">2019</subfield>
    <subfield code="d">Q2</subfield>
    <subfield code="e">T2</subfield>
  </datafield>
  <datafield tag="592" ind1=" " ind2=" ">
    <subfield code="a">1.023</subfield>
    <subfield code="b">2019</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Multidisciplinary</subfield>
    <subfield code="c">2019</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/publishedVersion</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Blanco, T.</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0002-1831-3342</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Marín, J.J.</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0003-3223-1324</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Moreno, A.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Martitegui, E.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Aragüés, J.C.</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0003-0180-0408</subfield>
  </datafield>
  <datafield tag="710" ind1="2" ind2=" ">
    <subfield code="1">3005</subfield>
    <subfield code="2">375</subfield>
    <subfield code="a">Universidad de Zaragoza</subfield>
    <subfield code="b">Dpto. Filosofía</subfield>
    <subfield code="c">Area Filosofía</subfield>
  </datafield>
  <datafield tag="710" ind1="2" ind2=" ">
    <subfield code="1">5002</subfield>
    <subfield code="2">720</subfield>
    <subfield code="a">Universidad de Zaragoza</subfield>
    <subfield code="b">Dpto. Ingeniería Diseño Fabri.</subfield>
    <subfield code="c">Área Proyectos de Ingeniería</subfield>
  </datafield>
  <datafield tag="710" ind1="2" ind2=" ">
    <subfield code="1">5002</subfield>
    <subfield code="2">305</subfield>
    <subfield code="a">Universidad de Zaragoza</subfield>
    <subfield code="b">Dpto. Ingeniería Diseño Fabri.</subfield>
    <subfield code="c">Área Expresión Gráfica en Ing.</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="g">14, 10 (2019), e0224409 [23 pp]</subfield>
    <subfield code="p">PLoS One</subfield>
    <subfield code="t">PLoS ONE</subfield>
    <subfield code="x">1932-6203</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">1578841</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/98224/files/texto_completo.pdf</subfield>
    <subfield code="y">Versión publicada</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">1975544</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/98224/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:98224</subfield>
    <subfield code="p">articulos</subfield>
    <subfield code="p">driver</subfield>
  </datafield>
  <datafield tag="951" ind1=" " ind2=" ">
    <subfield code="a">2023-10-06-14:08:26</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">ARTICLE</subfield>
  </datafield>
</record>
</collection>