<?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>Gunther Eysenbach</publisher-name>
                <publisher-loc>Centre for Global eHealth Innovation, Toronto, Canada</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="publisher-id">v12i4e45</article-id>
            <article-id pub-id-type="pmid">20923755</article-id>
            <article-id pub-id-type="doi">10.2196/jmir.1538</article-id>
            <article-categories>
                <subj-group subj-group-type="article-type">
                    <subject>Original Paper</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Biomedical Informatics Techniques for Processing and Analyzing Web Blogs of Military Service Members</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="editor">
                    <name>
                        <surname>Eysenbach</surname>
                        <given-names>Gunther</given-names>
                    </name>
                </contrib>
            </contrib-group>
            <contrib-group>
                <contrib contrib-type="reviewer">
                    <name>
                        <surname>Gundlapalli</surname>
                        <given-names>Adi</given-names>
                    </name>
                </contrib>
                <contrib contrib-type="reviewer">
                    <name>
                        <surname>Matheny</surname>
                        <given-names>Michael</given-names>
                    </name>
                </contrib>
                <contrib contrib-type="reviewer">
                    <name>
                        <surname>Freifeld</surname>
                        <given-names>Clark</given-names>
                    </name>
                </contrib>
            </contrib-group>
            <contrib-group>
                <contrib contrib-type="author" id="contrib1">
                    <name name-style="western">
                        <surname>Konovalov</surname>
                        <given-names>Sergiy</given-names>
                    </name>
                    <degrees>MD</degrees>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib2" corresp="yes">
                    <name name-style="western">
                        <surname>Scotch</surname>
                        <given-names>Matthew</given-names>
                    </name>
                    <degrees>PhD MPH</degrees>
                    <address>
                        <institution>Arizona State University</institution>
                        <addr-line>425 N 5th St., ABC1</addr-line>
                        <addr-line> Phoenix, AZ 85004</addr-line>
                        <country>USA</country>
                        <phone>1 602 827 2540</phone>
                        <fax>1 602 827 2564</fax>
                        <email>matthew.scotch@yale.edu</email>
                    </address>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib3">
                    <name name-style="western">
                        <surname>Post</surname>
                        <given-names>Lori</given-names>
                    </name>
                    <degrees>PhD</degrees>
                    <xref ref-type="aff" rid="aff2">2</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib4">
                    <name name-style="western">
                        <surname>Brandt</surname>
                        <given-names>Cynthia</given-names>
                    </name>
                    <degrees>MD MPH</degrees>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
            </contrib-group>
            <aff id="aff2" rid="aff2">
                <sup>2</sup>
                <institution>Department of Emergency Medicine</institution>
                <institution>Yale University</institution>
                <addr-line>New Haven, CT</addr-line>
                <country>USA</country>
            </aff>
            <aff id="aff1" rid="aff1">
                <sup>1</sup>
                <institution>Yale Center for Medical Informatics</institution>
                <institution>Yale University</institution>
                <addr-line>New Haven, CT</addr-line>
                <country>USA</country>
            </aff>
            <pub-date pub-type="collection">
                <season>Oct-Dec</season>
                <year>2010</year>
            </pub-date>
            <pub-date pub-type="epub">
                <day>05</day>
                <month>10</month>
                <year>2010</year>
            </pub-date>
            <volume>12</volume>
            <issue>4</issue>
            <elocation-id>e45</elocation-id>
            <!--history from ojs - api-xml-->
            <history>
                <date date-type="received">
                    <day>01</day>
                    <month>04</month>
                    <year>2010</year>
                </date>
                <date date-type="rev-request">
                    <day>25</day>
                    <month>04</month>
                    <year>2010</year>
                </date>
                <date date-type="rev-recd">
                    <day>11</day>
                    <month>08</month>
                    <year>2010</year>
                </date>
                <date date-type="accepted">
                    <day>21</day>
                    <month>08</month>
                    <year>2010</year>
                </date>
            </history>
            <!--(c) the authors - correct author names and publication date here if necessary. Date in form ', dd.mm.yyyy' after jmir.org-->
            <copyright-statement>&#169;Sergiy Konovalov, Matthew Scotch, Lori Post, Cynthia Brandt. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 05.10.2010 &#160;</copyright-statement>
            <copyright-year>2010</copyright-year>
            <license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/2.0/">
                <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/2.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 http://www.jmir.org/, as well as this copyright and license information must be included.</p>
            </license>
            <self-uri xlink:href="http://www.jmir.org/2010/4/e45/" xlink:type="simple" />
            <abstract>
                <sec>
                    <title>Introduction</title>
                    <p>Web logs (&#8220;blogs&#8221;) have become a popular mechanism for people to express their daily thoughts, feelings, and emotions. Many of these expressions contain health care-related themes, both physical and mental, similar to information discussed during a clinical interview or medical consultation. Thus, some of the information contained in blogs might be important for health care research, especially in mental health where stress-related conditions may be difficult and expensive to diagnose and where early recognition is often key to successful treatment. In the field of biomedical informatics, techniques such as information retrieval (IR) and natural language processing (NLP) are often used to unlock information contained in free-text notes. These methods might assist the clinical research community to better understand feelings and emotions post deployment and the burden of symptoms of stress among US military service members.</p>
                </sec>
                <sec>
                    <title>Methods</title>
                    <p>In total, 90 military blog posts describing deployment situations and 60 control posts of Operation Enduring Freedom/Operation Iraqi Freedom (OEF/OIF) were collected. After &#8220;stop&#8221; word exclusion and stemming, a &#8220;bag-of-words&#8221; representation and term weighting was performed, and the most relevant words were manually selected out of the high-weight words. A pilot ontology was created using Collaborative Prot&#233;g&#233;, a knowledge management application. The word lists and the ontology were then used within General Architecture for Text Engineering (GATE), an NLP framework, to create an automated pipeline for recognition and analysis of blogs related to combat exposure. An independent expert opinion was used to create a reference standard and evaluate the results of the GATE pipeline.</p>
                </sec>
                <sec>
                    <title>Results</title>
                    <p>The 2 dimensions of combat exposure descriptors identified were: words dealing with physical exposure and the soldiers&#8217; emotional reactions to it. GATE pipeline was able to retrieve blog texts describing combat exposure with precision 0.9, recall 0.75, and F-score 0.82.</p>
                </sec>
                <sec>
                    <title>Discussion</title>
                    <p>Natural language processing and automated information retrieval might potentially provide valuable tools for retrieving and analyzing military blog posts and uncovering military service members&#8217; emotions and experiences of combat exposure.</p>
                </sec>
            </abstract>
            <kwd-group>
                <kwd>Blogging</kwd>
                <kwd>medical informatics</kwd>
                <kwd>military personnel</kwd>
                <kwd>information storage and retrieval</kwd>
                <kwd>combat disorders</kwd>
            </kwd-group>
        </article-meta>
    </front>
    <body>
        <sec sec-type="introduction">
            <title>Introduction</title>
            <p>Web logs (&#8220;blogs&#8221;) have become a popular mechanism for people to express their daily thoughts, feelings, and emotions. Much of the information contained in blogs includes health-related themes, both physical and mental. The matters described in a blog post may be very similar to the information discussed during a clinical interview or psychological consultation. Therefore, blogs might contain information that could be important for clinical research, especially in the mental health field where stress-related symptoms are often difficult to ascertain or measure and where timely recognition is often key to successful therapy [<xref ref-type="bibr" rid="ref1">1</xref>].</p>
            <p>In the field of biomedical informatics, information retrieval (IR) techniques (such as automated indexing) and natural language processing (NLP) are commonly used to unlock information contained in free narrative-style text notes [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref4">4</xref>]. With a focus on blogs, these methods can support &#8220;infoveillance&#8221; [<xref ref-type="bibr" rid="ref5">5</xref>] and assist the clinical research community to better understand feelings and emotions post deployment and the burden of symptoms of stress among US military service members. In this study, we sought to evaluate the potential for using available IR and NLP tools to unlock information in blogs related to US military service members&#8217; experiences and emotions of combat exposure by analyzing the blogs of the military personnel deployed during Operation Enduring Freedom/Operation Iraqi Freedom (OEF/OIF).</p>
        </sec>
        <sec sec-type="methods">
            <title>Methods</title>
            <sec>
                <title>Blog Selection</title>
                <p>The authors evaluated military blogs available on the Internet and manually selected 90 blog posts describing combat exposure according to selection criteria. Military blogs catalog Milblogging.com [<xref ref-type="bibr" rid="ref6">6</xref>] lists over 2500 English-language military blogs and provides basic categorization functionality (sorting by location, time, popularity etc). Three authors (SK, MS, CB) independently used the ordered list of blogs from Iraq and Afghanistan in the period of 2002 to 2008 from this site and selected 1 to 3 blog posts from each site that (1) were in the English language, (2) contained a first person description of the events, (3) were not less than 5 sentences long, (4) were not written for business purposes (eg, news piece or military report), and (5) described concrete situations and events related to active duty.</p>
                <p>Of the collected blog posts describing combat exposure, 50 were used for indexing and term weighting and 40 for the pilot evaluation and analysis.</p>
                <p>Two of the authors (CB, MS) selected 60 blog posts from Milblogging.com conforming to the same selection criteria listed above except that they did not necessarily describe combat exposure. These 60 blogs were used as a control set during evaluation.</p>
            </sec>
            <sec>
                <title>Indexing and Term Weighting</title>
                <p>A &#8220;bag-of-words&#8221; representation was employed to analyze and categorize the blog texts. In this model, the word order is not taken into consideration, and each text is treated as simply a collection of words. Such text representation is used in most typical approaches to text classification [<xref ref-type="bibr" rid="ref7">7</xref>].</p>
                <p>Python version 2.6.2 [<xref ref-type="bibr" rid="ref8">8</xref>] with Natural Language Toolkit (NLTK) version 2.0b6 [<xref ref-type="bibr" rid="ref9">9</xref>] was used for data preprocessing and term weight calculation. Data preprocessing included tokenizing (breaking up the texts into separate words), stemming, and removal of &#8220;stop&#8221; words. Stemming is the process of reducing morphologically related words to their common base form. Alternate spellings were treated as unique words during the stemming phase. The stop word list was created in order to automatically discard common words, that is, stop words, that by definition do not have any combat-specific meaning (articles, prepositions, and words such as go, do, have).</p>
                <p>Term weighting is a standard procedure used in automated indexing to assess the importance of individual words in a corpus of documents [<xref ref-type="bibr" rid="ref10">10</xref>]. We used &#8220;TF*IDF&#8221; term weighting in order to evaluate word frequency distribution and assess the frequency of occurrence of the words related to combat exposure. In this approach, the indexing weight is a product of term frequency (TF) and inverse document frequency (IDF). TF is a measure of the frequency of a word across a set (corpus) of documents, and IDF is a measure of the frequency of a word within a given document.</p>
            </sec>
            <sec>
                <title>Ontology Creation and Use</title>
                <p>The resulting frequency distribution tables were reviewed by three authors (CB, MS, SK) in order to select the words relevant to combat exposure used in blog posts. Upon discussion and consensus from all authors, the list of relevant words was created. After that, the selected words were used in creation of a pilot ontology. An ontology is a way to create formal definitions of concepts by specifying semantic relationships between these concepts [<xref ref-type="bibr" rid="ref11">11</xref>]. Creation of the ontology is an important step for future research as several open-source NLP suites have ontology-aware tools. Collaborative Prot&#233;g&#233; (version 3.4.4, build 579) [<xref ref-type="bibr" rid="ref12">12</xref>], an ontology editor, was used to create and store the ontology.</p>
                <p>The ontology was imported into General Architecture for Text Engineering (GATE) NLP framework (version 5.2.1, build 3581) [<xref ref-type="bibr" rid="ref13">13</xref>]. GATE is one of several available open-source NLP tools. The ontology and word lists were used to construct ontology-based gazetteers: alphabetized word lists that are used by GATE for text analysis. The ontology annotation tool, Java Annotation Patterns Engine (JAPE) [<xref ref-type="bibr" rid="ref14">14</xref>], was then applied to further refine text tagging. JAPE grammar is a set of (modifiable) rules that determine actions that are implemented during the annotation [<xref ref-type="bibr" rid="ref14">14</xref>].</p>
            </sec>
            <sec>
                <title>Pilot Evaluation</title>
                <p>NLP performance was evaluated by an author (LP), who is an expert in the field of evaluation. Here, focus was on whether our system was able to identify blogs related to the deployment experience (and therefore of interest to the health care provider) from a larger set of texts. Selected posts from the combat exposure set and the control set were run through the GATE pipeline and at the same time reviewed by the fourth author (LP), who was previously unfamiliar with the ontology and word lists but who has had extensive experience in clinical work with military service members. The blog posts were categorized by this author into 2 groups: those that did and did not describe clinically relevant combat exposure. The results of the GATE pipeline on the same blog posts were then evaluated in reference to this clinical categorization (ie, the &#8220;expert standard&#8221;). Standard information retrieval metrics in biomedical informatics literature such as precision, recall, and F-score were used for the evaluation [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>].</p>
            </sec>
        </sec>
        <sec sec-type="results">
            <title>Results</title>
            <p>After stemming and stop words exclusion, the indexing weights of all word stems in blog posts were calculated. We selected 263 word stems related to combat exposure out of those which had indexing weight above 0.1. The 20 most frequent word stems (those with the largest weight) are shown in <xref ref-type="table" rid="table1">Table 1</xref>.</p>
            <table-wrap id="table1" position="float">
                <label>Table 1</label>
                <caption>
                    <p>Most frequent word stems related to combat exposure</p>
                </caption>
                <table cellpadding="8" cellspacing="0" border="1" rules="groups" frame="hsides" width="1000">
                    <col width="333" />
                    <col width="333" />
                    <col width="333" />
                    <thead>
                        <tr valign="top">
                            <td>Word Stem</td>
                            <td>Weight</td>
                            <td>Index Document <break /> Frequency (IDF)</td>
                        </tr>
                    </thead>
                    <tbody>
                        <tr valign="top">
                            <td>Explos</td>
                            <td>1.38</td>
                            <td>0.71</td>
                        </tr>
                        <tr valign="top">
                            <td>Mission</td>
                            <td>1.37</td>
                            <td>0.72</td>
                        </tr>
                        <tr valign="top">
                            <td>Truck</td>
                            <td>1.37</td>
                            <td>0.72</td>
                        </tr>
                        <tr valign="top">
                            <td>Soldier</td>
                            <td>1.24</td>
                            <td>0.82</td>
                        </tr>
                        <tr valign="top">
                            <td>See</td>
                            <td>1.20</td>
                            <td>0.85</td>
                        </tr>
                        <tr valign="top">
                            <td>Fire</td>
                            <td>1.17</td>
                            <td>0.87</td>
                        </tr>
                        <tr valign="top">
                            <td>Patrol</td>
                            <td>1.15</td>
                            <td>0.89</td>
                        </tr>
                        <tr valign="top">
                            <td>Vehicl</td>
                            <td>1.08</td>
                            <td>0.94</td>
                        </tr>
                        <tr valign="top">
                            <td>Hit</td>
                            <td>1.05</td>
                            <td>0.96</td>
                        </tr>
                        <tr valign="top">
                            <td>Attack</td>
                            <td>1.05</td>
                            <td>0.96</td>
                        </tr>
                        <tr valign="top">
                            <td>Stop</td>
                            <td>1.05</td>
                            <td>0.96</td>
                        </tr>
                        <tr valign="top">
                            <td>Deton</td>
                            <td>1.00</td>
                            <td>1.0</td>
                        </tr>
                        <tr valign="top">
                            <td>Bomb</td>
                            <td>0.97</td>
                            <td>1.02</td>
                        </tr>
                        <tr valign="top">
                            <td>Secur</td>
                            <td>0.91</td>
                            <td>1.07</td>
                        </tr>
                        <tr valign="top">
                            <td>Mortar</td>
                            <td>0.91</td>
                            <td>1.07</td>
                        </tr>
                        <tr valign="top">
                            <td>Deploy</td>
                            <td>0.88</td>
                            <td>1.10</td>
                        </tr>
                        <tr valign="top">
                            <td>Shot</td>
                            <td>0.84</td>
                            <td>1.12</td>
                        </tr>
                        <tr valign="top">
                            <td>Happen</td>
                            <td>0.81</td>
                            <td>1.15</td>
                        </tr>
                        <tr valign="top">
                            <td>Weapon</td>
                            <td>0.81</td>
                            <td>1.15</td>
                        </tr>
                    </tbody>
                </table>
            </table-wrap>
            <sec>
                <title>Combat Exposure Dimensions</title>
                <p>Words related to combat exposure events had 2 different dimensions: (1) characteristics of the physical exposure itself such as firing a weapon, being attacked, or witnessing an explosion (eg, &#8220;explosion,&#8221; &#8220;bomb,&#8221; &#8220;shot&#8221;) and (2) feelings and emotions associated with the exposure such as being scared, feeling compassion (eg, &#8220;secure,&#8221; &#8220;hope&#8221;). The most frequent words were manually separated into the 2 categories. These dimensions were then incorporated into the ontology structure.</p>
                <p>Within the ontology we created separate categories for the physical combat exposure and emotions associated with it. Under the exposure category, 2 subcategories were created: direct and indirect. We defined direct exposure as an active involvement in a combat situation (such as firing a weapon), while an example of an indirect exposure would be witnessing a combat-related event. We also created 2 subcategories for the emotions: protective (described by words such as &#8220;hope,&#8221; &#8220;safe,&#8221; &#8220;supporting&#8221;) and stressful (such as &#8220;scared,&#8221; &#8220;upsetting,&#8221; &#8220;nervous&#8221;). <xref ref-type="fig" rid="figure1">Figure 1</xref> shows the ontology we created and how the ontology was used to annotate a sample blog in GATE. Note that on the left in <xref ref-type="fig" rid="figure1">Figure 1</xref> is a GATE screenshot with color-coded ontology categories. The combat-related works in the text are annotated in accordance with the ontology (purple for physical exposure, and pink and brown for emotions). On the right in <xref ref-type="fig" rid="figure1">Figure 1</xref> is a Prot&#233;g&#233; screenshot with ontology.</p>
                <fig id="figure1" position="float">
                    <label>Figure 1</label>
                    <caption>
                        <p>Use of ontology in GATE</p>
                    </caption>
                    <!--Original graphic name: http://writer.zoho.com:80/image.do?imgurl=6d37aff7952c652b15981bdb67ae7d24753f78e991a900217e61b98366e8ce2ef026836400ed911cb1edd9070b272ce3-->
                    <graphic xlink:href="jmir_v12i4e45_fig1.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple" />
                </fig>
            </sec>
            <sec>
                <title>Pilot Evaluation</title>
                <p>We ran 20 randomly selected blog posts through our GATE pipeline and calculated the number of annotations (ie, the number of times words from our ontology were highlighted). For each document, the ratio of the number of annotations to the total word count (N<sub>ann</sub>/N<sub>wc</sub>) of the document was used as a measure of &#8220;richness&#8221; of the text in terms of the words related to combat exposure. We took the median of the ratios for all posts (4.95%) as a threshold. A given post was said to be recognized as relevant to combat exposure when the ratio N<sub>ann</sub>/N<sub>wc</sub> fell above the threshold and irrelevant if the ratio fell below the threshold.</p>
                <table-wrap id="table2" position="float">
                    <label>Table 2</label>
                    <caption>
                        <p>Classification of blog text by relevancy to combat exposure by expert opinion and by our GATE pipeline for which the threshold is 4.95%</p>
                    </caption>
                    <table cellpadding="8" cellspacing="0" border="1" rules="groups" frame="hsides" width="1000">
                        <col width="260" />
                        <col width="390" />
                        <col width="390" />
                        <thead>
                            <tr valign="top">
                                <td />
                                <td colspan="2">Relevance of Text to Combat Exposure (Italics = Relevant, Nonitalics = Irrelevant)</td>
                            </tr>
                            <tr valign="top">
                                <td>Post</td>
                                <td>According to <break /> Expert Opinion</td>
                                <td>According to <break /> GATE Pipeline (N<sub>ann</sub>/N<sub>wc</sub>)</td>
                            </tr>
                        </thead>
                        <tbody>
                            <tr valign="top">
                                <td>Post 1</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>4.59%</td>
                            </tr>
                            <tr valign="top">
                                <td>Post 2</td>
                                <td>No</td>
                                <td>
                                    <italic>5.05%</italic>
                                </td>
                            </tr>
                            <tr valign="top">
                                <td>Post 3</td>
                                <td>No</td>
                                <td>4.31%</td>
                            </tr>
                            <tr valign="top">
                                <td>Post 4</td>
                                <td>No</td>
                                <td>4.18%</td>
                            </tr>
                            <tr valign="top">
                                <td>Post 5</td>
                                <td>No</td>
                                <td>2.80%</td>
                            </tr>
                            <tr valign="top">
                                <td>Post 6</td>
                                <td>No</td>
                                <td>4.46%</td>
                            </tr>
                            <tr valign="top">
                                <td>Post 7</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>
                                    <italic>8.47%</italic>
                                </td>
                            </tr>
                            <tr valign="top">
                                <td>Post 8</td>
                                <td>No</td>
                                <td>3.03%</td>
                            </tr>
                            <tr valign="top">
                                <td>Post 9</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>
                                    <italic>6.83%</italic>
                                </td>
                            </tr>
                            <tr valign="top">
                                <td>Post 10</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>4.84%</td>
                            </tr>
                            <tr valign="top">
                                <td>Post 11</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>
                                    <italic>9.09%</italic>
                                </td>
                            </tr>
                            <tr valign="top">
                                <td>Post 12</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>
                                    <italic>6.74%</italic>
                                </td>
                            </tr>
                            <tr valign="top">
                                <td>Post 13</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>
                                    <italic>7.63%</italic>
                                </td>
                            </tr>
                            <tr valign="top">
                                <td>Post 14</td>
                                <td>No</td>
                                <td>4.73%</td>
                            </tr>
                            <tr valign="top">
                                <td>Post 15</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>
                                    <italic>7.09%</italic>
                                </td>
                            </tr>
                            <tr valign="top">
                                <td>Post 16</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>
                                    <italic>8.15%</italic>
                                </td>
                            </tr>
                            <tr valign="top">
                                <td>Post 17</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>3.81%</td>
                            </tr>
                            <tr valign="top">
                                <td>Post 18</td>
                                <td>No</td>
                                <td>3.44%</td>
                            </tr>
                            <tr valign="top">
                                <td>Post 19</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>
                                    <italic>7.77%</italic>
                                </td>
                            </tr>
                            <tr valign="top">
                                <td>Post 20</td>
                                <td>
                                    <italic>Yes</italic>
                                </td>
                                <td>
                                    <italic>6.83%</italic>
                                </td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>Compared to the expert opinion (&#8220;reference standard&#8221;) our system returned 9 true positives, 1 false positive, 7 true negatives, and 3 false negatives. Precision is defined as (TP/(TP+FP)) and is the fraction of documents retrieved that are actually relevant to the search criteria. Recall is defined as (TP/(TP+FN)) and is a measure of sensitivity, ie, the fraction of all possible relevant documents in the test set that are retrieved. F-score is a harmonized mean of precision and recall, and provides an overall measure of the effectiveness of an information retrieval system. Our GATE pipeline performed with a precision of 0.9, recall of 0.75, and F-score of 0.82.</p>
            </sec>
            <sec>
                <title>Examples</title>
                <p>In the highlighted passage in <xref ref-type="fig" rid="figure2">Figure 2</xref> many words related to combat exposure (purple) are found within 1 or 2 sentences of words related to emotions and senses (red, pink).</p>
                <fig id="figure2" position="float">
                    <label>Figure 2</label>
                    <caption>
                        <p>A section of an annotated blog describing the trauma of war</p>
                    </caption>
                    <!--Original graphic name: http://writer.zoho.com:80/image.do?imgurl=6d37aff7952c652b15981bdb67ae7d24753f78e991a900217e61b98366e8ce2e0dba4ff32c3c75ab0436b5eaed60adc0-->
                    <graphic xlink:href="jmir_v12i4e45_fig2.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple" />
                </fig>
                <p>This paragraph presents an example of a specific traumatic factor: an attack against a soldier that injured innocent civilians instead.</p>
                <p>Another example of the proximity of the words related to the 2 dimensions of combat exposure can be seen in the annotated paragraph in <xref ref-type="fig" rid="figure3">Figure 3</xref>. The purple labels mark the combat events and locations, while the red and brown mark the words from the emotions category.</p>
                <fig id="figure3" position="float">
                    <label>Figure 3</label>
                    <caption>
                        <p>A section of an annotated Web blog showing physical and emotional descriptors</p>
                    </caption>
                    <!--Original graphic name: http://writer.zoho.com:80/image.do?imgurl=6d37aff7952c652b15981bdb67ae7d24753f78e991a900217e61b98366e8ce2ebc2295a1784e1ed6a534c09baa1ad0bd-->
                    <graphic xlink:href="jmir_v12i4e45_fig3.jpg" alt-version="no" mimetype="image" position="float" xlink:type="simple" />
                </fig>
                <p>This passage follows the description of learning that some of the fellow soldiers were killed during convoy and clearly shows the deep emotional response to this event.</p>
            </sec>
        </sec>
        <sec sec-type="discussion">
            <title>Discussion</title>
            <sec>
                <title>Findings</title>
                <p>We identified 2 dimensions of combat exposure descriptions: physical and emotional. These have been incorporated into the ontology and given specific annotations in GATE. The results of the pilot evaluation show that even without taking context into account our pipeline was able to retrieve the relevant blog posts with relatively good precision and recall.</p>
                <p>We found that many of the words related to concrete experience and emotional reaction occurred within one or two sentences of each other frequently pointed to the paragraphs in the text that described the most dramatic combat situations. This may be instrumental in text analysis and uncovering the burden of combat exposure. This finding will be important for future research that will include context-aware analysis.</p>
            </sec>
            <sec>
                <title>Challenges</title>
                <p>Blog texts are a heterogeneous and, at times, poorly structured text material. This distinguishes them from more structured texts like radiology reports and makes text processing more challenging. Apart from typos and spelling errors, there are field-specific abbreviations, slang terms, and intentional spelling variants. For example, one of the commonly seen words was an exclamation &#8220;Boom!&#8221; that described an experience of sudden loud sound, such as explosion; this word came in many different shapes, such as &#8220;BOOM,&#8221; &#8220;Boooom,&#8221; and &#8220;Bo-o-om.&#8221; One of the commonly encountered words was an abbreviation IED, which stands for improvised explosive device; this word was also often misspelled (&#8220;IOD,&#8221; &#8220;IUD&#8221; etc). The analysis of context (such as negation and word proximity) in blogs will also be more difficult because of poor structure and the informal nature of the blog text.</p>
            </sec>
            <sec>
                <title>Limitations</title>
                <p>Although we found the bag-of-words weighting approach to be useful in discovering the vocabulary used by blog writers to describe combat situations and experiences, the adequacy of this approach for blogs remains a point of discussion. The bag-of-words approach is restrictive as it does not allow analyzing words in context. Thus, semantic ambiguity is difficulty to address with this approach. Other researchers have found similar limitations to this type of approach due to issues such as scarcity of data [<xref ref-type="bibr" rid="ref17">17</xref>]. However, a potentially more informative context-aware mechanism (&#8220;rich bag-of-words&#8221;) is not possible to construct without a domain-specific vocabulary that we will be able to create using the results of the basic bag-of-words algorithm. This work is the first step toward creating a vocabulary for future context-aware tools.</p>
                <p>There are other important limitations to this work. First, the generalizability of the sample may be questioned because of an important selection bias: by analyzing the blogs one can only know the experiences and opinions of people who have blogs. This is especially concerning in military blog analysis, because not every soldier at all times has access to the Internet even if they desire to have a blog and are allowed to do so by their commanding officers. Nevertheless, blogs can be used as a general measure of combat stress and may also be used to help identifyand quantify novel stressors specific to modern wars (for example, IEDs and suicide bombs). Another issue is that blogs represent a form of retrospective self-report and are by nature less reliable than the more objective methods of external surveillance such as videotaping or clinical interview. The external methods, however, are rarely available at the battlefield or are too expensive to be considered. Moreover, the consequences of combat stress may differ in their severity depending upon the attitudes and predeployment neurocognitive functioning of the person who experienced it [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
                <p>By analysis of the blogs it was not possible to reliably identify the authors of the blogs who were active duty soldiers. In fact, the nature of the &#8220;blogsphere&#8221; is such that one cannot be sure whether the author of the blog really exists or is a fictional character. In addition, accurate assessment of temporality is a challenge in blogs. It is not always clear when the soldier has described a particular experience, whether it was right after the events or after some time upon recollection. However, given that a blog post describes actual combat events from the first person, it is still possible to use this blog post in the analysis, because the language used is similar. An additional issue found was that a portion of the blogs retrieved by Internet search seemingly conforming to the search criteria and using military language proved to be descriptions of the video game experience. It is thus essential to design an NLP system that accurately identifies these posts as being negative for combat exposure.</p>
                <p>Another limitation is that the type of content and the personal details that are discussed in the blog may differ substantially from those mentioned during a person-to-person clinical interview.</p>
            </sec>
            <sec>
                <title>Possible Alternatives</title>
                <p>Our approach to blog analysis was based on lexicons and ontologies created manually, which is both time-consuming and domain-specific. An alternative to this could be unsupervised or semisupervised approaches that have been applied to online reviews and blogs analysis [<xref ref-type="bibr" rid="ref19">19</xref>]. Other alternatives to the GATE pipeline are possible, such as Unstructured Information Management Architecture (UIMA) [<xref ref-type="bibr" rid="ref20">20</xref>], which is also open source.</p>
                <p>There are ways to analyze natural text without creation of an ontology. However, ontologies play an important role in knowledge management and data integration [<xref ref-type="bibr" rid="ref21">21</xref>]. Having the data structured by way of ontology will help us in the future research that will involve optimization of the existing algorithm and development of context-aware analysis. Many available open-source NLP systems now include ontology-aware tools; creation and development of the ontology will make the knowledge obtained from our study transferable.</p>
            </sec>
            <sec>
                <title>Possible Applications and Future Research</title>
                <p>In the course of our study, we have encountered a multitude of blog posts of the military genre that had nothing to do with combat exposure. Selecting the relevant posts manually was a lengthy and tedious task. Our GATE pipeline, especially when evolved into a more context-aware tool, could be used for automated selection of blog posts (or diary entries, or even physician&#8217;s notes) that discuss combat exposure from all available text data. This can be instrumental in clinical work as it may help therapists and researchers to concentrate on the text material relevant to the combat exposure.</p>
                <p>Our present work is a first step toward creating a more comprehensive context-aware algorithm that can be used for large-scale blog text categorization and analysis. Without the context analysis (such as negation, word order, and proximity) and more sophisticated software framework, it will not be possible to analyze thousands of documents or correctly classify them by combat exposure descriptions.</p>
                <p>When developed to the point where the analysis of many thousands of documents is possible, an application such as ours could be used as a training tool for psychiatrists who are working with military personnel. It is also possible that an NLP application like this one may be used in clinical work to provide clinicians with text material discussing combat exposure and deployment-specific traumatic factors.</p>
                <p>Future research is needed to demonstrate possible correlations between a person's descriptions of his or her wartime experiences in their blog with the ensuing symptoms or disorders. Focus groups and medical records analysis could be used for this purpose. The information obtained from military blogs may also be used during the focus groups to facilitate discussion and elucidate difficult or unusual subjects.</p>
                <p>We conclude that available open-source natural language processing and automated information extraction tools may be instrumental in the analysis of free text contained in blogs. Analysis of military blog posts available on the Internet may help uncover the military service members&#8217; emotions and experiences of combat exposure.</p>
            </sec>
        </sec>
    </body>
    <back>
        <ack>
            <p>This project was supported in part by National Library Of Medicine (NLM) Training Grant T15 LM007056 to Sergiy Konovalov and Department of Veterans Affairs Health Services Research and Development (HSRD) grant HSR HIR 08-374 to Cynthia Brandt and Matthew Scotch. The opinions and views expressed are those of the authors and do not necessarily reflect those of the National Library Of Medicine, the National Institutes of Health, or the Department of Veterans Affairs.</p>
        </ack>
        <fn-group>
            <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>Hales</surname>
                            <given-names>RE</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Zatzick</surname>
                            <given-names>DF</given-names>
                        </name>
                    </person-group>
                    <article-title>What is PTSD?</article-title>
                    <source>Am J Psychiatry</source>
                    <year>1997</year>
                    <month>02</month>
                    <volume>154</volume>
                    <issue>2</issue>
                    <fpage>143</fpage>
                    <lpage>5</lpage>
                    <pub-id pub-id-type="medline">9016259</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>Demner-Fushman</surname>
                            <given-names>D</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Chapman</surname>
                            <given-names>WW</given-names>
                        </name>
                        <name name-style="western">
                            <surname>McDonald</surname>
                            <given-names>CJ</given-names>
                        </name>
                    </person-group>
                    <article-title>What can natural language processing do for clinical decision support?</article-title>
                    <source>J Biomed Inform</source>
                    <year>2009</year>
                    <month>10</month>
                    <day>13</day>
                    <volume>42</volume>
                    <issue>5</issue>
                    <fpage>760</fpage>
                    <lpage>72</lpage>
                    <pub-id pub-id-type="doi">10.1016/j.jbi.2009.08.007</pub-id>
                    <pub-id pub-id-type="medline">19683066</pub-id>
                    <pub-id pub-id-type="pii">S1532-0464(09)00108-7</pub-id>
                    <pub-id pub-id-type="pmcid">PMC2757540</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>Elkin</surname>
                            <given-names>PL</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Froehling</surname>
                            <given-names>D</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Wahner-Roedler</surname>
                            <given-names>D</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Trusko</surname>
                            <given-names>B</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Welsh</surname>
                            <given-names>G</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Ma</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Asatryan</surname>
                            <given-names>AX</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Tokars</surname>
                            <given-names>JI</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Rosenbloom</surname>
                            <given-names>ST</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Brown</surname>
                            <given-names>SH</given-names>
                        </name>
                    </person-group>
                    <article-title>NLP-based identification of pneumonia cases from free-text radiological reports</article-title>
                    <source>AMIA Annu Symp Proc</source>
                    <year>2008</year>
                    <volume>6</volume>
                    <fpage>172</fpage>
                    <lpage>6</lpage>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://ukpmc.ac.uk/abstract/MED/18998791" />
                    </comment>
                    <pub-id pub-id-type="medline">18998791</pub-id>
                    <pub-id pub-id-type="pmcid">PMC2656026</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>Hyun</surname>
                            <given-names>S</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Johnson</surname>
                            <given-names>SB</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Bakken</surname>
                            <given-names>S</given-names>
                        </name>
                    </person-group>
                    <article-title>Exploring the ability of natural language processing to extract data from nursing narratives</article-title>
                    <source>Comput Inform Nurs</source>
                    <year>2009</year>
                    <month>08</month>
                    <volume>27</volume>
                    <issue>4</issue>
                    <fpage>215</fpage>
                    <lpage>23; quiz 224</lpage>
                    <pub-id pub-id-type="doi">10.1097/NCN.0b013e3181a91b58</pub-id>
                    <pub-id pub-id-type="medline">19574746</pub-id>
                    <pub-id pub-id-type="pii">00024665-200907000-00005</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>Eysenbach</surname>
                            <given-names>G</given-names>
                        </name>
                    </person-group>
                    <article-title>Infodemiology and infoveillance: framework for an emerging set of public health informatics methods to analyze search, communication and publication behavior on the Internet</article-title>
                    <source>J Med Internet Res</source>
                    <year>2009</year>
                    <month>03</month>
                    <volume>11</volume>
                    <issue>1</issue>
                    <fpage>e11</fpage>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.jmir.org/2009/1/e11" />
                    </comment>
                    <pub-id pub-id-type="doi">10.2196/jmir.1157</pub-id>
                    <pub-id pub-id-type="medline">19329408</pub-id>
                    <pub-id pub-id-type="pii">v11i1e11</pub-id>
                    <pub-id pub-id-type="pmcid">PMC2762766</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref6">
                <label>6</label>
                <nlm-citation citation-type="web">
                    <source>Milblogging.com</source>
                    <access-date>2010-03-14</access-date>
                    <comment>
                      Listing by Language <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.milblogging.com/language.php">http://www.milblogging.com/language.php</ext-link>
                    </comment>
                    <pub-id pub-id-type="other">5oEgOeqrT</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>Scott</surname>
                            <given-names>S</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Matwin</surname>
                            <given-names>S</given-names>
                        </name>
                    </person-group>
                    <article-title>Text Classification Using WordNet Hypernyms</article-title>
                    <conf-name>the COLING/ACL Workshop on Usage of WordNet in Natural Language Processing Systems</conf-name>
                    <conf-date>Aug 16, 1998</conf-date>
                    <conf-loc>Montreal, QC, Canada</conf-loc>
                </nlm-citation>
            </ref>
            <ref id="ref8">
                <label>8</label>
                <nlm-citation citation-type="web">
                    <source>Python Programming Language -- Official Website</source>
                    <access-date>2010-03-20</access-date>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.python.org/.">http://www.python.org/.</ext-link>
                    </comment>
                    <pub-id pub-id-type="other">5oN2cUAHu</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref9">
                <label>9</label>
                <nlm-citation citation-type="web">
                    <source>Natural Language Toolkit</source>
                    <access-date>2010-03-20</access-date>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.nltk.org/.">http://www.nltk.org/.</ext-link>
                    </comment>
                    <pub-id pub-id-type="other">5oN2n1bR5</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref10">
                <label>10</label>
                <nlm-citation citation-type="book">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Hersh</surname>
                            <given-names>WP</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Stavri</surname>
                            <given-names>PZ</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Detmer</surname>
                            <given-names>WM</given-names>
                        </name>
                    </person-group>
                    <article-title>Information retrieval and digital libraries</article-title>
                    <source>Shortliffe EH, Cimino JJ, editors. Biomedical Informatics: Computer Applications in Health Care and Biomedicine. 3rd edition</source>
                    <year>2006</year>
                    <publisher-loc>New York, NY</publisher-loc>
                    <publisher-name>Springer</publisher-name>
                    <fpage>680</fpage>
                    <lpage>682</lpage>
                </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>Gruber</surname>
                            <given-names>T</given-names>
                        </name>
                    </person-group>
                    <article-title>Toward Principles for the Design of Ontologies Used for Knowledge Sharing</article-title>
                    <source>Int J Hum Comput Stud</source>
                    <year>1995</year>
                    <volume>43</volume>
                    <issue>5-6</issue>
                    <fpage>907</fpage>
                    <lpage>928</lpage>
                </nlm-citation>
            </ref>
            <ref id="ref12">
                <label>12</label>
                <nlm-citation citation-type="web">
                    <source>The Prot&#233;g&#233; Ontology Editor and Knowledge Acquisition System</source>
                    <access-date>2010-03-20</access-date>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://protege.stanford.edu/.">http://protege.stanford.edu/.</ext-link>
                    </comment>
                    <pub-id pub-id-type="other">5oN3I5SVv</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref13">
                <label>13</label>
                <nlm-citation citation-type="confproc">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Cunningham</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Maynard</surname>
                            <given-names>D</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Bontcheva</surname>
                            <given-names>K</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Tablan</surname>
                            <given-names>V</given-names>
                        </name>
                    </person-group>
                    <article-title>GATE: A Framework and Graphical Development Environment for Robust NLP Tools and Applications</article-title>
                    <conf-name>40th Anniversary Meeting of the Association for Computational Linguistics</conf-name>
                    <conf-date>Jul 7-12, 2002</conf-date>
                    <conf-loc>Philadelphia, PA, USA</conf-loc>
                </nlm-citation>
            </ref>
            <ref id="ref14">
                <label>14</label>
                <nlm-citation citation-type="web">
                    <source>JAPE: Regular Expressions over Annotations</source>
                    <access-date>2010-03-20</access-date>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://gate.ac.uk/sale/tao/splitch8.html#x12-1880008.">http://gate.ac.uk/sale/tao/splitch8.html#x12-1880008.</ext-link>
                    </comment>
                    <pub-id pub-id-type="other">5oN7fRwOL</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref15">
                <label>15</label>
                <nlm-citation citation-type="book">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Van Rijsbergen</surname>
                            <given-names>CJ</given-names>
                        </name>
                    </person-group>
                    <source>Information Retrieval. 2nd edition</source>
                    <year>1979</year>
                    <publisher-loc>Newton, MA</publisher-loc>
                    <publisher-name>Butterworth-Heinemann</publisher-name>
                </nlm-citation>
            </ref>
            <ref id="ref16">
                <label>16</label>
                <nlm-citation citation-type="confproc">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Makhoul</surname>
                            <given-names>J</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Kubala</surname>
                            <given-names>F</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schwartz</surname>
                            <given-names>R</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Weischedel</surname>
                            <given-names>R</given-names>
                        </name>
                    </person-group>
                    <article-title>Performance measures for information extraction</article-title>
                    <conf-name>DARPA Broadcast News Workshop</conf-name>
                    <conf-date>1999</conf-date>
                    <conf-loc>Herndon, VA</conf-loc>
                </nlm-citation>
            </ref>
            <ref id="ref17">
                <label>17</label>
                <nlm-citation citation-type="confproc">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Ulicny</surname>
                            <given-names>B</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Baclawski</surname>
                            <given-names>K</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Magnus</surname>
                            <given-names>A</given-names>
                        </name>
                    </person-group>
                    <article-title>New Metrics for Blog Mining</article-title>
                    <source>Dasarathy BV, editor. Data Mining, Intrusion Detection, Information Assurance, and Data Networks Security 2007</source>
                    <year>2007</year>
                    <conf-name>SPIE Volume 6570, 65700I</conf-name>
                    <conf-date>Apr 9, 2007</conf-date>
                    <conf-loc>Orlando, FL, USA</conf-loc>
                </nlm-citation>
            </ref>
            <ref id="ref18">
                <label>18</label>
                <nlm-citation citation-type="journal">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Marx</surname>
                            <given-names>BP</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Doron-Lamarca</surname>
                            <given-names>S</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Proctor</surname>
                            <given-names>SP</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Vasterling</surname>
                            <given-names>JJ</given-names>
                        </name>
                    </person-group>
                    <article-title>The influence of pre-deployment neurocognitive functioning on post-deployment PTSD symptom outcomes among Iraq-deployed Army soldiers</article-title>
                    <source>J Int Neuropsychol Soc</source>
                    <year>2009</year>
                    <month>11</month>
                    <volume>15</volume>
                    <issue>6</issue>
                    <fpage>840</fpage>
                    <lpage>52</lpage>
                    <pub-id pub-id-type="doi">10.1017/S1355617709990488</pub-id>
                    <pub-id pub-id-type="medline">19891817</pub-id>
                    <pub-id pub-id-type="pii">S1355617709990488</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref19">
                <label>19</label>
                <nlm-citation citation-type="confproc">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Melville</surname>
                            <given-names>P</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Gryc</surname>
                            <given-names>W</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Lawrence</surname>
                            <given-names>R</given-names>
                        </name>
                    </person-group>
                    <article-title>Sentiment Analysis of Blogs by Combining Lexical Knowledge with Text Classification</article-title>
                    <conf-name>15th Conference on Knowledge Discovery and Data Mining</conf-name>
                    <conf-date>Jun 28-Jul 1, 2009</conf-date>
                    <conf-loc>Paris, France</conf-loc>
                </nlm-citation>
            </ref>
            <ref id="ref20">
                <label>20</label>
                <nlm-citation citation-type="web">
                    <source>Apache UIMA</source>
                    <access-date>2010-03-24</access-date>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://incubator.apache.org/uima/.">http://incubator.apache.org/uima/.</ext-link>
                    </comment>
                    <pub-id pub-id-type="other">5sm6TWWXX</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref21">
                <label>21</label>
                <nlm-citation citation-type="journal">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Bodenreider</surname>
                            <given-names>O</given-names>
                        </name>
                    </person-group>
                    <article-title>Biomedical ontologies in action: role in knowledge management, data integration and decision support</article-title>
                    <source>Yearb Med Inform</source>
                    <year>2008</year>
                    <fpage>67</fpage>
                    <lpage>79</lpage>
                    <comment>
                        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://ukpmc.ac.uk/abstract/MED/18660879" />
                    </comment>
                    <pub-id pub-id-type="medline">18660879</pub-id>
                    <pub-id pub-id-type="pii">me08010067</pub-id>
                    <pub-id pub-id-type="pmcid">PMC2592252</pub-id>
                </nlm-citation>
            </ref>
        </ref-list>
        <glossary>
            <title>Abbreviations</title>
            <def-list>
                <def-item>
                    <term id="abb1">GATE</term>
                    <def>
                        <p>General Architecture for Text Engineering</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb2">HSRD</term>
                    <def>
                        <p>Health Services Research and Development</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb3">IED</term>
                    <def>
                        <p>improvised explosive device</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb4">IR</term>
                    <def>
                        <p>information retrieval</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb5">IDF</term>
                    <def>
                        <p>inverse document frequency</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb6">JAPE</term>
                    <def>
                        <p>Java Annotation Patterns Engine</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb7">NLM</term>
                    <def>
                        <p>National Library Of Medicine</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb8">NLP</term>
                    <def>
                        <p>natural language processing</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb9">OEF/OIF</term>
                    <def>
                        <p>Operation Enduring Freedom/Operation Iraqi Freedom</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb10">TF</term>
                    <def>
                        <p>term frequency</p>
                    </def>
                </def-item>
                <def-item>
                    <term id="abb11">UIMA</term>
                    <def>
                        <p>Unstructured Information Management Architecture</p>
                    </def>
                </def-item>
            </def-list>
        </glossary>
    </back>
</article>
