<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Technical Feasibility, Financial Viability, and Clinician Acceptance: On the Many Challenges to AI in Clinical Practice</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Nur Yildirim</string-name>
          <email>yildirim@cmu.edu</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>John Zimmerman</string-name>
          <email>johnz@cs.cmu.edu</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sarah Preum</string-name>
          <email>sarah.masud.preum@dartmouth.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Computer Science Department, Dartmouth College</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Human-Computer Interaction Institute, Carnegie Mellon University</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>Artificial intelligence (AI) applications in healthcare offer the promise of improved decision making for clinicians, and better healthcare outcomes for patients. While technical AI advances in healthcare showcase impressive performances in lab settings, they seem to fail when moving to clinical practice. In this position paper, we reflect on our experiences of designing for AI acceptance and discuss three interrelated challenges to AI in clinical practice: technical feasibility, financial viability, and clinician acceptance. We discuss each challenge and their implications for future research in clinical AI. We encourage the research community to take on these lenses in collaboratively tackling the challenges of moving AI systems into real-world healthcare applications.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Over the last decade, there has been lots of excitement about
what AI might do for healthcare. AI offers the promise of
improved cancer diagnosis, faster discovery of new drugs,
and even personalization of patients’ healthcare experiences.
The transition to electronic health records has produced a
wealth of data ripe for mining. Interestingly, AI systems that
work great in computer labs largely fail when they move
to clinical practice, and the number one reason they fail is
the lack of adoption by clinicians
        <xref ref-type="bibr" rid="ref12">(Yang, Zimmerman, and
Steinfeld 2015)</xref>
        .
      </p>
      <p>Our team has been investigating how AI might function
more effectively in the enterprise: How AI systems might
help professionals both make better decisions and also feel
like they are becoming better at their jobs. We have done
work in education, business, and healthcare. Currently, we
are working on a project to identify how AI might improve
ICU care. Can it automate mundane tasks? Can it discover
low-value care? Can it detect deviations between standards
of care and actual practice?</p>
      <p>For this position paper, we reflect on what we have
learned about AI acceptance in the workplace across many
domains, and we tailor our insights to aspects most relevant
to clinical practice. In our experience, AI only flourishes
when it is technically feasible, financially viable, and
acceptable or even desired by end-users. Research on clinical</p>
      <p>AI has largely focused on some aspects of technical
feasibility. Researchers have made many, stunning technical
advances that confirm this is a great space for innovation. Little
to no work has investigated how AI systems might pay for
themselves within the complex landscape of healthcare
reimbursement, and little work has explored when, where, and
in what form AI inferences might be viewed as valuable by
clinicians. Below we touch on each of these three areas that
we feel must be addressed for AI to thrive in the clinic.</p>
    </sec>
    <sec id="sec-2">
      <title>Technical Feasibility</title>
      <p>
        While there have been great technical advances around AI
in healthcare, much of the work is not clinically relevant
        <xref ref-type="bibr" rid="ref8">(Seneviratne, Shah, and Chu 2020)</xref>
        ; research has largely
reproduced human decision making, and researchers have
tended to focus on more difficult problems than searching
for low-hanging fruit. When we use the term “clinically
relevant” and apply it to AI innovation, we are talking about
research that offers empirical evidence that clinicians want
the AI output researchers are developing. Drawing from our
work on the ICU, researchers have created systems that
predict medication
        <xref ref-type="bibr" rid="ref10">(Suresh et al. 2017)</xref>
        , predict a patient will
need a ventilator
        <xref ref-type="bibr" rid="ref10">(Suresh et al. 2017)</xref>
        , predict if a patient will
die
        <xref ref-type="bibr" rid="ref9">(Song et al. 2018)</xref>
        or be discharged
        <xref ref-type="bibr" rid="ref14">(Zhang et al. 2020)</xref>
        ,
and predict the onset of conditions like sepsis
        <xref ref-type="bibr" rid="ref5">(Nemati et al.
2018)</xref>
        , tachycardia
        <xref ref-type="bibr" rid="ref4">(Liu et al. 2021)</xref>
        , or hypotension
        <xref ref-type="bibr" rid="ref13">(Yoon
et al. 2020)</xref>
        . Researchers detail the importance of this
