1 Ocak 2017 Dergi makalesi Açık Erişim

Capar, Ibrahim; Melouk, Sharif H.; Keskin, Burcu B.

MARC21 XML

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">user-tubitak-destekli-proje-yayinlari</subfield>
    <subfield code="o">oai:zenodo.org:111152</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">In the development of strategy for the response to emergent incidents, emergency medical services (EMS) organizations must properly manage their resources while also adhering to response time mandates established by contractual agreements. Performance of an EMS system is typically measured by focusing on the response time of its first responders. However, given that some incidents require the response of multiple emergency vehicles, investigating only the initial response to incidents is inadequate. In this research, we propose two new metrics, in addition to the first response metric, to evaluate the performance of EMS operations: total response time and last responder response time. We develop three mixed integer programming formulations, each one focused on minimizing one of the three metrics, to model the assignment of emergency vehicles to incidents. We also propose a fourth model that combines the metrics via a weighted objective function. This model allows for the simultaneous consideration of the response metrics when evaluating the effectiveness of an emergency response dispatch policy. Experimental results, from comparisons of the models against a greedy dispatch policy, suggest the consideration of multiple response metrics leads to a more robust and effective dispatch policy. Finally, analysis using the models has potential to shape improved strategic and operational policies of EMS organizations.</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">article</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="a">Creative Commons Attribution</subfield>
    <subfield code="u">http://www.opendefinition.org/licenses/cc-by</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Capar, Ibrahim</subfield>
    <subfield code="u">Bowling Green State Univ, Bowling Green, OH 43403 USA</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="z">md5:0a46b920a7253d593d2a3884fdaa44b8</subfield>
    <subfield code="s">158</subfield>
    <subfield code="u">https://aperta.ulakbim.gov.trrecord/111152/files/bib-d99c2583-3aea-4e9c-8b1a-a4df9a52625b.txt</subfield>
  </datafield>
  <controlfield tag="005">20210420141656.0</controlfield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2017-01-01</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.1057/jors.2016.39</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Alternative metrics to measure EMS system performance</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="4">
    <subfield code="v">68</subfield>
    <subfield code="p">JOURNAL OF THE OPERATIONAL RESEARCH SOCIETY</subfield>
    <subfield code="c">792-808</subfield>
    <subfield code="n">7</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Melouk, Sharif H.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Keskin, Burcu B.</subfield>
  </datafield>
  <controlfield tag="001">111152</controlfield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-tubitak-destekli-proje-yayinlari</subfield>
  </datafield>
</record>