<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="18158" 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/18158?output=omeka-xml" accessDate="2026-05-30T04:53:20+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="150213">
              <text>Internet of Things and Blockchain in Healthcare: Challenges and Solutions</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="150214">
              <text>Blockchain; Distributed; Hashed text; Healthcare domain; Internet of Things; Tokens</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="150215">
              <text>The Internet of Things (IoT) enables Internet-connected devices to transmit data to private blockchain networks, allowing for the creation of tamper-resistant documents with shareable exchanges. IoT blockchain technology enables you to communicate and connect IoT data with key stakeholders, while avoiding the need for extensive management and control. Each transfer can be checked to ensure there are no disagreements and to build trust in the network. Blockchain technology protects data from being changed, restricts access to Internet-connected devices, and allows vulnerable IoT devices to be shut down. Blockchain encryption eliminates the possibility of someone overwriting existing data records. In addition, storing IoT data on the blockchain adds an extra layer of security, preventing malicious attackers from accessing the system. The many blockchain IoT firms provide significant value in revolutionizing company operations and daily routines. IoT blockchain firms demonstrate the possibility of blockchain and IoT integration. For instance, Helium is a successful blockchain IoT company specializing in securing Internet connections. This chapter presents the vital role of the Internet of Things and blockchain in the healthcare domain. The integration of blockchain technology in the healthcare industry has given us a chance to solve some problems with IoT networks. In recent years, the need for blockchain-enabled IoT transactions has become an essential technology that will change how users share data. A scenario has been developed to enhance this study to analyse the integration, need, and obstacles associated with blockchain-enabled IoT transactions in the healthcare area. As a result, there is also an IoT model designed using devices for hospitals that take into account all of these people and their needs and the office space where they work.  The Author(s), under exclusive license to Springer Nature Switzerland AG. 2024.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="150216">
              <text>Arulkumar N.; Manimaran A.; Chandramohan D.; Goundar 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="150217">
              <text>EAI/Springer Innovations in Communication and Computing, Vol-Part F1496, pp. 17-29.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="150218">
              <text>Springer Science and Business Media Deutschland GmbH</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="150219">
              <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="150220">
              <text>&lt;a href="https://doi.org/10.1007/978-3-031-35751-0_2" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-031-35751-0_2&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85174805562&amp;amp;doi=10.1007%2F978-3-031-35751-0_2&amp;amp;partnerID=40&amp;amp;md5=22590d92142c7d62b87e991263aaf55f" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85174805562&amp;amp;doi=10.1007%2f978-3-031-35751-0_2&amp;amp;partnerID=40&amp;amp;md5=22590d92142c7d62b87e991263aaf55f&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="150221">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="150222">
              <text>ISSN: 25228595</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="150223">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="150224">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="150225">
              <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="150226">
              <text>Arulkumar N., Department of Computer Science, Christ University, Bangalore, India; Manimaran A., Department of Mathematics, School of Advanced Studies, VIT-AP University, Andhra Pradesh, Amaravati, India; Chandramohan D., Department of Computer Science and Engineering, Thapar Institute of Engineering &amp;amp; Technology, Punjab, Patiala, India; Goundar S., School of Science, Engineering, and Technology, RMIT University, Hanoi, Viet Nam</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
