Barometer for General Practice

Barometer for General Practice

Welcome to the documentation pages for the project Barometer for General Practice, provided by the service healthdata.be (Sciensano).

These pages provide information about the technical processes of the project. The following sections are provided:

For scientific information of the project, please contact the primary organization that oversees implementation of project (see section "General project information").

admin Tue, 06/03/2025 - 12:50

General barometer project information

General barometer project information

Project name

Barometer for General Practice

  • Diabetes
  • Antibiotics
  • Chronic Kidney Disease Barometer

Project abbreviation

  • GPBARO_DM
  • GPBARO_ABX
  • GPBARO_CKD

Project code

  • HDBP0271
  • HDBP0275
  • HDBP0276

Primary organization that oversees implementation of project

  • KU Leuven - Academisch Centrum Huisartsgeneeskunde (ACHG)

Partner organization participating in project

  • General practice centers

Organization that commissioned this project

Organization providing monetary or material support

Brief project description

The study aimed to provide a tool that will help general practitioners in Belgium to map the population of their patients and to receive feedback on the quality of care for their diabetes patients.

The main objective of this project is to monitor the quality of care in general practice. By giving individual feed-back to GP centers, this might stimulate them to improve the quality of their care.

Researcher is willing at first stage to collect aggregated data from individual GP centers in Belgium. These data will contain the number of diabetes patients in a GP center and the number of patients in whom quality indicators for care are fulfilled. This data collection will be used to provide feedback, with benchmarking, to individual GP centers about the quality of their diabetes care. This feedback can stimulate GP centers to improve their quality of care.

Bart.Servaes Tue, 06/03/2025 - 15:45

The GPBARO_DM data reporting and visualization

The GPBARO_DM data reporting and visualization Bart.Servaes Mon, 10/21/2024 - 15:32

Healthstat.be

Healthstat.be

For the general description of the HD application healthstat.be and the position thereof in the HD architecture go here.

Go here to learn how to log in into the HD application healthstat.be.

Bart.Servaes Fri, 06/21/2024 - 13:00

The data management process of Barometer for General Practice projects

The data management process of Barometer for General Practice projects

Below we describe (high level) the GPBARO data management process between the General Practice and the healthstat.be platform of healthdata.be.

Data management process: 

  1. Data is captured by the GP in their usual care management environment 
  1. The EMD software vendor transmits the relevant data to the eHealthbox environment 
  1. eHealthbox collects the data in a generic format 
  1. The messages are extracted from eHealth and loaded to the HD DWH environment, where treatment of the data through the data layers is done. 
  1. HD extracts the necessary data from the ehealth messages and injects them into the DWH external DB environment for the Diabetes Barometer 
  1. GP’s access the reports of their own practice through a SSO solution integrated in their EMD. 

Bart.Servaes Tue, 06/25/2024 - 08:00

Request access as a General Practitioner to healthstat.be for a specific project in EAM

Request access as a General Practitioner to healthstat.be for a specific project in EAM

In the new Entity Access Management system EAM there are three options for a General Practitioner to get access to projects in healthstat.be. Follow the links at the bottom of this page to have explore each one of them. Select the option that fits your needs or way of working.

All three options have the first step in common, which is described below. The options are then continued on the respective pages.

To navigate to the homepage of HD Entity Access Management (EAM) system you enter the URL https://eam.healthdata.be in your internet browser.

Select Login at the top left of the screen and then click on the red Log in with eID button.

You are directed to the government's Federal Authentication Service (FAS), where you can log in with multiple digital keys with eID or digital identity.

If you have chosen to connect with ItsMe, you need to enter your cell phone number.

Follow the instructions on your mobile device via the ItsMe application.

Once the itsme login procedure has been completed, you select the green profile validation button ("Profiel bevestigen" or "Confirmer le profil") to log in into the HD EAM system (see image below).

NLFR

You have landed on the portal page of the healthdata.be Entity Access Management system EAM showing the data you have shared by eID, itsme or another digital key, similar to the screen below:

Chose one of the three options below to continue your request for access to healthstat.be:

Bart.Servaes Fri, 06/28/2024 - 11:07

User roles in healthstat.be

User roles in healthstat.be

Each healthcare organization has at least one Access Manager who is managing the access rights to the applications of the own organization and is doing so in the HD Entity Access Management (EAM) system. In this process, access requests by healthcare organization employees are analyzed and validated if legitimized. The scope of the accesses granted to healtstat.be may differ, which is reflected in various combinations of user roles and data levels.

