of ergonomics, aesthetics, basic performance,
overall usability and safety, to reach the device
concept in the first stages of the development
process. They can also support in the creation of a
first minimally viable product for interacting with
healthcare professionals, patients, layperson.
Prototypes according to different design iterations,
consequence of the different decisions taken to
mitigate risks and to improve usability, can,
consequently, support the whole methodology and
approach we propose here.
This evaluation has shown that a risk-based
approach is easily adapted to a resource wise
approach. During early formative, low resource
review techniques such as expert reviews, standard
analysis, cognitive walkthrough are easily performed
on documentation and by design experts. They do
not require the participation of a large number of
real users nor the availability of a finalised
prototype, while low-cost replication tools may
provide effective samples to boost discussion.
Later stages of formative assessments may
benefit of more structured techniques, such as a
detailed task analysis that is linked to the FMEA
technique. User tests with 5-10 users may be
planned at later formative steps in order to allow
refinement.
3.3.2 Which Technique for Which Device?
Medical devices belong to varied categories in terms
of technology, intended use, intended users
(layperson or professional), invasiveness in the
human body or expected useful life, which affect
design decisions in connection with usability and
safety. For this reason, we have also assessed each
technique presented by the norm IEC 62366 (IEC,
2016) in terms of adequateness to different kinds of
devices. A detailed evaluation is shown in Table 2 .
In Table 2, the same technique is considered as
adequate or inadequate for devices that may be
apparently very similar from the usability point of
view. However, this is explained by the
technological differences in the device. As an
example, the technique “standard review” proves
“adequate” for very different devices such as heart
valves and nasogastric tubes, but is considered
“adequate with reserve” for Software as a Medical
Device (SaMD). This is due to the poor
standardisation that is still present in the SaMD
sector, while traditional devices can be assessed by
very consistent and complete international standards
and guidelines. Also consider, the technique
“participatory design” that is considered “not
appropriate” for traditional electromedical devices
for the layperson, such as pulse oximeters, but on the
other hand is “adequate” for SaMD and apps for the
layperson. This again is justified as participatory
design may allow the designers to align the medical
app to users’ expectations, by allowing users to
design an intuitive and user friendly app, with a user
interface as similar as possible to a consumer app.
3.4 Linking Usability to Risk
Identification
Each usability evaluation technique allows the
designers to identify risks and potentially hazardous
situations. We describe here some of the techniques
identified above, in terms of capability of the
assessment to be easily linked to a formal risk
analysis as per ISO 14971 (ISO, 2007).
The preferred methods for early feasibility help
the designers to identify risks in general terms and
are potentially adequate to determine risk severity
(worst case consequences of the risk scenario). For
example, at very early stages of ideation of a
electromedical device to be used in emergencies
(e.g. a defibrillator) designers may already be aware
of the importance of high visibility and audibility of
the device, since it is expected to be used in loud,
dark, confusing environments. During late
feasibility, we propose a more structured method, by
application of the Failure Modes and Effects
Analysis FMEA technique. The Application FMEA
technique yields the best results if the question
“what happens if…” is posed at each application
step or phase. So, we propose an integrated
technique: firstly describe the use of the device in
very fine detail by task analysis and then perform
Application FMEA on each step.
We propose a very detailed task analysis and,
where applicable, also a function analysis or use
flowchart. Description of the intended use interface
by a flowchart is particularly adequate for medical
device software, both stand alone and integrated in
an electromedical device. Use of this integrated
method allows a very precise assessment of risk
severity, thanks also to the possibility of obtaining a
description of the chain of events that arise from an
hazardous situation, for example thanks to
brainstorming or focused expert reviews.
If the designers do not have enough past data or
experience-based estimations to determine risk-
related probability, a user test can be very useful to
estimate probability of each hazard. If the user test
are planned in this phase, the task list and use
flowchart already available to designers from the
BIODEVICES 2019 - 12th International Conference on Biomedical Electronics and Devices
210