<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="17703" 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/17703?output=omeka-xml" accessDate="2026-04-29T04:25:30+00:00">
  <collection collectionId="15">
    <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="44496">
                <text>Book Chapter</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="27">
    <name>Book Chapter</name>
    <description>Faculty Publications- Book Chapter</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="144109">
              <text>Edge computing for smart disease prediction treatment therapy</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="144110">
              <text>Aautomated medical diagnosis systems; Cardio-vascular diseases; Deep learning; Edge computing; Healthcare system; Machine learning; Sensors; Smart devices; Surveillance frameworks</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="144111">
              <text>Healthcare systems are increasingly seeking to match patients' pace of life and be personalized, as they are demanding more advanced products and services. The only solution for collecting and analyzing health data in realtime is an edge computing (EC) environment, coupled with 5G speeds and modern computing techniques. The technology in healthcare is currently being used to develop smart systems that can expedite the diagnosis of disease and provide precise and timely treatment. The automated hospital monitoring system and medical diagnosis system enable doctors to monitor and diagnose patients from a variety of locations, including hospitals, workplaces, and homes and provide transportation options. As a result, overall doctor visits are reduced as well as patient care is improved. More than 162 billion healthcare IoT devices are expected to be used worldwide by 2021 thanks to the internet of things (IoT) sensors and applications for general healthcare. With edge intelligence (EI), wearable devices with sensors, like smartwatches or smartphones, and gateway devices, such as microcontrollers, can form edge nodes: smart devices with sensors, as well as gateway devices with sensors, can act as edge nodes. Smart sensor devices are typically installed at a greater distance from personal computers (PCs) and servers, which can be utilized in fog computing (FC). In healthcare, EC and FC are used to deliver reliable, low-latency, and location-aware healthcare services by utilizing sensors located within users' reach. Recently, many researchers have proposed using hierarchical computing for the distribution and allocation of inference-based tasks among edge devices and fog nodes, which could lead to an increase in computing power and compute capability of edge devices. For disease prediction, this chapter discusses a variety of EC techniques.  2024 Apple Academic Press, Inc. 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="144112">
              <text>Nanjundan P.; Jaisingh W.; George J.P.</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="144113">
              <text>Reconnoitering the Landscape of Edge Intelligence in Healthcare, pp. 89-114.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="144114">
              <text>Apple Academic Press</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="144115">
              <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="144116">
              <text>&lt;a href="" target="_blank" rel="noreferrer noopener"&gt;&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85185094359&amp;amp;partnerID=40&amp;amp;md5=21c020c5c7134f5c43794d07b3ef1726" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85185094359&amp;amp;partnerID=40&amp;amp;md5=21c020c5c7134f5c43794d07b3ef1726&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="144117">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="144118">
              <text>ISBN: 978-100089493-6; 978-177491436-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="144119">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="144120">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="144121">
              <text>Book chapter</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="144122">
              <text>Nanjundan P., Department of Data Science, Christ University, Lavasa, Pune, Maharashtra, India; Jaisingh W., School of Computing Science and Engineering, VIT Bhopal University, Bhopal, Madhya Pradesh, India; George J.P., Department of Data Science, Christ University, Lavasa, Pune, Maharashtra, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
