<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     naa a22        4500</leader>
  <controlfield tag="001">510808255</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180411083428.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">180411e20130301xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/s11548-012-0773-7</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/s11548-012-0773-7</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
   <subfield code="a">CT dataset anisotropy management for oral implantology planning software</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Tommaso Chiarelli, Evelina Lamma, Tommaso Sansoni]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">Purpose: Measurements accomplished on most oral implantology software are often affected by some systematic effects, of which those related to the CT dataset anisotropy are the most relevant. In fact, most of these commercial systems do not manage possible anisotropy in input datasets, leaving the responsibility to users and radiologists. Therefore, in order to achieve a better knowledge of the patient's anatomy before inserting the implants, and thus reducing the risk of damaging the surrounding structures, the implementation of a complete and precise anisotropy management system is required. Methods: We present an anisotropy management algorithm for pre-operative planning software that is able to handle any anisotropic CT dataset, and, as a result, provides a very precise isotropic equivalent. The developed algorithm exploits two interpolation passes to correct anisotropy and is characterised by linear complexity, needing just a few seconds to accomplish the tasks. The first pass concerns the integer-filling of possible intra-slice void spaces of the original slices, having the responsibility of a correct spreading of the radiographic details along the volume height axis. The second pass, instead, reformats its input dataset under isotropic conditions exploiting a contribution-based interpolation sub-algorithm. Results: The algorithm has been evaluated by comparing the anisotropy implied systematic effects for both anisotropic and interpolation-reconstructed radiographic volumes of five different scans. The proposed system demonstrated to be able to successfully handle any dataset interslice—pixel-size ratio. Moreover, the precision achieved proved to be even better than that of another precise algorithm that we previously developed and published, validating the proposed approach as a consequence. Conclusions: The proposed algorithm makes it possible to handle and correct anisotropy in input CT datasets, helping to avoid anisotropy implied systematic effects on related measurements, and consequently supporting pre-operative planning software by providing a precise and isotropic equivalent volume on which to work.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">CARS, 2012</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Diagnostic imaging</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">CT</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Image processing and display</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Measurement errors</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">3D environment</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Chiarelli</subfield>
   <subfield code="D">Tommaso</subfield>
   <subfield code="u">Dipartimento di Ingegneria, University of Ferrara, Via Saragat 1, 44122, Ferrara, Italy</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Lamma</subfield>
   <subfield code="D">Evelina</subfield>
   <subfield code="u">Dipartimento di Ingegneria, University of Ferrara, Via Saragat 1, 44122, Ferrara, Italy</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Sansoni</subfield>
   <subfield code="D">Tommaso</subfield>
   <subfield code="u">Era Scientific s.r.l., Cattolica, Italy</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">International Journal of Computer Assisted Radiology and Surgery</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">8/2(2013-03-01), 247-257</subfield>
   <subfield code="x">1861-6410</subfield>
   <subfield code="q">8:2&lt;247</subfield>
   <subfield code="1">2013</subfield>
   <subfield code="2">8</subfield>
   <subfield code="o">11548</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/s11548-012-0773-7</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1007/s11548-012-0773-7</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Chiarelli</subfield>
   <subfield code="D">Tommaso</subfield>
   <subfield code="u">Dipartimento di Ingegneria, University of Ferrara, Via Saragat 1, 44122, Ferrara, Italy</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Lamma</subfield>
   <subfield code="D">Evelina</subfield>
   <subfield code="u">Dipartimento di Ingegneria, University of Ferrara, Via Saragat 1, 44122, Ferrara, Italy</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Sansoni</subfield>
   <subfield code="D">Tommaso</subfield>
   <subfield code="u">Era Scientific s.r.l., Cattolica, Italy</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">International Journal of Computer Assisted Radiology and Surgery</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">8/2(2013-03-01), 247-257</subfield>
   <subfield code="x">1861-6410</subfield>
   <subfield code="q">8:2&lt;247</subfield>
   <subfield code="1">2013</subfield>
   <subfield code="2">8</subfield>
   <subfield code="o">11548</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
