<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="20028" 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/20028?output=omeka-xml" accessDate="2026-04-08T20:16:53+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="175993">
              <text>Integrated Health Care Delivery and Telemedicine: Existing Legal Impediments in India</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="175994">
              <text>Consent; Digital healthcare; Medico-legal standards; Telemedicine</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="175995">
              <text>The technological innovation in the healthcare sector has contributed to the growth of telemedicine in India. Health services fall under State responsibility as per the Indian Constitution by virtue of Schedule 7although policy and planning framework are under the scope of Central government. Telemedicine cannot not work as an autonomous service, rather, ought to be subjected to different regulations having complex ethical, medico-legal manifestations. As far as India is concerned, Ministry of Health and Family Welfare of India (MoHFW) is the body responsible for initiating the policy of digitization of healthcare. However the point ishow far digital health services going appropriately in India. Based on NDHBs comprehensive architectural framework of Federated National Health Information System in January 2020 and as the pandemic strategy Medical Council of India and the NITI Aayog released new guidelines on telemedicine with respect to registered medical practitioners, this research needed to be checked. Thus, the examination was done in these aspects. Guidelines were revisited to see how the hospitals in Delhi and NOIDA function based on the records submitted in medical consultation given to patients using telemedicine. It is felt that telemedicine being a nebulous concept in India, it needs to be analyzed in the light of prospective opportunities it would offer. There is a need for collaborative approaches on digital health, revision in the prevailing legal and ethical frameworks, the clinical practices corresponding to standing medical guidelines. Also, it is found that there exist no uniform telemedicine practices balancing the privacy norms, medico-legal responsibility and regulatory standards. To arrive at conclusion, the best practices prevailed in other countries are examined and adopted. It is felt that the policies existing in telemedicine need to be bifurcated as digital consultation, digital photography, remote patient monitoring (RPM) separately.  2023, The Author(s), under exclusive license to Springer Nature Singapore Pte Ltd.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="175996">
              <text>Mathew 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="175997">
              <text>Lecture Notes in Networks and Systems, Vol-490, pp. 527-534.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="175998">
              <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="175999">
              <text>2023-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="176000">
              <text>&lt;a href="https://doi.org/10.1007/978-981-19-4052-1_52" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-981-19-4052-1_52&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85138837411&amp;amp;doi=10.1007%2F978-981-19-4052-1_52&amp;amp;partnerID=40&amp;amp;md5=b63dfa28f0b77bb1d35cd8a741a01b7a" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85138837411&amp;amp;doi=10.1007%2f978-981-19-4052-1_52&amp;amp;partnerID=40&amp;amp;md5=b63dfa28f0b77bb1d35cd8a741a01b7a&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="176001">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="176002">
              <text>ISSN: 23673370; ISBN: 978-981194051-4</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="176003">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="176004">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="176005">
              <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="176006">
              <text>Mathew M., Associate Professor, School of Law, Christ (Deemed to be University) Delhi N.C.R, Delhi, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