Two user roles can be distinguished: Data Provider, which is a user linked to an existing organization, and Sponsor, being the sponsor/coordinator of the data collection. Both are allowed to view reports based on data level. There are two data levels that determine the scope of visibility of the reports: Hospital, i.e. consulted reports contain all data registered by hospital staff, Individual, i.e. consulted reports contain only data that have been registered by that very user.

Data Provider / Hospital:

The Data Provider / Hospital profile can:  

  • consult reports of a specific data collection that contain data from the concerned hospital

Data Provider / Individual:

The Data Provider / Individual profile can: 

  • consult reports of a specific data collection that only contain data that have been personally registered

Sponsor / Sponsor:

The Sponsor / Sponsor profile can:

  • consult all reports that contain data collected at hospital level

Sponsor / Individual:

The Sponsor / Individual profile can: 

  • consult all reports that only contain data that have been personally registered

Remarks:

  • It is up to the Access manager to change roles from or to Data Provider / Hospital, Data Provider / Individual, Sponsor / Sponsor and Sponsor / Individual. These actions are to be performed in the EAM system.
Bart.Servaes Fri, 06/21/2024 - 15:04

Option 1: The General Practitioner creates and completes an EAM account, the Access Manager approves it

Option 1: The General Practitioner creates and completes an EAM account, the Access Manager approves it

This option gives the request for access to healthstat.be mainly in the hands of the General Practitioner. The GP first completes the own user profile, then adds an EAM account to it and finally adds the grants, determining the specific registry and the role/data level requested. The General Practitioner then sends the access request for approval to the Access Manager, who fullfils the approving step.

Table of contents

The General Practitioner actions

Go back here if you want to know how to navigate to the My Profile page.

Completing the user profile and becoming an Authenticated User

The main My profile page shows the Personal information gathered during the FAS login procedure, and the list of accounts linked to your profile (Linked accounts section).

Attention: When the General Practitioner logs in for the first time, there will be no NIHDI number and the list with linked accounts will be empty too.

Now, click on your name and e-mail address on the top left of the screen to toggle a toolbar with a series of tabs: View profile, Edit profile, My Accounts and Log out. The View profile tab directs you to the My profile screen, which is the screen you are viewing now.

To complete your profile, select the Edit profile tab. The Edit tab contains two subtabs: User settings and Personal information. The red asterisks indicate required fields.

Select the User settings tab.

ATTENTION: When logging in for the first time, the User settings tab will feature a primary e-mail address field with a pre-filled default e-mail address, e.g.:

Replace this address with your professional e-mail address. This e-mail address is used to send necessary notifications to you. Preferably avoid the use of public e-mail addresses such as @gmail.com, @hotmail.com, @yahoo.com etc.

Confirm with the Save button.

The Personal information tab contains pre-populated information such as first name, last name and SSIN in greyed out fields. This information can't be changed. Next to this, you can provide a personal NIHDI number, or more than one, if applicable.

Use the Save button to confirm. You have now completed the fields in both User settings and Personal information tabs, which makes you known to the EAM system as an Authenticated User.

Adding and provisioning an EAM account

Return to the My profile page and select the My accounts tab.

On the My accounts page your personal information is displayed in the blue User details section, followed by a list of accounts you have created.

To add a new account, click on the Add new Account button at the bottom of the page.

The Add a new account window appears.

Complete the fields in the Add a new account window with the e-mail address you use for your organization. Then select the combination of your organization (General Practitioners) and the application (healthstat.be). This is what we call provisioning of an account.

Click on the Save button.

You will be automatically redirected to the My accounts page that has now been updated with your newly created account added at the bottom of the list. The account has received the status "Draft".

Adding grants for a project in healthstat.be

At this point you can start the process of adding grants, i.e. determining roles and data level for a project in Healthstat, adapting the EAM account status and requesting for approval by the Access Manager.

Select "n grants" in the Grants column.

The Account: Manage grants screen appears. To add new grants to an account you need to click on the Add new Grant button.

The Add a new grant window pops up. Select the desired project and the role of Data Provider / Hospital, Data Provider / Individual, Sponsor or Sponsor / Individual.

When you return to the My accounts page, you will see that the accounts list has been updated with the selected grant:

