<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="12529" 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/12529?output=omeka-xml" accessDate="2026-04-09T06:08:01+00:00">
  <collection collectionId="5">
    <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="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</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="72384">
              <text>A novel AI model for the extraction and prediction of Alzheimer disease from electronic health record</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72385">
              <text>Big data; Dark data; Electronic health record; Machine learning; Natural language processing</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72386">
              <text>Dark data is an emerging concept, with its existence, identification, and utilization being key areas of research. This study examines various aspects and impacts of dark data in the healthcare domain and designs a model to extract essential clinical parameters for Alzheimer's from electronic health records (EHR). The novelty of dark data lies in its significant impact across sectors. In healthcare, even the smallest data points are crucial for diagnosis, prediction, and treatment. Thus, identifying and extracting dark data from medical data corpora enhances decision-making. In this research, a natural language processing (NLP) model is employed to extract clinical information related to Alzheimer's disease, and a machine learning algorithm is used for prediction. Named entity recognition (NER) with SpaCy is utilized to extract clinical departments from doctors' descriptions stored in EHRs. This NER model is trained on custom data containing processed EHR text and associated entity annotations. The extracted clinical departments can then be used for future Alzheimer's diagnosis via support vector machine (SVM) algorithms. Results show improved accuracy with the use of extracted dark data, highlighting its importance in predicting Alzheimer's disease. This research also explores the presence of dark data in various domains and proposes a dark data extraction model for the clinical domain using NLP.  2025 Institute of Advanced Engineering and Science. 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="72387">
              <text>Maju S.V.; Prakasi G.; Pushpam O.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="72388">
              <text>Indonesian Journal of Electrical Engineering and Computer Science, Vol-37, No. 2, pp. 1023-1031.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="72389">
              <text>Institute of Advanced Engineering and Science</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="72390">
              <text>2025-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="72391">
              <text>&lt;a href="https://doi.org/10.11591/ijeecs.v37.i2.pp1023-1031" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.11591/ijeecs.v37.i2.pp1023-1031&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85210744676&amp;amp;doi=10.11591%2Fijeecs.v37.i2.pp1023-1031&amp;amp;partnerID=40&amp;amp;md5=a8cd65f57f1f383add56616138d82584" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85210744676&amp;amp;doi=10.11591%2fijeecs.v37.i2.pp1023-1031&amp;amp;partnerID=40&amp;amp;md5=a8cd65f57f1f383add56616138d82584&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="72392">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="72393">
              <text>ISSN: 25024752</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="72394">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72395">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72396">
              <text>Article</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="72397">
              <text>Maju S.V., Department of Computer Science and Engineering, CHRIST University, Bengaluru, India; Prakasi G., Department of Computer Science and Engineering, CHRIST University, Bengaluru, India; Pushpam O.S., Department of Computer Science and Engineering, CHRIST University, Bengaluru, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
