<node id="57654">
  <nid>57654</nid>
  <type>news</type>
  <uid>
    <user id="27279"><![CDATA[27279]]></user>
  </uid>
  <created>1211932800</created>
  <changed>1475895995</changed>
  <title><![CDATA[New Software Tool Keeps Kids' Vaccinations on Schedule]]></title>
  <body><![CDATA[<p>
</p><p><em>MedHeadlines </em>- May 28, 2008<br />Medical guidelines in the call for each child to receive about 27 doses of vaccine before turning two.  Booster shots are often recommended until the child turns six.  These vaccines protect the child against 15 diseases that are preventable with a proper vaccination schedule.  A lot of the time and for many reasons, however, that vaccination schedule isn't maintained adequately and vaccines get missed or delayed.  Until now, a very complicated set of calculations needed to be made before administering any missed or late vaccine doses.  Many factors, including the child's age, time since last vaccine, and which other vaccines, if any, are to be administered at the same time, must all be taken into consideration before continuing the vaccine schedule.  At the Georgia Institute of Technology, researchers have developed an online tool that helps parents and pediatricians stay on schedule.  After routine data is entered, the tool quickly structures an immunization schedule based on the child's age, previous vaccination history, and time elapsed since the last vaccine.  In the case of missed or late vaccinations, the software program can devise the optimum time to resume the vaccination schedule.<br />Read more on <a href="http://medheadlines.com/2008/05/28/new-software-tool-keeps-kids-vaccinations-on-schedule/">MedHeadlines.com</a>. </p>
<p class="MsoNormal"><a href="http://medheadlines.com/2008/05/28/new-software-tool-keeps-kids-vaccinations-on-schedule/"></a></p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2008-05-28T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[bchristopher@isye.gatech.edu]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[<strong>Barbara Christopher</strong><br />Industrial and Systems Engineering<br /><a href="http://www.gatech.edu/contact/index.html?id=bt3">Contact Barbara Christopher</a><br /><strong>404.385.3102</strong>]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>57458</item>
      </og_groups>
  <og_groups_both>
          <item>
        <![CDATA[Engineering]]>
      </item>
          <item>
        <![CDATA[Research]]>
      </item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>145</tid>
        <value><![CDATA[Engineering]]></value>
      </item>
          <item>
        <tid>135</tid>
        <value><![CDATA[Research]]></value>
      </item>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>57458</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[ISyE External News]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