You have now created an account for a project in Healthstat.be with the role of Data Provider / Hospital, Data Provider / Individual, Sponsor / Sponsor or Sponsor / Individual.

Requesting approval of EAM account with access grants for projects in healthstat.be

To request approval of this account you need to click on "n grant(s)" in the Grants column to open the Account: Manage grants page. You either can add a new grant or request for approval. To do so, click on the Request approval button.

The Account state is updated to Approval in the Account details section.

Return to the My accounts page where you notice the changed Account state to Approval.

The Access Manager will be notified of your request via e-mail. You will have to wait now for the Access Manager to take action. This can take multiple hours. After approval by the Access Manager (next step), the Account state will change to Approved.

The Access Manager actions

Approving EAM account with access grants for projects in healthstat.be

Click on Manage to the top left of the screen, so that EAM appears. When hovering over this, the items EAM Users and EAM Accounts become visible.

Select EAM Accounts and Approval successively.

When clicking on Approval you open the page with end-user accounts that are waiting to be approved:

There are two ways to approve these account requests:

  • By checking the selection box of the relevant account request and selecting the Approve action. Click on the Apply to selected item button to perform the action.
  • By clicking on the Edit button in the Operations column for the relevant account ...

... and subsequently on the Approve button in the Account: Manage grants screen.

The Account state changes to Approved.

After this, a fulfilment process will start to run in the background, finally resulting in an account state change to Published. Credentials are sent to the General Practitioner by e-mail.

Performing a push action

If this change does not take place within a reasonable amount of time - usually between 15 minutes and up to three hours - the account could be updated by means of a "push".

Therefore, return to the accounts overview screen.

First, check the Approved account that needs to be pushed (1). Then, open the Action drop-down menu and select the Update account (push) option (2). Finally, validate this action by clicking on the Apply to selected items button (3).

In case the push action does not trigger the expected result, you need to contact our Support service.

Bart.Servaes Tue, 06/25/2024 - 07:52

Option 2: The General Practitioner creates an EAM account, the Access Manager completes and approves it

Option 2: The General Practitioner creates an EAM account, the Access Manager completes and approves it

With this option the actions performed by the General Practitioner are restricted to the completion of the own user profile and the creation of an EAM account which is an absolute necessity to be retrieved by the Access Manager via the Users Overview. The Access Manager takes it from there and adds the grants to the EAM accounts of the General Practitioners, sends the access request for approval and finally approves this request.

Table of contents

The General Practitioner actions

Go back here if you want to know how to navigate to the My Profile page.

Completing the user profile and becoming an Authenticated User

The main My profile page shows the Personal information gathered during the FAS login procedure, and the list of accounts linked to your profile (Linked accounts section).

Attention: When the General Practitioner logs in for the first time, there will be no NIHDI number and the list with linked accounts will be empty too.

Now, click on your name and e-mail address on the top left of the screen to toggle a toolbar with a series of tabs: View profile, Edit profile, My Accounts and Log out. The View profile tab directs you to the My profile screen, which is the screen you are viewing now.

To complete your profile, select the Edit profile tab. The Edit tab contains two subtabs: User settings and Personal information. The red asterisks indicate required fields.

Select the User settings tab.

ATTENTION: When logging in for the first time, the User settings tab will feature a primary e-mail address field with a pre-filled default e-mail address, e.g.:

Replace this address with your professional e-mail address. This e-mail address is used to send necessary notifications to you.

Confirm with the Save button.

The Personal information tab contains pre-populated information such as first name, last name and SSIN in greyed out fields. This information can't be changed. Next to this, you can provide a personal NIHDI number, or more than one, if applicable.

Use the Save button to confirm. You have now completed the fields in both User settings and Personal information tabs, which makes you known to the EAM system as an Authenticated User.

Adding and provisioning an EAM account

Return to the My profile page and select the My accounts tab.

On the My accounts page your personal information is displayed in the blue User details section, followed by a list of accounts you have created.

To add a new account, click on the Add new Account button at the bottom of the page.

The Add a new account window appears.

Complete the fields in the Add a new account window with the e-mail address you use for your organization. Then select the combination of your organization (General Practitioners) and the application (healthstat.be). This is what we call provisioning of an account.

Click on the Save button.

You will be automatically redirected to the My accounts page that has now been updated with your newly created account added at the bottom of the list. The account has received the status "Draft".

