Integrated Computerized Network General Practices
Integrated Computerized Network General PracticesWelkom op de pagina's met technische documentatie over het project "Integrated Computerized Network General Practices (INTEGO)", aangeboden door de dienst healthdata.be (Sciensano).
Deze pagina's geven informatie over de technische processen van het project. De volgende onderdelen (zullen) worden verstrekt:
- Algemene informatie over het project
- De datacollectie
Voor wetenschappelijke informatie over het project kunt u contact opnemen met de primaire organisatie die toezicht houdt op de uitvoering van het project (zie hoofdstuk "Algemene informatie over het project").
Deze documentatie wordt regelmatig bijgewerkt. We proberen de informatie zo correct, volledig en zo duidelijk mogelijk weer te geven. Als u desondanks iets in de documentatie ziet dat niet correct is, niet overeenkomt met uw ervaring, of verdere verduidelijking vereist, maak dan een support ticket via ons portaal (https://healthdatabe.atlassian.net/servicedesk/customer/portals) of stuur ons een e-mail via support.healthdata@sciensano.be om dit documentatieprobleem te melden. Vergeet niet de URL of het webadres van de pagina met het documentatieprobleem te vermelden. Wij zullen de documentatie dan aanpassen. Bedankt!General INTEGO project information
General INTEGO project informationProject name
Integrated Computerized Network General Practices
Project abbreviation
INTEGO
Project code
HDBP0147
Primary organization that oversees implementation of project
- Academisch Centrum Huisartsgeneeskunde (KU Leuven)
Partner organization participating in project
- Not available
Organization that commissioned this project
- Zorg en Gezondheid (ZG)
Organization providing monetary or material support
- Zorg en Gezondheid (ZG)
Brief project description
"Intego" stands for “integrated computerized network”. In 1990, the project started at the Department of General Practice of the KULeuven. The intention was to develop a large database on morbidity in primary care, to provide information on incidence and prevalence of diseases in Flanders, but also on diagnostic tests and treatments in general practice. The collection of data had to be done semi-automatically by which the data from the electronic medical records were copied and imported into a database. For this purpose a partnership was set up with the software firm Datasoft (later the company OmegaSoft Medical from the group Omega Pharma Company and then separated from this group under the name Corilus as part of Arseus), producer of medical software Medidoc. Intego has built a database that contains about 3 million diagnoses, 27 million laboratory results and 12 million prescriptions for medication. Our data are collected in general practices in Flanders.
The INTEGO data collection
The INTEGO data collectionOrganizations and/or individuals that provide data
Network of general practitioners
Start date of the data collection
Not available
End date of the data collection
Ongoing
Periodicity of the data collection
Continuous
The INTEGO Data Collection Definition (HDBP0147)
The INTEGO Data Collection Definition (HDBP0147)In the file below you can find the Data Collection Definition (DCD) specifications of the project "Integrated Computerized Network General Practices (INTEGO)”. It is a detailed description of the content of one DCD.
The INTEGO dataflow description
The INTEGO dataflow description
General practitioners participating to INTEGO utilize the electronic medical record system provided by CareConnect. Data collection is conducted via CSV extracts from the CareConnect cloud database, transferred to the Sciensano healthdata.be platform. Importantly, data is only exported from the CareConnect cloud for physicians enrolled in INTEGO and for patients who have not expressed objections to data sharing. The communication of personal data by CareConnect to the healthdata.be platform is divided into two separate streams: (1) the patient identifier, and (2) the registry variables.
The patient identification code (NISS), along with a technical registration code generated by CareConnect, is transmitted through the TTP (Trusted Third Party) service of the eHealth platform. In this process, the technical registration code is encrypted by the sender, while the patient identifier remains unencrypted. Consequently, the TTP service of the eHealth platform pseudonymizes only the patient identifier.
The registry variables, accompanied by the same technical registration code used for the patient identifier, are transmitted separately via a direct, encrypted web service to the healthdata.be platform. Upon receipt, the healthdata.be platform decrypts both communications and consolidates the data based on the technical registration code. After successful consolidation and technical quality control, the technical registration code is immediately and permanently deleted from the healthdata.be platform. The healthdata.be platform maintains a log of all technical processes to ensure transparency and security.
Data validation, preservation, and analysis: Using the supplied data, researchers carry out their work, which includes conducting research and preparing reports for public and targeted audiences. Researchers only have access to the data specific to their assigned register (INTEGO).
Through the healthstat.be platform, scientific reports, diagrams, and figures from the INTEGO register are made accessible to the public at an aggregated level. This is achieved via a secure web application.
Healthstat
HealthstatThe healthstat.be application of healthdata.be is a data reporting platform based on SAS Visual Analytics and integrated in the Drupal CMS (Content Management System). With the healthstat.be application , researchers of data driven projects facilitated by healthdata.be, can publish tables, figures and maps they made based on the data they have collected among Belgian hospitals, laboratories, physicians, and patients. With these reports, researchers want to give health professionals, healthcare institutions, patients, governments and the general public an up-to-date insight into the prevalence of certain diseases, their causes and impact, and the effectiveness of their treatment
Request access to Healthstat for a specific register
Request access to Healthstat for a specific registerHealthdata.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 relevant user documentation can be found here.
User roles within Healthstat
User roles within HealthstatEach 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.
Access to Healthstat
Access to HealthstatGeneral login condition
The below described procedure to log in with eID or Itsme is reserved for Belgian nationals and foreigners with a residence title for Belgium. Latter users need to ensure that they have a NISS number available, because it is essential to set-up the Itsme application succesfully.
Login procedure
To access the healthstat.be portal, you need to navigate to https://www.healthstat.be. The landing page of the application is displayed.
Click on the user symbol at the top right of the screen, next to the flag symbol (Language selection) and the dots symbol (Support functions). Then click on Log in the pop-up text field.
The Sign in to your account screen appears.
Select the Belgium eID / Itsme option to continue the login procedure for healthstat.be.
You will be redirected to the government's Federal Authentication Service (FAS), where you can log in with multiple digital keys with eID or digital identity.
If you choose to connect via itsme, you will need to enter your cell phone number.
Follow the instructions on your mobile device via the itsme application.
Once you have completed the login procedure you will be redirected to the landing page of healthstat.be.
Select PROJECTS in the left navigation menu in order to display the data collections which you have access to. Select the data collection of your choice (blue arrow).
The relevant data collection is displayed. Select a report under Report title.
In order to consult the report and to select report criteria, you need to repeat the authentication procedure.
Consulting reports
Consulting reportsOn the left side of the screen you will notice different reports. All different reports (or folders containing reports) are available to be consulted.
The small lock icon indicates that this is a private reports to which only a limited number of people have access to these. After selecting one of the reports, it could be possible that you are presented with a parameters page. This page will allow the report to be generated with the parameters you request.
Please select a value for all the required parameters.
If all the parameters are correctly entered a report will be generated and it's directed to a page containing the output. Depending on the type of report, it could be a graph or a table.
Secured process environment (SPE)
Secured process environment (SPE) Adelaide.DAmore do, 04/03/2025 - 09:50Request access to SPE for a specific register
Request access to SPE for a specific register Adelaide.DAmore do, 04/03/2025 - 09:50User roles within SPE
User roles within SPE Adelaide.DAmore do, 04/03/2025 - 09:50Access to SPE
Access to SPE Adelaide.DAmore do, 04/03/2025 - 09:50Import and export of files
Import and export of files Adelaide.DAmore do, 04/03/2025 - 09:50Support 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).
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).
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).
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".
E-mailveiligheidsbeleid
E-mailveiligheidsbeleidWAT IS HET PROBLEEM?
We blokkeren e-mails van uw organisatie omdat de configuratie van uw e-mail- en/of DNS-diensten mogelijk misbruik door spammers / hackers mogelijk maakt. Meer in het bijzonder stelt uw huidige configuratie andere afzenders in staat om zich als uw organisatie voor te doen door hen toe te staan de "Header From" van de e-mail van uw organisatie na te bootsen.
Met andere woorden, ze kunnen phishing- en spamberichten versturen die niet te onderscheiden zijn van echte e-mails van uw organisatie.
Als u verantwoordelijk bent voor het beheer van uw ICT-infrastructuur, lees dan verder. Als u niet de verantwoordelijke bent, geef dit bericht dan door aan uw ICT-afdeling of aan de ICT-dienst die uw ICT-infrastructuur beheert.
HOE LOST U DIT OP?
U dient te controleren of uw configuratie voldoet aan de beveiligingseisen voor “Sender Alignment”. Meer specifiek moeten uw maildiensten en DNS geconfigureerd worden volgens ICT-standaarden.
Deze configuraties zijn gangbaar, goed gedocumenteerd en worden ondersteund door hostingbedrijven:
- 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 hebben gemerkt dat dit probleem vaak voorkomt bij organisaties die hun ICT-infrastructuur hebben verplaatst naar Cloud services zoals Microsoft (O365), Amazon, Google en MS Azure zonder de ICT-infrastructuur goed te configureren. (Die wordt immers niet beheerd door deze providers).
De configuraties en aanbevelingen moeten worden geïmplementeerd op de ICT-infrastructuur van de klant, ongeacht of die intern of extern is. DNS en Mailservices zijn de belangrijkste ICT-platformen voor deze acties.
HET GEBRUIK VAN VERSCHILLENDE DOMEINEN BIJ HET VERZENDEN VAN E-MAILS
E-mails bevatten een "Envelope From" en een "Header From". Beide moeten overeenkomen om te voorkomen dat de e-mail wordt geblokkeerd.
Enkele voorbeelden:
- Een openbare dienst gebruikt zijn nieuwe domeinnaam in de “Header From” en zijn oude domeinnaam in de “Envelope From”.
- Envelope From = noreply@publicservice.fgov.be
- Header From = noreply@publicservice.belgium.be
➔ Deze e-mails worden geblokkeerd.
Remark: Omdat het een noreply adres is, zal de afzender niet eens merken dat de e-mail geweigerd wordt …
2. Een organisatie gebruikt een Cloud-service (Freshservice) voor haar helpdesktool en de “Envelope From” is niet aangepast.
• EnvelopeFrom = bounces+us.3.52773-helpdesk=organisation.be@emailus.freshservice.com
• Header From = helpdesk@organisation.be
➔ Deze e-mails worden geblokkeerd.
3. Een bedrijf gebruikt een Cloud service (Amazon SES) om de leveringsmelding te versturen en de “Envelope From” is niet aangepast.
- Envelope From = 01020188573f374-96de6437-9134-45f4-8aa6-3e9ac18d5848-000000@euwest-1.amazonses.com
- Header From = noreply@company.be
➔ Deze e-mails worden geblokkeerd.