<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="16810" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/16810?output=omeka-xml" accessDate="2026-05-15T10:23:59+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="131984">
              <text>IoT based heart monitoring and alerting system with cloud computing and managing the traffic for an ambulance in India</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="131985">
              <text>Arduino; Healthcare; Heart attack; IOT</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="131986">
              <text>Global Burden of Disease Report, released in Sept 2017, shows that Cardiovascular Diseases caused 1.7 million deaths (17.8%) in 2016 and it is the leading cause of deaths in India [1]. According to the Indian Heart Association, 25% of all heart attacks happen under the age of 40. In most cases, the initial heart attacks are often ignored. Even post-diagnosis, as per government data [2], 50% of heart attack cases reach the hospital in more than 400 minutes against the ideal window time of 180 minutes; post which damage is irreversible. The delay is often attributed to delay in reaching a hospital or receiving primary aid. In India, traffic conditions also add to the grimace of the situation. Although the government is taking various measures; a holistic solution is required to minimize the delay at each of the steps like accessing the patient situation, contacting the Medical aid or making available the nearest aid possible. In this paper, we aim at providing the holistic solution using the Internet of Things technology (IOT) along with data analytics. IoT enables real-time capturing and computation of medical data from smart sensors built-in wearable devices. The amalgamation of Internet-based services with Medical Things (Smart sensors) enhance the chances of survival of patients. The proposed system analyses the inputs collected from the sensors fit with the patients prone to cardiovascular diseases to ascertain the emergency situation. In addition, to these data, the system also considers age, maximum and minimum heart rate. Based on computational results received from the input parameters, the system triggers the alert to emergency contacts such as the close relatives of the patient, doctors, the hospitals and nearby ambulance. The proposed system combines with the optimized navigation platform to guide the medical assistance to find the fastest route. Copyright  2019 Institute of Advanced Engineering and Science. All rights reserved.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="131987">
              <text>Bhagchandani K.; Peter Augustine D.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="131988">
              <text>International Journal of Electrical and Computer Engineering, Vol-9, No. 6, pp. 5068-5074.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="131989">
              <text>Institute of Advanced Engineering and Science</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="131990">
              <text>2019-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="131991">
              <text>&lt;a href="https://doi.org/10.11591/ijece.v9i6.pp5068-5074" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.11591/ijece.v9i6.pp5068-5074&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85071699062&amp;amp;doi=10.11591%2Fijece.v9i6.pp5068-5074&amp;amp;partnerID=40&amp;amp;md5=e522cbce0172ee664e96235acdc5d0b5" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85071699062&amp;amp;doi=10.11591%2fijece.v9i6.pp5068-5074&amp;amp;partnerID=40&amp;amp;md5=e522cbce0172ee664e96235acdc5d0b5&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="131992">
              <text>All Open Access; Gold Open Access; Green Open Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="131993">
              <text>ISSN: 20888708</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="131994">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="131995">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="131996">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="131997">
              <text>Bhagchandani K., Department of Computer Science, CHRIST (Deemed to be University), India; Peter Augustine D., Faculty of Computer Science, CHRIST (Deemed to be University), India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