Since the General Practitioner is now connected to an organization, he or she can now be found by the Access Manager via the EAM Users Overview. Underneath is explained how that exactly works.

The Access Manager actions

Retrieving the EAM account of the General Practitioner

Click on Manage at the top left of the screen, so that the EAM menu appears. When hovering over this, the menu items EAM Users and EAM Accounts become visible. Select EAM Users.

The following page with an overview of the different General Practitioners appears. Select the GP for whom you want to request access to a project in healthstat.be. Click on the corresponding First name, Last name or SSIN.

ATTENTION: General Practitioners that not yet appear in the list have either to register via the FAS procedure and create an account (see General Practitioner actions above) or have to be added via Bulk upload (Access Manager action, see Option 3) first.

The account that has been added and provisioned by the General Practitioner will be visible now and has the Draft status. Click on the Edit button at the end of the relevant account line.

Adding grants for a project in healthstat.be

Next, click on the Add new Grant button at the bottom of the Manage grants page.

The Add a new grant window with some required fields pops up. Select the Project you want to have access to from the drop-down list. Next, select the Role and the Data level that apply to your situation. Click on the Save button.

When returning to the Account: Manage grants page you will notice that the grant is added to your account, which is still in the Draft state.

Requesting approval of EAM account with access grants for projects in healthstat.be

Next step is to request approval of the newly added account with grants, thus enabling the General Practitioner to access the specified project(s) in healthstat.be. Therefore, click on the Request approval button.

The status immediately changes to Approval.

Since you are Access Manager, you will be able to follow up swiftly and to change the Account state to Approved.

Approving EAM account with access grants for projects in healthstat.be

Click on Manage to the top left of the screen, so that EAM appears. When hovering over this, the items EAM Users and EAM Accounts become visible.

Select EAM Accounts and Approval successively.

When clicking on Approval you open the page with end-user accounts that are waiting to be approved:

There are two ways to approve these account requests:

  • By checking the selection box of the relevant account request and selecting the Approve action. Click on the Apply to selected item button to perform the action.
  • By clicking on the Edit button in the Operations column for the relevant account ...

... and subsequently on the Approve button in the Account: Manage grants screen.

The Account state changes to Approved.

After this, a fulfilment process will start to run in the background, finally resulting in an account state change to Published.

Performing a push action

If this change does not take place within a reasonable amount of time - usually between 15 minutes and up to three hours - the account could be updated by means of a "push".

Therefore, return to the accounts overview screen.

First, check the Approved account that needs to be pushed (1). Then, open the Action drop-down menu and select the Update account (push) option (2). Finally, validate this action by clicking on the Apply to selected items button (3).

In case the push action does not trigger the expected result, you need to contact our Support service.

Bart.Servaes Tue, 06/25/2024 - 07:57

Option 3: The Access Manager creates Users and Accounts via csv batch upload

Option 3: The Access Manager creates Users and Accounts via csv batch upload

When chosing this option, all actions are to be carried out by the Access Manager. First, the Access Manager needs to create the EAM Users (i.e. General Practitioners) by means of a bulk upload using a csv file. After succesful import of this list, the same procedure is repeated for the EAM Accounts, including access grants. Based on the required fields in the csv files, the user and account data are linked, and only need to be approved by the Access Manager.

Table of contents

The General Practitioner actions

The Access Manager actions

The General Practitioner actions

No actions to be completed by the General Practitioner

The General Practitioner is an Authenticated User who does not have the rights to perform the necessary actions.

The Access Manager actions

Go back here if you want to know how to navigate to the My Profile page.

Creating EAM Users in batch

Click on Manage to the top left of the screen, so that EAM appears. When hovering over this, the items EAM Users and EAM Accounts become visible. Click on EAM Users and Bulk upload successively.

The Users Batch Creation page appears.

Select a valid .csv file on your system to upload or use the following example file:

Use the schema file to validate the csv example file:

ATTENTION:

Access Managers need to know the personal details of the users they are adding: first_name, last_name, email, ssin.

The NIHDI of the organization (org_nihdi) is: 333333333.

User roles and corresponding values

To complete the value for the field “role”, 2 different variables are possible:

  • access_manager
  • default

Additional tips:

  • If the user already exists, the line will be skipped.
  • Avoid using Excel as this can lead to unwanted formatting.
  • First_name and Last_name need to be capitalized.
  • Make sure that you have placed the quotes correctly. If the values have no comma, you can also leave out quotes.

