<!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>Requirement analysis for social acceptance of AI medical interview - from view of quality in use</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Shin'ichi Fukuzumi</string-name>
          <email>shin-ichi.fukuzumi@riken.jp</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Natsuko Noda</string-name>
          <email>nnoda@shibaura-it.ac.jp</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>RIKEN</institution>
          ,
          <addr-line>Tokyo</addr-line>
          ,
          <country country="JP">Japan</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Shibaura Institute of Technology</institution>
          ,
          <addr-line>Tokyo</addr-line>
          ,
          <country country="JP">Japan</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2021</year>
      </pub-date>
      <abstract>
        <p>- The purpose of this study is to clarify the requirements that must be met for AI-based medical interview to be accepted by humans and society. In this study, we set up personas of users who have various ideas, and create usage cases of AI medical interview service based on the personas. From the created usage cases, we extract and analyze the feelings and thoughts of the personas in response to each question and usage flow of the AI medical interview service. From this analysis, we clarify requirements on AI medical interview services referring to the concept of quality in use in ISO/IEC 25010:2011. Using this standard, we were able to extract the requirements of "usability," "reliability," and "acceptability" that have been not enough considered in the past. In this paper, we introduce the requirements acquired from the analysis.</p>
      </abstract>
      <kwd-group>
        <kwd>quality in use</kwd>
        <kwd>AI systems</kwd>
        <kwd>persona</kwd>
        <kwd>requirement analysis</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Please provide your occupation and address.</title>
    </sec>
    <sec id="sec-2">
      <title>Please provide your occupation and address.</title>
    </sec>
    <sec id="sec-3">
      <title>I'm not comfortable typing the answers to such private questions.</title>
    </sec>
    <sec id="sec-4">
      <title>I can answer this kind of (many)</title>
      <p>private question without
any hesitation with an AI.</p>
      <p>Are you mentally It's uncomfortable to be
depressed? asked such question when</p>
      <p>I'm depressed because of
my injury at a critical
time.</p>
      <p>Are you mentally If I talk to the AI about
depressed? mental issues, can the AI
understand it?</p>
      <p>I. INTRODUCTION</p>
      <p>Currently, AI technology is expected to be used in the
medical field in a wide variety of ways, such as medical image
diagnosis by AI-based image processing and medical record
analysis by natural language processing. As one of the medical
applications of AI, AI-based medical interview services are
being implemented to reduce opportunities for
human-tohuman contact in order to prevent infection and to improve
operational efficiency in hospitals.</p>
      <p>However, it is difficult to draw a line between the
responsibilities of the doctors and the AI-based services. In the
case of the first visit to the hospital, the relationship between
the user and the AI-system is simple because there is no
judgment by the doctor. In the case of the second visit, the
diagnosis and treatment by the doctors that the user has visited
before will occur, and that makes the relationship between the
user and the AI complex and blurs the lines of responsibility
between AI and doctors. Therefore, it is necessary to make
requirements for the acceptance of such AI diagnosis services
in society.</p>
      <p>
        To make such requirements, it is necessary to consider not
only the analysis from the physician's point of view, but also
the system that has contact with the patient and others [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. And
as pointed out in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], it is necessary to analyze not only from
the viewpoint of the service developer but also from the
viewpoint of the users.
      </p>
      <p>The purpose of this study is to clarify the requirements that
must be met for AI-based medical interview to be accepted by
humans and society.</p>
      <p>We set up personas of users with a variety of possible ideas,
and create usage cases for an AI medical interview service
based on the personas. In this study, patients are limited to
first-time patients; that means these personas have the first
contact with the AI medical interview service. Then, from the
created usage cases, we extract and analyze the feelings and
thoughts of the personas in response to each question and the
flow of use of the AI medical interview service. Finally, we
extract the requirements on AI medical interview services
referring to the concept of quality in use in ISO/IEC
25010:2011.</p>
      <p>II. EXTRACTION OF FEELINGS AND THOUGHTS FOR AI</p>
      <p>
        In this section, we first assume a free AI medical interview
