User manual of the application HD4DP v2

In this manual we describe the following functions of the application HD4DP v2:

Adelaide.DAmore Tue, 06/06/2023 - 13:52

Request access to an HD application for a specific project

Healthdata.be applications such as HD4DP v2 and healthstat.be process sensitive personal information. Therefore, strictly controlled processes are used to grant access to these applications. The Entity Access Management (EAM) portal of healthdata.be facilitates these processes.

Make sure to use the current version of the EAM system. The user documentation can be found here.

This documentation is being updated regularly. We try to provide as correct, complete and clear as possible information on these pages. Nevertheless, if you see anything in the documentation that is not correct, does not match your experience or requires further clarification, please create a request (type : request for information) via our portal (https://sciensano.service-now.com/sp) or send us an e-mail via support.healthdata@sciensano.be to report this documentation issue. Please, do not forget to mention the URL or web address of the page with the documentation issue. We will then adjust the documentation as soon as possible. Thank you!

Adelaide.DAmore Wed, 04/24/2024 - 14:44

User roles in HD4DP v2

Each healthcare organisation has at least one Access Manager who is watching over the access rights to the applications of the own organisation and is managing them in the HD Entity Access Management (EAM) system. In this process, access requests by healthcare organisation employees are analysed and validated if legitimised. The scope of the accesses granted to HD4DP2 may differ, which is reflected in various user roles. Based on access rights, following three user roles can be distinguished:

Local Study Lead (author):

The Local Study Lead can:

edit and review all peer registrations (regardless of role) for the study or project;
make registrations in HD4DP v2

This role might be but should not be limited to the responsible for the study or project within the participating healthcare institution.

Local Study Associate (author):

The Local Study Associate can:

edit and review the own registrations, not those of other colleagues from the same healthcare organisation participating in the same study or project. The indicated registrations are limited to the patients treated by the Local Study Associate;
make registrations in HD4DP v2.

The Local Study Associate is a healthcare provider participating in the study or project. This is reflected in the registration form.

Local Study Support (co-author):

The Local Study Support can:

edit and review registrations belonging to the author group they are linked to;
make registrations in HD4DP v2.

A Local Study Associate and Local Study Lead can delegate registration tasks to a Local Study Support. This might be but should not be limited to an administrative assistant or staff from a medical coding department. The Local Study Associate and Local Study Lead are still considered the author of the registration; the Local Study Support is considered the co-author. The Local Study Associate and Local Study Lead can view and modify Local Study Support entries.

By default, only 1 Local Study Lead is intended by healthdata.be (Sciensano) for each project within each organisation. The idea is that only one person is meant to see all submissions for that project within that organisation. This policy prevents users of HD4DP v2 from seeing personal and sensitive information from individuals with whom they do not have a therapeutic relationship. For policy deviations on this, healthcare organisation staff should contact their Data Protection Officer (DPO).

Remarks:

The scope of the access rights does not necessarily reflect the hierarchy within your healthcare organisation.
It is up to the Access manager to change roles from/to Local Study Lead, Local Study Associate and Local Study Support. These requests are carried out in the EAM system.

Adelaide.DAmore Sun, 01/07/2024 - 12:50

Access the application HD4DP v2

To access the application HD4DP v2, you must first request an account. If you do not have an account yet, please consult "Request access to an HD application for a specific project" first.

Once your account has been created and the registry is put in production, you will receive an e-mail with the following information (Note that the text between the [ ] will be adapted):

Organization: [RIZIV number - Name]
Login: [email]
Password: [password]
Application URL: [url]

With these credentials you can access the application HD4DP v2 of your organization:

Go to the url mentioned in the email
Select "your organization" from the list
Your organization: [RIZIV number – Name]
Click on "Next"
Fill in your "username" and "password"
Click on "Log in"

Please be sure to log off after making use of the application HD4DP 2.0, or any other Healthdata.be application. Just closing your internet browser does not guarantee that your application with registrations has been closed.

Adelaide.DAmore Tue, 06/06/2023 - 13:58

Navigate to the HIV_VL project

Navigate to the HIV_VL project Adelaide.DAmore Wed, 06/21/2023 - 14:51

Create a HIV_VL registration

Create a HIV_VL registration Adelaide.DAmore Wed, 06/21/2023 - 14:51

Find a HIV_VL registration

Find a HIV_VL registration Adelaide.DAmore Wed, 06/21/2023 - 14:51

Update a HIV_VL registration

Update a HIV_VL registration Adelaide.DAmore Wed, 06/21/2023 - 14:51

Delete a HIV_VL registration

Delete a HIV_VL registration Adelaide.DAmore Wed, 06/21/2023 - 14:51

Submit a HIV_VL registration

Submit a HIV_VL registration Adelaide.DAmore Wed, 06/21/2023 - 14:51

Send a correction of a registration

To send a correction of a submitted registration you need to submit the complete record again. An overview of the submitted corrections is available via the HD4DP v2 generic correction form.

The Add corrections function (and button) to a registration form has been discontinued. It is not available anymore, neither via the overview table, nor via the preview page of a registration.

Submitting the complete record again

The preferred way to send a correction is to fill out the complete registration form with the correct values and resubmit it. When you do so, the most recent version of the record that is received by healthdata.be will be considered to be the correct one.

Whether a record qualifies or not is determined by a so-called business key. This is a unique set of values of specific fields per record, such as a combination of the patient ID and the hospitalization date, or the niss code and the sample ID. The business key is created when submitting the original record, and so helps to identify the most recent record received in the healthdata.be database in case of resubmission.

Attention: In case one of the fields that build the business key needs to be corrected, the record that will be resubmitted will have a different business key. Consequently, both records will be considered as correct ones, since there is no identical business key.
You may consider to log a RITM ticket via our Service portal (https://sciensano.service-now.com/sp) to follow-up on this particular case.

There are two options to resubmit a record:

Option 1: Submission via S2S API / CSV Upload

The correction of the values is performed directly in the json or csv file. To resubmit the complete record via the back-end, please refer to the applicable technical documentation pages. The examples shown in the links below are for Pacemaker Primo-Implantation:

For submitting the complete record as a .json file via S2S API, go here.
For submitting the complete record as a .csv file via CSV Upload, go here.

Option 2: Submission via the HD4DP 2.0 web application

First, you need to access the HD4DP v2 web application, navigate to the study program and select the desired study project in the left dark blue menu. Then, fill out the complete registration form again manually with the correct values. Resubmit the completed registration form.

The previously submitted record will become irrelevant based on the business key.

The generic correction form

The Correction Form you can find in the list of study programmes and study projects in the HD4DP v2 web application contains an overview of all submitted corrections of registrations.

If you want to preview these corrections of registrations, navigate to the study program Correction form and then to the study project Correction form. Finally, select the most recent version.

The corrections of registrations of the different projects will be displayed READ-ONLY in the overview table.

Adelaide.DAmore Tue, 01/02/2024 - 13:42

Registration statuses in HD4DP v2

This article explains the different registration statuses in HD4DP v2.

Statuses are shown in Status column

You can select the columns you want to display via the menu Select visible columns located in the top-right corner:

Select the columns you want to display and click on Apply.

Description of the statuses:

Open: Registration is created and stored. It has not been submitted

Deleted: Registration has been deleted.

Submitted: Registration has been submitted and sent.

Adelaide.DAmore Tue, 06/06/2023 - 14:01

Reset password for HD4DP v2

After having received your credentials to login to the HD4DP 2.0 application, you can consider to reset the password to one that is easier for you to remember.

Go to URL https://acc.kubes.healthdata.be/, select your organization and click on the Next button.

Fill in your e-mail address and the password you received. Click on the Log in button.

The main HD4DP 2.0 application screen appears. On the left you can see the menu of study programmes and study projects, on the right you have the section in which the relevant registrations will become available.

At the top right of the screen you notice the Reset password link. Click on it.

Reset the password you have received by filling in the password of your preference. Repeat the new password in the verification field and click on the Submit button.

You will be redirected to the main screen, and the password will be automatically reset in the background. You don't need to log in again now.

When logging back in for a next registration session you will have to use your new password.

Jonas.VanBussel Sun, 01/07/2024 - 15:32