Abbreviations used in csv bulk upload files

  • ssin: Social Security Identification Number - Numéro d’identification de la sécurité sociale (NISS) - IdentificatieNummer Sociale Zekerheid (INSZ)
  • org_nihdi: National Institute for Health and Disability Insurance number of your organization (RIZIV/INAMI number)
  • nihdi: your personal National Institute for Health and Disability Insurance number (RIZIV/INAMI number)
  • app: application such as HD4DP, Healthstat
  • project_code: code of the healthdata.be Business Project, e.g. HDBP0001 for Belgian Cystic Fibrosis Registry (BCFR)

Now, run the batch creation by clicking on the corresponding button.

Return to the EAM Users overview page to verify the bulk uploaded list of General Practitioners.

Following this step, the Access Manager needs to link these Users with EAM accounts, having the access grants in them.

Creating EAM accounts in batch awaiting approval using CSV Upload

Click on Manage to the top left of the screen, so that EAM appears. When hovering over this, the items EAM Users and EAM Accounts become visible. Click on EAM Accounts and Bulk upload successively.

The Accounts Batch Creation page appears.

Select a valid .csv file on your system to upload or use the following example file:

Use the schema file to validate the csv:

ATTENTION:

Access Managers need to know the personal details of the users they are adding: first_name, last_name, email, ssin.

User roles and corresponding values

To complete the value for the “role” field for healthstat.be, 4 different variables are possible:

  • DATA_PROVIDER_HOSPITAL = Data Provider/Hospital
  • DATA_PROVIDER_INDIVIDUAL = Data Provider/Individual
  • SPONSOR_SPONSOR = Sponsor/Sponsor
  • SPONSOR_INDIVIDUAL = Sponsor/Individual

Make sure to use "healthstat" as value for the "app" field, since roles "Data Provider" and "Sponsor" combined with data levels "Hospital" and "Individual" are typical for the Healthstat.be data reporting and visualization application.

Additional csv bulk upload tips

  • When the "role" field has value "1" or "2", the "authorgroup" field should be left empty. Pay attention to this when changing "role" field from value "3" to "1" or "2".
  • When adding a user to role "3", the author group needs to be defined and needs to exist, or the line will be skipped. To guarantee a successful bulk upload of an extensive csv file, you want to place the accounts with role 3 at the end of the list to be uploaded. The accounts with role "1" and "2" are imported first, and thus prefilling the author group list with First_name and Last_name prior to importing the accounts with role "3".
  • First_name and Last_name need to be capitalized.
  • When adding more than one project code, use pipes to separate the codes.
  • If the user does not exist, the line will be skipped.
  • Avoid using Excel as this can lead to unwanted formatting of the csv file.
  • Make sure that you have placed the quotes correctly. If the values have no comma, you can also leave out quotes.

Abbreviations used in csv bulk upload files

  • ssin: Social Security Identification Number - Numéro d’identification de la sécurité sociale (NISS) - IdentificatieNummer Sociale Zekerheid (INSZ)
  • org_nihdi: National Institute for Health and Disability Insurance number of your organization (RIZIV/INAMI number)
  • nihdi: your personal National Institute for Health and Disability Insurance number (RIZIV/INAMI number)
  • app: application such as HD4DP, Healthstat
  • project_code: code of the healthdata.be Business Project, e.g. HDBP0001 for Belgian Cystic Fibrosis Registry (BCFR)

Then, make a selection in the Approval State menu shown below.

  • Create as awaiting approval: With this option the accounts will receive the status Approval and will be set ready for the Access Manager to be Approved.
  • Create as pre-approved: With this option the accounts will automatically receive the status Approved and will be uploaded directly without further input from the Access Manager (e.g. confidence in content quality is very high)

Finally, run the batch creation by clicking on the corresponding button.

Approving EAM account with access grants for projects in healthstat.be

When you as Access Manager have chosen to create the EAM accounts as awaiting approval, you need to complete the action with the step described in the following.

Go to the EAM menu as usual.

Select EAM Accounts and then Approval.

When clicking on Approval you open the page with the EAM accounts that are waiting to be approved:

There are two ways to approve these account requests:

  • By checking the selection box of the relevant account request and selecting the Approve action. Click on the Apply to selected item button to perform the action.
  • By clicking on the Edit button in the Operations column for the relevant account ...

