Collecting psychosocial data from patient-rated questionnaire for improvement of quality of care among youth with diabetes
Collecting psychosocial data from patient-rated questionnaire for improvement of quality of care among youth with diabetesWelcome at the technical documentation pages for the project "Collecting psychosocial data from patient-rated questionnaire for improvement of quality of care among youth with diabetes (IQECAD SDQ)", 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").
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!
General IQECAD SDQ project information
General IQECAD SDQ project informationProject name
Collecting psychosocial data from patient-rated questionnaire for improvement of quality of care among youth with diabetes
Project abbreviation
IQECAD SDQ
Project code
HDBP0246
Primary organization that oversees implementation of project
- Sciensano
Partner organization participating in project
- Not available
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
Regulatory framework of this project
Consult the regulatory framework information published on the fair.healthdata.be pages.
The IQECAD SDQ data collection
The IQECAD SDQ data collectionOrganizations and/or individuals that provide data
Not available
Start date of the data collection
Not available
End date of the data collection
Ongoing
Periodicity of the data collection
Continuous
The IQECAD SDQ Data Collection Definition (HDBP0246)
The IQECAD SDQ Data Collection Definition (HDBP0246)...
Explanation of DCD specifications
The above Data Collection Definition (DCD) specifications are published in an MS Excel file using a slightly modified XLSForm format. XLSForm is a form standard created to simplify the creation of forms. The creation is done in a human readable format. XLSForms are a convenient standard for sharing and collaborating on form creation. For a detailed guide to the XLSForm standard, we refer you to https://xlsform.org/en/.
Each DCD Excel workbook has three worksheets: "settings", "survey" and "choices". Sometimes a project is composed of several DCDs. In this case, a "survey" worksheet is created for each DCD. The lists of values for all DCDs are listed in a single "choice" worksheet.
While not all survey and choice characteristics are used by healthdata.be to describe the data collection definitions, all standard XLSForm columns are present in the MS Excel file.
Note: healthdata.be itself does not use the XLSForm standard to create its DCD in its own applications (HD4DP, HD4Patient). The XLSForm standard (used by popular electronic data capture systems such as OpenClinica, LibreClinica, ODK,…) is chosen to describe the DCD only because it is a human readable format.
The "Survey" worksheet
This worksheet gives the general structure of the DCD and contains most of the content. It contains the complete list of variables and information on how they should appear in the form. Each row usually represents one variable.
The following columns are primarily used in the survey worksheet to describe DCD:
- type: Defines the type of question/variable
- name: Unique ID (name) of the question / variable
- label::[English]: Question / variable in English, appears on the screen
- label::[French]: Question / variable in French, appears on the screen
- label::[Dutch]: Question / variable in Dutch, appears on the screen
- label::[German]: Question / variable in German, appears on the screen
- hint::[English]: Hint or explanatory text for a question, in English
- hint::[French]: Hint or explanatory text for a question, in French
- hint::[Dutch]: Hint or explanatory text for a question, in Dutch
- hint::[German]: Hint or explanatory text for a question, in German
- constraint_javascript: Constraint on the allowed values for a response defined in javascript
- constraint_message::[English]: The message displayed to the user if the answer is not valid, in English
- constraint_message::[French]: The message displayed to the user if the answer is not valid, in French
- constraint_message::[Dutch]: The message displayed to the user if the answer is not valid, in Dutch
- constraint_message::[German]: The message displayed to the user if the answer is not valid, in German
- required: If a question or variable must be completed for the form to continue or be submitted
- relevant_javascript: Skip logic condition (the relevant condition that must be met for this question to be displayed)
- read_only: If a variable question/answer can be changed
- calculation
- repeat_count: Number of repetitions for a group of repetitions
- hidden: Hidden fields in the HD4DP application
The "Choices" worksheet
This worksheet is used to specify answer choices for multiple choice questions. Each row represents an answer choice. Answer choices with the same list name are considered part of a set of related choices and appear together for a question/variable. This also allows a choice set to be reused for multiple questions/variables (for example, yes/no questions).
The following columns are primarily used in the choices worksheet to describe the DCD:
- list_name: A unique name for each choice set
- name: ID (name or code) of the specific choice
- label::[English]: The choice label, in English, appears on the screen
- label::[French]: The choice label, in French, appears on the screen
- label::[Dutch]: The choice label, in Dutch, appears on the screen
- label::[German]: The choice label, in German, appears on the screen
The "Settings" worksheet
- form_title: Title displayed at beginning of form, in form list
- public_key: Key required for encrypted forms
- submission_url: Specific URL for uploading data
- default_language: If form uses multiple languages, this one sets which to use by default
- style: Separate questions groups into pages. Switch to a different theme.
- instance_name: Allows user to create a dynamic naming convention for each submitted instance
- status: status of the form: options are "final" and "draft"
- start_date: date start form in production
- end_date: date end form in production
Support Service of healthdata.be
Support Service of healthdata.be johanvanbussel dim 10/04/2022 - 19:29How to report an incident
How to report an incidentThe 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 projects 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: https://sciensano.service-now.com/sp.
After the login step, you will arrive at the main page of the portal.
On the main page, you must select "Get Help".
A new page with the title "Create an incident" will appear.
You can now document your incident or problem by providing the following information:
Please indicate the urgency of resolving your issue based on its criticality to the business.
Please indicate the type of problem you are experiencing.
When the problem type "Application" is selected, two additional fields appear: "Project Name" and "Application".
Please select the appropriate information.
Please describe clearly and briefly (1 sentence) the subject of your problem.
Please describe the problem in detail. The following aspects are important for us to understand and solve the problem:
- a description of the actions you want to perform but fail to perform (e.g. provide us with a field name, a validation rule, a button, etc.)
- a description (if possible) of the sequential steps you follow to use the service or the application of healthdata.be for which you need support;
- a brief description of the technical problem you are experiencing (e.g. error messages)
We strongly recommend that you add a screenshot describing the problem (IMPORTANT: do not provide us with patient data!).
You can add the screenshot by clicking on "Add attachments".
On the right side of the form, the mandatory information items of the incident form are listed. When these fields are completed, their names disappear from the "required information" box.
The form can only be submitted if all required fields are filled in, by pressing the green "Submit" button.
If all required fields have not been completed, a warning message will appear at the top of the form.
In addition, missing mandatory fields will be highlighted in green.
When the incident form has been successfully submitted, a preview of your submission appears in a new screen.
On the right side of the screen you will find the details, including the incident number.
On the left side of the screen, you will find a chronology of your incident processing, starting with your creation.
Submit a request for information about HD
Submit a request for information about HDTo request information about the healthdata.be platform, you first need to log in to the HD Service and Support portal: https://sciensano.service-now.com/sp.
Om informatie op te vragen over het healthdata.be platform, moet u eerst inloggen op het HD Service- en Supportportaal.
Politique de sécurité des e-mails
Politique de sécurité des e-mailsQUEL EST LE PROBLÈME ?
Nous bloquons les e-mails de votre organisation parce que la configuration de vos services de messagerie et/ou de DNS peut permettre aux spammeurs/pirates informatiques d'en abuser. Plus précisément, votre configuration actuelle permet à d'autres expéditeurs d'usurper l'identité de votre organisation en leur permettant d'imiter le « Header From» de l'e-mail de votre organisation.
En d'autres termes, ils peuvent envoyer des messages de phishing et de spam qu'il est impossible de distinguer des e-mails authentiques de votre organisation.
Si vous êtes responsable de la gestion de votre infrastructure TIC, lisez ce qui suit. Sinon, transmettez ce message à votre département TIC ou au service TIC qui gère votre infrastructure TIC.
COMMENT RÉSOUDRE LE PROBLÈME ?
Vous devez vérifier que votre configuration répond aux exigences de sécurité du « Sender Alignment ». Plus précisément, vos services de messagerie et votre DNS doivent être configurés conformément aux normes TIC.
Ces configurations sont courantes, bien documentées et prises en charge par les hébergeurs :
- 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/
Nous avons constaté que ce problème est fréquent dans les organisations qui ont déplacé leur infrastructure TIC vers des services en Cloud tels que Microsoft (O365), Amazon, Google et MS Azure sans configurer correctement l'infrastructure TIC (qui n'est pas gérée par ces fournisseurs).
Les configurations et les recommandations doivent être mises en œuvre sur l'infrastructure TIC du client, qu'elle soit interne ou externe. Les DNS et les services de messagerie sont les principales plateformes TIC pour ces actions.
L'UTILISATION DE DIFFÉRENTS DOMAINES LORS DE L'ENVOI D'E-MAILS
Les e-mails contiennent une « Envelope From » et un « Header From ». Les deux doivent correspondre pour éviter que l'e-mail ne soit bloqué.
Quelques exemples :
1. Un service public utilise son nouveau nom de domaine dans le « Header From » en son ancien nom de domaine dans l'« Envelope From ».
- Envelope From = noreply@publicservice.fgov.be
- Header From = noreply@publicservice.belgium.be
➔ Ces e-mails seront bloqués.
Remarque : Comme il s'agit d'une adresse « noreply », l'expéditeur ne remarquera même pas que l'e-mail est rejeté.
2. Une organisation utilise un service Cloud (Freshservice) pour son outil d'assistance et l'« Envelope From » n'a pas été modifié.
• Envelope From = bounces+us.3.52773-helpdesk=organisation.be@emailus.freshservice.com
• Header From = helpdesk@organisation.be
➔ Ces e-mails seront bloqués.
3. Une entreprise utilise un service Cloud (Amazon SES) pour envoyer la notification de l'envoi et « Envelope From » n'a pas été modifié.
- Envelope From = 01020188573f374-96de6437-9134-45f4-8aa6-3e9ac18d5848-000000@euwest-1.amazonses.com
- Header From = noreply@company.be
➔ Ces e-mails seront bloqués.