<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JFR</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id>
      <journal-title>JMIR Formative Research</journal-title>
      <issn pub-type="epub">2561-326X</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v8i1e55798</article-id>
      <article-id pub-id-type="pmid">38833694</article-id>
      <article-id pub-id-type="doi">10.2196/55798</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Using the Natural Language Processing System Medical Named Entity Recognition-Japanese to Analyze Pharmaceutical Care Records: Natural Language Processing Analysis</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Yamamoto</surname>
            <given-names>Koujirou</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Matsuda</surname>
            <given-names>Shinichi</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Ohno</surname>
            <given-names>Yukiko</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0001-2378-2629</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Kato</surname>
            <given-names>Riri</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0007-0029-743X</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Ishikawa</surname>
            <given-names>Haruki</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0004-0633-5482</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Nishiyama</surname>
            <given-names>Tomohiro</given-names>
          </name>
          <degrees>MEng</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1538-8266</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Isawa</surname>
            <given-names>Minae</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0007-3068-0800</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Mochizuki</surname>
            <given-names>Mayumi</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6772-4327</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Aramaki</surname>
            <given-names>Eiji</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0201-3609</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Aomori</surname>
            <given-names>Tohru</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <address>
            <institution>Faculty of Pharmacy</institution>
            <institution>Takasaki University of Health and Welfare</institution>
            <addr-line>37-1 Nakaorui-machi</addr-line>
            <addr-line>Takasaki-shi</addr-line>
            <addr-line>Gunma, 370-0033</addr-line>
            <country>Japan</country>
            <phone>81 273521290</phone>
            <email>aomori-t@takasaki-u.ac.jp</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7697-6446</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Faculty of Pharmacy</institution>
        <institution>Keio University</institution>
        <addr-line>Tokyo</addr-line>
        <country>Japan</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Nara Institute of Science and Technology</institution>
        <addr-line>Nara</addr-line>
        <country>Japan</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Faculty of Pharmacy</institution>
        <institution>Takasaki University of Health and Welfare</institution>
        <addr-line>Gunma</addr-line>
        <country>Japan</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Tohru Aomori <email>aomori-t@takasaki-u.ac.jp</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2024</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>4</day>
        <month>6</month>
        <year>2024</year>
      </pub-date>
      <volume>8</volume>
      <elocation-id>e55798</elocation-id>
      <history>
        <date date-type="received">
          <day>26</day>
          <month>12</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>23</day>
          <month>3</month>
          <year>2024</year>
        </date>
        <date date-type="rev-recd">
          <day>5</day>
          <month>4</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>26</day>
          <month>4</month>
          <year>2024</year>
        </date>
      </history>
      <copyright-statement>©Yukiko Ohno, Riri Kato, Haruki Ishikawa, Tomohiro Nishiyama, Minae Isawa, Mayumi Mochizuki, Eiji Aramaki, Tohru Aomori. Originally published in JMIR Formative Research (https://formative.jmir.org), 04.06.2024.</copyright-statement>
      <copyright-year>2024</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on https://formative.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://formative.jmir.org/2024/1/e55798" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Large language models have propelled recent advances in artificial intelligence technology, facilitating the extraction of medical information from unstructured data such as medical records. Although named entity recognition (NER) is used to extract data from physicians’ records, it has yet to be widely applied to pharmaceutical care records.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>In this study, we aimed to investigate the feasibility of automatic extraction of the information regarding patients’ diseases and symptoms from pharmaceutical care records. The verification was performed using Medical Named Entity Recognition-Japanese (MedNER-J), a Japanese disease-extraction system designed for physicians’ records.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>MedNER-J was applied to subjective, objective, assessment, and plan data from the care records of 49 patients who received cefazolin sodium injection at Keio University Hospital between April 2018 and March 2019. The performance of MedNER-J was evaluated in terms of precision, recall, and <italic>F</italic><sub>1</sub>-score.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The <italic>F</italic><sub>1</sub>-scores of NER for subjective, objective, assessment, and plan data were 0.46, 0.70, 0.76, and 0.35, respectively. In NER and positive-negative classification, the <italic>F</italic><sub>1</sub>-scores were 0.28, 0.39, 0.64, and 0.077, respectively. The <italic>F</italic><sub>1</sub>-scores of NER for objective (0.70) and assessment data (0.76) were higher than those for subjective and plan data, which supported the superiority of NER performance for objective and assessment data. This might be because objective and assessment data contained many technical terms, similar to the training data for MedNER-J. Meanwhile, the <italic>F</italic><sub>1</sub>-score of NER and positive-negative classification was high for assessment data alone (<italic>F</italic><sub>1</sub>-score=0.64), which was attributed to the similarity of its description format and contents to those of the training data.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>MedNER-J successfully read pharmaceutical care records and showed the best performance for assessment data. However, challenges remain in analyzing records other than assessment data. Therefore, it will be necessary to reinforce the training data for subjective data in order to apply the system to pharmaceutical care records.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>natural language processing</kwd>
        <kwd>NLP</kwd>
        <kwd>named entity recognition</kwd>
        <kwd>pharmaceutical care records</kwd>
        <kwd>machine learning</kwd>
        <kwd>cefazolin sodium</kwd>
        <kwd>electronic medical record</kwd>
        <kwd>EMR</kwd>
        <kwd>extraction</kwd>
        <kwd>Japanese</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Natural language processing (NLP) is a computer technology to process the language people read and write in their daily lives. Machine translation and search engines are examples of NLP technologies.</p>
        <p>In recent years, with advancements in artificial intelligence technology, it has become possible to extract information related to patients’ diseases and symptoms from unstructured data such as medical records [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>].</p>
        <p>NLP technology that is used to extract information such as that related to diseases and symptoms, the names of people and organizations, time expressions, and numerical expressions from text is generally referred to as named entity recognition (NER). Some NER systems also have a positive-negative (P-N) classification function that can be used to determine the onset of extracted findings.</p>
        <p>To date, most research on NLP technology has focused on English-language texts. NLP technology that is focused on Japanese texts has lagged due to certain aspects of the Japanese language, including that words are not separated by spaces and subjects are often omitted [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
      </sec>
      <sec>
        <title>Related Studies</title>
        <p>Among Japanese NLP studies that focused on medical issues, the study by Imai et al [<xref ref-type="bibr" rid="ref4">4</xref>] developed a system that performs extraction and P-N classification of malignant findings from radiological reports such as computed tomography reports and magnetic resonance imaging reports; Ma et al [<xref ref-type="bibr" rid="ref5">5</xref>] built a system that performs extraction and P-N classification of abnormal findings from discharge summaries, progress notes, and nursery notes; and Aramaki et al [<xref ref-type="bibr" rid="ref6">6</xref>] developed a system that performs extraction and P-N classification of disease names and symptoms from case history summaries. In addition, Mashima et al [<xref ref-type="bibr" rid="ref7">7</xref>] extracted adverse events from progress notes of patients who received intravenous injections of cytotoxic anticancer drugs, and Usui et al [<xref ref-type="bibr" rid="ref8">8</xref>] extracted symptomatic states from data stored in the electronic medical records of a community pharmacy and standardized them according to the codes of the <italic>ICD-10</italic> (<italic>International Classification of Diseases, Tenth Revision</italic>) in order to create a data set of patients’ complaints [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. The National Institute of Informatics Test beds and Community for Information Access Research Project’s <italic>Medical Natural Language Processing for Web Document</italic> task aimed to classify pseudotweets according to whether they contained information about patients’ symptoms [<xref ref-type="bibr" rid="ref9">9</xref>], and several teams collaborated to build a system to accomplish this task. Nishioka et al [<xref ref-type="bibr" rid="ref10">10</xref>] established a system to identify from blog posts whether a patient is positive or negative for hand-foot syndrome on a per-patient and per-sentence basis. Although various approaches have been taken to analyze unstructured medical data as described above in this section, most have targeted physicians’ records, including case history summaries, discharge summaries, and radiological reports, and NER has not been widely applied to pharmaceutical care records.</p>
        <p>Pharmaceutical care records are documents about patients and are written by pharmacists, who collect information from a pharmacological perspective. Because pharmaceutical care records contain an entry for the change in patients’ physical condition while taking medication, including symptoms of suspected adverse drug effects [<xref ref-type="bibr" rid="ref11">11</xref>], many such symptoms are documented in pharmaceutical care records. Thus, developing an NER system that can extract and analyze information from pharmaceutical care records would facilitate investigations of adverse drug effects.</p>
        <p>The study by Usui et al [<xref ref-type="bibr" rid="ref8">8</xref>], mentioned in the beginning of this section, targeted data similar to this study. Because their system was a rule-based model, it had difficulty handling symptoms and contexts that were not set in the rules. Although rules can be added, it is difficult to manage them with consistency. Therefore, we aimed to overcome this problem by using machine learning.</p>
      </sec>
      <sec>
        <title>Study Aim</title>
        <p>In this study, we applied Medical Named Entity Recognition-Japanese (MedNER-J), a Japanese-language system designed to extract disease information from physicians’ records [<xref ref-type="bibr" rid="ref6">6</xref>], to pharmaceutical care records in order to verify the feasibility of NER and P-N classification for this task. Target data were pharmaceutical care records of patients who received cefazolin sodium (CEZ) injection. CEZ is a cephem antibiotic that is often used to prevent secondary infection from operative wounds. The system was applied only to the records of patients who received CEZ injection, with the expectation of mainly collecting target drug information due to fewer concomitant drugs.</p>
        <p>This is the first study to apply the existing system to pharmaceutical care records. This study provides the baseline performance for analyzing Japanese pharmaceutical care records using the machine learning method.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Materials</title>
        <p>Pharmaceutical care records of patients who received CEZ injection between April 2018 and March 2019 at Keio University Hospital were used as test data (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Researchers accessed and obtained those data on November 19, 2021.</p>
        <p>Pharmaceutical care records were written by pharmacists, and the format consisted of (1) free-text columns and (2) subjective, objective, assessment, and plan (SOAP) columns: subjective information such as patients’ complaints were included in the subjective data; objective information such as clinical history, clinical findings, and laboratory data were included in the objective data; assessments by pharmacists were included in the assessment data; and future plans were included in the plan data.</p>
        <p>Data that satisfied the following criteria were used in this research: (1) records with a description in at least 1 SOAP column and (2) records including any of the following keywords in the free-text column or objective column: <italic>cefazolin</italic> (written in full-width or half-width katakana characters), <italic>cefamezin</italic> (written in full-width or half-width katakana characters), <italic>CEZ</italic>, and <italic>cez</italic>.</p>
        <p>MedNER-J was applied to the records that satisfied the above criteria and that corresponded to the period from the first CEZ dosing day to 12 days after the last dosing for each patient for each month.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Data set preparation. Among the records from April 2018 to March 2019, those from the date of first cefazolin sodium (CEZ) administration to 12 days after the end of administration that also contained the keywords in the objective column or the free-text column and a record in one of the subjective, objective, assessment, and plan (SOAP) columns were included in the analysis.</p>
          </caption>
          <graphic xlink:href="formative_v8i1e55798_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>NER and P-N Classification</title>
        <p>We used MedNER-J [<xref ref-type="bibr" rid="ref12">12</xref>] for NER and P-N classification (<xref rid="figure2" ref-type="fig">Figure 2</xref>). MedNER-J is an NLP system to extract information related to diseases and symptoms from physicians’ records. It is based on the bidirectional encoder representations from transformers (BERT) [<xref ref-type="bibr" rid="ref13">13</xref>]–conditional random fields (CRF) model [<xref ref-type="bibr" rid="ref14">14</xref>], which fine-tuned case history summaries to pretrained Japanese BERT model established by Tohoku NLP group [<xref ref-type="bibr" rid="ref15">15</xref>]. CRF was used in a previous NER task [<xref ref-type="bibr" rid="ref6">6</xref>]; however, BERT-CRF performed better than CRF [<xref ref-type="bibr" rid="ref16">16</xref>]. In addition, MedNER-J can extract data related to a wide range of diseases and symptoms although many systems in previous studies targeted specific diseases and symptoms. Therefore, we used MedNER-J for this study. The system can perform P-N classification in order to determine the onset or absence of presumed findings from the context.</p>
        <p>At the preprocessing stage, all characters in the records were converted to full-width characters, and exclamation marks were converted to periods.</p>
        <p>Preprocessed records were input to MedNER-J on a sentence-by-sentence basis to perform NER and P-N classification. A sentence break was defined as a line break or a period.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Processing of pharmaceutical care records. Each subjective, objective, assessment, and plan (SOAP) column underwent preprocessing as well as named entity recognition (NER) and positive-negative (P-N) classification by Medical Named Entity Recognition-Japanese (MedNER-J) to obtain the final results.</p>
          </caption>
          <graphic xlink:href="formative_v8i1e55798_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Performance Evaluation</title>
        <p><xref rid="figure3" ref-type="fig">Figure 3</xref> shows the performance evaluation flow. A total of 2 researchers independently extracted named entities from the same records, performed P-N classification by visual confirmation, and created the correct answer data following the original criteria. Exact and partial matches of extracted terms between MedNER-J and the 2 researchers were examined, and P-N classification matches were also investigated. The criteria the researchers followed to create the correct answer data will be explained in the <italic>Judging Criteria for Researchers</italic> section.</p>
        <p>In cases where 1 sentence contained the same named entities multiple times, researchers also checked whether the positional relationships in the sentence were matched for the same extracted named entities. If the extracted terms matched exactly, they were judged as exact matches. In cases where they did not match exactly but overlapped by ≥1 Japanese characters, they were judged as partial matches. Both exact match extractions and partial match extractions were checked in terms of P-N classification.</p>
        <p>Precision, recall, and <italic>F</italic><sub>1</sub>-score were calculated and evaluated for the following: matches of NER (including partial matches), and matches of NER in addition to P-N classification results (including partial matches).</p>
        <p>Precision = number of true positive/number of true positive and false positive <bold>(1)</bold></p>
        <p>Recall = number of true positive/number of true positive and false negative <bold>(2)</bold></p>
        <p><italic>F</italic><sub>1</sub>-score = (2 × precision × recall)/(precision + recall) <bold>(3)</bold></p>
        <p>When counting the results, including partial matches, the number of matched terms varied depending on whether they were counted in units of the researchers’ extracted terms or in units of the system’s extracted terms. In such cases, counts were made according to the units that reduced the total number of matched terms.</p>
        <p>The validity of researchers’ evaluations was examined using κ coefficients [<xref ref-type="bibr" rid="ref17">17</xref>]. Mismatched results between 2 researchers were discussed, and judgment results between the researchers were adjusted to be reasonable. The κ coefficient of the 2 researchers was 0.87, indicating a high degree of concordance; this showed that researchers’ evaluations were appropriate.</p>
        <p>The mismatched results between MedNER-J and the researchers were categorized as follows: (1) system extraction failure, (2) incorrect extraction by the system, (3) difference in P-N classification, and (4) difference in the length of the extracted terms. The number of mismatched terms also varied depending on whether they were counted in units of terms extracted by the system or terms extracted by the researchers. In such cases, counts were made according to units that increased the number of mismatched terms.</p>
        <p>After categorization, the features of mismatched terms in each category were explored, with the aim of understanding what the system was then incapable of doing and discussing how those features had affected the analyses performed by the system.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Flow of result matching. The system’s results were matched with the researchers’ results, and performance evaluation indexes were calculated based on the number of named entity recognition (NER) matches alone and the number of NER and positive-negative (P-N) classification matches. Both exact matches as well as partial matches were obtained for NER. Epi: epidural anesthesia.</p>
          </caption>
          <graphic xlink:href="formative_v8i1e55798_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Judging Criteria for Researchers</title>
        <p>This section outlines the criteria that the researchers used to create the correct answer data. Not only nouns such as <italic>pain</italic> but also verbs such as <italic>hurt</italic>, adjectives such as <italic>sore</italic>, and adverbs such as <italic>painfully</italic> were considered targets for extraction. Symptom modifiers such as site, timing, and severity of symptom onset were also considered together with the symptoms to be extracted. With regard to terms meaning patients’ conditions such as <italic>sleep</italic>, <italic>appetite</italic>, <italic>state of bowel movements</italic>, <italic>renal function</italic>, <italic>hepatic function</italic>, and <italic>blood electrolyte levels</italic>, if only a statement of normality such as “appetite is fine” was given, it was also considered to be a target for extraction. For example, pharmacists often ask patients whether they have experienced a loss of appetite, and patients’ responses such as “appetite is fine” are recorded frequently. Such normal states were difficult to consider as diseases or symptoms. Though targets of extraction for records analysis were diseases and symptoms, they are also considered to be important information about patients. Therefore, the terms indicating these six conditions were considered for extraction by the researchers. English abbreviations other than laboratory values were consistently excluded from extraction by the researchers. This is because some of them have different meanings among different medical departments, and it was difficult to use the extracted terms by themselves. Laboratory values and vital signs were considered for extraction only if words or symbols clearly stated the numerical change or how it was abnormal, with the exceptions of <italic>renal function</italic>, <italic>hepatic function</italic>, and <italic>blood electrolyte concentration</italic>. If only numerical information on laboratory values and vital signs were provided, the information was excluded from extraction because this information is obtainable from the structured data of the medical records, and thus there is no need to extract it from the text data. When symptoms were described consecutively, each symptom was considered as an individual symptom. For <italic>allergy</italic>, any modifiers that indicate the types of allergies listed in the medical dictionary for regulatory activities (MedDRA) were also considered for extraction. For example, if there was a description of “allergy caused by a drug,” this could be classified as “drug hypersensitivity” in MedDRA. Therefore, the modifier “caused by a drug” was included in the extracted data. In some cases, specific drug names were mentioned, for example, the description “allergy caused by cefazolin.” However, the drug name “cefazolin” does not appear in MedDRA. If a drug name that does not appear in MedDRA was included in description, only <italic>allergy</italic> was considered as an extraction target, and any modifiers were excluded. Although the description “medication for diseases (eg, diabetes)” was also included, it was not possible to determine whether the medication was used for the patients themselves. Therefore, “diseases (diabetes)” in “medication for diseases (diabetes)” was excluded from extraction. “Symptom (eg, pain)” in “symptom (pain) monitoring” was excluded from extraction because that symptom could not be detected in terms of onset or absence.</p>
        <p>In the P-N classification process, the researchers considered symptoms that were currently present in the patients themselves as positive symptoms in principle. The onset and absence of symptoms were determined by referring only to the context within a given sentence. Use of medication to be taken as needed, such as “times of pain,” was regarded as a negative symptom because onset had not yet occurred. Adverse drug effects mentioned in the explanation of the drug used were considered to be negative symptoms because they did not actually occur. Past symptoms that were not stated to have resolved, such as “I couldn’t sleep last night,” were considered to be positive symptoms. If there was even a slight improvement in symptoms, they were considered to be negative symptoms. Other cases in which the onset of symptoms could not be determined were considered to be positive symptoms.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>This study was approved by the Keio University School of Medicine ethics committee (approval number 2020067). The researchers used only record data that have been previously deidentified by removing patient names and replacing real patient IDs with dummy IDs. Only the personal information manager, who was not included in the authors, had access to the correspondence table between the real patient ID and the dummy ID. A written opt-out form was implemented instead of informed consent. The opt-out document is available from the website of Keio University Hospital.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Target Records Features</title>
        <p>Of the 15,327 records of patients who received CEZ injection during the 2018 fiscal year, 317 (2.07%) pharmaceutical care records satisfied both the inclusion criteria (<xref rid="figure1" ref-type="fig">Figure 1</xref>). The number of records (n=60) obtained within the period following CEZ injection were 43 (72%) for subjective data (38 patients), 60 (100%) for objective data (49 patients), 54 (90%) for assessment data (45 patients), and 56 (93%) for plan data (46 patients). The total number of sentences contained in the records obtained decreased in the following order: objective data&#62;assessment data&#62;subjective data&#62;plan data (<xref ref-type="table" rid="table1">Table 1</xref>). The median value of characters per sentence decreased in the following order: objective data&#62;subjective data&#62;assessment data&#62;plan data (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Features of target records (number of sentences and characters).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="310"/>
            <col width="0"/>
            <col width="160"/>
            <col width="0"/>
            <col width="160"/>
            <col width="0"/>
            <col width="170"/>
            <col width="0"/>
            <col width="170"/>
            <thead>
              <tr valign="top">
                <td colspan="3">
                  <break/>
                </td>
                <td colspan="2">Subjective data</td>
                <td colspan="2">Objective data</td>
                <td colspan="2">Assessment data</td>
                <td>Plan data</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="10">
                  <bold>Sentences (n=3090)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Total, n (%)</td>
                <td colspan="2">211 (6.83)</td>
                <td colspan="2">2431 (78.7)</td>
                <td colspan="2">338 (10.9)</td>
                <td colspan="2">110 (3.56)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Median (per record)</td>
                <td colspan="2">4</td>
                <td colspan="2">37</td>
                <td colspan="2">4.5</td>
                <td colspan="2">2</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Maximum value (per record)</td>
                <td colspan="2">17</td>
                <td colspan="2">120</td>
                <td colspan="2">21</td>
                <td colspan="2">5</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Minimum value (per record)</td>
                <td colspan="2">1</td>
                <td colspan="2">5</td>
                <td colspan="2">2</td>
                <td colspan="2">1</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Characters (n=85,824)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Total, n (%)</td>
                <td colspan="2">4378 (5.10)</td>
                <td colspan="2">72,991 (85.0)</td>
                <td colspan="2">7125 (8.30)</td>
                <td colspan="2">1330 (1.55)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Median (per sentence)</td>
                <td colspan="2">18</td>
                <td colspan="2">29</td>
                <td colspan="2">15</td>
                <td colspan="2">10</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Maximum value (per sentence)</td>
                <td colspan="2">61</td>
                <td colspan="2">113</td>
                <td colspan="2">97</td>
                <td colspan="2">44</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Minimum value (per sentence)</td>
                <td colspan="2">1</td>
                <td colspan="2">1</td>
                <td colspan="2">3</td>
                <td colspan="2">1</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>NER and P-N Classification</title>
        <p>The number of the records analyzed and the extraction results are shown in <xref ref-type="table" rid="table2">Table 2</xref>.</p>
        <p><xref ref-type="table" rid="table3">Table 3</xref> shows the results of the performance evaluation. The recall of subjective and assessment data was lower than precision for both NER alone and for NER and P-N classification. Precision was higher than recall for plan data. Recall was similar to precision for objective data.</p>
        <p>A trade-off relationship exists between precision and recall, meaning that when one increases, the other decreases. Therefore, the <italic>F</italic><sub>1</sub>-score, which is the harmonic mean of precision and recall, is used as an evaluation index for overall performance. The results of <italic>F</italic><sub>1</sub>-score in <xref ref-type="table" rid="table3">Table 3</xref> show that MedNER-J was able to conduct NER and P-N classification with high performance in the following order: assessment data&#62;objective data&#62;subjective data&#62;plan data.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Number of the records analyzed and extraction results by the MedNER-J<sup>a</sup> system and researchers.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="270"/>
            <col width="180"/>
            <col width="170"/>
            <col width="190"/>
            <col width="160"/>
            <thead>
              <tr valign="top">
                <td colspan="2">
                  <break/>
                </td>
                <td>Subjective data, n (%)</td>
                <td>Objective data, n (%)</td>
                <td>Assessment data, n (%)</td>
                <td>Plan data, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">Records analyzed (n=60)</td>
                <td>43 (71.7)</td>
                <td>60 (100)</td>
                <td>54 (90)</td>
                <td>56 (93.3)</td>
              </tr>
              <tr valign="top">
                <td colspan="6">
                  <bold>Extracted terms</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>System (n=633)</td>
                <td>50 (7.9)</td>
                <td>411 (64.9)</td>
                <td>135 (21.3)</td>
                <td>37 (5.8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Researchers (n=805)</td>
                <td>130 (16.1)</td>
                <td>444 (55.2)</td>
                <td>216 (26.8)</td>
                <td>15 (1.9)</td>
              </tr>
              <tr valign="top">
                <td colspan="6">
                  <bold>Matches</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>NER<sup>b,c</sup> (n=483)</td>
                <td>41 (8.5)</td>
                <td>300 (62.1)</td>
                <td>133 (27.5)</td>
                <td>9 (1.9)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>NER<sup>c</sup> +P-N<sup>d</sup> classification (n=305)</td>
                <td>25 (8.2)</td>
                <td>165 (54.1)</td>
                <td>113 (37)</td>
                <td>2 (0.7)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>MedNER-J: Medical Named Entity Recognition-Japanese.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>NER: named entity recognition.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>Including partial matches.</p>
            </fn>
            <fn id="table2fn4">
              <p><sup>d</sup>P-N: positive-negative.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Performance evaluation of named entity recognition (NER) and positive-negative (P-N) classification.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="370"/>
            <col width="200"/>
            <col width="200"/>
            <col width="200"/>
            <thead>
              <tr valign="top">
                <td colspan="2">
                  <break/>
                </td>
                <td>Precision</td>
                <td>Recall</td>
                <td><italic>F</italic><sub>1</sub>-score</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5">
                  <bold>NER (including partial matches)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>All data</td>
                <td>0.76</td>
                <td>0.60</td>
                <td>0.67</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Subjective data</td>
                <td>0.82</td>
                <td>0.32</td>
                <td>0.46</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Objective data</td>
                <td>0.73</td>
                <td>0.68</td>
                <td>0.70</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Assessment data</td>
                <td>0.99</td>
                <td>0.62</td>
                <td>0.76</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Plan data</td>
                <td>0.24</td>
                <td>0.60</td>
                <td>0.35</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>NER (including partial matches)+P-N classification</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>All data</td>
                <td>0.48</td>
                <td>0.38</td>
                <td>0.42</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Subjective data</td>
                <td>0.50</td>
                <td>0.19</td>
                <td>0.28</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Objective data</td>
                <td>0.40</td>
                <td>0.37</td>
                <td>0.39</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Assessment data</td>
                <td>0.84</td>
                <td>0.52</td>
                <td>0.64</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Plan data</td>
                <td>0.054</td>
                <td>0.13</td>
                <td>0.077</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Error Analysis</title>
        <p><xref ref-type="table" rid="table4">Table 4</xref> shows the categories of causes of mismatches between the system and the researchers.</p>
        <p>As each type of SOAP data contained differing amounts of information about diseases and symptoms, a comparison of mismatch causes between these data should be based on the percentage of mismatched terms out of the total extracted terms (sum of the number of extracted terms by the system and the researchers−number of matched terms), not the number of mismatched terms. In the calculation of this percentage, partial matches were considered matches in system extraction failure (cause category 1), incorrect extraction by the system (cause category 2), and difference in P-N classification (cause category 3), while partial matches were considered mismatches in cause category 4. Therefore, the percentage of system extraction failure (cause category 1), incorrect extraction by the system (cause category 2), difference in P-N classification (cause category 3), and difference in the length of the extracted terms (cause category 4) does not add up to 100%. Comparing the percentages, the largest percentage of mismatches was subjective data (89/139, 64%) in cause category 1, plan data (28/43, 65%) in cause category 2, objective data (138/555, 24.9%) in cause category 3, and objective data (81/555, 14.6%) in cause category 4.</p>
        <p>The researchers classified terms in the 4 cause categories shown in <xref ref-type="table" rid="table4">Table 4</xref> into subcategories according to the features of the mismatched term itself and the context around the mismatched term. If a mismatched term had multiple features, it was counted in &#62;1 subcategory.</p>
        <p>The subjective and assessment data were expected to contain a large amount of adverse drug effect information due to the characteristics of the SOAP format. The researchers focused on subjective and assessment data because they expected that the analysis of pharmaceutical care records would facilitate the collection and analysis of information on adverse drug effects. Given that the performance for subjective data was low, in <xref ref-type="table" rid="table5">Table 5</xref>, we listed the top 5 subcategories that had the highest number of eligible cases in cause category 1, with the highest percentage of mismatches in the subjective data.</p>
        <p>The common mismatches in cause category 1 “system extraction failure” were “verbs, adjectives, and adverbs”; “expressions that are difficult to grasp as diseases or symptoms”; and “lists of dosages (medication to be taken as needed; eg, at times of the symptoms).” The most common mismatches in the subjective data were “verbs, adjectives, and adverbs.”</p>
        <p>In mismatches of “verbs, adjectives, and adverbs,” many expressions were general terms or colloquialisms that could be included in the patients’ speech, such as “sore” and “I couldn’t sleep.” The mismatches of “expressions that are difficult to grasp as diseases or symptoms” corresponded to expressions such as “bowel movements are fine.” Although they characterized a normal status, they were important for understanding the patient’s health status. “Lists of dosages (medication to be taken as needed) (eg, times of the symptoms)” was a description of the dosage of the medication to be taken as needed.</p>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Percentage of mismatched terms out of the total number of extracted terms<sup>a</sup> and the number of mismatched terms in each cause category.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="280"/>
            <col width="170"/>
            <col width="170"/>
            <col width="190"/>
            <col width="190"/>
            <thead>
              <tr valign="top">
                <td>Cause category</td>
                <td>Subjective data (n=139)<sup>b</sup>, n (%)</td>
                <td>Objective data (n=555)<sup>b</sup>, n (%)</td>
                <td>Assessment data (n=218)<sup>b</sup>, n (%)</td>
                <td>Plan data (n=43)<sup>b</sup>, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>(1) System extraction failure</td>
                <td>89 (64)</td>
                <td>139 (25)</td>
                <td>83 (38.1)</td>
                <td>5 (11.6)</td>
              </tr>
              <tr valign="top">
                <td>(2) Incorrect extraction by the system</td>
                <td>9 (6.5)</td>
                <td>111 (20)</td>
                <td>2 (0.9)</td>
                <td>28 (65.1)</td>
              </tr>
              <tr valign="top">
                <td>(3) Difference in P-N<sup>c</sup> classification</td>
                <td>16 (11.5)</td>
                <td>138 (24.9)</td>
                <td>20 (9.2)</td>
                <td>8 (18.6)</td>
              </tr>
              <tr valign="top">
                <td>(4) Difference in the length of the extracted terms</td>
                <td>13 (9.4)</td>
                <td>81 (14.6)</td>
                <td>30 (13.8)</td>
                <td>2 (4.7)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table4fn1">
              <p><sup>a</sup>Total number of extracted terms = (number of extracted terms by the system + number of extracted terms by researchers) – number of matched terms between the system and researchers (exact matches and partial matches).</p>
            </fn>
            <fn id="table4fn2">
              <p><sup>b</sup>Total number of terms extracted from each subjective, objective, assessment, and plan data.</p>
            </fn>
            <fn id="table4fn3">
              <p><sup>c</sup>P-N: positive-negative.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Example breakdown of cause category 1 “system extraction failure.”</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="300"/>
            <col width="0"/>
            <col width="210"/>
            <col width="0"/>
            <col width="120"/>
            <col width="0"/>
            <col width="120"/>
            <col width="0"/>
            <col width="130"/>
            <col width="0"/>
            <col width="90"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Subcategory and example given in Japanese (English)</td>
                <td colspan="2">Scope of the researchers’ extraction, Japanese (English)</td>
                <td colspan="2">Subjective data, n (%)</td>
                <td colspan="2">Objective data, n (%)</td>
                <td colspan="2">Assessment data, n (%)</td>
                <td>Plan data, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5">
                  <bold>Verbs, adjectives, and adverbs (n=86)</bold>
                </td>
                <td colspan="2">50 (58.1)</td>
                <td colspan="2">23 (26.7)</td>
                <td colspan="2">13 (15.1)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>まだ痛いですね。 (still hurts)</td>
                <td colspan="2">痛い (hurts)</td>
                <td colspan="2">1 (1.2)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>昨晩はベルソムラを服用しませんでしたが、眠れなかったそうです。(although he didn’t take Belsomra last night, he couldn’t sleep)</td>
                <td colspan="2">眠れなかった (couldn’t sleep)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">1 (1.2)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>また、腎機能も悪く薬剤の投与量に関しては注意必要 (also, kidney function is poor and drug dosage needs to be carefully monitored)</td>
                <td colspan="2">腎機能も悪く(kidney function is poor)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">1 (1.2)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Expressions that are difficult to grasp as diseases or symptoms (n=32)</bold>
                </td>
                <td colspan="2">8 (25)</td>
                <td colspan="2">4 (12.5)</td>
                <td colspan="2">20 (62.5)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>腎機能、肝機能問題なし (kidney function and liver function are fine)</td>
                <td colspan="2">腎機能、肝機能 (kidney function and liver function)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">4 (12.5)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>電解質問題なし (electrolytes are fine)</td>
                <td colspan="2">電解質 (electrolytes)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">5 (15.6)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>今は睡眠について困ってないです。 (I have no trouble sleeping now)</td>
                <td colspan="2">睡眠 (sleeping)</td>
                <td colspan="2">1 (3.1)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>お通じは1日1回は出ているので問題ないと思います。 (I have a bowel movement once a day, so I think I’m doing OK)</td>
                <td colspan="2">お通じ (bowel movement)</td>
                <td colspan="2">1 (3.1)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Lists of dosages (medication to be taken as needed; eg, at times of symptoms; n=20)</bold>
                </td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">20 (100)</td>
                <td colspan="2">0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>ロゼレム(8 mg)　1 T 不眠時 1日1回まで (Rozerem, 8 mg, 1 T time of insomnia up to once a day)</td>
                <td colspan="2">不眠 (insomnia)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">2 (10)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>用法 指示簿参照(疼痛時) (use: refer to the instruction manual [time of pain])</td>
                <td colspan="2">疼痛 (pain)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">2 (10)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Linguistic representation of laboratory values (n=26)</bold>
                </td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">9 (34.6)</td>
                <td colspan="2">17 (65.4)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>INR<sup>a</sup>短い (INR is short)</td>
                <td colspan="2">INR短い (INR is short)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">1 (3.85)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>WBC<sup>b</sup>とCRP<sup>c</sup>減少傾向を確認した。 (decreasing trends in WBC and CRP were observed)</td>
                <td colspan="2">WBCとCRP減少傾向 (decreasing trends in WBC and CRP)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">1 (3.85)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>L/D<sup>d</sup>より入院時高値だったKは正常値まで低下した。(from L/D, the potassium level, which was high on admission, decreased to normal)</td>
                <td colspan="2">高値だったK (potassium level, which was high)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">1 (3.85)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Item names (n=13)</bold>
                </td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">13 (100)</td>
                <td colspan="2">0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>＜副作用＞ (＜adverse drug effects＞)</td>
                <td colspan="2">副作用 (adverse drug effects)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">2 (15.4)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>副作用： アレルギー、肝機能障害、冷汗など (adverse drug effects: allergy, impaired liver function, cold sweat)</td>
                <td colspan="2">副作用 (adverse drug effects)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">1 (7.7)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>副作用）アナフィラキシーショック,皮膚症状,消化器症状等の副作用の可能性。(adverse drug effects: possibility of adverse drug effects such as anaphylactic shock, skin symptoms, and digestive symptoms)</td>
                <td colspan="2">副作用 (adverse drug effects)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">3 (23.1)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table5fn1">
              <p><sup>a</sup>INR: international normalized ratio.</p>
            </fn>
            <fn id="table5fn2">
              <p><sup>b</sup>WBC: white blood cell.</p>
            </fn>
            <fn id="table5fn3">
              <p><sup>c</sup>CRP: C-reactive protein.</p>
            </fn>
            <fn id="table5fn4">
              <p><sup>d</sup>L/D: laboratory data.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>Our results showed that when MedNER-J was applied to pharmaceutical care records, NER and P-N classification could successfully be performed. However, the performance of the system differed for each type of SOAP data, and some issues remain for practical use. Furthermore, cases in which the system performed inadequately were identified by the analysis of mismatch cause categories.</p>
      </sec>
      <sec>
        <title>Application to Pharmaceutical Care Records</title>
        <p>The number of extracted terms by both the system and the researchers were greater in the following order: objective&#62;assessment&#62;subjective&#62; plan data.</p>
        <p>The pharmaceutical care records that were targeted in this study included an average of 13.4 (SD 9.3) diseases or symptoms per record. From these records, MedNER-J correctly extracted an average of 8.1 (SD 6.0) terms and correctly extracted and performed P-N classification on an average of 5.1 (SD 4.2) terms. Therefore, MedNER-J was able to extract 60% (8.1/13.4) of findings from the pharmaceutical care records and correctly classify 63% (5.1/8.1) of those findings as positive or negative.</p>
      </sec>
      <sec>
        <title>Performance Evaluation</title>
        <p>In this study, we focused on results that included not only exact matches but also partial matches between MedNER-J and the researchers. Word segments in Japanese are unclear, and the necessary extraction range of words varies depending on the situation and the reader. As an example of variations, for the term <italic>itakute</italic> (“in pain”), it is sufficient to extract <italic>itaku</italic> or it may be necessary to extract <italic>itakute</italic>, including the conjunctive particle <italic>te</italic>. In addition, we considered whether expressions related to severity should also be extracted. We speculated that enough information would be extracted from partial matches to ascertain diseases and symptoms. Therefore, we decided to include partial matches and then analyze the results.</p>
        <p>Although the <italic>F</italic><sub>1</sub>-scores for all data were 0.67 for NER alone and 0.42 for NER and P-N classification, values varied among the SOAP data. This variation indicates that the applicability of the system differs for each data set. The <italic>F</italic><sub>1</sub>-scores of NER for the objective (0.70) and assessment data (0.76) was high, while those of NER for the subjective and plan data were only 0.46 and 0.35, respectively. This indicates that the NER performance for the objective and assessment data was superior to that for the subjective and plan data. At the same time, the <italic>F</italic><sub>1</sub>-score of NER and P-N classification was high only for assessment data (<italic>F</italic><sub>1</sub>-score=0.64).</p>
        <p>The training data for MedNER-J consisted of case history summaries. Because machine learning systems are generally optimized for the analysis of the training data, the system was optimized for the analysis of case history summaries. Case history summaries include chief complaints, medical history, laboratory findings, and discussions of each case, as summarized by physicians. Thus, in case history summaries, unlike the pharmaceutical care records written in the SOAP format, the patients’ raw statements in the subjective data could have been replaced by the physicians’ expressions. In addition, the plan data used in this study contained only 15 terms of symptoms, and many records ended with brief descriptions such as “observe the progress.” These points are considered to differ from case history summaries, which describe follow-up plan along with the discussion. This might have resulted in lower performance for the subjective and plan data. In contrast, the objective and assessment data were written in the pharmacists’ expressions and described diseases and symptoms in technical terminology, which likely contributed to the high NER performance. Moreover, “progress and discussion of the disease” are a requisite part of case history summaries [<xref ref-type="bibr" rid="ref18">18</xref>], and this point was similar to the description of the assessment data. This is probably why the <italic>F</italic><sub>1</sub>-score including P-N classification for the assessment data was high. A decrease in recall implies an increase in false negatives, while a decrease in precision implies an increase in false positives. Therefore, the lower recall compared to precision for the subjective and assessment data indicate that many mismatches were due to cause category 1 “system extraction failure” in <xref ref-type="table" rid="table4">Table 4</xref>. In contrast, the lower recall compared to precision for the plan data indicate that cause category 2, which is “incorrect extraction by the system,” was more common. For the objective data, recall showed similar values to precision, which means that false positives and false negatives occurred equally without bias.</p>
      </sec>
      <sec>
        <title>Mismatch Cause Subcategories</title>
        <p>On the basis of the features frequently observed in the cause subcategories, this section discusses possible failures when the system is used in practice for analysis of pharmaceutical care records. The discussion here focuses on cause category 1, which was the most common cause of mismatches for subjective data. <xref ref-type="table" rid="table5">Table 5</xref> shows typical examples of cause category 1, which was further divided into 17 subcategories, including “verbs, adjectives, and adverbs”; “expressions that are difficult to grasp as diseases or symptoms”; “lists of dosages (medication to be taken as needed)”; “linguistic representation of laboratory values”; and “item names.”</p>
        <p>In cause category 1 “system extraction failure,” many extracted terms are categorized as “verbs, adjectives, adverbs” or “expressions that are difficult to grasp as diseases or symptoms.” In “verbs, adjectives, adverbs,” the system was not supposed to extract general terms, such as <italic>sore</italic>, used by patients. The pharmacist receives the patients’ complaints and clinical information and then describes the patient’s condition and other information in objective and assessment columns, replacing them with technical terminology. However, the system’s inability to extract “verbs, adjectives, and adverbs” might cause the pharmacists to overlook symptoms that they did not consider important. Examples of mismatches for extracted terms in the subcategory “expressions that are difficult to grasp as diseases or symptoms” are terms that are related to the disease state but do not directly indicate the disease state, including <italic>normal appetite</italic>, <italic>sleep</italic>, <italic>bowel</italic> <italic>movements</italic>, <italic>renal function</italic>, <italic>hepatic function</italic>, and <italic>blood electrolyte levels</italic> (<xref ref-type="table" rid="table5">Table 5</xref>). Such normal findings might be missed due to the system’s inability to extract them. One limitation of investigations involving medical records is the inability to determine the actual occurrence of symptoms that are not explicitly documented in the medical records. The extraction of normal findings is also important because the information that “status of symptoms was documented but they did not occur” is expected to increase the reliability of the results of medical record investigation.</p>
      </sec>
      <sec>
        <title>Future Tasks</title>
        <p>Not only for cause category 1 but for the other cause categories as well, the cause of the mismatches between the system and the researchers can be explained by one of the following 2 factors: the training data for the system did not contain similar expressions, or there was a difference between the criteria that the system had learned and the criteria that the researchers used in this study. In particular, expressions that are difficult to grasp as diseases or symptoms were the terms that the researchers decided to collect additionally since they were considered important from the pharmacists’ perspective. Therefore, the systems are often constructed without considering them as extraction targets in studies that aim to collect diseases and symptoms in a simple manner. Using the analysis targets in training data should improve the performance of the system. From a medical safety standpoint, overlooking patients’ information is highly detrimental. Therefore, a high recall is preferable, even if precision decreases somewhat. However, recall was significantly lower than precision for the subjective data (precision=0.82; recall=0.32). Therefore, it is critical to improve recall for the subjective data going forward.</p>
        <p>Although the SOAP format used in pharmaceutical care records has been the focus of this study, records are sometimes written in SOAP format by other medical staff, including physicians. In this study, we referred to the subjective data in pharmaceutical care records because of the differences in the kind of attention paid to patients’ changes in clinical state depending on the profession. For example, physicians follow up with patients extensively from disease diagnosis to treatment. Nurses provide not only treatment but also daily care for patients during their hospitalization. In contrast, pharmacists conduct follow-up with patients from a pharmacological perspective, which inevitably includes asking about the beneficial and adverse effects of medications. Therefore, it can be inferred that the descriptions contained in the subjective data of pharmaceutical care records differ from those contained in the subjective data of records by other medical staff, despite the fact they are both subjective data. Consequently, to implement a system that can also analyze pharmaceutical care records, it is imperative to study the subjective data of pharmaceutical care records rather than those of other medical staff.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>A limitation of this study is the small sample size, consisting only of patients who received CEZ injection at a single institution. When the system is applied to data from different facilities or data of patients who used different drugs, different results might be obtained due to the differences in recording formats, adverse drug effect profiles, characterizations of the patients’ chief complaints, and the perspectives of the health care providers. Furthermore, the number of records that met the eligibility criteria was smaller than the number of records of patients who received CEZ administration, and the records related to CEZ were possibly the subject of analysis in which pharmacists were less able to show their professional competence.</p>
      </sec>
      <sec>
        <title>Future Use</title>
        <p>The possibilities for the use of NER in health care are broad and varied, as shown by the various efforts undertaken in previous studies [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref10">10</xref>]. Because pharmaceutical care records contain a large amount of information on adverse drug effects, it should be possible to alert health care professionals when symptoms of possible adverse drug reactions are extracted with reference to the attached document information. Although medical safety must always be ensured in clinical practice, there is a limit to what can be undertaken due to limited human resources and heavy workloads. However, MedNER-J is expected to help medical staff avoid overlooking patients’ symptoms and thereby improve medical safety. MedNER-J showed relatively high performance on assessment data. Therefore, we can easily follow the pharmacist’s assessment of a patient’s clinical status over time by analyzing all the records of the patient. This follow-up allows the pharmacist to collect patient information without overlooking past medical history. Pharmacists can use this information to check whether a patient has a clinical condition that requires discontinuation or dosage adjustment of the prescribed medication. Through these steps, the pharmacist can provide well-prepared patient guidance. Another possibility is to use the results obtained from analyzing large records to investigate the frequency of adverse drug effects or to discover unknown adverse drug effects based on real-world data. When the system is used to identify adverse drug effects, a larger data set than that of this study is required. For example, the frequency of skin symptoms, a common adverse effect with cefazolin administration, is reported to be approximately 0.5%. The sample size required to identify adverse drug effects with a frequency of 0.5% is 4778 patients, assuming a 95% CI with an error of 0.2%. Several innovations are required to achieve this sample size, such as extending the study period and adding participating facilities. More accurate research can be conducted by assuming the incidence of target adverse effects and trying to ensure the sample size in this manner.</p>
        <p>Two research tools “FDA Adverse Event Reporting System” and “Japanese Adverse Drug Event Report database” are currently being used for analyzing adverse drug events. Although these databases have several advantages such as large data size and ease of processing due to structured data, they also have the disadvantage of bias in the reporting process. By contrast, pharmaceutical care records have some difficulties in handling due to unstructured data; however, they have no reporting bias and enable epidemiological studies that directly project the clinical practice. Another major advantage of using pharmaceutical care records is potential for real-time monitoring. New discoveries might be obtained from analyzing large amounts of data that were previously unavailable.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>MedNER-J, a system designed to extract information from physicians’ records, was applied to extract data from pharmaceutical care records. The system showed high performance for assessment data and was less reliable for other types of SOAP data. Our results suggest that to apply the system more effectively to pharmaceutical care records, the amount of training data needs to be increased to focus mainly on subjective data, which include patients’ complaints. This study provides the baseline of Japanese pharmaceutical care records analysis.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">BERT</term>
          <def>
            <p>bidirectional encoder representations from transformers</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CEZ</term>
          <def>
            <p>cefazolin sodium</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CRF</term>
          <def>
            <p>conditional random fields</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">
            <italic>ICD-10</italic>
          </term>
          <def>
            <p>
              <italic>International Classification of Diseases, Tenth Revision</italic>
            </p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">MedDRA</term>
          <def>
            <p>medical dictionary for regulatory activities</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">MedNER-J</term>
          <def>
            <p>Medical Named Entity Recognition-Japanese</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">NER</term>
          <def>
            <p>named entity recognition</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">NLP</term>
          <def>
            <p>natural language processing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">P-N</term>
          <def>
            <p>positive-negative</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">SOAP</term>
          <def>
            <p>subjective, objective, assessment, and plan</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study was supported by Japanese Science and Technology Agency, Support for Pioneering Research Initiated by the Next Generation (grant JPMJSP2123).</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>MM is an audit and supervisory board member (outside) of Sumitomo Pharma. The other authors have declared that no competing interests exist.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aramaki</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Wakamiya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yada</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Nakamura</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Natural language processing: from bedside to everywhere</article-title>
          <source>Yearb Med Inform</source>
          <year>2022</year>
          <month>08</month>
          <day>02</day>
          <volume>31</volume>
          <issue>1</issue>
          <fpage>243</fpage>
          <lpage>253</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0042-1742510"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0042-1742510</pub-id>
          <pub-id pub-id-type="medline">35654422</pub-id>
          <pub-id pub-id-type="pmcid">PMC9719781</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dreisbach</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Koleck</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Bourne</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Bakken</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A systematic review of natural language processing and text mining of symptoms from electronic patient-authored text data</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <month>05</month>
          <volume>125</volume>
          <fpage>37</fpage>
          <lpage>46</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30914179"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.02.008</pub-id>
          <pub-id pub-id-type="medline">30914179</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(18)31378-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC6438188</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Katsuki</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Narita</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Matsumori</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ishida</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Watanabe</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tominaga</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Preliminary development of a deep learning-based automated primary headache diagnosis model using Japanese natural language processing of medical questionnaire</article-title>
          <source>Surg Neurol Int</source>
          <year>2020</year>
          <volume>11</volume>
          <fpage>475</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33500813"/>
          </comment>
          <pub-id pub-id-type="doi">10.25259/SNI_827_2020</pub-id>
          <pub-id pub-id-type="medline">33500813</pub-id>
          <pub-id pub-id-type="pii">SNI-11-475</pub-id>
          <pub-id pub-id-type="pmcid">PMC7827501</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Imai</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Aramaki</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kajino</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Miyo</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Onogi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ohe</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Finding malignant findings from radiological reports using medical attributes and syntactic information</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2007</year>
          <volume>129</volume>
          <issue>Pt 1</issue>
          <fpage>540</fpage>
          <lpage>544</lpage>
          <pub-id pub-id-type="medline">17911775</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Imai</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Shinohara</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Sakurai</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kozaki</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Ohe</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>A semi-automatic framework to identify abnormal states in EHR narratives</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2017</year>
          <volume>245</volume>
          <fpage>910</fpage>
          <lpage>4</lpage>
          <pub-id pub-id-type="medline">29295232</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aramaki</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Yano</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wakamiya</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>MedEx/J: a one-scan simple and fast NLP tool for Japanese clinical texts</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2017</year>
          <volume>245</volume>
          <fpage>285</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="medline">29295100</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mashima</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Tamura</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kunikata</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tada</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yamada</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tanigawa</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hayakawa</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tanabe</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yokoi</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Using natural language processing techniques to detect adverse events from progress notes due to chemotherapy</article-title>
          <source>Cancer Inform</source>
          <year>2022</year>
          <volume>21</volume>
          <fpage>11769351221085064</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/abs/10.1177/11769351221085064?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/11769351221085064</pub-id>
          <pub-id pub-id-type="medline">35342285</pub-id>
          <pub-id pub-id-type="pii">10.1177_11769351221085064</pub-id>
          <pub-id pub-id-type="pmcid">PMC8943584</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Usui</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Aramaki</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Iwao</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wakamiya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sakamoto</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Mochizuki</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Extraction and standardization of patient complaints from electronic medication histories for pharmacovigilance: natural language processing analysis in Japanese</article-title>
          <source>JMIR Med Inform</source>
          <year>2018</year>
          <month>09</month>
          <day>27</day>
          <volume>6</volume>
          <issue>3</issue>
          <fpage>e11021</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2018/3/e11021/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11021</pub-id>
          <pub-id pub-id-type="medline">30262450</pub-id>
          <pub-id pub-id-type="pii">v6i3e11021</pub-id>
          <pub-id pub-id-type="pmcid">PMC6231790</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wakamiya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Morita</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kano</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ohkuma</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Aramaki</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Tweet classification toward Twitter-based disease surveillance: new data, methods, and evaluations</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>02</month>
          <day>20</day>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>e12783</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/2/e12783/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12783</pub-id>
          <pub-id pub-id-type="medline">30785407</pub-id>
          <pub-id pub-id-type="pii">v21i2e12783</pub-id>
          <pub-id pub-id-type="pmcid">PMC6401666</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nishioka</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Watanabe</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Asano</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yamamoto</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kawakami</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Yada</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Aramaki</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Yajima</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kizaki</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hori</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Identification of hand-foot syndrome from cancer patients' blog posts: BERT-based deep-learning approach to detect potential adverse drug reaction symptoms</article-title>
          <source>PLoS One</source>
          <year>2022</year>
          <month>5</month>
          <day>4</day>
          <volume>17</volume>
          <issue>5</issue>
          <fpage>e0267901</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0267901"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0267901</pub-id>
          <pub-id pub-id-type="medline">35507636</pub-id>
          <pub-id pub-id-type="pii">PONE-D-21-37107</pub-id>
          <pub-id pub-id-type="pmcid">PMC9067685</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <source>Ministry of Health, Labour and Welfare, Japan</source>
          <access-date>2022-12-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mhlw.go.jp/content/001075622.pdf">https://www.mhlw.go.jp/content/001075622.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ujiie</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yata</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>sociocom / MedNER-J</article-title>
          <source>GitHub</source>
          <access-date>2022-12-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/sociocom/MedNER-J">https://github.com/sociocom/MedNER-J</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Devlin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>MW</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Toutanova</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>BERT: pre-training of deep bidirectional transformers for language understanding</article-title>
          <source>Proceedings of the 2019 Annual Conference of the North American Chapter of the Association for Computational Linguistics</source>
          <year>2019</year>
          <conf-name>NAACL-HLT '19</conf-name>
          <conf-date>June 2-7, 2019</conf-date>
          <conf-loc>Minneapolis, MN</conf-loc>
          <fpage>4171</fpage>
          <lpage>86</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aclanthology.org/N19-1423.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lafferty</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>McCallum</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pereira</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Conditional random fields: Probabilistic models for segmenting and labeling sequence data</article-title>
          <source>Proceedings of the 18th International Conference on Machine Learning</source>
          <year>2001</year>
          <conf-name>ICML '01</conf-name>
          <conf-date>June 28-July 1, 2001</conf-date>
          <conf-loc>San Francisco, CA</conf-loc>
          <fpage>282</fpage>
          <lpage>289</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dl.acm.org/doi/10.5555/645530.655813"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Suzuki</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Takahashi</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>cl-tohoku/bert-japanese</article-title>
          <source>GitHub</source>
          <access-date>2023-12-21</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/cl-tohoku/bert-Japanese">https://github.com/cl-tohoku/bert-Japanese</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kong</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Yue</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Entity extraction of electrical equipment malfunction text by a hybrid natural language processing algorithm</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <volume>9</volume>
          <fpage>40216</fpage>
          <lpage>26</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2021.3063354</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A coefficient of agreement for nominal scales</article-title>
          <source>Educ Psychol Meas</source>
          <year>2016</year>
          <month>07</month>
          <day>02</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>37</fpage>
          <lpage>46</lpage>
          <pub-id pub-id-type="doi">10.1177/001316446002000104</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <article-title>Guide to create and evaluate medical history summaries</article-title>
          <source>Japanese Society of Internal Medicine</source>
          <access-date>2023-01-23</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.naika.or.jp/wp-content/uploads/J-OSLER/Tebiki_ByorekiHyoka.pdf">https://www.naika.or.jp/wp-content/uploads/J-OSLER/Tebiki_ByorekiHyoka.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