... and subsequently on the Approve button in the Account: Manage grants screen.

The Account state changes to Approved.

After this, a fulfilment process will start to run in the background, finally resulting in an account state change to Published.

Performing a push action

If this change does not take place within a reasonable amount of time - usually between 15 minutes and up to three hours - the account could be updated by means of a "push".

Therefore, return to the accounts overview screen.

First, check the Approved account that needs to be pushed (1). Then, open the Action drop-down menu and select the Update account (push) option (2). Finally, validate this action by clicking on the Apply to selected items button (3).

In case the push action does not trigger the expected result, you need to contact our Support service.

Bart.Servaes Tue, 06/25/2024 - 07:57

Glossary of EAM concepts

Glossary of EAM concepts

Underpinning the new HD Entity Access Management system, short "EAM", is an architecture purpose-built to give the control of users back into the hands of Access Managers, ensuring an end-to-end management of the lifecycle of a user in the system.

The EAM architecture

The new architecture and its underlying processes bring along some new concepts. We have listed them for you below, supplemented with familiar concepts.

Access Manager

An Access Manager is an Authenticated User having additional Access Manager rights within the EAM system. These rights are granted by healthdata.be to the first Access Manager of a certain Organization. Any additional access managers are to be appointed by the Organization and rights are to be granted by the existing Access Manager of that Organization.

An Access Manager validates and manages user accounts within the Entity Access Management system, approves and manages the accesses of these EAM users to different applications for any available projects, and has the power to create EAM users and EAM accounts by means of csv bulk upload.

Indication of roles - the standard Authenticated User role is not explicitly mentioned

Account (EAM account)

An account in EAM is a combination of an e-mail address and a provision completed with a set of rights (access grants) giving access to a certain registry. An account thus links EAM user to the desired registry within an application.

A user can have more than one account, each with a different e-mail address, e.g. when working in different healthcare organizations (HCOs), and each with another provision.

Account state

The below overview shows the different states of an EAM account throughout the workflow.

The Label column mentions the name of the action button available for the Authenticated User and/or Access Manager in the relevant GUI screens. (Only Create New Draft and Request approval actions are available for an Authenticated User.)

Admin

The Admin or administrator is part of the healthdata.be staff and has all permissions and functionalities within the EAM system. This user type should be used sparingly and only for highly technical or emergency purposes.

Authenticated User

An Authenticated User is a person who is logged in to the HD EAM system via itsme or eID and has a user profile based on First name, Last name and NISS code shared when logging in via the Federal Authentication Service (FAS). An Authenticated User is able to access the EAM application, create accounts and request access grants for projects in applications such as HD4DP2 and healthstat.be. He or she also has access to the own account information in case changes are necessary.

Author group

An Author Group is a group of users with equal editing and reviewing rights to a registration in a certain application of the organisation. The Author Group creation is based on First_name Last_name of the user requesting access. It is thereafter managed in the HD Entity Access Management (EAM) system.

For the HD4DP2 application the Author Group field is automatically populated for user roles 1 (Study Lead) and 2 (Study Associate). The Author Group for role 3 (Study Support) needs to be selected from the relevant drop-down list.

FAS

The Federal Authentication Service (FAS) is a system that authenticates individuals to grant them access to secure online government applications. It ensures the genuineness of users before allowing them to use protected government services in Belgium.

Grants (Access grants)

Grants define a user's access to a registry in an certain application with a specific role. They are added to a provisioned EAM account and need to be approved by the Access Manager of the relevant organization. E.g.:

Pip Lup has access to HDBP0025 in HD4DP2 as Local Study Support with Author Group ACC group

Legacy requests

The Legacy requests tab retrieves the information shown under the "Requests overview" within the previous EAM version (2.7). The purpose of this overview is to follow-up on pending requests after migration to EAM 3.0.

Legacy requests in EAM
Requests overview in former EAM 2.7

Manager (HD Manager)

The Manager is a user type in EAM performed by healthdata.be Service Desk staff. Compared to an Access Manager the manager profile has more extensive rights for advanced actions, without the emergency functionalities of an Administrator.

Messages (log)

Messages are created whenever actions are performed on EAM account level, e.g. password reset, request of account approval, approving of grants etc. A message is the representation of something we send to or receive from Service bus. The messages will be logged within EAM for history purposes.

Organization

