FAQ Practical questions

Nr

CR

Question

Answer

1

V1

Is the given presentation shared?

Yes, look here for the presentations of the consultation rounds.

2

V1

Is the obstacle list of the Obstacle Removal Route (OVT) available?

Obstacle Removal Trajectory | Health-RI  

3

V1

Why was the session held in Dutch? There are many people in the nodes who do not speak Dutch.

In view of our communication strategy and objectives and the current and future target group of Health-RI, Health-RI chooses Dutch as the primary language of communication in our communications. This involves context-dependent deviations to Dutch and English.

Why was this choice made?

Health-RI is setting up a national health data infrastructure with impulse funding from the National Growth Fund (EZK). We mainly deal with Dutch-speaking stakeholders and policy/laws and regulations. By doing our communication in the Dutch language, we can communicate more effectively with our entire target group. This is important because it helps Health-RI to communicate our working methods, ideals and needs more clearly and can increase the trust and accessibility of the organization. An important part of Health-RI is to arrive at a national agreement system together with the Ministries of Health, Welfare and Sport, EZK, OCW and many field parties.

A separate session has now been organised in English.

4

V2

The consultation has been recorded. Will it be shared later so that others can watch it?

No, the recording is for our own use in order to be able to process the input in the wiki.

5

V2

I've read the wiki. If I'm a potential data contributor, what things do I need to adhere to in order to be a part of Health-RI. EJP-RD has an "onboarding document".

At the end of plateau 1, we want to have a supported handbook for onboarding, especially the minimum metadata; With Plateau 2 we add the extra metadata. We are also building the API and the Secure Processing Environment at the same time so that we can actually work with the requested data. To sum up: the plateau planning shows you more and more what you need to do to be on board.

6

V2

If I have a tool for IAA (identification, authenticatio and authorization), how can I link it to Health-RI, and I can't wait until year 4 to get started.

We are working with SURF on a proof of concept to connect to SRAM, which should be made available in Plateau 2. The Analysis Working Group has the leading role in this. By discussing your solution direction in this working group, it would be possible to determine together how the solution direction could fit into the future Health-RI solution.

When making the choice, we pay attention to the feasibility of the solution. We start a PoC in which we can serve the largest Health-RI target group – for example the researcher from a UMC. The solution direction must be expandable later by means of a different identity provider for other target groups. We have a limited capacity; you can bring in your specific wish as a priority and discuss this with the Analysis working group (of which IAA is a part) to see if it can become part of the pilot.

7

V2

Much depends on the working groups that work on each topic. How do you ensure that the right parties are/are involved?

Who we don't know, or who doesn't know us, we can't join. Anyone can nominate parties that need to be involved. Through broad appeals on media such as LinkedIn, we try to get in touch with the right parties.

8

V2

How can (new) working groups be formed? Is there a process for that?

At the moment, it is not possible to form new working groups. If there is a topic that needs to be worked out, we bring that topic to an existing working group.

9

V2

Is it known who the contact persons of the working groups are (not on the wiki)?

The contacts of the working groups are listed on the colophon.

10

V2

We need to mobilize more people. We need to learn from how others do standard development. For example, W3C has lightweight groups to test technology. In the nodes, we have the capacity to work on these things; Nodes are already working together in projects.

We can look at these collaboration techniques. We have to make sure everything works, we work together and avoid reinventing the wheel.  Also, don't forget that we already have working groups! We will also be holding a roadshow to discuss the broad activity planned in each of the nodes

11

V3

We cannot set up a federated data station in terms of compute. Are there solutions for this?

For these types of cases, we are thinking of a shared service center, where the compute can be offered to parties that do not have enough capacity themselves.

Solutions for too little compute would be: a compute node at SURF or anDREa

12

V3

1. what is the planning?

2. When will the environment be operational?

3. If we want to connect as an organization, what do we need to set up/do internally?

1. The delivery of the first plateau is a matter of weeks

2. At the end of this year (2024) we will launch a platform/portal where, for example, researchers can find a catalog, an application tool, a list of potentially safe processing environments.

3. Connecting in terms of data will take place via the onboarding process.