<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="20875" 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/20875?output=omeka-xml" accessDate="2026-04-29T12:10:21+00:00">
  <collection collectionId="16">
    <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="51377">
                <text>Conference Papers</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="28">
    <name>Conference Paper</name>
    <description>Faculty Publications- Conference Papers</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="187737">
              <text>IoT based continuous monitoring of cardiac patients using Raspberry Pi</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="187738">
              <text>ECG; Heart attack; Heartbeat; Internet of Things(IoT)</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="187739">
              <text>In the recent development the Internet of Things (IoT) brings all electronics objects in to a single domain and it is easy to access everything through internet. The applications of IoT are Smart agriculture, Smart Home, Smart City, Smart health monitoring system etc. The automation of health care is one of the application which monitors the patient health status using IoT to make medical equipments more efficient by monitoring the patient's health, in which identifies the body conditions and reduces the human error. A health care monitoring system is used to monitor patient's body parameters for the particular disese and obtain the various values about it. The heart rate monitor is one of the in system using IoT to recognize the cardic patients condition and monitor the status in emergency situations. It monitors the heart rate of the patient with long term cardiovascular disease. Here the Arduino based microcontroller is used to communicate to the sensors such as pulse sensor and ECG Sensor. The system can analyze the signal, extract features from it, detect the normal or abnormal conditions with the help of Raspberry Pi and the results of the ECG signals is sent to the web server. It ensures the signal transmission of heart rate signal to the database through IoT. This also suggests doctors to care the patient follow-up their patient using the patient's data stored in the database. Thus IoT brings one of the solution for cardiac patient monitoring and also reduces the complexity between patient outcome and technology.  2018 Author(s).</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="187740">
              <text>Mathivanan M.; Balamurugan M.; Harish L.; Nandini; Reddy M.</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="187741">
              <text>AIP Conference Proceedings, Vol-2039</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="187742">
              <text>American Institute of Physics Inc.</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="187743">
              <text>2018-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="187744">
              <text>&lt;a href="https://doi.org/10.1063/1.5078984" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1063/1.5078984&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85060949061&amp;amp;doi=10.1063%2F1.5078984&amp;amp;partnerID=40&amp;amp;md5=858640b835a7a11bdfd6d125dd740c8e" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85060949061&amp;amp;doi=10.1063%2f1.5078984&amp;amp;partnerID=40&amp;amp;md5=858640b835a7a11bdfd6d125dd740c8e&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="187745">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="187746">
              <text>ISSN: 0094243X; ISBN: 978-073541765-6</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="187747">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="187748">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="187749">
              <text>Conference paper</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="187750">
              <text>Mathivanan M., Dept of ECE, ACS College of Engineering, Bangalore, India; Balamurugan M., School of Computer Science and Engineering, Christ University, Bangalore, India; Harish L., Dept of ECE, ACS College of Engineering, Bangalore, India; Nandini, Dept of ECE, ACS College of Engineering, Bangalore, India; Reddy M., Dept of ECE, ACS College of Engineering, Bangalore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