In full: Healthcare Organization (HCO). A list of all organizations including Name, NIHDI number and the respective list of Access Managers is managed by the HD Manager. An organization that is not active anymore, will receive the status Disabled, without being deleted from the EAM system.

Provision

The provision is the deployment of a certain Application to a certain Organization along with any specific parameters providing extra information on the deployment.

Service Bus

Is a communication layer between our EAM portal and the installations at the DP's side. Whereas the former EAM system mainly managed access requests, it now focusses on complete User management incl. access requests, account creating, feedback loop ... aiming at faster user onboarding, a better user experience and less manual intervention by Support / DevOps.

User (EAM user)

The user is the main entity within the EAM system. Once the user's profile, containing basic information such as Username, Primary e-mail address, First name, Last name, SSIN and professional NIHDI code, has been validated, the user has access to EAM, ready to interact. EAM offers the possibility to add more than one NIHDI code. Each user can be linked to more than one Account.

User matrix

In general, a user matrix is a structured way to organize information about users and their action radius. We have used the user matrix as a starting point of our documentation of the new Entity Access Management system: a cross-table of the different functionalities of the user types Authenticated User and Access Manager. From here, you can reach the exact information.

User roles

User roles determine your access rights in HD applications such as HD4DP2 or healthstat.be for the desired project. The role hierarchy do not necessarily correspond to the staff structure within your organization. More on User roles in HD4DP2 can be found here. The user roles in healhtstat.be are documented here.

User types

User types determine the level of managing rights you have within the EAM system:

  • Authenticated user
  • Validated user (see below)
  • Access manager
  • (HD) Manager
  • Administrator

Different from User roles which are typical for HD applications.

Validated user

User type. After migration of your healthcare organisation to the current EAM system, the Access Manager might notice the user type of Validated user in the Role(s) column on the EAM Users overview page.

The label "Validated user" is a remnant of EAM version 2.7 where it meant to indicate that a user's profile had been completed and validated by the Access Manager. This migrated user type corresponds to the Authenticated user type in the current EAM system. As such, "Validated user" is not an active role in the current system, nor does it influence the functionality thereof.

Bart.Servaes Fri, 06/21/2024 - 17:11

Additional actions

Additional actions

Now that all General Practitioners and their EAM accounts with access grants to a project in healthstat.be have been approved, the Access Manager can follow-up on the management of EAM Users and EAM Accounts by means of functionalities that are available when necessary.

These actions start from the Entity Access Management homepage:

On the following pages you will find the most common additional actions:

Bart.Servaes Tue, 06/25/2024 - 08:02

Disabling an EAM account

Disabling an EAM account

Disabling an EAM account

Click on Manage on the top left of the screen in order to reveal the EAM menu. Select EAM Accounts.

Scroll down the displayed list of accounts and tick the selection box of the account(s) you want to disable. Go to the bottom of the page and click on the Action toggle button to select Disable account. Then, click on the Apply to selected items button.

Confirm with the Execute action button

This action triggers an email notification for the Authenticated User to inform about the account being disabled. The user is no longer able to login with the credentials at hand, and needs to contact the Access Manager to have the account enabled again.

Bart.Servaes Tue, 06/25/2024 - 08:02

Enabling an EAM account

Enabling an EAM account

Enabling an EAM account

Click on Manage on the top left of the screen in order to reveal the EAM menu. Select EAM Accounts.

Scroll down the displayed list of accounts and tick the selection box of the account(s) you want to enable. Go to the bottom of the page and click on the Action toggle button to select Enable Account.

To complete the action, you need to click on the Execute action button.

This action triggers an email being submitted to the Authenticated User with new credentials. All previously approved accesses will be restored.

Bart.Servaes Fri, 06/21/2024 - 17:32

Viewing all General Practitioners and their EAM accounts with grants

Viewing all General Practitioners and their EAM accounts with grants

Viewing all users within the organization HDGP3333 for healthstat.be using the EAM interface?

Click on Manage to the top left of the screen, so that EAM appears. When hovering over this menu item, the subitems EAM Users and EAM Accounts become visible. Select EAM Accounts.

The page shown gives an overview of all accounts of all users within the organization(s) for the different applications, including the grants.

Filtering accounts for healthstat.be

Use "CTRL+F" and enter "Healthstat" in order to find the accounts for projects in the application healthstat.be.

Bart.Servaes Tue, 06/25/2024 - 08:11