information to a patient’s health, but they do not provide evidence
that clinicians currently find the use of their own expertise
to make these predictions challenging, that clinicians make
a high rate of errors, or that clinicians have expressed an
explicit desire to know this prediction.
      </p>
      <p>Technology follows a familiar adoption process. First,
there is a need for technical capabilities. Once capabilities
exist, there is a need to map these capabilities to situations
that might benefit from this capability. Finally, there is a
need for evidence that applying the new capability
actually created a desirable benefit. Almost all AI innovation in
healthcare is working on new capabilities. That is an
important first step. But now, we need more work showing the
capabilities actually map to authentic needs. When we have
a body of work showing AI can address real needs, the next
step will be deployment studies showing the new technology
has real-world impact, that it improves health outcomes and
lowers the cost of delivering care.</p>
      <p>
        One driver of the disconnect between AI capability and
clinical need is the fact that most AI innovations in health
focus on reproducing the work of human decision-makers.
These are often approaching problems from a machine
learning perspective because the diagnosis (human
decision) and selected treatment (human decision) are well
documented. The labeled data exists for training a system. Most
healthcare decisions like these are “textbook”, they are
obvious to a clinical expert. And an AI system trained on this
data will work the best for textbook cases. This is not where
clinicians need help, unless the intent is to automate
clinicians out of existence. Clinicians need the most help with the
unusual cases, cases with high clinician uncertainty
        <xref ref-type="bibr" rid="ref12">(Yang
et al. 2016)</xref>
        . Clinicians also need help with the social aspects
of their work, with getting a team to work better together in
order to benefit from the collective intelligence.
      </p>
      <p>In the ICU, patients on a ventilator receive input from the
Interventionist, the ICU nurse, and the Respiratory
Therapists (RT). The RTs will perform breathing tests on
ventilated patients in the early morning. When the Interventionist
arrives, they use the results of this test to decide if a
patient should be extubated. But RTs and Interventionists do
not always agree on who should get a breathing test,
leading to situations where the doctor wants the results but the
test has not been conducted. An AI system that tries to
predict expert disagreement could raise this issue ahead of time,
allowing the experts to make a decision before the window
for decision making has closed. Situations like expert
disagreement are only indirectly captured in EHRs, but they
show real moments where clinicians would benefit from a
machine prediction.</p>
      <p>In our experience, AI researchers working in healthcare
are most interested in working on difficult challenges. This
helps researchers publish, as they can offer clear evidence
that they have advanced the state of the art for AI and
machine learning. However, by doing this, they most often
overlook the low-hanging fruit, situations where a little bit
of well-known AI might actually help accelerate or enhance
clinical practice. In our ICU work, we noticed that clinicians
must frequently input orders for new medication. This is not
a difficult task, but it is a tedious task. As they type, they
see a list of possible medications and doses they might be
looking for, shown as an alphabetical list. Sometimes this
helps. In examining this mundane, tedious task, we noticed
that a list of medications ordered by frequency as opposed
to alphabetically significantly reduced the task completion
time by more than 50%. This is not a “sexy” innovation nor
even a use of AI. But it does help to illustrate how the
mundane labor of interaction with IT systems is largely ignored
by data scientists and AI researchers.</p>
    </sec>
    <sec id="sec-3">
      <title>Financial Viability</title>
      <p>In our work on AI innovation in the enterprise, we have
observed that the biggest barrier for getting a new AI capability
off of the whiteboard and onto a product roadmap is a strong
business case. Software product managers want to know that
the value of the innovation will be much higher than the
development costs and the operational costs for the innovation.
This can be challenging due to the near-monopoly held by
the tiny number of EHR vendors and from the software
development culture that has shifted to lean-agile, with a focus
on making an MVP – the minimum viable product.
Technical AI healthcare research never addresses how the advance
will make money, how it will pay for itself. The work does
not detail the changes needed to current data pipelines. It
does not talk about the increased amount of computing
required. It does not specify how this will save time, allowing
clinicians to treat more people in the same amount of time,
and it does not detail how clinicians might be able to charge
more, because the quality of the decision-making should get
better. The flow of money in healthcare is complicated, from
patient to insurance company to the many intersecting
clinicians delivering care. Unlike with consumer goods, a better
product (healthcare decision) does not directly relate to
increased demand or higher price. While this challenge may
seem out of scope for technical AI innovation, it still
constitutes a significant barrier to AI adoption compared to other
industries.</p>
      <p>
        EHR are an expensive problem. Many hospitals will have
