Care Trajectories: Chronic Kidney Disease
Care Trajectories: Chronic Kidney DiseaseWelcome at the technical documentation pages for the project "Care Trajectories: Chronic Kidney Disease (CT CKD)", provided by the service healthdata.be (Sciensano).
These pages provide information about the technical processes of the project. The following sections are (will be) provided:
- General project information
- The data collection
- The data transfer (documentation in progress)
- The data validation (documentation in progress)
- The data analysis (documentation in progress)
- The data reporting and visualisation (documentation in progress)
For scientific information of the project, please contact the primary organization that oversees implementation of project (see section "General project information").
General CT CKD project information
General CT CKD project informationProject name
Care Trajectories: Chronic Kidney Disease
Project abbreviation
CT CKD
Project code
HDBP0141
Primary organization that oversees implementation of project
- National Institute for Health and Disability Insurance (RIZIV-INAMI)
Partner organization participating in project
- Sciensano
Organization that commissioned this project
- National Institute for Health and Disability Insurance (RIZIV-INAMI)
Organization providing monetary or material support
- National Institute for Health and Disability Insurance (RIZIV-INAMI)
Brief project description
Not available
The CT CKD data collection
The CT CKD data collectionOrganizations and/or individuals that provide data
Not available
Start date of the data collection
Not available
End date of the data collection
Closed
Periodicity of the data collection
Continuous
The CT CKD Data Collection Definition (HDBP0141)
The CT CKD Data Collection Definition (HDBP0141)Data Collection Definition (DCD) specifications
Below you can find the weblink to the Data Collection Definition (DCD) specifications published in an MS Excel file:
Support service of healthdata.be
Support service of healthdata.beThe 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:
Create a Support ticket
Create a Support ticketThe 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.
You will see the page below. Once you have filled in all the mandatory fields, click on "Send".
Suggest improvement
Suggest improvementTo 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.
On this page you need to fill in all the mandatory fields and click on "Send".
Email security policy
Email security policyWHAT 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:
- https://dmarcian.com/alignment/
- https://mxtoolbox.com/dmarc/spf/spf-alignment
- https://o365info.com/how-does-sender-verification-work-how-we-identify-spoof-mail-the-fiveheros-spf-dkim-dmarc-exchange-and-exchange-online-protection-part-9-of-9/
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:
- 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.