Support service of healthdata.be

Support service of healthdata.be

The Service Desk of healthdata.be (Sciensano) helps users of our applications and services and deals with requests and incidents.

The Service Desk focuses on those services run by our IT Services (HD4DP, HD4RES, healthstat.be,...) and helps you with accounts and passwords. For questions about the content and objective(s) of the projects, we kindly refer users to the managing research organizations.

For most efficient processing of your request, we advise you to use our service portal: Jira Service management (JSM) portal.

Please find below our support window hours:

Bart.Servaes Tue, 12/02/2025 - 13:55

Create a Support ticket

Create a Support ticket

The healthdata.be service (Sciensano) processes each incident report according to a Standard Operating Procedure (SOP). A public version of this SOP "HD Incident Management Process" is also available on this portal docs.healthdata.be.

To submit an incident related to registries and applications in production and facilitated or managed by Sciensano's healthdata.be service, you must first log into the HD Service and Support portal: Jira Service Management (JSM) portal.

More info concerning how to request an account is available here.

After the login step, you will arrive at the main page of the portal

To create a ticket click on "Create a Support ticket"' on the main page.

This image has an empty alt attribute

You will see the page below. Once you have filled in all the mandatory fields, click on "Send".

This image has an empty alt attribute
Bart.Servaes Tue, 12/02/2025 - 13:55

Suggest improvement

Suggest improvement

To suggest improvement about the healthdata.be platform, you first need to log in to the HD Service and Support portal: Jira Service Management (JSM) portal.

More info concerning how to request an account is available here.

After the login step, you will arrive at the main page of the portal.

If you have questions, remarks or if you would like to submit a complaint, you can do so by clicking on the "Suggest improvement" button on the main page of the Jira Service Management portal.

This image has an empty alt attribute

On this page you need to fill in all the mandatory fields and click on "Send".

This image has an empty alt attribute
Bart.Servaes Tue, 12/02/2025 - 13:55

Email security policy

Email security policy

WHAT IS THE PROBLEM?

Sciensano blocks e-mails from organizations if the configuration of their e-mail and/or DNS services allow potential abuse by spammers/attackers. More specifically, if the configuration enables other senders to impersonate your organization by allowing them to mimic your organization’s e-mail “Header From”.

In other words, they can send phishing and spam mails that cannot be distinguished from genuine mails from your organization.

If you’re responsible for managing your ICT infrastructure, keep reading. If not, pass this message on to your ICT department or to the ICT service that’s managing your ICT infrastructure.

HOW TO SOLVE IT?

You’ll have to verify that your configuration complies with “Sender Alignment” security requirements.
More specifically, your mail services and DNS will have to be configured according to ICT standards.

These configurations are common, well-documented and supported by hosting companies. Some useful links:

We’ve noticed that this issue frequently occurs in organizations which moved their ICT infrastructure to cloud services such as Microsoft (O365), Amazon, Google, and MS Azure without properly configuring the ICT infrastructure which is not managed by these providers.

The configurations and recommendations need to be implemented on the customer’s ICT infrastructure, either internally or externally. DNS and Mail services are the main ICT platforms for these actions.

THE USE OF DIFFERENT DOMAINS IN THE MAIL SENDING PROCESS

E-mails contain an “Envelope From” and a “Header From”. Both need to match to avoid that the mail is blocked.

Some examples:

  1. A public service is using its new domain name in the “Header From” and its old domain name in the “Envelope From”.
  • Envelope From = noreply@publicservice.fgov.be
  • Header From = noreply@publicservice.belgium.be

➔ These e-mails will be blocked.

Remark: Because it’s a noreply address, the sender will not even be aware of us rejecting the e-mail …

2. An organization is using a cloud service (Freshservice) for its helpdesk tool and the “Envelope From” has not been customised.

• EnvelopeFrom = bounces+us.3.52773-helpdesk=organisation.be@emailus.freshservice.com
• Header From = helpdesk@organisation.be

➔ These e-mails will be blocked.

3. A company uses a cloud service (Amazon SES) to send the delivery notification and the “Envelope From” has not been customized.

  • Envelope From = 01020188573f374-96de6437-9134-45f4-8aa6-3e9ac18d5848-000000@euwest-1.amazonses.com
  • Header From = noreply@company.be

➔ These e-mails will be blocked.

Bart.Servaes Tue, 12/02/2025 - 13:55