10 or more different systems that all seem designed to be
inoperable with one another
        <xref ref-type="bibr" rid="ref2 ref7">(Reisman 2017; Glaser 2020)</xref>
        .
Clinicians and healthcare providers are not software
companies, yet they must constantly make large IT investments
to make systems run and to get them to trade data with one
another
        <xref ref-type="bibr" rid="ref3">(He et al. 2019)</xref>
        . Adding on an AI system in this
environment is expensive in ways that are not the case in other
industries. The development cost never really ends, as each
time an EHR vendor offers a major upgrade, almost all of
the additional code and enhancements a healthcare provider
previously developed must be rewritten.
      </p>
      <p>An additional financial barrier comes from the current
culture of software development. With the rapid growth of
agile development, software development has become much
more risk averse, with development teams searching for
clear evidence of value. Increasingly, teams are working
toward defining and rapidly deploying an MVP that can
produce clear evidence of its beneficial impact in weeks. This
is fine for retail companies that might want to try out new
personalization approaches, where they can deploy and run
A/B studies within a few weeks to collect evidence of the
positive impact for their innovation. This seems to be out
of reach for almost any AI healthcare system that focuses
on high-risk clinician decision-making. Healthcare is
unprepared for A/B testing, and we are not suggesting this would
be a good thing. Our point is that new employees coming
into software development bring a mindset that is in conflict
with the pace AI in healthcare will need.</p>
    </sec>
    <sec id="sec-4">
      <title>Clinician Acceptance and Desire</title>
      <p>
        Unfortunately, very little research documents the details
of clinician decision-making and identifies the time and
place an AI inference might be experienced as most
valuable or explores which forms of AI output are most useful
        <xref ref-type="bibr" rid="ref1 ref12">(Cai et al. 2019; Yang et al. 2016)</xref>
        . It does seem like
increased funding for the human-AI interaction aspects of AI
in healthcare is one way this might be addressed. The lack
of human-centered approach in healthcare AI innovation is
evident. The current standard, the assumptions made by AI
researchers working on healthcare systems often indicates a
lack of understanding of clinical practice workflows
        <xref ref-type="bibr" rid="ref11">(Topol
2019)</xref>
        . Many if not most research systems are built with the
assumption that clinicians recognize that they need help with
a decision, and that in their “free time” the clinicians will
walk up and use a separate IT system to get advice on what
they should do
        <xref ref-type="bibr" rid="ref12">(Yang et al. 2016)</xref>
        . The reality is that
clinicians have no free time and they are unsure when a smart
system might help. Their main experience with clinical
decision support systems mostly involves continuous, irrelevant
alerts that distract them from their work, and that provide a
negative orientation to spending time on the computer
        <xref ref-type="bibr" rid="ref6">(Rajkomar, Dean, and Kohane 2019)</xref>
        .
      </p>
      <p>The lack of a human-centered approach to AI innovation
means that many innovation avenues are under-investigated.
For example, little work has been done to apply techniques
such as business process mining to healthcare. This would
help reveal what the actual standard of care is, and
clinicians could use this type of insight on their own behaviors
to better understand and identify areas for improvement. As
we mentioned previously, predicting events like expert
disagreement empowers human decision-makers to reflect and
consider before they have committed to a path of action.
Healthcare practice has many goals; for example, rounding
often mixes goals of patient care and health worker training.
More human-learning focused AI systems might capture the
dialog and provide feedback to an attending physician on the
quality of their rounding – feedback such as waiting longer
after asking a question and monitoring for implicit bias in
who they ask questions of and who they compliment.
Systems could also help with orchestration, the work of
effectively coordinating work across the many experts. For
example, in the ICU, a system might recommend an order for
visiting patients during rounding based on the estimated time
needed, the importance of early decision making for a
patient (will they likely be extubated), and the physical layout
of the rooms. There are many types of insights around
human performance and processes that have been largely
ignored by current technically focused research.</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>In this position paper, we elaborated on the interrelated
challenges of feasibility, viability, and acceptance for moving
clinical AI into the real world. These challenges will
require thinking about not only the AI capabilities that are ripe
for application, but also the business of healthcare, and the
needs and desires of the frontline healthcare workers. We
envision a future where researchers from AI, HCI, healthcare,
design, and business research communities work together to
take on these challenges. HCI and design researchers can
focus on how technical advances in clinical AI might match
to current needs and workflows of clinicians. AI and
business researchers can work on low hanging fruit – worker
needs and desires design research reveals that are likely
to be solved with well known AI capabilities and existing
healthcare data and infrastructure. We invite clinical AI
researchers to advance collaborative research practices,
effectively bridging the gap between research communities.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgements</title>
      <p>This material is based upon work supported by the
