<node id="603003">
  <nid>603003</nid>
  <type>event</type>
  <uid>
    <user id="27707"><![CDATA[27707]]></user>
  </uid>
  <created>1519761158</created>
  <changed>1519761158</changed>
  <title><![CDATA[PhD Defense by Anthony Bonifonte]]></title>
  <body><![CDATA[<p>Title:&nbsp;Data-Driven Healthcare Management: An Analytics Approach to Blood Pressure Control and Cardiovascular Disease Prevention</p>

<p>&nbsp;</p>

<p>Advisor: Dr.&nbsp;Turgay Ayer</p>

<p>&nbsp;</p>

<p>Committee members (ordered alphabetically):</p>

<p>Dr. Benjamin Haaland&nbsp;</p>

<p>Dr. Kamran Paynabar</p>

<p>Dr. Julie Swann</p>

<p>Dr. Emir Veledar (Emory University)</p>

<p>Dr. Yao Xie</p>

<p>&nbsp;</p>

<p>Date and Time:&nbsp;Monday March 12, 10:00am</p>

<p>&nbsp;</p>

<p>Location:&nbsp;Groseclose 403</p>

<p>&nbsp;</p>

<p>Summary:</p>

<p>This thesis develops analytics based tools using operations research and statistical methodologies to address problems in the domain of cardiovascular disease and blood pressure management.&nbsp; Cardiovascular disease is the leading cause of death in the United States and worlwide, and a major component of healthcare costs.&nbsp; Elevated blood pressure (hypertension) has been shown as a significant risk factor for cardiovascular disease.&nbsp; We develop data-driven mathematical models to optimize treatment decisions, monitor blood pressure from mobile health technologies, and maximize population health.</p>

<p>&nbsp;</p>

<p>In chapter I, we show that history of a patient&#39;s blood pressure is an important predictor of future cardiovascular risk.&nbsp; Standard risk prediction models consider only a patient&#39;s current blood pressure and ignore history.&nbsp; Using Cox model survival analysis and the Framingham Heart Study data set, we&nbsp;demonstrate improved predictive ability by incorporating antecedent blood pressure measurements.&nbsp; The results of this chapter motivate the following chapters by emphasizing the importance of a time integrated measure of blood pressure as a risk for cardiovascular disease.</p>

<p>&nbsp;</p>

<p>In chapter II, we develop a population level optimal antihypertensive treatment policy.&nbsp; We model blood pressure as a continuous time, continuous state stochastic process, specifically a geometric Brownian motion mixture model, which we demonstrate is a good statistical fit.&nbsp; Using published parameters of cardiovascular disease risk as a function of blood pressure, we create a closed form analytical expression for the expectation and variance of hazard a patient experiences over the following T years.&nbsp; Using meta-analyses of randomized control trials, we estimate the effects of different dosages of antihypertensive treatment and optimize over treatment decisions.&nbsp; We create a threshold based population level optimal treatment policy for initiation and intensification of antihypertensive treatment, and show significant improvement over current guidelines in a large scale simulation model.</p>

<p>&nbsp;</p>

<p>In chapter III, we develop two changepoint detection-based algorithms for monitoring blood pressure from wearables and other mobile health technologies, which can gather many more&nbsp; measurements than traditional clinical measurements.&nbsp; The first algorithm uses knowledge of the disease progression to maintain a Bayesian belief of the true state.&nbsp; This method is highly accurate, but may be difficult to implement in practice due to the parameter estimation and necessity of simulation to calibrate the algorithm.&nbsp; We subsequently develop a Naive changepoint detection algorithm that is simple and generalizable to other continuous health characteristics such as cholesterol, glucose level, and pulse.</p>
]]></body>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Data-Driven Healthcare Management: An Analytics Approach to Blood Pressure Control and Cardiovascular Disease Prevention  ]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_time>
    <item>
      <value><![CDATA[2018-03-12T11:00:00-04:00]]></value>
      <value2><![CDATA[2018-03-12T13:00:00-04:00]]></value2>
      <rrule><![CDATA[]]></rrule>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_time>
  <field_fee>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_fee>
  <field_extras>
      </field_extras>
  <field_audience>
          <item>
        <value><![CDATA[Faculty/Staff]]></value>
      </item>
          <item>
        <value><![CDATA[Public]]></value>
      </item>
          <item>
        <value><![CDATA[Graduate students]]></value>
      </item>
      </field_audience>
  <field_media>
      </field_media>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_phone>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_phone>
  <field_url>
    <item>
      <url><![CDATA[]]></url>
      <title><![CDATA[]]></title>
            <attributes><![CDATA[]]></attributes>
    </item>
  </field_url>
  <field_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_email>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>221981</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Graduate Studies]]></item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>1788</tid>
        <value><![CDATA[Other/Miscellaneous]]></value>
      </item>
      </field_categories>
  <field_keywords>
          <item>
        <tid>100811</tid>
        <value><![CDATA[Phd Defense]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