service [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and create user personas for it. We create not only
just one persona but several personas. Although we survey just
one specific AI medical interview service in this study, our
goal is to obtain requirements for general AI-based medical
services. Those services should be used by various users, that
cannot be represent by one persona. Thus, we create several
personas that could cover broader range of those users. We
assume that each persona has a symptom, comes to a hospital
outpatient clinic for the first time, uses the AI medical
interview service in the hospital, and receives information on
possible symptoms and recommended departments. Next, we
analyze how the user feels and thinks about the AI interview
service based on the assumed usage case. Table 1 shows some
examples of questions asked by the AI medical interview
service and the users' feelings and thoughts toward it.
      </p>
      <p>indicate
age and</p>
    </sec>
    <sec id="sec-5">
      <title>Since they use AI, can't they just use my patient registration card and skip this question?</title>
      <p>indicate If I were genderless, what (many)
age and could I answer?</p>
    </sec>
    <sec id="sec-6">
      <title>Please your gender.</title>
    </sec>
    <sec id="sec-7">
      <title>Please</title>
      <p>your
gender.
No.7
No.8</p>
      <p>In this study, we call this set of question and corresponding
feeling/thought pairs as usage data. Note that there can be
more than one feeling/thought for a single question by AI, so
the set of the pairs of question and feeling/thought in the usage
data contains more than one pair of question and
feeling/thought for the same question. Each pair of question
and feeling/thought, i.e. each usage data is numbered for
identification. Note that this number is just for identification
and the order of the numbers has no meaning.</p>
      <p>III. CLASSIFICATION OF FEELINGS, THOUGHTS AND</p>
      <p>IMPORTANCE</p>
      <p>As a preliminary step for clarifying the requirements for
AI medical interview services, we classify the extracted usage
data. To extract the requirements, we classify the usage data
with high importance in the medical diagnosis and those with
low importance.</p>
      <p>A two-axis matrix diagram is used to classify the data from
two perspectives: the perspective of "extracted feelings and
thoughts" and the perspective of "questions" from which the
feelings and thoughts are extracted.</p>
      <p>•
•</p>
      <p>Horizontal axis: Extracted feelings and thoughts.
In the horizontal axis, the criterion is whether or not
the extracted feelings and thoughts are unique to
systems and services using AI. For example, feelings
and thoughts such as "It's easy to answer private
questions with the AI." can be regarded as unique to
AI-based services. On the other hand, feelings and
thoughts such as "If I were genderless, what could I
answer?" may be general thought to all medical
interviews. This categorization is used to classify
important usage data regarding feelings and thoughts
that should be considered in the context of AI medical
interview service.</p>
      <p>Vertical axis: Questions of the extraction source.
On the vertical axis, the criterion is whether the
question from which feelings and thoughts are
extracted is easy to answer in the medical interview.
For example, questions that deal with information on
demographic attributes may be easy to answer. On the
other hand, a question such as "have you been in a
dense space or a poorly ventilated room recently?" is
slightly less easy to answer, because it deals with
information on the patient's factual behavior, which
may depend on the user's memory and feelings.</p>
      <p>Based on the above classification method, a classification
table of usage data is created, as shown in Figure 1. Each circle
shows a usage data and the number in it means the
identification number of the usage data.</p>
      <p>The classification is based on a two-axis matrix analysis
from two perspectives: the perspective of "strength of
relevance of AI in extracted feeling and thought" of the usage
data, and the perspective of "easiness of answering question."
On the horizontal axis, the degree of specificity of "feelings
and thoughts" as AI interview is classified. and on the vertical
axis, the degree of ease of answering "questions" is classified.</p>
      <p>According to this classification, the lower right the data is
in the table, the more important it is considered to be for
requirement acquisition for AI medical interview services
from the following reasons. First, the data is in the right side
is strongly related to the AI services. Because we try to extract
requirements for AI medical interview services, not for
medical interview services generally, the right side data is
more important. Secondly, to be accepted widely in society,
services should have high quality in use. However, difficult
questions to answer that the services ask contribute to making
the services harder to use. Therefore, the lower down the table
the data is, the more carefully it has to be analyzed.</p>
    </sec>
    <sec id="sec-8">
      <title>IV. REQUIREMENTS ACQUISITION</title>
      <p>
        In this study, we refer to the quality in use incorporated in
ISO/IEC 25010:2011 [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] in order to clarify the requirements
for AI medical interviews from the perspective of use by
patients, attendants, etc.
      </p>
      <p>Based on the classification table shown in Figure 1, we
find requirements for AI medical interview services. First, we
examine the "feelings and thoughts" of the usage data and
extract the issues for AI medical interviews. The issues are
compared with the elements of the quality model of quality in
use, and the quality elements related to the issues are identified.
Then, the requirements to be satisfied by AI medical
interviews are extracted for these quality elements. Figure 2
shows the extracted requirements, categorized according to
the importance of the usage data.</p>
    </sec>
    <sec id="sec-9">
      <title>Usability requirements</title>
    </sec>
    <sec id="sec-10">
      <title>Reliability</title>
      <p>requirements
Acceptability
requirements
- A number of metaphors and
onomatopoeias should be
available to convey the pain.
- Use UI and background music
that does not cause anxiety.
- Use an objective method of
answering the question.
- Similar or peripheral questions
should be grouped together.
- Consider the surrounding
environment and make the UI easy
to handle private information.
- Make the UI concise and easy to
use.
- The output results should be
comparable to the doctor's
diagnosis results.
- To cover all diseases.
- Indicate the need for questions.
- Include a phase to ask for
medical history and medication
history.
- Provide strict protection of
information.
- As an infection control measure,
use voice UI and other methods to
reduce the number of contacts.
- Tell the user that the purpose is
screening.
- It should be like spoken, not
mechanical.
- Observing the patient's state of
tension in real time (for example,
by measuring the heart rate),
change the system's behavior.
- Understand the characteristics of
the patient and the background of
the visit.
- Assume errors in patient
judgment and input of responses.
- Identify the patient's
unrecognized symptoms and cover
the symptoms.
- Make a comprehensive
assessment of Covid-19 based on
occupation, commuting method,
and whether or not he/she
participates in events.
- The presentation of questions
that assume input support by a
caregiver should also be prepared.
- To be linked with other systems
for the prevention of the spread of
Covid-19 infection (e.g. cocoa).
- Clearly inform the user of the
intended use of the input
information.</p>
      <p>From low importance usage data
- The total time from start to result
output should be shortened.
- Provide a rationale for the
results.
- The response method should be
such that it results in accurate
input of information.
- Consideration should be given to
various ideas of gender to the
extent that it is not medically
problematic.</p>
      <p>Table 2 Extracted requirements
From high importance usage data From medium importance usage
data
- Provide a good tutorial or guide.</p>
      <p>As a result, we were able to capture the impact of "use"
(quality in use) from the patient's perspective and the medical
side's perspective, and incorporate them as requirements. In
addition, since the system requirements for improving the
quality were presented in relation to "use," they were not
simply functional requirements, but system requirements from
the user's perspective. Although it is difficult to express these
things as product or system specifications, they can be
effective requirements for acceptance in society.</p>
      <p>V. CONCLUSION</p>
      <p>The demand for the use of AI in the medical field is rapidly
increasing. Against this backdrop, we examined the
requirements for AI to be accepted in society, with AI medical
interviews as the first target.</p>
      <p>Referring ISO/IEC 25010:2011, we were able to capture
the impact of "use" (quality in use) from both the patient's and
the medical side's perspectives and incorporate it into the
requirements. In the future, we will consider more diverse
usage scenarios to make the requirements more practical.</p>
      <p>Acknowledgments: This paper is based on the research
and discussions conducted by Mr. Junpei Sakura (2020
graduate of Shibaura Institute of Technology) under our
guidance.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Fukuzumi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , et al.
          <article-title>Extraction of new guideline items for ELSI-like perspectives in AI-based services</article-title>
          ,
          <source>Proc. 32nd National Conference of the Japanese Society for Artificial Intelligence</source>
          (
          <year>2018</year>
          ).
          <article-title>(in Japanese)</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Ema</surname>
            , Yusa; Nagakura, Katsue; Fujita,
            <given-names>Takusen.</given-names>
          </string-name>
          <article-title>Trust in Medical AI from Physician Survey</article-title>
          ,
          <source>Proc.34th National Conference of the Japanese Society for Artificial Intelligence</source>
          (
          <year>2020</year>
          ).
          <article-title>(in Japanese)</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Ubie</surname>
            <given-names>AI</given-names>
          </string-name>
          consultation Ubie Corporation, https://ubie.app (referred Oct.
          <volume>30</volume>
          ,
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Fukuzumi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wada</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Hirasawa</surname>
          </string-name>
          , N.:
          <article-title>"Quality in Use -Issues and proposal-"</article-title>
          ,
          <source>proceedings of IWESQ2020</source>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>