National Science Foundation under Grant No. (2007501)
and work supported by the National Institutes of Health
(R35HL144804). Any opinions, findings, and conclusions
or recommendations expressed in this material are those of
the authors and do not necessarily reflect the views of the
National Science Foundation or the National Institutes of
Health.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Cai</surname>
            ,
            <given-names>C. J.</given-names>
          </string-name>
          ; Winter,
          <string-name>
            <given-names>S.</given-names>
            ;
            <surname>Steiner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ;
            <surname>Wilcox</surname>
          </string-name>
          ,
          <string-name>
            <surname>L.</surname>
          </string-name>
          ; and Terry,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <year>2019</year>
          .
          <article-title>” Hello AI”: Uncovering the Onboarding Needs of Medical Practitioners for Human-AI Collaborative Decision-Making</article-title>
          .
          <source>Proceedings of the ACM on Humancomputer Interaction</source>
          <volume>3</volume>
          (CSCW):
          <fpage>1</fpage>
          -
          <lpage>24</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Glaser</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <year>2020</year>
          .
          <article-title>Its time for a new kind of electronic health record</article-title>
          .
          <source>Harvard Business Review. June</source>
          <volume>12</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>He</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ; Baxter,
          <string-name>
            <given-names>S. L.</given-names>
            ;
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ;
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ;
            <surname>Zhou</surname>
          </string-name>
          ,
          <string-name>
            <surname>X.</surname>
          </string-name>
          ; and Zhang,
          <string-name>
            <surname>K.</surname>
          </string-name>
          <year>2019</year>
          .
          <article-title>The practical implementation of artificial intelligence technologies in medicine</article-title>
          .
          <source>Nature medicine 25</source>
          <volume>(1)</volume>
          :
          <fpage>30</fpage>
          -
          <lpage>36</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ; Liu,
          <string-name>
            <given-names>T.</given-names>
            ;
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            ;
            <surname>Kuo</surname>
          </string-name>
          , P.-C.;
          <string-name>
            <surname>Xu</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Yang</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Lan</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Ouyang</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Ng</surname>
            ,
            <given-names>Y. L.</given-names>
          </string-name>
          ; et al.
          <year>2021</year>
          .
          <article-title>TOPNet Prediction Model Using Bidirectional Long Short-term Memory and Medical-Grade Wearable Multisensor System for Tachycardia Onset: Algorithm Development Study</article-title>
          .
          <source>JMIR Medical Informatics</source>
          <volume>9</volume>
          (
          <issue>4</issue>
          ):
          <fpage>e18803</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Nemati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Holder</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Razmi</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Stanley</surname>
            ,
            <given-names>M. D.</given-names>
          </string-name>
          ; Clifford, G. D.; and Buchman,
          <string-name>
            <surname>T. G.</surname>
          </string-name>
          <year>2018</year>
          .
          <article-title>An interpretable machine learning model for accurate prediction of sepsis in the ICU</article-title>
          .
          <source>Critical care medicine 46</source>
          <volume>(4)</volume>
          :
          <fpage>547</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>Rajkomar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Dean</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ; and
          <string-name>
            <surname>Kohane</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          <year>2019</year>
          .
          <article-title>Machine learning in medicine</article-title>
          .
          <source>New England Journal of Medicine</source>
          <volume>380</volume>
          (
          <issue>14</issue>
          ):
          <fpage>1347</fpage>
          -
          <lpage>1358</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <string-name>
            <surname>Reisman</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <year>2017</year>
          .
          <article-title>EHRs: the challenge of making electronic data usable and interoperable</article-title>
          .
          <source>Pharmacy and Therapeutics</source>
          <volume>42</volume>
          (
          <issue>9</issue>
          ):
          <fpage>572</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <string-name>
            <surname>Seneviratne</surname>
            ,
            <given-names>M. G.</given-names>
          </string-name>
          ; Shah,
          <string-name>
            <given-names>N. H.</given-names>
            ; and
            <surname>Chu</surname>
          </string-name>
          ,
          <string-name>
            <surname>L.</surname>
          </string-name>
          <year>2020</year>
          .
          <article-title>Bridging the implementation gap of machine learning in healthcare</article-title>
          .
          <source>BMJ Innovations</source>
          <volume>6</volume>
          (
          <issue>2</issue>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <string-name>
            <surname>Song</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Rajan</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Thiagarajan</surname>
            ,
            <given-names>J. J.;</given-names>
          </string-name>
          and
          <string-name>
            <surname>Spanias</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          <string-name>
            <surname>Suresh</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ; Hunt,
          <string-name>
            <given-names>N.</given-names>
            ;
            <surname>Johnson</surname>
          </string-name>
          , A.;
          <string-name>
            <surname>Celi</surname>
            ,
            <given-names>L. A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Szolovits</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ; and Ghassemi,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <year>2017</year>
          .
          <article-title>Clinical intervention prediction and understanding using deep networks</article-title>
          .
          <source>arXiv preprint arXiv:1705</source>
          .
          <fpage>08498</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <string-name>
            <surname>Topol</surname>
            ,
            <given-names>E. J.</given-names>
          </string-name>
          <year>2019</year>
          .
          <article-title>High-performance medicine: the convergence of human and artificial intelligence</article-title>
          .
          <source>Nature</source>
          medicine
          <volume>25</volume>
          (
          <issue>1</issue>
          ):
          <fpage>44</fpage>
          -
          <lpage>56</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <string-name>
            <surname>Yang</surname>
            ,
            <given-names>Q.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Zimmerman</surname>
          </string-name>
          , J.; and
          <string-name>
            <surname>Steinfeld</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <year>2015</year>
          .
          <article-title>Review of Medical Decision Support Tools: Emerging Opportunity for Interaction Design</article-title>
          .
          <article-title>IASDR 2015 Interplay Proceedings</article-title>
          . Yang,
          <string-name>
            <given-names>Q.</given-names>
            ;
            <surname>Zimmerman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ;
            <surname>Steinfeld</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ;
            <surname>Carey</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ; and
            <surname>Antaki</surname>
          </string-name>
          ,
          <string-name>
            <surname>J. F.</surname>
          </string-name>
          <year>2016</year>
          .
          <article-title>Investigating the heart pump implant decision process: opportunities for decision support tools to help</article-title>
          .
          <source>In Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems</source>
          ,
          <volume>4477</volume>
          -
          <fpage>4488</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <string-name>
            <surname>Yoon</surname>
            ,
            <given-names>J. H.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Jeanselme</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Dubrawski</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Hravnak</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Pinsky</surname>
            ,
            <given-names>M. R.</given-names>
          </string-name>
          ; and Clermont,
          <string-name>
            <surname>G.</surname>
          </string-name>
          <year>2020</year>
          .
          <article-title>Prediction of hypotension events with physiologic vital sign signatures in the intensive care unit</article-title>
          .
          <source>Critical Care</source>
          <volume>24</volume>
          (
          <issue>1</issue>
          ):
          <fpage>1</fpage>
          -
          <lpage>9</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Thadajarassiri</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ; Sen,
          <string-name>
            <given-names>C.</given-names>
            ; and
            <surname>Rundensteiner</surname>
          </string-name>
          ,
          <string-name>
            <surname>E.</surname>
          </string-name>
          <year>2020</year>
          .
          <article-title>Time-Aware Transformer-based Network for Clinical Notes Series Prediction</article-title>
          .
          <source>In Machine Learning for Healthcare Conference</source>
          ,
          <volume>566</volume>
          -
          <fpage>588</fpage>
          . PMLR.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>