<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="19114" 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/19114?output=omeka-xml" accessDate="2026-04-29T10:33:45+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="163228">
              <text>Enhancing Patient Well-Being in Healthcare Through the Integration of IoT and Neural Network</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="163229">
              <text>Healthcare; IoT systems; machine learning; patient monitoring; user-friendly interfaces</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="163230">
              <text>This study analyses the revolutionary integration of Internet of Things (IoT) structures in healthcare through a complete examination of outstanding case research. The first case study focuses on real-time patient fitness monitoring in a clinic setting. The suggested device utilizes an Internet of Things-ready device that has many sensors, including oxygen, pressure, and temperature sensors. The issues of forecasting patient health in advance are handled with the deployment of machine learning models, notably Artificial Neural Networks (ANN), Decision Trees (DT), and Support Vector Machines (SVM). The second case study analyses IoT's effect on patient-precise medication identification and remote fitness monitoring, uncovering issues associated with accessibility, pricing, and human interfaces. Proposed alternatives, which incorporates greater education, increased accessibility, and user-pleasant interfaces with robust technical assistance, have been evaluated with 30 patients over a three-month duration. The results reveal a great growth in impacted person health, along with heightened attention of periodic health monitoring. The results highlight how IoT technologies may transform healthcare procedures by offering pro-active solutions for patients' well-being. This study offers insightful information that may be used to solve practical issues, promote patient-centered solutions, and broaden the scope of the healthcare period. A significant step towards a patient-centered and technologically advanced healthcare environment, the successful outcomes validate the capacity for sustained innovation, cooperation, and improvement in the integration of IoT systems for optimal patient care.  2024 IEEE.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="163231">
              <text>Singh J.; Shelke N.A.; Upreti K.; Divakaran P.; Lingareddy N.; Deepika S.</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="163232">
              <text>Proceedings - 2024 International Conference on Emerging Innovations and Advanced Computing, INNOCOMP 2024, pp. 241-246.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="163233">
              <text>Institute of Electrical and Electronics Engineers 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="163234">
              <text>2024-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="163235">
              <text>&lt;a href="https://doi.org/10.1109/INNOCOMP63224.2024.00047" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/INNOCOMP63224.2024.00047&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85205541532&amp;amp;doi=10.1109%2FINNOCOMP63224.2024.00047&amp;amp;partnerID=40&amp;amp;md5=79f06348ccc77dcfcf2efb12099cc7c6" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85205541532&amp;amp;doi=10.1109%2fINNOCOMP63224.2024.00047&amp;amp;partnerID=40&amp;amp;md5=79f06348ccc77dcfcf2efb12099cc7c6&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="163236">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="163237">
              <text>ISBN: 979-835037647-0</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="163238">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="163239">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="163240">
              <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="163241">
              <text>Singh J., School of Computer Science Engineering &amp;amp; Technology, Bennett University, Greater Noida, India; Shelke N.A., School of Computer Science Engineering &amp;amp; Technology, Bennett University, Greater Noida, India; Upreti K., CHRIST (Deemed to Be University), Department of Computer Science, Ghaziabad, India; Divakaran P., Himalayan University, Itanagar, India; Lingareddy N., Vignan Institute of Technology and Science, Department of CSE, Deshmukhi, India; Deepika S., Sreyas Institute of Engineering and Technology, Department of CSE, Hyderabad, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
