<?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">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</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">v26i1e46857</article-id>
      <article-id pub-id-type="pmid">38289669</article-id>
      <article-id pub-id-type="doi">10.2196/46857</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>Natural Language Processing of Referral Letters for Machine Learning–Based Triaging of Patients With Low Back Pain to the Most Appropriate Intervention: Retrospective Study</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>Wang</surname>
            <given-names>MengYing</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Han</surname>
            <given-names>Yu</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Fudickar</surname>
            <given-names>Sebastian</given-names>
          </name>
          <degrees>PD, Dr habil</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Institute of Medical Informatics</institution>
            <institution>University of Lübeck</institution>
            <addr-line>Ratzeburger Allee 160</addr-line>
            <addr-line>Lübeck, D-23538</addr-line>
            <country>Germany</country>
            <phone>49 160 7979077</phone>
            <email>sebastian.fudickar@uni-luebeck.de</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3553-5131</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Bantel</surname>
            <given-names>Carsten</given-names>
          </name>
          <degrees>Priv Doz, Dr med, PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1165-8081</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Spieker</surname>
            <given-names>Jannik</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0007-8713-7120</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Töpfer</surname>
            <given-names>Heinrich</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0007-3422-3500</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Stegeman</surname>
            <given-names>Patrick</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1632-2197</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Schiphorst Preuper</surname>
            <given-names>Henrica R</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9460-3459</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Reneman</surname>
            <given-names>Michiel F</given-names>
          </name>
          <degrees>Prof Dr</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4058-3437</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Wolff</surname>
            <given-names>André P</given-names>
          </name>
          <degrees>Prof Dr</degrees>
          <xref rid="aff6" ref-type="aff">6</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6240-3903</ext-link>
        </contrib>
        <contrib id="contrib9" contrib-type="author">
          <name name-style="western">
            <surname>Soer</surname>
            <given-names>Remko</given-names>
          </name>
          <degrees>MSc, PhD</degrees>
          <xref rid="aff6" ref-type="aff">6</xref>
          <xref rid="aff7" ref-type="aff">7</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4154-1711</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Institute of Medical Informatics</institution>
        <institution>University of Lübeck</institution>
        <addr-line>Lübeck</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Medicine and Public Health</institution>
        <institution>University of Oldenburg</institution>
        <addr-line>Oldenburg</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>University Clinic for Anesthesiology, Intensive Care Medicine, Emergency Medicine and Pain Therapy</institution>
        <institution>University of Oldenburg</institution>
        <addr-line>Oldenburg</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>University Oldenburg</institution>
        <addr-line>Oldenburg</addr-line>
        <country>Germany</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Department of Rehabilitation Medicine</institution>
        <institution>University Medical Center Groningen</institution>
        <institution>University of Groningen</institution>
        <addr-line>Groningen</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="aff6">
        <label>6</label>
        <institution>Department of Anesthesiology</institution>
        <institution>University Medical Center Groningen</institution>
        <institution>University of Groningen</institution>
        <addr-line>Groningen</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="aff7">
        <label>7</label>
        <institution>Research Group Smart Health</institution>
        <institution>Saxion University of Applied Sciences</institution>
        <addr-line>Enschede</addr-line>
        <country>Netherlands</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Sebastian Fudickar <email>sebastian.fudickar@uni-luebeck.de</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2024</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>30</day>
        <month>1</month>
        <year>2024</year>
      </pub-date>
      <volume>26</volume>
      <elocation-id>e46857</elocation-id>
      <history>
        <date date-type="received">
          <day>28</day>
          <month>2</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>13</day>
          <month>4</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>12</day>
          <month>7</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>11</day>
          <month>10</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Sebastian Fudickar, Carsten Bantel, Jannik Spieker, Heinrich Töpfer, Patrick Stegeman, Henrica R Schiphorst Preuper, Michiel F Reneman, André P Wolff, Remko Soer. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 30.01.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 the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2024/1/e46857" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Decision support systems (DSSs) for suggesting optimal treatments for individual patients with low back pain (LBP) are currently insufficiently accurate for clinical application. Most of the input provided to train these systems is based on patient-reported outcome measures. However, with the appearance of electronic health records (EHRs), additional qualitative data on reasons for referrals and patients’ goals become available for DSSs. Currently, no decision support tools cover a wide range of biopsychosocial factors, including referral letter information to help clinicians triage patients to the optimal LBP treatment.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The objective of this study was to investigate the added value of including qualitative data from EHRs and referral letters to the accuracy of a quantitative DSS for patients with LBP.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A retrospective study was conducted in a clinical cohort of Dutch patients with LBP. Patients filled out a baseline questionnaire about demographics, pain, disability, work status, quality of life, medication, psychosocial functioning, comorbidity, history, and duration of pain. Referral reasons and patient requests for help (patient goals) were extracted via natural language processing (NLP) and enriched in the data set. For decision support, these data were considered independent factors for triage to neurosurgery, anesthesiology, rehabilitation, or minimal intervention. Support vector machine, k-nearest neighbor, and multilayer perceptron models were trained for 2 conditions: with and without consideration of the referral letter content. The models’ accuracies were evaluated via F1-scores, and confusion matrices were used to predict the treatment path (out of 4 paths) with and without additional referral parameters.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Data from 1608 patients were evaluated. The evaluation indicated that 2 referral reasons from the referral letters (for anesthesiology and rehabilitation intervention) increased the F1-score accuracy by up to 19.5% for triaging. The confusion matrices confirmed the results.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This study indicates that data enriching by adding NLP-based extraction of the content of referral letters increases the model accuracy of DSSs in suggesting optimal treatments for individual patients with LBP. Overall model accuracies were considered low and insufficient for clinical application.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>decision support</kwd>
        <kwd>triaging</kwd>
        <kwd>NLP</kwd>
        <kwd>natural language processing</kwd>
        <kwd>neural network</kwd>
        <kwd>LBP</kwd>
        <kwd>low back pain</kwd>
        <kwd>back</kwd>
        <kwd>pain</kwd>
        <kwd>decision-making</kwd>
        <kwd>machine learning</kwd>
        <kwd>artificial intelligence</kwd>
        <kwd>clinical application</kwd>
        <kwd>patient records</kwd>
        <kwd>qualitative data</kwd>
        <kwd>support system</kwd>
        <kwd>questionnaire</kwd>
        <kwd>quality of life</kwd>
        <kwd>psychosocial</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Triaging patients with low back pain (LBP) for the best-fitting treatment is a complex interaction between evidence-based standard application, clinical reasoning, and patient preferences. Many factors interact within the biopsychosocial model for LBP, making it difficult to provide the best-possible treatment by the right professional based on the best evidence. In general, the pain of 95% of patients with LBP is considered nonspecific, meaning that a clear somatic cause for pain cannot be determined [<xref ref-type="bibr" rid="ref1">1</xref>]. The diagnosis of LBP, therefore, is often insufficient to choose the best treatment modality. Within the broad spectrum of complaints and the lack of a clear-cut diagnosis, conservative treatments, such as interdisciplinary rehabilitation or other activating therapies, are considered to have the highest level of evidence [<xref ref-type="bibr" rid="ref2">2</xref>]. Other treatment options, including anesthesiology or surgery, may be indicated for subgroups. However, the complex biopsychosocial interactions make identifying which patient may require which treatment difficult.</p>
      <p>Attempts have been made to group patients with overlapping characteristics to individualize treatment [<xref ref-type="bibr" rid="ref3">3</xref>]. Groups have been established based on psychosocial characteristics (among others, the Örebro Musculoskeletal Pain Questionnaires [<xref ref-type="bibr" rid="ref4">4</xref>]), case complexity (eg, the Start Back Screening Tool [<xref ref-type="bibr" rid="ref5">5</xref>]), or, for example, clinical prediction rules [<xref ref-type="bibr" rid="ref6">6</xref>]. These subgrouping studies are a step forward in providing patients with targeted treatment based on their characteristics. Although the generalization of these models appears limited, they are not easily adaptable to other contexts. They are insufficiently capable of stratifying treatment based on a possibly infinite number of patient characteristics.</p>
      <p>Health care professionals have been able to triage patients to surgical, anesthesiologic, or rehabilitation interventions with moderate agreement [<xref ref-type="bibr" rid="ref7">7</xref>]. To progress in individualizing treatment and referrals, artificial intelligence systems, particularly machine learning (ML), are a relatively new method that can identify patient patterns based on more input than can be incorporated into traditional models. A few examples have appeared on LBP previously, showing that models could be applied to the data [<xref ref-type="bibr" rid="ref7">7</xref>] and support the decision of who should get low back surgery [<xref ref-type="bibr" rid="ref8">8</xref>]. A clinical decision support system (CDSS) may lead to an increase in triaging patients to the best-possible or targeted treatment and increase the cost-effectiveness of current care for LBP. These models, however, are limited to self-report questionnaires as input and may consequently still have low model fit values, leading to nonvaluable support tools [<xref ref-type="bibr" rid="ref7">7</xref>].</p>
      <p>Electronic health records (EHRs) potentially contain a huge source of qualitative data, including scans, referral information, and other free-text information data, which may increase the information quality as input for a CDSS. The data’s value, however, for the triaging process of patients with LBP and how these data can be enriched are unknown.</p>
      <p>Therefore, this study aimed to investigate the added predictive value of qualitative referral letter information for ML-based triaging of patients with LBP to either neurosurgery, anesthesiology, rehabilitation, or a minimal intervention based on information and education.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Recruitment</title>
        <p>A retrospective study was conducted in a clinical cohort of patients with chronic LBP. Patients referred to the Groningen Spine Center, a university-based tertiary center, were invited to participate. To be eligible for participation, patients had to be at 18 years or older and need to report predominantly LBP, either with or without radiation to the legs. We decided not to exclude patients based on comorbidity, life expectancy, work, or health status to reflect daily care. The Groningen Spine Center is a multidisciplinary center comprising, among others, rehabilitation, neurosurgery, and anesthesiology departments. Prior to participation, patients received informative material on the purpose of a larger 10-year prospective cohort study (the Groningen Spine Cohort Study [<xref ref-type="bibr" rid="ref9">9</xref>]) to study long-term outcomes with LBP. This study was part of the cohort study.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>Patients provided signed informed consent. The Medical Ethical Committee of the University Medical Center Groningen provided a waiver for this study because no other data other than care as usual were being used (M15.169472). The research followed the Declaration of Helsinki and the Good Clinical Practice.</p>
      </sec>
      <sec>
        <title>Clinical Procedures and Measures</title>
        <p>After referral by a general practitioner or a second-line specialist, the referral letters were automatically stored in the spine center’s EHRs (Hyperspace version February 2022, Epic Systems). The retrieved referral letters were digitized as text. After enrollment, patients were sent an online set of questionnaires to screen for potential impact, pain intensity, disability, and psychosocial factors that have been described to be correlated with LBP. All questionnaires were validated on LBP. The quality of life was assessed using the EQ-5D [<xref ref-type="bibr" rid="ref10">10</xref>] Pain Impact, and patient characteristics, medical history, and symptoms and functioning were gathered using the National Institutes of Health (NIH) minimal data set for LBP [<xref ref-type="bibr" rid="ref11">11</xref>]. Work ability was measured using the Work Ability Score (WAS [<xref ref-type="bibr" rid="ref12">12</xref>]), and the psychosocial work environment was measured using the short Copenhagen Psychosocial Questionnaire (COPSOQ II [<xref ref-type="bibr" rid="ref13">13</xref>]). Further details of the study characteristics are described in the study by Dutmer et al [<xref ref-type="bibr" rid="ref9">9</xref>]. If patients were unable to fill out the questionnaires online, paper versions were sent by mail.</p>
        <p>Prior to the first consultation, all patients were triaged by 1 of 4 physician assistants (PAs) specifically educated in spinal disorders. For this study, PAs’ referrals to rehabilitation, anesthesiology, surgery, or others consisted of education and advice, no treatment, further diagnostics, or referral to primary care (see <xref ref-type="table" rid="table1">Table 1</xref> for details of the corresponding categorization). These referrals were considered our primary outcome, whereas the baseline questionnaires and EHR data were our predicting features. In addition to these established questionnaires, we considered the textual content of the digitized referral letters. With this dependency on the availability of digitized referral letters, cases without referral letters were not considered and were excluded. In the EHR data, we searched for the referral reason as well as the patient’s question for help, which was reported as the patient goal in this study.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Considered referral categories and corresponding data entries (N=1209).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="360"/>
            <col width="370"/>
            <col width="270"/>
            <thead>
              <tr valign="top">
                <td>Referral category</td>
                <td>Training set<sup>a</sup> samples (pre-SMOTE), n (%)</td>
                <td>Evaluation set samples, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Rehabilitation</td>
                <td>521 (43.1)</td>
                <td>50 (4.1)</td>
              </tr>
              <tr valign="top">
                <td>Anesthesiologic pain therapy</td>
                <td>178 (14.7)</td>
                <td>50 (4.1)</td>
              </tr>
              <tr valign="top">
                <td>Neurosurgery</td>
                <td>59 (4.9)</td>
                <td>50 (4.1)</td>
              </tr>
              <tr valign="top">
                <td>Other treatment<sup>b</sup></td>
                <td>251 (20.8)</td>
                <td>50 (4.1)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>The training set was balanced afterward via the synthetic minority oversampling technique (SMOTE), resulting in each class holding 521 samples.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>“Other treatment” represents a minimal intervention based on information material.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <sec>
          <title>Data Preprocessing</title>
          <p>The following preprocessing steps were applied to the data. A data set including all questionnaires was enriched with additional referral letter parameters (see the following section). The selection of multiple referral reason or patient goal features/answers per letter was supported. However, if patients had multiple referral letters, only the referral reasons and patient goal of the initial referral letter were considered for processing. Missing data from the questionnaire were not replaced by imputation of any kind, whereas all data gathered from the EHRs were included in the analysis. Subsequently, this extended data set (ED) was randomly separated into an evaluation data set (with 50 samples per treatment category) and a training data set consisting of the remaining data set entries (see <xref ref-type="table" rid="table1">Table 1</xref> for descriptive statistics per treatment category). <xref ref-type="table" rid="table1">Table 1</xref> indicates that the given data set is unbalanced, a common challenge for training ML-based CDSSs. Using original samples for the evaluation data set ensured that our findings were meaningful, and the equal distribution of samples among treatment categories in this evaluation data set ensured fair classification results without considering the original distribution among treatment categories. With the evaluation data set being balanced, sample distribution among the considered treatment categories in the training set (for the original sample distribution among classes, see <xref ref-type="table" rid="table1">Table 1</xref>) was balanced via the synthetic minority oversampling technique (SMOTE) [<xref ref-type="bibr" rid="ref14">14</xref>] (with k-nearest neighbors=5 and strategy=auto). SMOTE is a data augmentation approach that augments data entries for minority categories [<xref ref-type="bibr" rid="ref15">15</xref>], thereby supporting multiclass resampling using a one-versus-rest scheme [<xref ref-type="bibr" rid="ref14">14</xref>]. The balancing via SMOTE ensures that each treatment category is considered equally relevant.</p>
          <p>All previous processing steps were performed in the ED. A basic data set (BD) was generated by duplicating the ED and removing additional EHR parameters to investigate the ED’s relevance. Both data sets were z-score-normalized (separately for training, validation, and evaluation) via the <italic>scikit-learn</italic> library of Python.</p>
        </sec>
        <sec>
          <title>Natural Language Processing</title>
          <p>To quantify and embed the EHR data into the BD, natural language processing (NLP) was applied. NLP is a technique used to extract meaning from qualitative data, which can be used to structure large amounts of unstructured, qualitative data. It is well accepted that in referral letters, meaningful information is included, but automatic extraction can only be achieved via NLP. In our programmed processing pipeline, we conducted named entity recognition (NER) via specific words (see <xref ref-type="table" rid="table2">Tables 2</xref> and <xref ref-type="table" rid="table3">3</xref>) via the regular expression operations module <italic>RE-Package</italic> of Python. With RE-Package, regular words or expressions were identified, which are a sequence of characters that specify a search pattern for defined code words in between which additional characters might occur.</p>
          <p>The American Standard Code for Information Interchange (ASCII)–encoded referral letter texts were analyzed by trained clinical personnel regarding the description of the following data: referral reason and patient goals</p>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>Referral reason features, including search term examples, meaning, and statistics of occurrence (overall referral letters) in all detected referral reason findings. For a comprehensive list of code words, see <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="200"/>
              <col width="270"/>
              <col width="360"/>
              <col width="170"/>
              <thead>
                <tr valign="top">
                  <td>Feature</td>
                  <td>Meaning</td>
                  <td>Dutch code word example (English translation)</td>
                  <td>Occurrences, n (%)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>SecondOpinionReRe<sup>a</sup></td>
                  <td>Referral for a second opinion/diagnostics</td>
                  <td><italic>aanvullend onderzoek</italic> (additional investigation)</td>
                  <td>383 (29)</td>
                </tr>
                <tr valign="top">
                  <td>AnesthesiologyReRe</td>
                  <td>Referral for anesthesiology</td>
                  <td><italic>blockade</italic> (nerve block)</td>
                  <td>180 (14)</td>
                </tr>
                <tr valign="top">
                  <td>RehabReRe</td>
                  <td>Referral for interdisciplinary rehabilitation</td>
                  <td><italic>revalidatie</italic> (rehabilitation)</td>
                  <td>442 (34)</td>
                </tr>
                <tr valign="top">
                  <td>AdviceReRe</td>
                  <td>Could you give advice to the patient?</td>
                  <td><italic>advies</italic> (advice)</td>
                  <td>141 (11)</td>
                </tr>
                <tr valign="top">
                  <td>OptionsReRe</td>
                  <td>Are there treatment options?</td>
                  <td><italic>behandelbare opties</italic> (options for treatment)</td>
                  <td>172 (13)</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table2fn1">
                <p><sup>a</sup>ReRe: referral reason.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Patient goal features, including search term examples, meaning, and statistics of occurrence among all recognized patient questions for help finding. For a comprehensive list of code words, see Multimedia Appendix 2.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="210"/>
              <col width="270"/>
              <col width="350"/>
              <col width="170"/>
              <thead>
                <tr valign="top">
                  <td>Feature</td>
                  <td>Meaning</td>
                  <td>Dutch code word example (English translation)</td>
                  <td>Occurrences, n (%)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>MoreCausePaG<sup>a</sup></td>
                  <td>More diagnostics</td>
                  <td><italic>2e mening</italic> (2nd opinion)</td>
                  <td>128 (22)</td>
                </tr>
                <tr valign="top">
                  <td>PainRedPaG</td>
                  <td>Pain reduction</td>
                  <td><italic>pijn</italic> (pain)</td>
                  <td>241 (42)</td>
                </tr>
                <tr valign="top">
                  <td>BetterFuncPaG</td>
                  <td>Better functioning</td>
                  <td><italic>behandelopties</italic> (treatment options)</td>
                  <td>188 (32)</td>
                </tr>
                <tr valign="top">
                  <td>AdvicePaG</td>
                  <td>Advice</td>
                  <td><italic>advies</italic> (advice)</td>
                  <td>23 (4)</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table3fn1">
                <p><sup>a</sup>PaG: patient goal.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <p>RE-Package was used to find free-text words related to the referral reasons and patient goals, which were stated in Dutch. The corresponding code words are summarized in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendices 1</xref> and <xref ref-type="supplementary-material" rid="app2">2</xref>. Corresponding information was extracted via an NLP processing pipeline. In a preprocessing step of the processing pipeline, ambiguous wordings were unified. To create this pipeline, referral letters were manually studied by 2 authors (RS and PS) independently to determine relevant types of referral reasons and patient goals and corresponding code words indicating them. All words were classified. The resulting categories of referral reasons and patient goals are summarized in <xref ref-type="table" rid="table2">Tables 2</xref> and <xref ref-type="table" rid="table3">3</xref>, respectively, with their number of occurrences.</p>
          <p>The initial textual data were transferred to JavaScript Object Notation (JSON) data interchange format via the <italic>Panda</italic> library [<xref ref-type="bibr" rid="ref16">16</xref>]. Filtering of referral letters was implemented via RE-Package [<xref ref-type="bibr" rid="ref17">17</xref>], resulting in lists of referral letters that contained the corresponding code words. Redundant framings were unified via regular expressions. Subsequently, relevant text segments, especially the ones covering the referral reasons and patient goals, were identified via regular expressions in the referral letters’ extracted text. Within these text segments, the corresponding code words from the EHRs (see <xref ref-type="table" rid="table2">Tables 2</xref> and <xref ref-type="table" rid="table3">3</xref>) were screened via regular expressions. All referral reason features were extracted from the referral reason text; if multiple referral reason entries were available per patient, all were considered. Similarly, all patient goal features were extracted from the patient questions for help text; if multiple patient goal entries per patient were identified, all were considered (eg, “I want a solution for my pain, and I want to know what is wrong with my back.”). Correspondingly, 4 of the 5 new referral reason features and 4 new patient goal features were included in the data set. Henceforth, we refer to all parameters extracted from the referral letters (specifically the referral reasons and patient goals) as “referral letter parameters.”</p>
          <p>To ensure the interpretability of the ML models and of the effect of the additional referral parameters, we excluded any feature engineering but kept the input parameters as they were. By not constructing features by recombining the input parameters, we investigated the relevance and benefit of each feature and ensured high explainability of the network.</p>
        </sec>
        <sec>
          <title>Feature Selection</title>
          <p>To identify the relevance of the ED compared to the BD and to limit the number of features so that they could be gathered in a questionnaire in standard clinical use, we applied the ReliefF feature selection algorithm [<xref ref-type="bibr" rid="ref18">18</xref>] to both the ED and the BD. For feature selection, only the entries in the training sets were considered before applying SMOTE.</p>
          <p>The general aim of feature selection was to identify a subset of features by which the data space spanned as much as possible (including as much variety as possible), while data points in the same class (an alternative naming of the treatment category) remained as small as possible. The ReliefF algorithm [<xref ref-type="bibr" rid="ref18">18</xref>] is a supervised feature selection method for multiclass problems that is robust against incomplete and noisy data, considering the k-nearest neighbors (kNNs) [<xref ref-type="bibr" rid="ref19">19</xref>]. It is a multivariate filter that completely ranks individual features according to their relevance for class separation in the context of other features throughout the observations in the training set [<xref ref-type="bibr" rid="ref20">20</xref>]. ReliefF calculates a feature score based on the differences among feature (parameter) values between neighboring instances. By considering the differences in features among neighboring samples of class hits (NH) that belong to the same class and neighboring samples of class misses (NM), the algorithm can calculate the relevance each feature contributes to determining class membership. With the original Relief function supporting only biclass problems, ReliefF supports multiclass search and considers k-near misses per class.</p>
          <p>The feature relevance score (S) for a particular feature was consequently calculated as follows, with x representing the feature value, abs() denoting the absolute value, and n representing the total number of instances in the data set:</p>
          <disp-formula>S = sum(abs(x – NH) – abs(x – NM))/n</disp-formula>
          <p>Correspondingly, each feature’s weight update (W) was calculated as follows, with M representing the total number of features:</p>
          <disp-formula>W = W – (abs(x – NH) – abs(x – NM))/(n × M)</disp-formula>
          <p>These equations were used iteratively, and the feature scores were averaged over all instances.</p>
          <p>By applying ReliefF, the input parameters were ranked in accordance with their relevance for class separation. The ReliefF algorithm was configured for m=n (to all numbers of training samples) [<xref ref-type="bibr" rid="ref21">21</xref>], the number of kNNs=50 [<xref ref-type="bibr" rid="ref19">19</xref>], and the feature relevance threshold τ=0.7 [<xref ref-type="bibr" rid="ref22">22</xref>] for selecting features as common parameter settings.</p>
        </sec>
        <sec>
          <title>Training and Machine Learning</title>
          <p>To analyze the benefit of the referral letter parameters regarding a treatment path decision, ML models were trained for both data sets, the BD and the ED, after feature selection. For achieving good results in small, unbalanced data sets, such as the given ones, and allowing for interpretability of the results, the kNN algorithm, support vector machine (SVM), and multilayer perceptron (MLP) models were used in the evaluation. Being one of the first studies to apply both quantitative and qualitative (NLP-extracted) data, we decided to focus on applying well-established neural network architectures, as they are well understood and especially allow interpretability of the classification processes, which is essential when investigating new data types. We contacted the clinicians, and they confirmed the high criticality of having interpretability of the neural networks, which should lead to applicable or treatable options for the patient.</p>
          <p>Another advantage is that these classical ML approaches are much better suited than deep neural networks for small, unbalanced data sets. In recent works, we found that in smaller data sets, the classical approaches perform similarly well as deep learning networks.</p>
          <p>For training of the models, 4-fold cross-validation, the rectified linear unit (ReLU) activation function, the Adam optimizer, and the cross-entropy loss function via scikit-learn were used. Further implementation details can be found in the code available in Ref. [<xref ref-type="bibr" rid="ref23">23</xref>]. For training and evaluation, an AMD Ryzen 9 5900X with 64GB RAM and NVIDIA GeForce RTX 3070 was used running 64-bit Windows 11 Pro, Python 3.8, Keras 2.4.3, Keras-Preprocessing 1.1.2, Keras-tuner 1.0.1, pandas 1.1.1, scikit-learn 0.23.2, skrebate 0.62, and TensorFlow 2.4.1. A complete overview of all the steps is presented in <xref rid="figure1" ref-type="fig">Figure 1</xref>.</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Process to reach the final ML algorithm. BD: basic data set; ED: extended data set; kNN: k-nearest neighbor; ML: machine learning; MLP: multilayer perceptron; ReLU: rectified linear unit; SMOTE: synthetic minority oversampling technique; SVM: support vector machine.</p>
            </caption>
            <graphic xlink:href="jmir_v26i1e46857_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Statistical Analysis</title>
        <p>The data set was characterized by sociodemographic and health-related data and distribution characteristics of the referral reasons and patient goals on the treatment categories. The relevance of the referral letter parameters was investigated based on the ReliefF ranking for both data sets (ED and BD). The accuracy of the ML models was evaluated via the <italic>F</italic><sub>1</sub>-score and confusion matrices.</p>
        <p>The <italic>F</italic><sub>1</sub>-score is a commonly used metric to evaluate the performance of a classification model via precision (P) and recall (R). Precision measures the ratio of correctly predicted true-positive (TP) instances to the total predicted TP instances and false-positive (FP) instances:</p>
        <disp-formula>P = TP/(TP + FP)</disp-formula>
        <p>Recall measures the ratio of correctly predicted TP instances to the total actual TP instances, thus including the number of incorrectly predicted false-negative (FN) instances:</p>
        <disp-formula>R = TP/(TP + FN)</disp-formula>
        <p>In the following equation, the <italic>F</italic><sub>1</sub>-score represents the harmonic mean of precision and recall and thus represents a balanced evaluation of the model’s performance:</p>
        <disp-formula><italic>F</italic><sub>1</sub>-score = 2 × (P × R)/(P + R)</disp-formula>
        <p>The <italic>F</italic><sub>1</sub>-scores were averaged over 4 separate training runs.</p>
        <p>Confusion matrices were plotted for the BD and ED classifiers. A confusion matrix summarizes prediction results on a classification problem in a visual manner. By analyzing confusion matrices, we can investigate where the classifier misperforms regularly, indicating lower feature variability.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Study Cohort</title>
        <p>We originally included 1608 patients and corresponding 3907 letters in the data set. The age of the patients ranged from 18 to 66 years, with a mean age of 46 (SD 12.93) years, and 914 (57.2%) patients were female and on average 45 (SD 13.3) years younger than men, who had a mean age of 48 (SD 12.4) years. Of the 1608 patients, 1341 (83.4%) had referral letters included. Of these, 1209 (90.2%) patients were included because their referral letters included referral reasons (n=1062, 87.8%, cases) or patient goals (n=746, 61.7%); 160 referral letters contained only patient goals. Multiple referral letters were available and included for 1012 (83.7%) patients, with redundant referral letters for 1006 (75%) patients with referral letters. Once balanced, the training set included 521 entries per treatment category.</p>
        <p>The training data set included 1009 patients, who were distributed among the treatment categories, as shown in <xref ref-type="table" rid="table1">Table 1</xref>. Within the training and evaluation sets, <xref ref-type="table" rid="table4">Tables 4</xref> and <xref ref-type="table" rid="table5">5</xref> present the category-specific extracted referral reasons and corresponding patient goals, respectively.</p>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Category-specific statistics of the available referral reasons specified within the referral letters, considered in the training and evaluation data sets. Sample distribution among categories and the corresponding sums and overall percentage distribution are shown. “Referral reason” categories refer to Table 2.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="180"/>
            <col width="80"/>
            <col width="120"/>
            <col width="0"/>
            <col width="80"/>
            <col width="140"/>
            <col width="0"/>
            <col width="80"/>
            <col width="120"/>
            <col width="0"/>
            <col width="80"/>
            <col width="120"/>
            <thead>
              <tr valign="top">
                <td>Referral reason category</td>
                <td colspan="3">Treatment: rehabilitation (1), n (%)</td>
                <td colspan="3">Treatment: anesthesiology (2), n (%)</td>
                <td colspan="3">Treatment: neurosurgery (3), n (%)</td>
                <td colspan="2">Treatment: no treatment (0), n (%)</td>
              </tr>
              <tr valign="top">
                <td/>
                <td>Training</td>
                <td>Evaluation</td>
                <td colspan="2">Training</td>
                <td>Evaluation</td>
                <td colspan="2">Training</td>
                <td>Evaluation</td>
                <td colspan="2">Training</td>
                <td>Evaluation</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>SecondOpinionReRe<sup>a</sup> (1)</td>
                <td>167 (13)</td>
                <td>17 (1)</td>
                <td colspan="2">56 (4)</td>
                <td>24 (2)</td>
                <td colspan="2">33 (3)</td>
                <td>21 (2)</td>
                <td colspan="2">76 (6)</td>
                <td>15 (1)</td>
              </tr>
              <tr valign="top">
                <td>AnesthesiologyReRe (2)</td>
                <td>22 (2)</td>
                <td>3 (0)</td>
                <td colspan="2">80 (6)</td>
                <td>34 (3)</td>
                <td colspan="2">6 (0)</td>
                <td>9 (1)</td>
                <td colspan="2">6 (0)</td>
                <td>3 (0)</td>
              </tr>
              <tr valign="top">
                <td>RehabReRe (3)</td>
                <td>302 (23)</td>
                <td>28 (2)</td>
                <td colspan="2">30 (2)</td>
                <td>10 (1)</td>
                <td colspan="2">8 (1)</td>
                <td>5 (0)</td>
                <td colspan="2">47 (4)</td>
                <td>7 (1)</td>
              </tr>
              <tr valign="top">
                <td>AdviceReRe (4)</td>
                <td>71 (5)</td>
                <td>7 (1)</td>
                <td colspan="2">20 (2)</td>
                <td>5 (0)</td>
                <td colspan="2">7 (1)</td>
                <td>4 (0)</td>
                <td colspan="2">24 (2)</td>
                <td>3 (0)</td>
              </tr>
              <tr valign="top">
                <td>OptionsReRe (5)</td>
                <td>85 (6)</td>
                <td>9 (1)</td>
                <td colspan="2">36 (3)</td>
                <td>5 (0)</td>
                <td colspan="2">10 (1)</td>
                <td>6 (0)</td>
                <td colspan="2">16 (1)</td>
                <td>5 (0)</td>
              </tr>
              <tr valign="top">
                <td>Sum</td>
                <td>647 (48.9)</td>
                <td>64 (4.8)</td>
                <td colspan="2">222 (16.8)</td>
                <td>78 (5.9)</td>
                <td colspan="2">64 (4.8)</td>
                <td>45 (3.4)</td>
                <td colspan="2">169 (12.8)</td>
                <td>33 (2.5)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table4fn1">
              <p><sup>a</sup>ReRe: referral reason.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Category-specific statistics of the available patient goal specified within the referral letters, considered in the training and evaluation data sets. Sample distribution among categories and the corresponding sums and overall percentual distribution are shown. “Patient goal” categories refer to Table 3.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="190"/>
            <col width="80"/>
            <col width="130"/>
            <col width="0"/>
            <col width="130"/>
            <col width="90"/>
            <col width="0"/>
            <col width="80"/>
            <col width="110"/>
            <col width="0"/>
            <col width="80"/>
            <col width="110"/>
            <thead>
              <tr valign="top">
                <td>Patient goal category</td>
                <td colspan="3">Treatment: rehabilitation (1), n (%)</td>
                <td colspan="3">Treatment: anesthesiology (2), n (%)</td>
                <td colspan="3">Treatment: neurosurgery (3), n (%)</td>
                <td colspan="2">Treatment: no treatment (0), n (%)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Training</td>
                <td>Evaluation</td>
                <td colspan="2">Training</td>
                <td>Evaluation</td>
                <td colspan="2">Training</td>
                <td>Evaluation</td>
                <td colspan="2">Training</td>
                <td>Evaluation</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>MoreCausePAG<sup>a</sup> (1)</td>
                <td>78 (14)</td>
                <td>5 (1)</td>
                <td colspan="2">9 (2)</td>
                <td>1 (0)</td>
                <td colspan="2">2 (0)</td>
                <td>2 (0)</td>
                <td colspan="2">30 (5)</td>
                <td>1 (0)</td>
              </tr>
              <tr valign="top">
                <td>PainRedPAG (2)</td>
                <td>126 (22)</td>
                <td>9 (2)</td>
                <td colspan="2">16 (3)</td>
                <td>5 (1)</td>
                <td colspan="2">4 (1)</td>
                <td>2 (0)</td>
                <td colspan="2">65 (11)</td>
                <td>14 (2)</td>
              </tr>
              <tr valign="top">
                <td>BetterFuncPAG (3)</td>
                <td>107 (19)</td>
                <td>8 (1)</td>
                <td colspan="2">13 (2)</td>
                <td>5 (1)</td>
                <td colspan="2">4 (1)</td>
                <td>1 (0)</td>
                <td colspan="2">44 (8)</td>
                <td>6 (1)</td>
              </tr>
              <tr valign="top">
                <td>AdvicePAG (4)</td>
                <td>13 (2)</td>
                <td>1 (0)</td>
                <td colspan="2">1 (0)</td>
                <td>0</td>
                <td colspan="2">0</td>
                <td>0</td>
                <td colspan="2">5 (1)</td>
                <td>3 (1)</td>
              </tr>
              <tr valign="top">
                <td>Sum</td>
                <td>324 (55.9)</td>
                <td>23 (4.0)</td>
                <td colspan="2">39 (6.7)</td>
                <td>11 (1.9)</td>
                <td colspan="2">10 (1.7)</td>
                <td>5 (0.9)</td>
                <td colspan="2">144 (24.8)</td>
                <td>24 (4.1)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table5fn1">
              <p><sup>a</sup>PaG: patient goal.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Feature Selection and Information Gain</title>
        <p>The number of features to be considered in both cases was determined to be 29 for the BD and 30 for the ED based on the applied feature relevance threshold of 0.7. <xref ref-type="table" rid="table6">Table 6</xref> summarizes the selected features in the order of decreasing information gain, indicating the information gain of the AnesthesiologyReRe and RehabReRe referral reason features as the second- and fourth-most important referral features. Including the referral letter parameters in the BD did not change the general feature-ranking types between the data sets.</p>
        <table-wrap position="float" id="table6">
          <label>Table 6</label>
          <caption>
            <p>Ranked features based on ReliefF feature selection for the BD<sup>a</sup> and the ED<sup>b</sup>.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="80"/>
            <col width="340"/>
            <col width="120"/>
            <col width="0"/>
            <col width="350"/>
            <col width="110"/>
            <thead>
              <tr valign="top">
                <td>Rank</td>
                <td colspan="3">ED</td>
                <td colspan="2">BD</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Feature</td>
                <td>ReliefF</td>
                <td colspan="2">Feature</td>
                <td>ReliefF</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>Have you been absent from your work in the past 4 weeks because you were sick?</td>
                <td>0.127</td>
                <td colspan="2">Have you been absent from your work in the past 4 weeks because you were sick?</td>
                <td>0.128</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>AnesthesiologyReRe<sup>c,d</sup></td>
                <td>0.118</td>
                <td colspan="2">Have there been days in the past 4 weeks when you worked but suffered from physical or psychological problems during your work?</td>
                <td>0.109</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>Have there been days in the past 4 weeks when you worked but suffered from physical or psychological problems during your work?</td>
                <td>0.107</td>
                <td colspan="2">How many hours a week do you work? Add together all the hours for which you are paid.</td>
                <td>0.103</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>RehabilitationReRe<sup>d</sup></td>
                <td>0.106</td>
                <td colspan="2">Have you used injections (eg, epidural steroid or facet injections)?</td>
                <td>0.103</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>How many hours a week do you work? Add together all the hours for which you are paid.</td>
                <td>0.104</td>
                <td colspan="2">Have you ever had a low back operation?</td>
                <td>0.101</td>
              </tr>
              <tr valign="top">
                <td>6</td>
                <td>Have you used injections (eg, epidural steroid or facet injections)?</td>
                <td>0.103</td>
                <td colspan="2">Have you used exercise therapy?</td>
                <td>0.093</td>
              </tr>
              <tr valign="top">
                <td>7</td>
                <td>Have you ever had a low back operation?</td>
                <td>0.102</td>
                <td colspan="2">Do you think, based on your current health situation, you will still be able to work for the next 2 years?</td>
                <td>0.092</td>
              </tr>
              <tr valign="top">
                <td>8</td>
                <td>Leg pain is dominant.</td>
                <td>0.093</td>
                <td colspan="2">Regarding your work in general, how pleased are you with your job as a whole, considering everything?</td>
                <td>0.091</td>
              </tr>
              <tr valign="top">
                <td>9</td>
                <td>Do you think, based on your current health situation, you will still be able to work for the next 2 years?</td>
                <td>0.092</td>
                <td colspan="2">Leg pain is dominant.</td>
                <td>0.090</td>
              </tr>
              <tr valign="top">
                <td>10</td>
                <td>Have you used exercise therapy?</td>
                <td>0.092</td>
                <td colspan="2">Is your work recognized and appreciated by management?</td>
                <td>0.085</td>
              </tr>
              <tr valign="top">
                <td>11</td>
                <td>Regarding your work in general, how pleased are you with your job as a whole, considering everything?</td>
                <td>0.088</td>
                <td colspan="2">How often is your immediate superior willing to listen to your work-related problems?</td>
                <td>0.085</td>
              </tr>
              <tr valign="top">
                <td>12</td>
                <td>Is your work recognized and appreciated by management?</td>
                <td>0.085</td>
                <td colspan="2">Are you treated fairly at your workplace?</td>
                <td>0.085</td>
              </tr>
              <tr valign="top">
                <td>13</td>
                <td>How often is your immediate superior willing to listen to your work-related problems?</td>
                <td>0.084</td>
                <td colspan="2">How often are your colleagues willing to listen to your work-related problems?</td>
                <td>0.084</td>
              </tr>
              <tr valign="top">
                <td>14</td>
                <td>Are you treated fairly at your workplace?</td>
                <td>0.084</td>
                <td colspan="2">Is your work meaningful?</td>
                <td>0.084</td>
              </tr>
              <tr valign="top">
                <td>15</td>
                <td>How often are your colleagues willing to listen to your work-related problems?</td>
                <td>0.084</td>
                <td colspan="2">Are conflicts resolved in a fair way?</td>
                <td>0.083</td>
              </tr>
              <tr valign="top">
                <td>16</td>
                <td>Are conflicts resolved in a fair way?</td>
                <td>0.083</td>
                <td colspan="2">How often do you get help and support from your nearest superior?</td>
                <td>0.082</td>
              </tr>
              <tr valign="top">
                <td>17</td>
                <td>Is your work meaningful?</td>
                <td>0.082</td>
                <td colspan="2">Do you have enough time for your work tasks?</td>
                <td>0.080</td>
              </tr>
              <tr valign="top">
                <td>18</td>
                <td>How often do you get help and support from your nearest superior?</td>
                <td>0.082</td>
                <td colspan="2"> Have you used opioid painkillers (prescription medications, such as Vicodin, Lortab, Norco, hydrocodone, codeine, Tylenol, Fentanyl, Duragesic, MS Contin, Percocet, Tylox, OxyContin, oxycodone, methadone, tramadol, Ultram, or Dilaudid)?</td>
                <td>0.080</td>
              </tr>
              <tr valign="top">
                <td>19</td>
                <td>Do you have enough time for your work tasks?</td>
                <td>0.079</td>
                <td colspan="2">Do you have to relate to other people’s personal problems as part of your work?</td>
                <td>0.079</td>
              </tr>
              <tr valign="top">
                <td>20</td>
                <td>How often do you get help and support from your colleagues?</td>
                <td>0.079</td>
                <td colspan="2">How often do you get help and support from your colleagues?</td>
                <td>0.079</td>
              </tr>
              <tr valign="top">
                <td>21</td>
                <td>Is your workload unevenly distributed so it piles up?</td>
                <td>0.078</td>
                <td colspan="2">Do you feel that the work you do is important?</td>
                <td>0.079</td>
              </tr>
              <tr valign="top">
                <td>22</td>
                <td>Do you feel that the work you do is important?</td>
                <td>0.078</td>
                <td colspan="2">Is your workload unevenly distributed so it piles up?</td>
                <td>0.078</td>
              </tr>
              <tr valign="top">
                <td>23</td>
                <td>Do you have to relate to other people’s personal problems as part of your work?</td>
                <td>0.078</td>
                <td colspan="2">Do you feel that your work drains so much of your energy that it has a negative effect on your private life?</td>
                <td>0.076</td>
              </tr>
              <tr valign="top">
                <td>24</td>
                <td>Have you used opioid painkillers (prescription medications, such as Vicodin, Lortab, Norco, hydrocodone, codeine, Tylenon, Fentanyl, Duragesic, MS Contin, Percocet, Tylox, OxyContin, oxycodone, methadone, tramadol, Ultram, or Dilaudid)?</td>
                <td>0.076</td>
                <td colspan="2">Can you influence the amount of work assigned to you?</td>
                <td>0.076</td>
              </tr>
              <tr valign="top">
                <td>25</td>
                <td>Do you feel that your work drains so much of your energy that it has a negative effect on your private life?</td>
                <td>0.076</td>
                <td colspan="2">Does your work put you in emotionally disturbing situations?</td>
                <td>0.075</td>
              </tr>
              <tr valign="top">
                <td>26</td>
                <td>Do you have to work fast?</td>
                <td>0.075</td>
                <td colspan="2">Do you have to work fast?</td>
                <td>0.075</td>
              </tr>
              <tr valign="top">
                <td>27</td>
                <td>Would you ask a good friend to apply for a position at your workplace?</td>
                <td>0.074</td>
                <td colspan="2">Would you ask a good friend to apply for a position at your workplace?</td>
                <td>0.075</td>
              </tr>
              <tr valign="top">
                <td>28</td>
                <td>Does your work put you in emotionally disturbing situations?</td>
                <td>0.074</td>
                <td colspan="2">Do you get behind with your work?</td>
                <td>0.071</td>
              </tr>
              <tr valign="top">
                <td>29</td>
                <td>Can you influence the amount of work assigned to you?</td>
                <td>0.074</td>
                <td colspan="2">Do you feel that your work takes so much of your time that it has a negative effect on your personal life?</td>
                <td>0.070</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table6fn1">
              <p><sup>a</sup>BD: basic data set.</p>
            </fn>
            <fn id="table6fn2">
              <p><sup>b</sup>ED: extended data set.</p>
            </fn>
            <fn id="table6fn3">
              <p><sup>c</sup>ReRe: referral reason.</p>
            </fn>
            <fn id="table6fn4">
              <p><sup>d</sup>AnesthesiologyReRe and RehabReRe were the second- and fourth-most important referral reason features.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Accuracy of Machine Learning Models</title>
        <p>In general, <italic>F</italic><sub>1</sub>-scores were low for both the BD and the ED, with values ranging from 0.28 to 0.54. Comparing the <italic>F</italic><sub>1</sub>-scores between the BD and the ED showed an increase of up to 19.5% for the <italic>F</italic><sub>1</sub>-score when considering the additional referral reason features (see <xref ref-type="table" rid="table7">Table 7</xref>).</p>
        <table-wrap position="float" id="table7">
          <label>Table 7</label>
          <caption>
            <p>Table 7.F1-scores of the ML<sup>a</sup> methods for both data sets.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="260"/>
            <col width="370"/>
            <col width="370"/>
            <thead>
              <tr valign="top">
                <td>ML method</td>
                <td><italic>F</italic><sub>1</sub>-scores for the ED<sup>b</sup> (top 30)</td>
                <td><italic>F</italic><sub>1</sub>-scores for the BD<sup>c</sup> (top 29)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>SVM<sup>d</sup></td>
                <td>0.535</td>
                <td>0.355</td>
              </tr>
              <tr valign="top">
                <td>kNN<sup>e</sup></td>
                <td>0.505</td>
                <td>0.315</td>
              </tr>
              <tr valign="top">
                <td>MLP<sup>f</sup></td>
                <td>0.470</td>
                <td>0.275</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table7fn1">
              <p><sup>a</sup>ML: machine learning.</p>
            </fn>
            <fn id="table7fn2">
              <p><sup>b</sup>ED: extended data set.</p>
            </fn>
            <fn id="table7fn3">
              <p><sup>c</sup>BD: basic data set.</p>
            </fn>
            <fn id="table7fn4">
              <p><sup>d</sup>SVM: support vector machine.</p>
            </fn>
            <fn id="table7fn5">
              <p><sup>e</sup>kNN: k-nearest neighbor.</p>
            </fn>
            <fn id="table7fn6">
              <p><sup>f</sup>MLP: multilayer perceptron.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>In addition, the confusion matrices of the SVM, kNN, and MLP among both conditions are shown in <xref rid="figure2" ref-type="fig">Figure 2</xref>. Each column and row represent 1 treatment category. The rows represent the actual (annotated) categories. The columns represent the predicted treatment categories by classifier. The numbers in the cells of a confusion matrix represent the number of samples that have been predicted for the column but are annotated for the row. High numbers in the cells on the diagonal line from the upper left to the lower right cell represent TPs (correctly predicted samples). The numbers in the surrounding cells represent faulty detections. Consequently, yellow and green colors in the diagonal are good, and blue in the surrounding is good as it represents a low number of misses. Yellow and green in the surroundings indicate a stronger error.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Confusion matrices for data set–specific ML models for the ED with 30 features and the BD with 29 features. BD: basic data set; ED: extended data set; kNN: k-nearest neighbor; ML: machine learning; MLP: multilayer perceptron; SVM: support vector machine.</p>
          </caption>
          <graphic xlink:href="jmir_v26i1e46857_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>The confusion matrices highlighted the benefit of the additional referral letter parameters, as the ED had a much higher agreement among the predicted and true labels than the BD, which is indicated by having more yellow and green on the diagonal upper left to lower right and more blue surrounding cells in the ED compared to the BD.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>The results of this study indicate that quantitative self-report data from patients with LBP can be enriched by unstructured and qualitative data collected from referral letters as part of EHRs using NLP. NLP appears as a feasible option, and we found that the performance of our ML models increased significantly by up to 19.5%. When considering the relevance of referral reasons from EHRs, especially the referral reasons for the AnesthesiologieReRe and RehabReRe categories were relevant, being the second- and fourth-most important referral features of the 30 relevant items. Considering the occurrence of corresponding fields, in 180 referrals, there was a question for the anesthesiology treatment, whereas 228 patients were actually triaged to anesthesiology. For the 571 patients triaged to rehabilitation, in 442 occurrences, the referral reason indicated rehabilitation as well, with an agreement of 38.4%, indicating that the referrer influences the triaging process for the patient in secondary and tertiary care.</p>
        <p>What we could not find were direct referrals to a neurosurgery intervention, probably because this is unusual in the Netherlands. More common is to refer patients with a referral reason to more diagnostics by, for example, a neurologist who will, in positive cases, refer them to neurosurgery. With neurosurgery being a small sample in our data set and the code words resulting from visual inspection of the data set, that might relate to one of the following:</p>
        <list list-type="bullet">
          <list-item>
            <p>The suggestion is less specific within the text and may also be stated as “Please, more diagnosis” or “Are there treatment options?”</p>
          </list-item>
          <list-item>
            <p>The small data sample is less representative of the neurosurgery category because only limited cases included neurosurgery and we used the unbalanced data set in the feature selection.</p>
          </list-item>
        </list>
        <p>Although the patient goals for help in the domains of “pain reduction” with 42% and “better functioning” with 32% cover the majority of clusters, none of these goals could be directly associated with the triaging decision.</p>
        <p>Evaluating the effect of the 2 included referral reasons on the accuracy of the ML models, classic ML approaches (ie, SVM, kNN, and MLP) were chosen as these are reportedly more suitable for such small data sets than deeper neural network architectures. The corresponding results in <xref ref-type="table" rid="table6">Table 6</xref> clarify the relevance of the referral reasons in achieving a significantly improved triaging accuracy ranging between 18% and 19.5%. To investigate the effect, these 2 referral reasons hold for ML-supported decision support, and we investigated the confusion matrices (<xref rid="figure2" ref-type="fig">Figure 2</xref>). In all cases, we saw a significantly enhanced accuracy of the predicted and annotated treatment categories when considering the referral reasons (ED) compared to not considering them (BD).</p>
        <p>It can be concluded that for clinical significance, EHR data can hold valuable information for the prediction of triaging patients with LBP to their treatment. Especially the wording and referrals of the general physician or secondary care specialist significantly and relevantly increase ML model fits. The goals and desires of the patient do not contribute to the prediction of triaging.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>There are a number of limitations that should be addressed. First, the unbalanced data set and the overrepresented rehabilitation intervention category held 571 (47%) cases, while neurosurgery held only 109 (9%) cases. Considering the referral reasons, we found a similar unbalanced distribution. These unbalanced data might have led to an overrepresented data accuracy of rehabilitation compared to neurosurgery. Therefore, we applied SMOTE data augmentation for the ML model training. With only 59 data entries being available for training the treatment category neurosurgery, nearly 90% of the corresponding training entries were augmented. In addition, only a limited number of referral letters and the included referral reasons and patient goals were available for this treatment category. Consequently, the meaningfulness of the findings regarding the treatment category neurosurgery should be confirmed in another data set. In contrast to this minority treatment category, the results of the other treatment categories can be assumed to be representative.</p>
        <p>A second limitation is the number of missing data and letters that we could derive from the EHRs. Although most could be retrieved, it appeared impossible to retrieve all letters, and in some cases, letters may have bene be missing or may not have been uploaded properly. In addition, although cases were missing, it may have led to higher external validity. In many real-world clinical situations, data sets are incomplete. Therefore, we decided to include what we could derive following a commonly applied approach.</p>
        <p>Lastly, we could, based on these baseline data, not conclude whether the triaging to the treatment was the correct triaging in terms of the treatment with the highest benefit to the patient and whether the patient indeed was successfully treated. Future longitudinal studies may lead to a better understanding of the use of ML-based clinical decision-making in patients with LBP, for example, by including the results of treatments.</p>
      </sec>
      <sec>
        <title>Strengths</title>
        <p>In addition to the quantitative research questions that we answered, this study contributes to the discussion of the meaningfulness of the general physician’s referral reasons and patient goals in a group of patients with LBP. Correspondingly, the resulting input feature ranking of both data sets is expected to represent the information relevance of the feature and might indicate the impact, referral reasons, and patient goals have on treatment category (class) selection.</p>
        <p>Considering the generalizability toward an additional language or to other LBP-related questionnaires should be straightforward. Although adjustments of search terms and potential alternative document structures are required, the proposed approach allows quick adaptability. Covering additional diseases or using additional or different questionnaires will require clinical and methodological knowledge of the corresponding domain experts.</p>
      </sec>
      <sec>
        <title>Conclusion</title>
        <p>Among the ReliefF-prioritized features, 2 referral reason features were highly relevant, and their consideration increased the <italic>F</italic><sub>1</sub>-score accuracy of the models by up to 19.5%. The results were confirmed by visual inspection of confusion matrices, although the overall performance of the ML models remains low and they cannot be clinically applied at this moment.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Referral reason categories and code words.</p>
        <media xlink:href="jmir_v26i1e46857_app1.png" xlink:title="PNG File , 198 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Patient goal categories and code words.</p>
        <media xlink:href="jmir_v26i1e46857_app2.png" xlink:title="PNG File , 221 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">BD</term>
          <def>
            <p>basic data set</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CDSS</term>
          <def>
            <p>clinical decision support system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">DSS</term>
          <def>
            <p>decision support system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">ED</term>
          <def>
            <p>extended data set</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">FN</term>
          <def>
            <p>false negative</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">FP</term>
          <def>
            <p>false positive</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">kNN</term>
          <def>
            <p>k-nearest neighbor</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">LBP</term>
          <def>
            <p>low back pain</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">ML</term>
          <def>
            <p>machine learning</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">MLP</term>
          <def>
            <p>multilayer perceptron</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">NH</term>
          <def>
            <p>neighboring samples of class hits</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">NLP</term>
          <def>
            <p>natural language processing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">NM</term>
          <def>
            <p>neighboring samples of class misses</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">PA</term>
          <def>
            <p>physician assistant</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">ReLU</term>
          <def>
            <p>rectified linear unit</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb17">SMOTE</term>
          <def>
            <p>synthetic minority oversampling technique</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb18">SVM</term>
          <def>
            <p>support vector machine</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb19">TP</term>
          <def>
            <p>true positive</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study was funded by the Oldenburg Research Pool (FP 2019-035).</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>SF contributed to the design, methods, analysis, and drafting of the paper; CB, design, methods, discussion, and review of the paper; JS and HT, design, methods, analyses, and review of the paper; PS, design, methods, analysis, discussion, and review of the paper; HRS, MFR, and APW, design, data gathering, results, discussion, and review of the paper; and RS, design, methods, analyses, discussion, and drafting of the paper.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</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>Maher</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Underwood</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Buchbinder</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Non-specific low back pain</article-title>
          <source>Lancet</source>
          <year>2017</year>
          <month>02</month>
          <volume>389</volume>
          <issue>10070</issue>
          <fpage>736</fpage>
          <lpage>747</lpage>
          <pub-id pub-id-type="doi">10.1016/s0140-6736(16)30970-9</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>Foster</surname>
              <given-names>NE</given-names>
            </name>
            <name name-style="western">
              <surname>Anema</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Cherkin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Chou</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>Gross</surname>
              <given-names>DP</given-names>
            </name>
            <name name-style="western">
              <surname>Ferreira</surname>
              <given-names>PH</given-names>
            </name>
            <name name-style="western">
              <surname>Fritz</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Koes</surname>
              <given-names>BW</given-names>
            </name>
            <name name-style="western">
              <surname>Peul</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Maher</surname>
              <given-names>CG</given-names>
            </name>
            <name name-style="western">
              <surname>Buchbinder</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hartvigsen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cherkin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Foster</surname>
              <given-names>NE</given-names>
            </name>
            <name name-style="western">
              <surname>Maher</surname>
              <given-names>CG</given-names>
            </name>
            <name name-style="western">
              <surname>Underwood</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Tulder</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Anema</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Chou</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>Menezes Costa</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Croft</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ferreira</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ferreira</surname>
              <given-names>PH</given-names>
            </name>
            <name name-style="western">
              <surname>Fritz</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Genevay</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gross</surname>
              <given-names>DP</given-names>
            </name>
            <name name-style="western">
              <surname>Hancock</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hoy</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Karppinen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Koes</surname>
              <given-names>BW</given-names>
            </name>
            <name name-style="western">
              <surname>Kongsted</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Louw</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Öberg</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Peul</surname>
              <given-names>WC</given-names>
            </name>
            <name name-style="western">
              <surname>Pransky</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Schoene</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sieper</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Smeets</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Woolf</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Prevention and treatment of low back pain: evidence, challenges, and promising directions</article-title>
          <source>Lancet</source>
          <year>2018</year>
          <month>06</month>
          <volume>391</volume>
          <issue>10137</issue>
          <fpage>2368</fpage>
          <lpage>2383</lpage>
          <pub-id pub-id-type="doi">10.1016/s0140-6736(18)30489-6</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>Foster</surname>
              <given-names>NE</given-names>
            </name>
            <name name-style="western">
              <surname>Hill</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>O'Sullivan</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hancock</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Stratified models of care</article-title>
          <source>Best Pract Res Clin Rheumatol</source>
          <year>2013</year>
          <month>10</month>
          <volume>27</volume>
          <issue>5</issue>
          <fpage>649</fpage>
          <lpage>61</lpage>
          <pub-id pub-id-type="doi">10.1016/j.berh.2013.10.005</pub-id>
          <pub-id pub-id-type="medline">24315146</pub-id>
          <pub-id pub-id-type="pii">S1521-6942(13)00081-8</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>Linton</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Halldén</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Can we screen for problematic back pain? A screening questionnaire for predicting outcome in acute and subacute back pain</article-title>
          <source>Clin J Pain</source>
          <year>1998</year>
          <month>09</month>
          <volume>14</volume>
          <issue>3</issue>
          <fpage>209</fpage>
          <lpage>15</lpage>
          <pub-id pub-id-type="doi">10.1097/00002508-199809000-00007</pub-id>
          <pub-id pub-id-type="medline">9758070</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>Hill</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Dunn</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mullis</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Main</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Foster</surname>
              <given-names>NE</given-names>
            </name>
            <name name-style="western">
              <surname>Hay</surname>
              <given-names>EM</given-names>
            </name>
          </person-group>
          <article-title>A primary care back pain screening tool: identifying patient subgroups for initial treatment</article-title>
          <source>Arthritis Rheum</source>
          <year>2008</year>
          <month>05</month>
          <day>15</day>
          <volume>59</volume>
          <issue>5</issue>
          <fpage>632</fpage>
          <lpage>41</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://onlinelibrary.wiley.com/doi/10.1002/art.23563"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/art.23563</pub-id>
          <pub-id pub-id-type="medline">18438893</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>da Silva</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Macaskill</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kongsted</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mills</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Maher</surname>
              <given-names>CG</given-names>
            </name>
            <name name-style="western">
              <surname>Hancock</surname>
              <given-names>MJ</given-names>
            </name>
          </person-group>
          <article-title>Predicting pain recovery in patients with acute low back pain: updating and validation of a clinical prediction model</article-title>
          <source>Eur J Pain</source>
          <year>2019</year>
          <month>02</month>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>341</fpage>
          <lpage>353</lpage>
          <pub-id pub-id-type="doi">10.1002/ejp.1308</pub-id>
          <pub-id pub-id-type="medline">30144211</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>d’Hollosy</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>van Velsen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Poel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Groothuis-Oudshoorn</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Soer</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Stegeman</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hermens</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Applying machine learning on patient-reported data to model the selection of appropriate treatments for low back pain: a pilot study</article-title>
          <year>2020</year>
          <conf-name>BIOSTEC 2020: 13th International Joint Conference on Biomedical Engineering Systems and Technologies</conf-name>
          <conf-date>February 24-26, 2020</conf-date>
          <conf-loc>Valetta, Malta</conf-loc>
          <pub-id pub-id-type="doi">10.5220/0008962101170124</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>van Hooff</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>van Loon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>van Limbeek</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>de Kleuver</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The Nijmegen decision tool for chronic low back pain. Development of a clinical decision tool for secondary or tertiary spine care specialists</article-title>
          <source>PLoS One</source>
          <year>2014</year>
          <month>8</month>
          <day>18</day>
          <volume>9</volume>
          <issue>8</issue>
          <fpage>e104226</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0104226"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0104226</pub-id>
          <pub-id pub-id-type="medline">25133645</pub-id>
          <pub-id pub-id-type="pii">PONE-D-14-13335</pub-id>
          <pub-id pub-id-type="pmcid">PMC4136789</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>Dutmer</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Schiphorst Preuper</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Soer</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Brouwer</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bültmann</surname>
              <given-names>Ute</given-names>
            </name>
            <name name-style="western">
              <surname>Dijkstra</surname>
              <given-names>PU</given-names>
            </name>
            <name name-style="western">
              <surname>Coppes</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Stegeman</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Buskens</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>van Asselt</surname>
              <given-names>ADI</given-names>
            </name>
            <name name-style="western">
              <surname>Wolff</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Reneman</surname>
              <given-names>MF</given-names>
            </name>
          </person-group>
          <article-title>Personal and societal impact of low back pain: The Groningen Spine Cohort</article-title>
          <source>Spine (Phila Pa 1976)</source>
          <year>2019</year>
          <month>12</month>
          <day>15</day>
          <volume>44</volume>
          <issue>24</issue>
          <fpage>E1443</fpage>
          <lpage>E1451</lpage>
          <pub-id pub-id-type="doi">10.1097/BRS.0000000000003174</pub-id>
          <pub-id pub-id-type="medline">31369481</pub-id>
          <pub-id pub-id-type="pii">00007632-201912150-00009</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>EuroQol Group</collab>
          </person-group>
          <article-title>EuroQol--a new facility for the measurement of health-related quality of life</article-title>
          <source>Health Policy</source>
          <year>1990</year>
          <month>12</month>
          <volume>16</volume>
          <issue>3</issue>
          <fpage>199</fpage>
          <lpage>208</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/0168-8510(90)90421-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/0168-8510(90)90421-9</pub-id>
          <pub-id pub-id-type="medline">10109801</pub-id>
          <pub-id pub-id-type="pii">0168-8510(90)90421-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Deyo</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Dworkin</surname>
              <given-names>SF</given-names>
            </name>
            <name name-style="western">
              <surname>Amtmann</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Andersson</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Borenstein</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Carragee</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Carrino</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chou</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Cook</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>DeLitto</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Goertz</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Khalsa</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Loeser</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mackey</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Panagis</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rainville</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tosteson</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Turk</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Von Korff</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Weiner</surname>
              <given-names>DK</given-names>
            </name>
          </person-group>
          <article-title>Report of the NIH Task Force on research standards for chronic low back pain</article-title>
          <source>Spine</source>
          <year>2014</year>
          <volume>39</volume>
          <issue>14</issue>
          <fpage>1128</fpage>
          <lpage>1143</lpage>
          <pub-id pub-id-type="doi">10.1097/brs.0000000000000434</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>El Fassi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bocquet</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Majery</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Lair</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Couffignal</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mairiaux</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Work ability assessment in a worker population: comparison and determinants of Work Ability Index and Work Ability score</article-title>
          <source>BMC Public Health</source>
          <year>2013</year>
          <month>04</month>
          <day>08</day>
          <volume>13</volume>
          <fpage>305</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpublichealth.biomedcentral.com/articles/10.1186/1471-2458-13-305"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1471-2458-13-305</pub-id>
          <pub-id pub-id-type="medline">23565883</pub-id>
          <pub-id pub-id-type="pii">1471-2458-13-305</pub-id>
          <pub-id pub-id-type="pmcid">PMC3637198</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pejtersen</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Kristensen</surname>
              <given-names>TS</given-names>
            </name>
            <name name-style="western">
              <surname>Borg</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Bjorner</surname>
              <given-names>JB</given-names>
            </name>
          </person-group>
          <article-title>The second version of the Copenhagen Psychosocial Questionnaire</article-title>
          <source>Scand J Public Health</source>
          <year>2010</year>
          <month>02</month>
          <volume>38</volume>
          <issue>3 Suppl</issue>
          <fpage>8</fpage>
          <lpage>24</lpage>
          <pub-id pub-id-type="doi">10.1177/1403494809349858</pub-id>
          <pub-id pub-id-type="medline">21172767</pub-id>
          <pub-id pub-id-type="pii">38/3_suppl/8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chawla</surname>
              <given-names>NV</given-names>
            </name>
            <name name-style="western">
              <surname>Bowyer</surname>
              <given-names>KW</given-names>
            </name>
            <name name-style="western">
              <surname>Hall</surname>
              <given-names>LO</given-names>
            </name>
            <name name-style="western">
              <surname>Kegelmeyer</surname>
              <given-names>WP</given-names>
            </name>
          </person-group>
          <article-title>SMOTE: synthetic minority over-sampling technique</article-title>
          <source>J Artif Intell Res</source>
          <year>2002</year>
          <month>06</month>
          <day>01</day>
          <volume>16</volume>
          <fpage>321</fpage>
          <lpage>357</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1613/jair.953"/>
          </comment>
          <pub-id pub-id-type="doi">10.1613/jair.953</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <article-title>Over-sampling methods</article-title>
          <source>Imbalanced learn</source>
          <access-date>2023-12-11</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://imbalanced-learn.org/stable/references/over_sampling.html#module-imblearn.over_sampling">https://imbalanced-learn.org/stable/references/over_sampling.html#module-imblearn.over_sampling</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bray</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>STD 90, RFC 8259: the JavaScript Object Notation (JSON) Data Interchange Format</article-title>
          <source>RFC Editor</source>
          <year>2017</year>
          <month>12</month>
          <access-date>2023-12-11</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.rfc-editor.org/info/rfc8259">https://www.rfc-editor.org/info/rfc8259</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <article-title>re — Regular expression operations</article-title>
          <source>Python Software Foundation</source>
          <access-date>2023-12-11</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://docs.python.org/3/library/re.html">https://docs.python.org/3/library/re.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Robnik-Šikonja</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kononenko</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>An adaptation of Relief for attribute estimation in regression</article-title>
          <year>1997</year>
          <conf-name>ICML '97: Fourteenth International Conference on Machine Learning</conf-name>
          <conf-date>July 8-12, 1997</conf-date>
          <conf-loc>Nashville, TN</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Robnik-Šikonja</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kononenko</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Theoretical and empirical analysis of ReliefF and RReliefF</article-title>
          <source>Mach Learn</source>
          <year>2003</year>
          <month>10</month>
          <volume>53</volume>
          <issue>1/2</issue>
          <fpage>23</fpage>
          <lpage>69</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1023/a:1025667309714"/>
          </comment>
          <pub-id pub-id-type="doi">10.1023/a:1025667309714</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Guyon</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Nikravesh</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gunn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zadeh</surname>
              <given-names>LA</given-names>
            </name>
          </person-group>
          <source>Feature Extraction</source>
          <year>2006</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kononenko</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Estimating attributes: analysis and extensions of RELIEF</article-title>
          <year>1994</year>
          <conf-name>Machine Learning: ECML-94; European Conference on Machine Learning</conf-name>
          <conf-date>April 6-8, 1994</conf-date>
          <conf-loc>Catania, Italy</conf-loc>
          <fpage>171</fpage>
          <lpage>182</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1007/3-540-57868-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/3-540-57868-4_57</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kira</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rendell</surname>
              <given-names>LA</given-names>
            </name>
          </person-group>
          <article-title>The feature selection problem: traditional methods and a new algorithm</article-title>
          <year>1992</year>
          <conf-name>AAAI-92: Tenth National Conference on Artificial Intelligence</conf-name>
          <conf-date>July 12-16, 1992</conf-date>
          <conf-loc>San Jose, CA</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <article-title>NLP_Triaging Source Code</article-title>
          <source>GitHub</source>
          <access-date>2023-12-11</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/fudickar-lab/NLP_Triaging">https://github.com/fudickar-lab/NLP_Triaging</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
