IEEE Robotics & Automation Magazine - June 2019 - 77

Table 3. Tabular checklist for implementing transparency in robot development.
General task

Sources

Create a data flow map that identifies the collection of personal
data (who collects what and how?), transfer (how is the data transferred; where to; which additional considerations regarding transfer,
such as security and contracts, need to be taken into account?),
processing (who processes the data and what safeguards are in
place?), storage (where are the data stored internally or externally;
for how long; how secure are they?), and erasure (when are the
data erased?)

Consult with experts in GDPR

2) Differentiate transparency needs of
stakeholders

Identify likely contexts of use (e.g., domestic, hospital, nursing
home, rehabilitation)

Refer to design use cases

Identify likely core user groups (e.g., health-care manager, nurse,
physiotherapist, patient, informal caretaker)

Consult with experts familiar
with context of use

Identify likely relevant background knowledge of core user groups
(educational background, IT expertise level, familiarity with robots,
familiarity with health-care processes, and familiarity with data
protection)

Consult with experts familiar
with context of use; consult
with stakeholder representatives

Identify likely transparency information needs and interests of core
user groups (e.g., general functionality of robot, data security, health
record compatibility, user privacy)

Consult with experts familiar
with context of use; consult
with stakeholder representatives

Identify stakeholder characteristics relevant for transparency communication (e.g., education level, physical or sensory impairments,
and cognitive limitations)

Consult with experts familiar
with context of use; consult
with stakeholder representatives

Provide differentiated access to transparency communications
tailored to user groups

HRI expertise
Explain the GDPR to different
target audiences

Identify suitable modality for transparency communication for user
groups, given user characteristics and context of use

HRI expertise
Consult with experts familiar
with context of use; consult
with stakeholder representatives

Ensure easy accessibility of transparency communication for users

HRI expertise
Consult with stakeholder
representatives

Track use of transparency functions

HRI expertise
User behavior

Observe user behavior in response to transparency communication

HRI expertise
User behavior

Evaluate effectiveness of transparency communication

HRI expertise
Assess users' understanding

Evaluate user satisfaction with transparency communication

HRI expertise
Consult users

Adapt and integrate users' feedback to increase positive results

HRI expertise
Results of user testing process

Provide understandable and easily accessible information on transparency functions for different user groups

Articles 12-15, 22 GDPR

Allow options and facilitate choice with regard to users' engagement with transparency communications

HRI expertise
Informed-consent requirements

3) Adapt transparency communication
to user groups

4) User testing

5) Provide guidance
for users on transparency functions

●

Steps

1) Identify general
transparency obligations

Union citizens or in the European Union territory. Engineers whose products might be used in the European
Union need to become familiar with and abide by the transparency requirements of the GDPR.
Transparency in HRI is underexplored, and findings
on the user value of transparency are mixed. More

●

research is needed to understand what constitutes
effective versus counterproductive implementations
of transparency.
More interdisciplinary collaboration is needed to translate
the relatively abstract and technology-agnostic GDPR into
the design of robot technology and to understand how
JUNE 2019

*

IEEE ROBOTICS & AUTOMATION MAGAZINE

*

77
IEEE Robotics & Automation Magazine - June 2019

Table of Contents for the Digital Edition of IEEE Robotics & Automation Magazine - June 2019
