<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     caa a22        4500</leader>
  <controlfield tag="001">397500017</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180308164530.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">161202e199509  xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1093/imammb/12.3-4.259</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)oxford-10.1093/imammb/12.3-4.259</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">VISSERS</subfield>
   <subfield code="D">JAN M. H.</subfield>
   <subfield code="u">Graduate School of Industrial Engineering and Management Science, Eindhoven University of Technology, Eindhoven, The Netherlands, Utrecht, The Netherlands</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
   <subfield code="a">Patient flow based allocation of hospital resources</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[JAN M. H. VISSERS]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">The current practice of allocating resources within a hospital introduces peaks and troughs in the workloads of departments and leads therefore to loss of capacity. This happens when requirements for capacity coordination are not adequately taken into account in the decision making process of allocating resources to specialties. The first part of this research involved an analysis of the hospital's production system on dependencies between resources, resulting in a number of capacity coordination requirements that need to be fulfilled for optimized resource utilization. The second, modelling, part of the study involved the development of a framework for resource management decision making, of a set of computer models to support hospital managerial decision making on resource allocation issues in various parts of the hospital, and of an implementation strategy for the application of the models to concrete hospital settings. The third part of the study was devoted to a number of case-studies, illustrating the use of the models when applied in various resource management projects, such as a reorganization of an operating theatre timetable, or the development of a master plan for activities of a group of general surgeons serving two locations of a merged hospital system. The paper summarizes the main findings of the study and concludes with a discussion of results obtained with the new allocation procedure and with recommendations for future research.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">© 1995 Oxford University Press</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Part 2: Provider Issues</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">hospital planning</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">decision support modelling</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">resource allocation</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Mathematical Medicine and Biology: A Journal of the IMA</subfield>
   <subfield code="d">Oxford University Press</subfield>
   <subfield code="g">12/3-4(1995-09), 259-274</subfield>
   <subfield code="x">1477-8599</subfield>
   <subfield code="q">12:3-4&lt;259</subfield>
   <subfield code="1">1995</subfield>
   <subfield code="2">12</subfield>
   <subfield code="o">imammb</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1093/imammb/12.3-4.259</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.1093/imammb/12.3-4.259</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">100</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">VISSERS</subfield>
   <subfield code="D">JAN M. H.</subfield>
   <subfield code="u">Graduate School of Industrial Engineering and Management Science, Eindhoven University of Technology, Eindhoven, The Netherlands, Utrecht, The Netherlands</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">Mathematical Medicine and Biology: A Journal of the IMA</subfield>
   <subfield code="d">Oxford University Press</subfield>
   <subfield code="g">12/3-4(1995-09), 259-274</subfield>
   <subfield code="x">1477-8599</subfield>
   <subfield code="q">12:3-4&lt;259</subfield>
   <subfield code="1">1995</subfield>
   <subfield code="2">12</subfield>
   <subfield code="o">imammb</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">CC BY-NC-4.0</subfield>
   <subfield code="u">http://creativecommons.org/licenses/by-nc/4.0</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-oxford</subfield>
  </datafield>
 </record>
</collection>
