Compilation of presentations of the second day of the VITALISE Summer School 2023. Harmonization of the Health and Wellbeing Living Lab process and ICT tools, Hands-on workshop on VITALISE system for data discovery and analysis are presented.
1. This project has received funding from European
Union’s Horizon 2020 Research and Innovation
Programme under Grant Agreement No 101007990.
Virtual health and Wellbeing Living Lab Infrastructure
Welcome Day 4
Evdokimos Konstantinidis (ENoLL)
3. This project has received funding from European
Union’s Horizon 2020 Research and Innovation
Programme under Grant Agreement No 101007990.
Virtual health and Wellbeing Living Lab Infrastructure
Harmonization of the
Health and Wellbeing
Living Lab process and
ICT tools
Despoina Petsani (AUTH)
4. Harmonization of the Health and
Wellbeing Living Lab process and ICT
tools
Change the Footer from "Insert" / "Header and Footer" 4
6. This project has received funding from European
Union’s Horizon 2020 Research and Innovation
Programme under Grant Agreement No 101007990.
Virtual health and Wellbeing Living Lab Infrastructure
Hands-on workshop on
VITALISE system for data
discovery and analysis
Gorka Epelde (VICOM)
7. VITALISE System: Discovery Portal
7
Visit: https://vitalise-portal.iti.gr/
As a New User, you will need to
register
click on the
yellow button
at the upper
right
8. Registration of a New User
8
Fill the form with the mandatory fields *,
indicating your name, a username, a
valid email, password, profession and
country,
then accept the terms
and click on the blue button "Register"
Remember to save your
password as you won't be
able to retrieve it from the
system.
9. Login as a User
9
Once you Registration process is
validated, you are going to be prompted
to the Login page.
There, indicate your username and
password to access, and click on the
blue button "Login".
10. Explore the System: Discover
10
After the Login is
successful, you will be
re-directed to the main
page of the system
within the Discovery
Portal.
To explore the
available datasets,
click on the "Discover"
option on the top left
menu.
11. Explore the System: Dataset Discovery
11
A complete list of the
available datasets will
appear, showing a
short description of
each one, like the
name, author, RAI
Node location and
type of dataset
(Anonymised, Non-
anonymised or Non-
Data Compliant)
12. Explore the System: Dataset Discovery
12
If you click on one of
the options of the
menu indicating the
type of dataset, the
system will filter the list
to show only that
specific dataset type.
Here is the example in
the case you click on
Non Data Model
Compliant.
If you want to explore
in more detail one
specific dataset, you
can click on the blue
button "GO TO
DATASET"
14. Explore the System: Go to dataset
14
Inside a dataset
description, you will
find a summary of the
dataset variables,
descriptive statistics,
among other
generalities of the
data.
If you decide to
access and
request the dataset,
you can click on the
green button "Request
Dataset"
15. Explore the System: Request dataset
sample
15
Then, you will receive
a message stating:
"Your Data are ready!".
This message is
adapted according to
the type of data, In
this example, NDM
data.
To download the
requested dataset,
you can click on the
green button
"Download".
16. Explore the System: Download dataset
sample
16
You will see the
download process on
your local device, and
clicking on the .zip
folder, you will find two
files: the .csv
containing the dataset
requested (in the case
of NDM, a maximum
of 1000 rows), and a
json file with the
information of the
dataset.
17. Alternatively, you can
find the dataset id in
the url.
17
In case, you want to
use this dataset for an
experiment:
The first step is to
check the json file you
obtain, and note down
the dataset id from the
field "dataset_id"
Explore the System: Download dataset
sample – Note down dataset id
18. Explore the System: Target RAI Node
18
A second step is to
check the RAI node
where the dataset you
are planning to use is,
You can find the RAI
Node id in the url.
MedPhys AUTH 41f31c07-659e-4b05-8106-8a3704e79030
Vicomtech 4ae4b106-0e89-453c-b107-02807aeec177
You can find the RAI
Node id and name
mapping here. Note
down the RAI Node
name
19. Explore the System: Target RAI Node
19
Alternative is to check
the RAI node where
the dataset you are
planning to use is
hosted by returning to
the general Discover
section of the portal,
then locate the
dataset and check the
RAI Node where it is
placed. This is
indicated just below
the dataset
description.
20. Explore the System: Experiment Run
20
With the RAI Node
location and the dataset
id noted down in
previous steps,
the next step is to click
on the "Experiment Run"
option in the top left
menu of the Discovery
Portal.
21. Explore the System: Experiment Run
21
You will be prompted
to the Run Experiment
page.
Here, you will find a
short description of
the 3 files you need to
Run an experiment:
1. Your Python code
(.py format)
2. Configuration of
the experiment
(.yaml format)
3. The Python venv
dependencies to
run your
Experiment (.txt
format)
22. Explore the System: Experiment Run
22
In detail, each of these
files should contain:
1. The code you
will apply to
process the select
dataset (current
version supports
Python scripts)
2. The general
configuration, which
includes the dataset
id information
3. (Python)
Libraries, packages
and modules, with
their versions, to
Run your Experiment
correctly
23. Explore the System: Experiment Run
23
To help you creating
these files, the
system makes 3
templates available
for you by clicking
on the “Download
Experiment
Template Files”
button.
24. Explore the System: Experiment Run
24
A .zip file will be
downloaded automatically
to your local machine.
Extract the files inside the
.zip into your selected
location. You will see 3 files:
1. MyExperiment.py: your
python code to be
executed
2. Experiment_config.yaml:
defined which dataset
you are going to used
3. Requirements.txt: what
libraries, packages,
modules your
experiment will use
25. Explore the System: Experiment Run
25
In your local machine,
open the
experiment_config file
with a proper
application.
Recommendation: use
Notepad
26. Explore the System: Experiment Run
26
Inside the file, you will
see a content like the
one showed in the
figure.
The only input you
need to introduce is for
the variable
“hash_query_real:”.
Recover the dataset id
you saved before and
paste this value in front
of the variable.
27. Explore the System: Experiment Run
27
Inside the file, you will
see a content like the
one showed in the
figure.
The only input you
need to introduce is for
the variable
“hash_query_real:”
Recover the dataset id
you saved before and
paste this value in front
of the variable. Then,
save the file.
Note: You have to
change this value each
time you want to use a
different dataset.
28. Explore the System: Experiment Run
28
The other 2 files
(MyExperiment.py and
Requirements.txt) are
functional and you can
use them as they are to
recover the column
names of the selected
dataset.
In case you want to
apply your own
processing code, open
MyExperiment.py and
save your code with
the adequate format.
Modify the
Requirements.txt
accordingly.
29. Explore the System: Experiment Run
29
Once your 3 files are
ready for running, you
need to select the
location of the dataset on
the dropdown tab “Select
RAI Node”.
Currently, there are 2 RAI
Node options: MedPhys
AUTH and Vicomtech.
Select the RAI Node
where your selected
dataset is hosted.
MedPhys AUTH 41f31c07-659e-4b05-8106-8a3704e79030
Vicomtech 4ae4b106-0e89-453c-b107-02807aeec177
A reminder of the RAI
Node id and name
mapping. Select the
RAI Node name
30. Explore the System: Experiment Run
30
After the RAI Node
selection, you need to
upload your files into
the system.
To do so, below the
dropdown tab, there
are three boxes that
allow you to select the
files from your local
machine.
31. Explore the System: Experiment Run
31
Click on “Select file” (or
the equivalent in your
language) in each
option.
Be aware of uploading
each file in the correct
option:
1. The python code
2. The Experiment
configuration
3. Requirements
32. Explore the System: Experiment Run
32
Be aware of uploading
each file in the correct
option:
1. The python code
2. The Experiment
configuration
3. Requirements
33. Explore the System: Experiment Run
33
You can confirm the correct
upload of the file by checking
on the final space of the row
if the name of the file is in there.
34. Explore the System: Experiment Run
34
Make sure all three files
are uploaded, thus all
three rows show the
name of each file.
35. Explore the System: Experiment Run
35
The fourth and last box
is an open format for
you to write any
description you
consider relevant
related to your
Experiment.
Once all files are
uploaded, and you are
ready to run your
experiment, click on
the blue button below
“RUN EXPERIMENT”.
36. Explore the System: Experiment Run
36
You will be prompted
to a page with the
message “Your
Experiment Results are
being processed…”.
You will have to wait
some minutes while the
experiment is
performed. The time
frame for waiting is
related to the size of
the dataset and the
complexity of the code
you are implementing.
37. Explore the System: Experiment Run
37
When your results are
ready, you are able to
see the message
“Results are correctly
produced!”,
and the green button
“Access Results” is
activated. Click on this
button.
38. Explore the System: Experiment Run
38
On clicking, two
options are available to
you:
1. A green button
“Download
Results”: clicking
here will
automatically
download the
results of your
experiments
2. A blue button
“Register Results”:
clicking here will
start the process to
register your results
and to assign a
unique identifier for
your experiment
39. Explore the System: Experiment Run
39
Following option 1. and
obtaining the results
file, you can open this
file using Notepad.
An example of a results
file is shown here, in
which column names
were retrieved for the
selected dataset.
40. Explore the System: Experiment Run
40
Following option 2. and
registering successfully
the experiment, you will
be presented with a
message stating
“Experiment Results are
registered!”, together
with the RAI identifier
assigned to your
experiment.
41. This project has received funding from European
Union’s Horizon 2020 Research and Innovation
Programme under Grant Agreement No 101007990.
Virtual health and Wellbeing Living Lab Infrastructure
Workshop on the
VITALISE Living Lab
Lexicon
Eva Kehayia (McGill)
42. The Living Lab Lexicon (LLL)
§ Why do we need a LLL?
–To facilitate and increase a common understanding
and communication between the different ‘players’
within the Living Lab communities and all those
who come in contact with Living Labs.
42
43. Where do we start
1. Determine which words/terms to define
a. Consider who the target audience(s) is (are)
2. Identify already existing definitions (if available)
3. Establish a process that will result in the definitions of the
selected terms within the context of LLs
45. User Design Research
45
§ User-centered design (UCD) is an iterative design process in which
designers focus on the users and their needs in each phase of the
design process. In UCD, design teams involve users throughout the
design process via a variety of research and design techniques, to
create highly usable and accessible products for them.
(https://www.interaction-design.org/literature/topics/user-centered-
design)
47. Participatory Research
47
§ Research that includes the active involvement of those who are the
subject of the research. Participatory research is usually action-
oriented, where those involved in the research process collaborate to
define the research project, collect and analyze the data, produce a
final product and act on the results. (https://ethics.gc.ca/eng/tcps2-
eptc2_2018_glossary-glossaire.html#p)
49. Knowledge User
49
§ A knowledge-user is an individual who is likely to be able to use the
knowledge generated through research to make informed decisions
about [...] policies, programs and/or practices. A knowledge-user's
level of engagement in the research process may vary in intensity and
complexity depending on the nature of the research and his/her
information needs. A knowledge-user can be, but is not limited to, a
practitioner, policy-maker, educator, decision-maker, health care
administrator, community leader, or an individual in a health charity,
patient group, private sector organization, or media outlet.
(https://cihr-irsc.gc.ca/e/29418.html#3)
51. Stakeholder
51
§ [...] individuals, organizations or communities that have a direct
interest in the process and outcomes of a project, research or policy
endeavor (Deverka et al., 2012).
§ 7Ps Framework to identify stakeholders in Patient-Centered Outcomes
Research and Comparative Effectiveness Research in the US. The
7Ps are patients and the public, providers, purchasers, payers, public
policy-makers and policy advocates working in the non-governmental
sector, product makers, and principal investigators (Concannon et al.,
2012).
52. Super Lab
52
§ What are the first 3 words or phrases that come to mind when you
hear ‘Super Lab’
Word cloud activity
53. Sustainability
53
§ What are the first 3 words or phrases that come to mind when you
hear ‘Sustainability’
Word cloud activity
54. User engagement
54
§ What are the first 3 words or phrases that come to mind when you
hear ‘User engagement’
Word cloud activity
55. Sandboxes
55
§ What are the first 3 words or phrases that come to mind when you
hear ‘sandboxes’
Word cloud activity
56. Testbed
56
§ What are the first 3 words or phrases that come to mind when you
hear ‘testbed’
Word cloud activity
57. Determining which words/terms to
define
Compiled a corpus of articles that used Living lab methodology
and the ENoLL Proceedings
§ To identify and select the articles, we created a search strategy
that included terms commonly used by those who use a Living
Lab methodology:
§ “living labs, co-creation, real life settings, user centered,
interactive exchange, interdisciplinary and transdisciplinary
research, innovation, users as partners, controlled environment,
participatory design”
§ These terms were searched in the abstract or the keywords
provided in the article.
58. Determining which words/terms to
define
§ The collaborating Health Sciences Librarian at McGill
conducted a multifile search of three databases, MEDLINE,
EMBASE, and PsycInfo on the Ovid platform in August 12, 2022)
– 567 articles identified and entered in Rayyan platform
– 340 were excluded
– 54 were possible
– 173 articles included
§ We added the articles of all proceedings from the ENoLL Open
Living Lab Days (2013-2022)
59. Determining which words/terms to
define
The corpus of articles identified through the search AND the ENoLL
Proceedings were entered in a word mining software, WordStat
61. Determining which words/terms to
define
§ Words do not exist in a void.
§ They are linked and co-exist with other concepts
§ A first map of the different concepts was created
62. Orchestration
LL operates as the
orchestrator within the
open innovation
ecosystem
LIVING
LAB
Multi-stakeholder
participation
Taking a holistic
view on society,
involving
stakeholders from
the quadruple
helix model
Active user
involvement
LL involves relevant
stakeholders 'actively' in
all relevant activities,
ensuring their feedback
is captured and
implemented throughout
the whole lifecycle of
the innovation
Co-creation
in LL , values are bottom-
up co-created not only for
but also by all relevant
stakeholders, ensuring a
higher adoption at the end
Real-life settings
LL operates in the
real-life setting of the
end users, infusing
innovations into their
real life instead of
moving the users to
test sites to explore
the innovations
Multi method approach
each LL activity is problem
driven. Therefore, the
methodological approach
towards every individual
activity will be selected based
on the expected outcomes of
the activity and the
stakeholders who needs to be
involved.
Open
Innovatio
n
ecosyste
m
to connect and
partner up with
relevant
stakeholders
Citizen
Public
sector
Private
sector
Education
and
research
Lead user
End-user
Consumer
Expert
Non-user
User centric/
centered
TRL1
TRL2
TRL3
TRL4
TRL 5
TRL 6
TRL 7
TRL 8
TRL 9
User
panel
LL
Project
Living lab
infrastructure
s
Innovation
process
Quadruple
helix
User driven
Stakeholder typology
Degree of
involvemen
t
63. Living Lab
§ Living Labs are open innovation ecosystems in real-
life environments based on a systematic user co-
creation approach that integrates research and
innovation activities in communities, placing citizens
at the centre of innovation. (ENoLL)
65. Stakeholder typology (typology
was replaced by involvement)
§ Stakeholder involvement:
– Lead user
– End-user
– Customer
– Expert
– Nonuser
– Target user
– Early adopter
66. Lead user
– Lead user: They are the ‘leading edge’, well qualified and motivated to make significant
contributions to the development of new products and services. Lead users face new needs
of the market and this significantly earlier than the majority of the customers in a market
segment. They will profit strongly from innovations that provide a solution for those needs.
Lead users do not just experience any new need, but those needs that most customers will
face in the future.
– Examples of lead user from Vienna: Hospital management,
governmental bodies (public procurement), patient experts,
technology (MedTech), caregivers, patient associations…
Identifying Lead Users in a Living Lab Environment. Available from:
https://www.researchgate.net/publication/256988097_Identifying_Lead_Users_in_a_Living_Lab_Environment
67. End user
– End user: The term "end user" refers to the consumer of a good or service, often who
has some innate know-how that is unique to consumers. End user experience and support
are crucial for the success of user-oriented products and services. End user experience and
support are crucial for the success of user-oriented products and services.
68. Consumer (replaced with
customer)
– Consumer: instead, Customer was proposed: In comparison to the
end user, a customer is the person performing the purchasing transaction of the technology,
who may or may not also be the ultimate end user. At a place of business, for example, the
boss may be the one that purchases the computer, so the boss is the customer, but a junior-
level employee would be the actual end user.
– Did not like this definition, instead proposed the following:
– LL perspective: An entity (individual, private or public organization, or company) that pays a
LL to perform services (co-creation/research) and pays for the results of those services
– Stakeholder perspective: An entity who pays for the end-product of the co-creation/research
(results) within the general context of the “market”
69. Expert
§ Expert: An expert is somebody who has a broad and deep
understanding and competence in terms of knowledge, skill and
experience through practice and education in a particular field.
§ Informally, an expert is someone widely recognized as a reliable
source of technique or skill whose faculty for judging or
deciding rightly, justly, or wisely is accorded authority and
status by peers or the public in a specific well-distinguished
domain.
§ An expert, more generally, is a person with extensive knowledge
or ability based on research, experience, or occupation and in a
particular area of study.
https://en.wikipedia.org/wiki/Expert
70. Non-user
§ Non-user: a potential user or a group of people who are not
using the LL services, persons who may be interested but not
using yet.
§ They are customers and experts who are not currently using the
LL services but could.
§ Could be users who used the services in the past but no longer
do.
71.
72. Super Lab
72
Multidisciplinary experimental research and
design laboratory that elaborates with digital
physical and mental worlds
Help companies and organizations to transform
their brands products and services so they are
prepared for the future.
73. Testbed
73
Platform for conducting rigorous transparent and
replicable testing of scientificid theories
computing tools and new technologies
74. Sandboxes
74
Regulatory sandboxing is a framework for testing
innovation and rules and regulations and
underpinning in a real world setting typically
under a temporary regulatory exemption.
75. Sustainability
75
The quality of being able to continue over a
period of time and the ability of being maintained
at a certain rate or level.
77. Workshop on the VITALISE Living Lab
Lexicon
Change the Footer from "Insert" / "Header and Footer" 77
78. This project has received funding from European
Union’s Horizon 2020 Research and Innovation
Programme under Grant Agreement No 101007990.
Virtual health and Wellbeing Living Lab Infrastructure
Wrap up, opportunities for
collaboration and
conclusions
Evdokimos Konstantinidis (ENoLL)
79. This project has received funding from European Union’s Horizon 2020 Research and Innovation Programme under Grant Agreement No 101007990.
Contact us
Online presence
https://vitalise-project.eu
https://twitter.com/VITALISEproject
https://www.facebook.com/VITALISEproject/
https://www.linkedin.com/company/vitalise-project/
Subscribe to our newsletter:
European Network of Living Labs (ENoLL)
https://enoll.org/
https://openlivinglabdays.com/
info@vitalise-project.eu
Project coordinator:
Dr. Evdokimos Konstantinidis
Scientific coordinator:
Prof. Panos Bamidis
Name and affiliation of the presenter
email of the presenter
90. This project has received funding from European Union’s Horizon 2020 Research and Innovation Programme under Grant Agreement No 101007990.
Contact us
Online presence
https://vitalise-project.eu
https://twitter.com/VITALISEproject
https://www.facebook.com/VITALISEproject/
https://www.linkedin.com/company/vitalise-project/
Subscribe to our newsletter:
European Network of Living Labs (ENoLL)
https://enoll.org/
https://openlivinglabdays.com/
info@vitalise-project.eu
Project coordinator:
Dr. Evdokimos Konstantinidis
Scientific coordinator:
Prof. Panos Bamidis
Name and affiliation of the presenter
email of the presenter