<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">135362</controlfield>
  <controlfield tag="005">20260217205602.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.1007/s00366-024-01964-6</subfield>
  </datafield>
  <datafield tag="024" ind1="8" ind2=" ">
    <subfield code="2">sideral</subfield>
    <subfield code="a">138596</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">ART-2024-138596</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Hervas-Raluy, Silvia</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0001-8324-5596</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Image-based biomarkers for engineering neuroblastoma patient-specific computational models</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2024</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">Childhood cancer is a devastating disease that requires continued research and improved treatment options to increase survival rates and quality of life for those affected. The response to cancer treatment can vary significantly among patients, highlighting the need for a deeper understanding of the underlying mechanisms involved in tumour growth and recovery to improve diagnostic and treatment strategies. Patient-specific models have emerged as a promising alternative to tackle the challenges in tumour mechanics through individualised simulation. In this study, we present a methodology to develop subject-specific tumour models, which incorporate the initial distribution of cell density, tumour vasculature, and tumour geometry obtained from clinical MRI imaging data. Tumour mechanics is simulated through the Finite Element method, coupling the dynamics of tumour growth and remodelling and the mechano-transport of oxygen and chemotherapy. These models enable a new application of tumour mechanics, namely predicting changes in tumour size and shape resulting from chemotherapeutic interventions for individual patients. Although the specific context of application in this work is neuroblastoma, the proposed methodologies can be extended to other solid tumours. Given the difficulty for treating paediatric solid tumours like neuroblastoma, this work includes two patients with different prognosis, who received chemotherapy treatment. The results obtained from the simulation are compared with the actual tumour size and shape from patients. Overall, the simulations provided clinically useful information to evaluate the effectiveness of the chemotherapy treatment in each case. These results suggest that the biomechanical model could be a valuable tool for personalised medicine in solid tumours.</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/grantAgreement/ES/DGA/2019-23</subfield>
    <subfield code="9">info:eu-repo/grantAgreement/EC/H2020/826494/EU/PRedictive In-silico Multiscale Analytics to support cancer personalized diaGnosis and prognosis, Empowered by imaging biomarkers/PRIMAGE</subfield>
    <subfield code="9">This project has received funding from the European Union’s Horizon 2020 research and innovation program under grant agreement No H2020 826494-PRIMAGE</subfield>
    <subfield code="9">info:eu-repo/grantAgreement/ES/MCIU/FPU18/04541</subfield>
    <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO-AEI-FEDER/PID2021-122409OB-C21</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
    <subfield code="a">by</subfield>
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/deed.es</subfield>
  </datafield>
  <datafield tag="590" ind1=" " ind2=" ">
    <subfield code="a">4.9</subfield>
    <subfield code="b">2024</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">ENGINEERING, MECHANICAL</subfield>
    <subfield code="b">30 / 182 = 0.165</subfield>
    <subfield code="c">2024</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">43 / 177 = 0.243</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="592" ind1=" " ind2=" ">
    <subfield code="a">1.11</subfield>
    <subfield code="b">2024</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Computer Science Applications</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Software</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Modeling and Simulation</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Engineering (miscellaneous)</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="594" ind1=" " ind2=" ">
    <subfield code="a">18.6</subfield>
    <subfield code="b">2024</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">Sainz-DeMena, Diego</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0001-7452-0437</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Gómez-Benito, Maria José</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0002-1878-8997</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">García-Aznar, José Manuel</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0002-9864-7683</subfield>
  </datafield>
  <datafield tag="710" ind1="2" ind2=" ">
    <subfield code="1">5004</subfield>
    <subfield code="2">605</subfield>
    <subfield code="a">Universidad de Zaragoza</subfield>
    <subfield code="b">Dpto. Ingeniería Mecánica</subfield>
    <subfield code="c">Área Mec.Med.Cont. y Teor.Est.</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="g">40 (2024), 3215–3231</subfield>
    <subfield code="p">Eng. comput.</subfield>
    <subfield code="t">ENGINEERING WITH COMPUTERS</subfield>
    <subfield code="x">0177-0667</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">3563791</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/135362/files/texto_completo.pdf</subfield>
    <subfield code="y">Versión publicada</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">2516999</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/135362/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:135362</subfield>
    <subfield code="p">articulos</subfield>
    <subfield code="p">driver</subfield>
  </datafield>
  <datafield tag="951" ind1=" " ind2=" ">
    <subfield code="a">2026-02-17-20:45:17</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">ARTICLE</subfield>
  </datafield>
</record>
</collection>