docs.healthdata.beTo give access to the applications of healthdata.be (like HD4DP v2 and healthstat.be), you need to click on GIVE ACCESS in the white text box on the EAM portal page.
You can give access to
Give access to a single user
After selection of GIVE ACCESS on the EAM portal page, an ACCESS REQUEST form is shown.
Completing this form is similar to the process on the Request Access page for standard end-users. In the capacity of a SPOC, however, you will now fill in an Access Request form for a user within your organization.
Please fill in all required fields (indicated with a red asterisk *), make a selection in the mandatory drop-down lists and, optionally, tick the check boxes for additional help and/or information.
Organization NIHDI number
The NIHDI number of the organization is already provided, since your account is connected to this organization.
Role in project
When selecting Local Study Support, you will be asked to make a selection in the drop-down list of Author groups. These author groups are specified for the organization in question.
HD4DP2.0 field
Click in the field under HD4DP2.0 if you want to access the application to make registrations for the selected project:
Healthstat.be field
Click in the field under healthstat.be if you want to access the reporting of the selected project:
Once you have completed the access request form, click on the Submit button. When the submisson was successful, you will receive a confirmation message.
The Profiles tab of the validated SPOC profile offers the possibility to Search, Select and Sort profiles. Selected user profiles in the list can be Validated or Rejected via the Action drop-down menu.
In the Requests tab the SPOC can manage the overview of requests. More information is to be found on SPOC actions upon a request.
See documentation under Give access to multiple users in batch for more information on the Batch create requests tab.
The Edit tab (see image below) offers the possibility for a SPOC to modify the own profile regarding NIHDI number, Organization, Email address and State. Select the Save button to install the new profile information.
Continue to Give access to multiple users in batch in order to give access to multiple users in one operation.
Give access to multiple users in batch
The person whom has been assigned the SPOC role for the healthcare organization (HCO) is able to give access to multiple users in batch. The SPOC therefore needs to return to the User profile page and select the tab Batch create requests.
In the tab Batch create requests a CSV file can be selected via the file selection button.
Upload the CSV file and click on the Run the batch creation button. An example of a CSV file structure is available here:
By doing so, a master request per line will be automatically generated, and then the information will be split into sub-requests (one per application or project) and saved in the healthdata.be DB2 for further processing.
A table schema (https://specs.frictionlessdata.io//table-schema/) to validate CSV looks as follows. An example file is available here: eam_csv_batch_requests_schema.json
User roles and corresponding values
To complete the “role”, 3 different choices are possible:
- 1= Local Study Lead: Only 1 Local Study Lead can be created by healthdata.be (Sciensano) for each registry within each organization.
- 2= Local Study Associate (= author). This will be the default role a user will receive, the reason why it was prefilled with “2”.
- 3= Local Study Support (= co-author). This role can be given if it is more suitable for the user. A Support will always need an Associate to which he/she will be assigned.
When selecting role 1 and 2 (= Local Study Lead and Local Study Associate), the name of the ‘Local Study Lead or Associate’ is expected in the field “author_group”. To be filled in in the format <first_name last_name> of the Associate, with just 1 space (tab) between the two names).
When selecting role 3 (= Local Study Support), the name of the ‘Local Study Associate’ is expected in the field “author_group”. To be filled in in the format <first_name last_name> of the Associate, with just 1 space (tab) between the two names).