{ "id": "i-am-connect", "url": "/fr/i-am-identity-access-management/", "md_url": "/fr/i-am-identity-access-management.md", "json_url": "/fr/i-am-identity-access-management.json", "claims_url": "/fr/i-am-identity-access-management/beweringen/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "schema_type": "Service", "lang": "fr", "translation": { "lang": "fr", "source_url": "/i-am-connect/", "date": "2026-11-03", "stale": false, "fields": [ "bewering:CLM-0208ef96", "bewering:CLM-0ed01ce5", "bewering:CLM-1001f865", "bewering:CLM-1ba5fb92", "bewering:CLM-1bc4601f", "bewering:CLM-1e4fad67", "bewering:CLM-1f1c9fde", "bewering:CLM-29e794ae", "bewering:CLM-2d703e64", "bewering:CLM-343bfceb", "bewering:CLM-35abe524", "bewering:CLM-39af4293", "bewering:CLM-3f8edeaf", "bewering:CLM-48ff1c55", "bewering:CLM-4b8e9309", "bewering:CLM-4bb9e907", "bewering:CLM-589ff844", "bewering:CLM-5b389c3b", "bewering:CLM-5e03d5ff", "bewering:CLM-5f3eeead", "bewering:CLM-66bb1f47", "bewering:CLM-6abf95a5", "bewering:CLM-6ae3796a", "bewering:CLM-79851bad", "bewering:CLM-7c0c3785", "bewering:CLM-7cb73384", "bewering:CLM-7cdc7fdf", "bewering:CLM-7e0e1964", "bewering:CLM-86f257af", "bewering:CLM-8a750437", "bewering:CLM-8c432cbb", "bewering:CLM-94bf1882", "bewering:CLM-9a00446a", "bewering:CLM-a555b445", "bewering:CLM-aeed1d32", "bewering:CLM-bbad888e", "bewering:CLM-d0015248", "bewering:CLM-d9f27bf8", "bewering:CLM-e471550d", "bewering:CLM-e72751b5", "bewering:CLM-e959b23e", "bewering:CLM-ed611fb8", "bewering:CLM-f07c7dfe", "bewering:CLM-f1e829b3", "bewering:CLM-f3bce076", "bewering:CLM-f9493a5a", "lifecycle_note", "sectie:onzekerheden-en-tegenstrijdige-informatie", "sectie:waar-staat-het-en-wie-gebruikt-het", "sectie:wat-betekent-het-voor-een-ziekenhuis", "sectie:wat-is-het", "sectie:welke-diensten", "summary", "title" ] }, "title": "I.AM et I.AM Connect (Identity & Access Management)", "aliases": [ "I.AM", "I.AM Connect", "I.AM IDP", "I.AM STS", "I.AM AA", "Attribute Authority", "Secure Token Service", "geïntegreerd gebruikers- en toegangsbeheer" ], "names": { "nl": "I.AM (Identity & Access Management)", "fr": "I.AM (Identity & Access Management)", "en": "I.AM (Identity & Access Management)", "de": null }, "jurisdiction": [ { "code": "belgie", "label": "Belgique (fédéral/interfédéral)" } ], "themes": [ { "code": "identiteit-en-toegang", "label": "Identité, accès et audit" }, { "code": "architectuur-en-infrastructuur", "label": "Architecture et infrastructure" } ], "lifecycle": { "code": "productie", "label": "en production" }, "lifecycle_note_html": "Service de base en production ; renouvellement des clés en juillet-août 2026 (avec erratum du 07/07/2026). Un nouveau certificat TLS pour *.ehealth.fgov.be est annoncé en production à partir du 13/10/2026.", "version": null, "vendor": null, "sectors": [], "homologations": [], "links": [ { "kind": { "code": "website", "label": "Site web" }, "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-i.am-identity-access-management", "label": "I.AM (eHealth-platform)", "host": "www.ehealth.fgov.be", "lang": "nl" } ], "summary_text": "I.AM est le service de base par lequel les applications eHealth identifient, authentifient et autorisent les acteurs de soins et les systèmes. La famille utilise l'IDP pour les applications web classiques, le STS pour les services web SOAP, I.AM Connect pour le REST et les applications mobiles, et l'Attribute Authority pour les attributs provenant de sources authentiques. Le service est en production et prend en charge notamment Vitalink FHIR, eHealthBox REST et certains clients UHMEP. Pour les hôpitaux, le composant choisi détermine les certificats, les jetons, l'enregistrement de client et les renouvellements de clés dont une interface a besoin.", "summary_html": "

I.AM est le service de base par lequel les applications eHealth identifient, authentifient et autorisent les acteurs de soins et les systèmes. La famille utilise l'IDP pour les applications web classiques, le STS pour les services web SOAP, I.AM Connect pour le REST et les applications mobiles, et l'Attribute Authority pour les attributs provenant de sources authentiques. Le service est en production et prend en charge notamment Vitalink FHIR, eHealthBox REST et certains clients UHMEP. Pour les hôpitaux, le composant choisi détermine les certificats, les jetons, l'enregistrement de client et les renouvellements de clés dont une interface a besoin.

", "last_verified": "2026-10-08", "verification_outdated": false, "sections": [ { "id": "qu-est-ce-que-c-est", "title": "Qu'est-ce que c'est ?", "kind": "tekst", "html": "

I.AM (Identity & Access Management) est le service eHealth intégré d'identification, d'authentification et d'autorisation des acteurs de soins qui demandent l'accès à des services de la Plate-forme eHealth et de ses partenaires[1]. Il intègre la gestion des accès, des utilisateurs et de l'accès aux données, et distingue quatre contextes techniques : applications web, services web SOAP, services web REST et accès aux données (Data Access)[1]. L'utilisateur choisit un profil sur la base de sa qualité telle qu'elle est consignée dans CoBRHA[2].

" }, { "id": "quels-services", "title": "Quels services ?", "kind": "tekst", "html": "

I.AM fait en sorte que chaque application qui appelle des services eHealth ou des services partenaires établisse d'une manière commune qui est l'utilisateur ou le système et en quelle qualité il agit[1][2]. Le certificat identifie le système (logiciel/organisation), l'eID ou un jeton identifie l'utilisateur individuel[3].

\n

Pour les applications web, la spécification IDP (version 1.4, 14/10/2025) distingue trois niveaux de sécurité : itsme, eID et MyGov sont de niveau High, TOTP Substantial et nom d'utilisateur/mot de passe Low[4]. L'IDP s'appuie sur le service d'authentification fédéral BOSA FAS[4] ; en production, la plupart des applications redirigent automatiquement l'utilisateur vers le FAS[4]. La spécification annonce que le « Belgian citizen token » (carte comportant 24 codes personnels) disparaîtra prochainement des méthodes d'authentification (spécification du 14/10/2025 ; le moment effectif n'a pas été trouvé)[4]. Après l'authentification, I.AM applique les règles d'accès de l'application[5].

" }, { "id": "ou-en-est-il-et-qui-l-utilise", "title": "Où en est-il et qui l'utilise ?", "kind": "tekst", "html": "

Statut : production, comme service de base de la plate-forme eHealth[2]. Les composants :

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ServiceQuoiPour quiPage
I.AM IDPaccès SAML pour les applications web classiques côté serveur[1]Gestionnaires d'applications webcette page
I.AM STSjeton SAML pour les services web SOAP après authentification par certificat ou eID[6]Intégrateurs de logicielsCertificats eHealth et chiffrement (ETEE)
I.AM ConnectOpenID Connect et JWT pour les applications mobiles et REST[1][7]Applications et organisationscette page
I.AM AAConsultation de sources authentiques telles que CoBRHA et les mandats[1][2]Services partenairesCoBRHA
\n\n

Applications : l'environnement FHIR de Vitalink (en production depuis le 22/03/2024) utilise I.AM Connect[10], de même que Vaccinnet 2.0[11]. Selon le cookbook FHIR de Recip-e, l'API FHIR d'UHMEP exige, pour les clients du realm Healthcare, le flux IAM token exchange, de sorte que les providers techniques n'obtiennent pas de droits de pseudonymisation[12] (voir UHMEP et la prescription de renvoi électronique (eReferral)) ; pour les clients M2M, cela n'a pas été vérifié. Les variantes REST de l'eHealthBox et de l'Addressbook demandent un onboarding I.AM Connect distinct[13] (voir eHealthBox).

\n

Interfaces techniques

\n\n

État et feuille de route

\n" }, { "id": "qu-est-ce-que-cela-signifie-pour-un-hopital", "title": "Qu'est-ce que cela signifie pour un hôpital ?", "kind": "tekst", "html": "\n

Conditions de mise en œuvre et limites

\n

Voir Certificats eHealth et chiffrement (ETEE) pour les certificats et Connecteurs eHealth (eHealth platform services connectors) pour les bibliothèques qui gèrent l'authentification STS et le chiffrement. Dans l'environnement d'acceptation, outre un certificat d'acceptation, le connecteur est également nécessaire[22]. L'aperçu par service cible se trouve sur Intégration technique avec l'infrastructure eHealth.

" }, { "id": "incertitudes-et-informations-contradictoires", "title": "Incertitudes et informations contradictoires", "kind": "tekst", "html": "" } ], "relation_groups": [ { "type": "ownedBy", "direction": "uit", "label": "relève de", "relations": [ { "direction": "uit", "type": "ownedBy", "label": "relève de", "other": { "id": "ehealth-platform", "title": "Plate-forme eHealth", "url": "/fr/plate-forme-ehealth/" }, "status": "established", "status_label": "établi", "note_html": "I.AM is een basisdienst van het eHealth-platform.", "valid_from": null, "valid_to": null, "historical": false, "refs": [ 1, 2 ] } ] }, { "type": "dependsOn", "direction": "uit", "label": "dépend de", "relations": [ { "direction": "uit", "type": "dependsOn", "label": "dépend de", "other": { "id": "ehealth-certificaten", "title": "Certificats eHealth et chiffrement (ETEE)", "url": "/fr/certificats-ehealth/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 6 ] }, { "direction": "uit", "type": "dependsOn", "label": "dépend de", "other": { "id": "cobrha", "title": "CoBRHA", "url": "/fr/cobrha/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 1, 2 ] } ] }, { "type": "seeAlso", "direction": "uit", "label": "voir aussi", "relations": [ { "direction": "uit", "type": "seeAlso", "label": "voir aussi", "other": { "id": "therapeutische-relatie", "title": "Relation thérapeutique", "url": "/fr/relation-therapeutique/" }, "status": "established", "status_label": "établi", "note_html": "De ingebruikname van de eind 2025 herschreven TherLink-diensten via I.AM AA en Metahub was gepland op 2 december 2025; de effectieve ingebruikname is niet bevestigd.", "valid_from": null, "valid_to": null, "historical": false, "refs": [ 9 ] } ] }, { "type": "connectsTo", "direction": "uit", "label": "se connecte à", "relations": [ { "direction": "uit", "type": "connectsTo", "label": "se connecte à", "other": { "id": "recip-e", "title": "Recip-e (prescription électronique dans le secteur ambulatoire)", "url": "/fr/recip-e/" }, "status": "established", "status_label": "établi", "note_html": "Recip-e gebruikt I.AM-clients en was volgens een presentatie van 30 januari 2026 onderwerp van een geplande SAML-v2-migratie.", "valid_from": null, "valid_to": null, "historical": false, "refs": [ 21, 12 ] } ] }, { "type": "about", "direction": "in", "label": "porte sur (entrant)", "relations": [ { "direction": "in", "type": "about", "label": "porte sur (entrant)", "other": { "id": "authenticatie-in-de-zorg", "title": "Authentification dans les soins de santé", "url": "/fr/authentification-dans-les-soins-de-sante/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 4, 23, 24 ] }, { "direction": "in", "type": "about", "label": "porte sur (entrant)", "other": { "id": "ehealth-basisdiensten", "title": "Services de base de la plate-forme eHealth", "url": "/fr/services-de-base-de-la-plate-forme-ehealth/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 2 ] }, { "direction": "in", "type": "about", "label": "porte sur (entrant)", "other": { "id": "ehealth-diensten", "title": "Services et API de la plate-forme eHealth", "url": "/fr/services-et-api-de-la-plate-forme-ehealth/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 1 ] }, { "direction": "in", "type": "about", "label": "porte sur (entrant)", "other": { "id": "technische-integratie-ehealth", "title": "Intégration technique avec l'infrastructure eHealth", "url": "/fr/integration-technique-avec-l-infrastructure-ehealth/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 1 ] } ] }, { "type": "connectsTo", "direction": "in", "label": "se connecte à (entrant)", "relations": [ { "direction": "in", "type": "connectsTo", "label": "se connecte à (entrant)", "other": { "id": "csam-fas", "title": "Service fédéral d'authentification (FAS) au sein de CSAM", "url": "/fr/service-federal-d-authentification-fas-au-sein-de-csam/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 4, 24 ] } ] }, { "type": "dependsOn", "direction": "in", "label": "dépend de (entrant)", "relations": [ { "direction": "in", "type": "dependsOn", "label": "dépend de (entrant)", "other": { "id": "ehealth-addressbook", "title": "eHealth Addressbook", "url": "/fr/ehealth-addressbook/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 13 ] }, { "direction": "in", "type": "dependsOn", "label": "dépend de (entrant)", "other": { "id": "ehealth-connector", "title": "Connecteurs eHealth (eHealth platform services connectors)", "url": "/fr/connecteurs-ehealth/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 16 ] }, { "direction": "in", "type": "dependsOn", "label": "dépend de (entrant)", "other": { "id": "ehealth-pseudonimisering", "title": "Pseudonymisation et anonymisation (plate-forme eHealth)", "url": "/fr/pseudonymisation-et-anonymisation-plate-forme-ehealth/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 25 ] }, { "direction": "in", "type": "dependsOn", "label": "dépend de (entrant)", "other": { "id": "ehealthbox", "title": "eHealthBox", "url": "/fr/ehealthbox-boite-aux-lettres-electronique-securisee/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 13 ] }, { "direction": "in", "type": "dependsOn", "label": "dépend de (entrant)", "other": { "id": "implantatenregister", "title": "Registre central de traçabilité des implants (CTR) et SADMI", "url": "/fr/registre-central-de-tracabilite-implants/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 26 ] }, { "direction": "in", "type": "dependsOn", "label": "dépend de (entrant)", "other": { "id": "recip-e", "title": "Recip-e (prescription électronique dans le secteur ambulatoire)", "url": "/fr/recip-e/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 12 ] }, { "direction": "in", "type": "dependsOn", "label": "dépend de (entrant)", "other": { "id": "toegangsmatrix-dienst", "title": "Service matrice d'accès de la plate-forme eHealth (WS Matrix, PADAC)", "url": "/fr/service-matrice-d-acces-ws-matrix-padac/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 27 ] }, { "direction": "in", "type": "dependsOn", "label": "dépend de (entrant)", "other": { "id": "uhmep", "title": "UHMEP et la prescription de renvoi électronique (eReferral)", "url": "/fr/uhmep-prescription-de-renvoi-electronique/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 12 ] }, { "direction": "in", "type": "dependsOn", "label": "dépend de (entrant)", "other": { "id": "vaccinnet", "title": "Vaccinnet", "url": "/fr/vaccinnet/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 11, 28 ] }, { "direction": "in", "type": "dependsOn", "label": "dépend de (entrant)", "other": { "id": "vitalink", "title": "Vitalink", "url": "/fr/vitalink/" }, "status": "established", "status_label": "établi", "note_html": null, "valid_from": null, "valid_to": null, "historical": false, "refs": [ 10, 29 ] } ] } ], "relation_count": 20, "hypothesis_count": 0, "neighbours": [ { "id": "ehealth-platform", "title": "Plate-forme eHealth", "url": "/fr/plate-forme-ehealth/", "type": { "code": "Organization", "label": "Organisation" }, "status": "established" }, { "id": "ehealth-certificaten", "title": "Certificats eHealth et chiffrement (ETEE)", "url": "/fr/certificats-ehealth/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" }, { "id": "cobrha", "title": "CoBRHA", "url": "/fr/cobrha/", "type": { "code": "Dataset", "label": "Jeu de données" }, "status": "established" }, { "id": "therapeutische-relatie", "title": "Relation thérapeutique", "url": "/fr/relation-therapeutique/", "type": { "code": "Rule", "label": "Règle ou cadre" }, "status": "established" }, { "id": "recip-e", "title": "Recip-e (prescription électronique dans le secteur ambulatoire)", "url": "/fr/recip-e/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" }, { "id": "authenticatie-in-de-zorg", "title": "Authentification dans les soins de santé", "url": "/fr/authentification-dans-les-soins-de-sante/", "type": { "code": "Topic", "label": "Aperçu ou dossier" }, "status": "established" }, { "id": "csam-fas", "title": "Service fédéral d'authentification (FAS) au sein de CSAM", "url": "/fr/service-federal-d-authentification-fas-au-sein-de-csam/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" }, { "id": "ehealth-addressbook", "title": "eHealth Addressbook", "url": "/fr/ehealth-addressbook/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" }, { "id": "ehealth-basisdiensten", "title": "Services de base de la plate-forme eHealth", "url": "/fr/services-de-base-de-la-plate-forme-ehealth/", "type": { "code": "Topic", "label": "Aperçu ou dossier" }, "status": "established" }, { "id": "ehealth-connector", "title": "Connecteurs eHealth (eHealth platform services connectors)", "url": "/fr/connecteurs-ehealth/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" }, { "id": "ehealth-diensten", "title": "Services et API de la plate-forme eHealth", "url": "/fr/services-et-api-de-la-plate-forme-ehealth/", "type": { "code": "Topic", "label": "Aperçu ou dossier" }, "status": "established" }, { "id": "ehealth-pseudonimisering", "title": "Pseudonymisation et anonymisation (plate-forme eHealth)", "url": "/fr/pseudonymisation-et-anonymisation-plate-forme-ehealth/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" }, { "id": "ehealthbox", "title": "eHealthBox", "url": "/fr/ehealthbox-boite-aux-lettres-electronique-securisee/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" }, { "id": "implantatenregister", "title": "Registre central de traçabilité des implants (CTR) et SADMI", "url": "/fr/registre-central-de-tracabilite-implants/", "type": { "code": "Dataset", "label": "Jeu de données" }, "status": "established" }, { "id": "technische-integratie-ehealth", "title": "Intégration technique avec l'infrastructure eHealth", "url": "/fr/integration-technique-avec-l-infrastructure-ehealth/", "type": { "code": "Topic", "label": "Aperçu ou dossier" }, "status": "established" }, { "id": "toegangsmatrix-dienst", "title": "Service matrice d'accès de la plate-forme eHealth (WS Matrix, PADAC)", "url": "/fr/service-matrice-d-acces-ws-matrix-padac/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" }, { "id": "uhmep", "title": "UHMEP et la prescription de renvoi électronique (eReferral)", "url": "/fr/uhmep-prescription-de-renvoi-electronique/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" }, { "id": "vaccinnet", "title": "Vaccinnet", "url": "/fr/vaccinnet/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" }, { "id": "vitalink", "title": "Vitalink", "url": "/fr/vitalink/", "type": { "code": "Platform", "label": "Plateforme ou service" }, "status": "established" } ], "open_questions_html": [ "Is er een gepubliceerd migratieplan om resterende SOAP/SAML-koppelingen (STS) naar OIDC/I.AM Connect te brengen, en tegen welke datum?", "Betekent de in een publiek gepubliceerde personeelspresentatie genoemde 'SAML v1 naar v2'-verplichting in 2026 een protocolwijziging voor alle STS-gebruikers, of enkel voor Recip-e? Een officiële verplichtingsdatum is niet gevonden.", "Welke impact had de sleutelvernieuwing van juli-augustus 2026 op EPD's (storingen, verlengde deadlines)?", "Wanneer volgt de productie-uitrol van de nieuwe IDP-versie? De planning was op 28/07/2026 nog niet vastgelegd.", "Werden de herschreven diensten voor therapeutische relaties effectief op 2 december 2025 in productie genomen? Enkel de planning werd gevonden." ], "open_questions": [ { "id": "oq-c6ba5f", "html": "Is er een gepubliceerd migratieplan om resterende SOAP/SAML-koppelingen (STS) naar OIDC/I.AM Connect te brengen, en tegen welke datum?", "text": "Is er een gepubliceerd migratieplan om resterende SOAP/SAML-koppelingen (STS) naar OIDC/I.AM Connect te brengen, en tegen welke datum?" }, { "id": "oq-747bf8", "html": "Betekent de in een publiek gepubliceerde personeelspresentatie genoemde 'SAML v1 naar v2'-verplichting in 2026 een protocolwijziging voor alle STS-gebruikers, of enkel voor Recip-e? Een officiële verplichtingsdatum is niet gevonden.", "text": "Betekent de in een publiek gepubliceerde personeelspresentatie genoemde 'SAML v1 naar v2'-verplichting in 2026 een protocolwijziging voor alle STS-gebruikers, of enkel voor Recip-e? Een officiële verplichtingsdatum is niet gevonden." }, { "id": "oq-7bfdff", "html": "Welke impact had de sleutelvernieuwing van juli-augustus 2026 op EPD's (storingen, verlengde deadlines)?", "text": "Welke impact had de sleutelvernieuwing van juli-augustus 2026 op EPD's (storingen, verlengde deadlines)?" }, { "id": "oq-c2ca50", "html": "Wanneer volgt de productie-uitrol van de nieuwe IDP-versie? De planning was op 28/07/2026 nog niet vastgelegd.", "text": "Wanneer volgt de productie-uitrol van de nieuwe IDP-versie? De planning was op 28/07/2026 nog niet vastgelegd." }, { "id": "oq-35ca7c", "html": "Werden de herschreven diensten voor therapeutische relaties effectief op 2 december 2025 in productie genomen? Enkel de planning werd gevonden.", "text": "Werden de herschreven diensten voor therapeutische relaties effectief op 2 december 2025 in productie genomen? Enkel de planning werd gevonden." } ], "exchanges": [ "zh-ereferral-thuisverpleging", "ziekenhuis-uhmep-thuisverpleging", "trusted-platform-iam-exchange-saml-hok", "epd-sts-sso-naar-ehealth-webtoepassing" ], "sources": [ { "n": 1, "id": "SRC-81723a4a0f", "title": "I.AM (Identity & Access Management) | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-i.am-identity-access-management", "published": null, "first_retrieved": "2026-09-26T10:52:43+00:00", "last_checked": "2026-09-26T10:52:43+00:00", "content_sha256": "7bd6ead93abd8dbd54bd194c896caf308b34f1f9808557234a79a9814ecd7a22", "link_unreachable_since": null }, { "n": 2, "id": "SRC-6fdf93f016", "title": "Welcome Pack (eHealth-platform)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/ehealth-welcome-pack.pdf", "published": null, "first_retrieved": "2026-09-25T20:17:32+00:00", "last_checked": "2026-09-25T21:02:58+00:00", "content_sha256": "9870190cbce8511b5a665416589acde1ea8cde99833b221e0922f6a120cc1c63", "link_unreachable_since": null }, { "n": 3, "id": "SRC-9bfcb37059", "title": "eHealth-certificaten | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealth-certificaten", "published": null, "first_retrieved": "2026-09-26T10:52:10+00:00", "last_checked": "2026-09-26T10:52:10+00:00", "content_sha256": "8354aeb9558fdadcfe50671572a5167764ce37adbf9ee8260fed3d8150874ccf", "link_unreachable_since": null }, { "n": 4, "id": "SRC-a5c92698de", "title": "I.AM Identity Provider – Tech Specs v1.4", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/73c34e477b3b24ae14866882b24506e84f78a948/i-am-idp-cookbook-v1-4.pdf", "published": "2025-10-14", "first_retrieved": "2026-10-07T21:19:55+00:00", "last_checked": "2026-10-07T21:19:55+00:00", "content_sha256": "46a53092cd92bf4e29060b9c01246346c2c10c53a894ded4501dcddcc164579a", "link_unreachable_since": null }, { "n": 5, "id": "SRC-e6b4005113", "title": "Geïntegreerd gebruikers- en toegangsbeheer (IAM)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/geintegreerd-gebruikers-en-toegangsbeheer-iam", "published": null, "first_retrieved": "2026-09-28T17:01:13+00:00", "last_checked": "2026-09-28T17:01:13+00:00", "content_sha256": "cb0ce1a43bf9e03b647b1a6f640233b1ab8cef42ce9dd4f7d48c763d84f4f1d0", "link_unreachable_since": null }, { "n": 6, "id": "SRC-8846f43048", "title": "Beveiliging van webservices | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/beveiliging-van-webservices", "published": null, "first_retrieved": "2026-09-26T10:52:35+00:00", "last_checked": "2026-09-26T10:52:35+00:00", "content_sha256": "09330e2c0719bfa88f44bb90b8bd296dc72778b0a67b49e60de4d6662d48f329", "link_unreachable_since": null }, { "n": 7, "id": "SRC-e00a751dd4", "title": "I.AM (Identity & Access Management)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/fr/service-i.am-identity-access-management", "published": null, "first_retrieved": "2026-09-26T21:19:36+00:00", "last_checked": "2026-09-26T21:19:36+00:00", "content_sha256": "cb954ed05ff5bff8b3a419dc9adc3e013681276925103f8a4ab08ca09e2f96e8", "link_unreachable_since": null }, { "n": 8, "id": "SRC-2c2e9d7ae5", "title": "STS – WS Trust - Cookbook", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/5f9e569e0c2436a8ed38f8fc47cd5fba93af5667/sts-ws-trust-cookbook-v1-2.pdf", "published": "2025-07-04", "first_retrieved": "2026-09-26T21:19:38+00:00", "last_checked": "2026-09-26T21:19:38+00:00", "content_sha256": "fb67b45e6ee5f9a8bc1ab8626fb1158135e7bbdb920810e48f42d8d83fc92488", "link_unreachable_since": null }, { "n": 9, "id": "SRC-7fad05ed3d", "title": "Bericht aan de gebruikers van de diensten Metahub en eHealth Therapeutic Links", "publisher": "eHealth-platform (service management)", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/dbbaeb2626d0108a68c23f0b95e72bab92fd7cac/metahub-comm-09102025.pdf", "published": "2025-10-08", "first_retrieved": "2026-09-25T20:17:52+00:00", "last_checked": "2026-09-25T21:06:56+00:00", "content_sha256": "ab26d48e5e63318f2f7358b4e105eba0a81a8a8de460871cdc037fff48957691", "link_unreachable_since": null }, { "n": 10, "id": "SRC-a7e3a494e9", "title": "Nieuwe FHIR-omgeving van Vitalink in productie!", "publisher": "Vitalink (Departement Zorg)", "url": "https://www.vitalink.be/nieuwe-fhir-omgeving-van-vitalink-in-productie", "published": "2024-03-22", "first_retrieved": "2026-09-25T20:19:03+00:00", "last_checked": "2026-09-26T05:57:39+00:00", "content_sha256": "0628be4db12957f3bcd9265a102a94a8a7112991d8554b08db67dac5c2521668", "link_unreachable_since": null }, { "n": 11, "id": "SRC-401473d268", "title": "Vaccinnet integreren in uw softwarepakket", "publisher": "Departement Zorg", "url": "https://www.zorg-en-gezondheid.be/per-domein/infectieziekten-en-vaccinaties/vaccinaties/vaccinnet/vaccinnet-integreren-in-uw-softwarepakket", "published": null, "first_retrieved": "2026-09-25T20:19:27+00:00", "last_checked": "2026-09-26T05:58:05+00:00", "content_sha256": "525b5ff0a676a57e510ffa3273de8542a7eba04d569eecadaadeae7bb094ff32", "link_unreachable_since": null }, { "n": 12, "id": "SRC-b4bdb9101a", "title": "Recip-e FHIR Cookbook (UHMEP-MedicationPrescription-Cookbook.pdf)", "publisher": "Smals / Recip-e", "url": "https://raw.githubusercontent.com/smals-belgium/shared-digital-medication-prescription/master/UHMEP-MedicationPrescription-Cookbook.pdf", "published": "2026-06-04", "first_retrieved": "2026-09-26T10:36:17+00:00", "last_checked": "2026-10-27T21:19:37+00:00", "content_sha256": "1c1be4db40fc49042e7d926c4d8fe420cef4be7d211589ab6c33a8594a770f9b", "link_unreachable_since": null }, { "n": 13, "id": "SRC-771a066b18", "title": "Procedure: Onboarding IAM Connect eHealthBox - Addressbook v2.0", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/c519e44be8f41c3a3534de725dc9b2e7e906bce7/onboarding-iam-connect-ehbox-addressbook-v2-0-dd-29052024.pdf", "published": "2024-05-29", "first_retrieved": "2026-09-26T10:54:34+00:00", "last_checked": "2026-09-26T10:54:34+00:00", "content_sha256": "cf046c0e6e61e6b27e0cf44cd191068fa764acbc94491c96389d8fd366fa97ab", "link_unreachable_since": null }, { "n": 14, "id": "SRC-96b0dd314a", "title": "IAM Mobile integration — Technical specifications", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/9a7dc4d16e58378f81f999fc3a5333448bcdec8b/iam-mobile-integration-tech-specs-v1-13.pdf", "published": null, "first_retrieved": "2026-09-26T21:19:40+00:00", "last_checked": "2026-09-26T21:19:40+00:00", "content_sha256": "b49d45e07cc4b5526c4ff0ba1ea20c85a3a828a3331f7a43a85843474e505bca", "link_unreachable_since": null }, { "n": 15, "id": "SRC-0eb97991a9", "title": "Architecturen | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-architecturen", "published": null, "first_retrieved": "2026-09-26T10:54:37+00:00", "last_checked": "2026-09-26T10:54:37+00:00", "content_sha256": "0dab3b09a4a3129f3dbc37dbca331c2d7ef039e5d480af2f9e4ac8277d7b5a1e", "link_unreachable_since": null }, { "n": 16, "id": "SRC-ef6afc402c", "title": "eHealth platform services connectors | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealth-platform-services-connectors", "published": null, "first_retrieved": "2026-09-26T10:52:11+00:00", "last_checked": "2026-09-26T10:52:11+00:00", "content_sha256": "7e296c8a3bb3c976bf97f4ecdfe5cd4f23fa8d202127c49b4782a0b9972ad039", "link_unreachable_since": null }, { "n": 17, "id": "SRC-2e3ed33307", "title": "eHealth Communication: Renewal of I.AM Certificates - Required Actions for SAML and I.AM Connect Integrations (07/07/2026)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/495de6aa05b964876ee1d65cf26e3c521522b1a2/ehealth-communication-renewal-of-i-am-certificat-required-actions-for-saml-and-i-am-connect-integrations.pdf", "published": "2026-07-07", "first_retrieved": "2026-09-26T10:53:03+00:00", "last_checked": "2026-09-26T10:53:03+00:00", "content_sha256": "605787754dfd140e003740e7f0711a73d4fcb8a5c39c3fc93022f3dacfa2ba95", "link_unreachable_since": null }, { "n": 18, "id": "SRC-83aa4238fd", "title": "eHealth Communication: Renewal of I.AM Certificates - Required Actions for SAML and I.AM Connect Integrations (bericht 11/06/2026)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/1b97265db93b792d41e775f131d09559d41d8008/renewal-of-i-am-certificates-required-actions-for-saml-and-i-am-connect.pdf", "published": "2026-06-11", "first_retrieved": "2026-10-08T16:04:47+00:00", "last_checked": "2026-10-08T16:04:47+00:00", "content_sha256": "f645dc33dee0151c345cde702f9474d75f9a0b159d9715def385750e046218d7", "link_unreachable_since": null }, { "n": 19, "id": "SRC-9cac292f1a", "title": "eHealth platform communication - 28/07/2026: IDP migration (ACC)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/f0ac320472e1b3ccf800f5ef5fc35021f37267d5/ehealth-platform-communication-idp-acc.pdf", "published": "2026-07-28", "first_retrieved": "2026-10-08T16:04:49+00:00", "last_checked": "2026-10-08T16:04:49+00:00", "content_sha256": "62243c6d761ec6b6bc91a82836687fe6cf9dfdb06746706da597fefac2d0c66d", "link_unreachable_since": null }, { "n": 20, "id": "SRC-7100738e3f", "title": "eHealth platform communication - 18/08/2026: Replacement of the HARICA Root CA for SSL Certificates *.ehealth.fgov.be", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/2b1eb1212d86a9436c5afa34c807190b88132e14/ehealth-platform-communication-news.pdf", "published": "2026-08-18", "first_retrieved": "2026-10-08T16:04:51+00:00", "last_checked": "2026-10-08T16:04:51+00:00", "content_sha256": "585a08d0c745fca3a53d380693c838b941b7640ceb24dd6363de9cfd830d18a6", "link_unreachable_since": null }, { "n": 21, "id": "SRC-88e226b672", "title": "Réalisations 2025 – Perspectives 2026 (Plate-forme eHealth)", "publisher": "eHealth-platform (publieke presentatie op de persoonlijke website van de administrateur-generaal)", "url": "https://www.frankrobben.be/wp-content/uploads/2026/01/20260130a.pptx", "published": "2026-01-30", "first_retrieved": "2026-09-26T10:41:48+00:00", "last_checked": "2026-09-26T10:43:39+00:00", "content_sha256": "b58fc6b2201308cb26efebd98d0f8f2828ddef92794f0997183697b391b0de28", "link_unreachable_since": null }, { "n": 22, "id": "SRC-5e41adfb50", "title": "Richtlijn betreffende de vernieuwing van de publieke sleutel van een certificaat. | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/de-acceptatieomgeving-van-het-ehealth-platform", "published": null, "first_retrieved": "2026-09-26T10:55:54+00:00", "last_checked": "2026-09-26T10:55:54+00:00", "content_sha256": "d507a85f590e7840f7c94ddecda7ece43d3a5dbc47a168a4aede3e11e7661421", "link_unreachable_since": null }, { "n": 23, "id": "SRC-a881336f8b", "title": "IAM STS to IDP/IAM Connect - Cookbook (SSO from fat to thin client) v1.5", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/0be0ea08d97f7ceeb2db573142df0090e4c83927/iam-sso-from-fat-to-thin-client-tech-specs-v1-5.pdf", "published": "2026-09-11", "first_retrieved": "2026-10-07T21:19:59+00:00", "last_checked": "2026-10-07T21:19:59+00:00", "content_sha256": "35f4ece0bc267c380f5aacb03c180bfc3e59beb690647851be7e8db689a6cd56", "link_unreachable_since": null }, { "n": 24, "id": "SRC-a64792a86d", "title": "IAM eXchange - Tech Specs v1.4", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/7b7924a2b772b28caab82b0aec53cd7b1f218f29/iam-exchange-technical-specifications-v1-4.pdf", "published": "2026-09-10", "first_retrieved": "2026-10-07T21:19:57+00:00", "last_checked": "2026-10-07T21:19:57+00:00", "content_sha256": "ef87b9624f73fa6d4364b54fb88bf9703f7e625a7cbadbbcc4fab204d9f59d50", "link_unreachable_since": null }, { "n": 25, "id": "SRC-34079b24cd", "title": "Blinded pseudonymisation REST service — Cookbook", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/c6094d06e6a7b74d2e3c1a8c93cce78acb2d6359/pseudonymisation-rest-v1-9-1.pdf", "published": "2026-07-23", "first_retrieved": "2026-09-28T11:46:21+00:00", "last_checked": "2026-09-28T11:46:21+00:00", "content_sha256": "caff810b44d1c14ab2ce4ac8db7c02d1047d985f946ebc2ed67643cbac63118d", "link_unreachable_since": null }, { "n": 26, "id": "SRC-dfb54b9e7d", "title": "CTR - Centraal Traceerbaarheidsregister | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-ctr-centraal-traceerbaarheidsregister", "published": null, "first_retrieved": "2026-09-28T16:06:56+00:00", "last_checked": "2026-09-28T16:06:56+00:00", "content_sha256": "3f29a72419097b93134032c6248319f7b4cb4da386f4e08fbd4a83fe5e335678", "link_unreachable_since": null }, { "n": 27, "id": "SRC-f740dd2081", "title": "eHealth Patient Access Matrix", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealth-patient-access-matrix", "published": null, "first_retrieved": "2026-09-27T17:28:15+00:00", "last_checked": "2026-09-27T17:28:15+00:00", "content_sha256": "010cd90ced8877622f274b104a2cc7f512a0005134aea713e15d6ad8ecbce20d", "link_unreachable_since": null }, { "n": 28, "id": "SRC-4c9940d738", "title": "Vaccinnet 2026 | VAPH", "publisher": "Vlaams Agentschap voor Personen met een Handicap", "url": "https://www.vaph.be/over-het-vaph/actueel/nieuws/vaccinnet-2026", "published": null, "first_retrieved": "2026-09-25T20:19:29+00:00", "last_checked": "2026-09-26T05:58:10+00:00", "content_sha256": "9b0eed3b5eb0db8fbe7600230b28a9ea1a42b0dff0045ac25e6a26921b9ebdb5", "link_unreachable_since": null }, { "n": 29, "id": "SRC-a33755cf27", "title": "Onboarding I.AM Connect Vitalink v2.1", "publisher": "Vitalink (Departement Zorg)", "url": "https://www.vitalink.be/sites/default/files/2026-03/2026-Onboarding-I.AM-Connect-Vitalink-v2.1_0.docx", "published": "2026-03-01", "first_retrieved": "2026-10-27T21:18:42+00:00", "last_checked": "2026-10-27T21:18:42+00:00", "content_sha256": "4154baff45f98a53f5e775056272dee0708cdc11d856527f79146c7d6e2ce6e0", "link_unreachable_since": null } ], "claims": [ { "id": "CLM-4bb9e907", "statement": "I.AM (Identity & Access Management) est le service eHealth intégré d'identification, d'authentification et d'autorisation des acteurs de soins de santé qui demandent l'accès à des services de la plate-forme eHealth et de ses partenaires.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Wat is de dienst Geïntegreerd gebruikers- en toegangsbeheer/I.AM?'", "as_of": "2026-09-26", "source": { "id": "SRC-81723a4a0f", "title": "I.AM (Identity & Access Management) | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-i.am-identity-access-management", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-8c432cbb", "statement": "I.AM intègre la gestion des accès, la gestion des utilisateurs et la gestion de l'accès aux données dans un seul système qui distingue quatre contextes techniques: la sécurisation des applications web, des services web SOAP, des services web REST, et l'accès aux données (Data Access).", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Identity & Access management - Technische organisatie'", "as_of": "2026-09-26", "source": { "id": "SRC-81723a4a0f", "title": "I.AM (Identity & Access Management) | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-i.am-identity-access-management", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-6ebc31a3", "statement": "Le service I.AM (Identity & Access Management) assure l'identification, l'authentification et l'autorisation des acteurs des soins de santé; l'utilisateur choisit son profil en fonction de sa qualité telle qu'elle est enregistrée dans la base de données CoBRHA.", "kind": "fact", "kind_label": "fait", "locator": "p. 15, sectie '3. I.AM'", "as_of": "2026-09-25", "source": { "id": "SRC-6fdf93f016", "title": "Welcome Pack (eHealth-platform)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/ehealth-welcome-pack.pdf", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-58bbae3f", "statement": "Le certificat permet d'identifier et d'authentifier le partenaire « système » (le logiciel/l'organisation), tandis que l'eID ou un token permet d'identifier et d'authentifier l'utilisateur individuel.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Wat is een eHealth-certificaat?'", "as_of": "2026-09-26", "source": { "id": "SRC-9bfcb37059", "title": "eHealth-certificaten | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealth-certificaten", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-7cb73384", "statement": "La spécification IDP (version 1.4, 14/10/2025) distingue trois niveaux de sécurité pour l'authentification et classe itsme, eID et MyGov au niveau High, TOTP au niveau Substantial et nom d'utilisateur/mot de passe au niveau Low.", "kind": "fact", "kind_label": "fait", "locator": "p. 8, 4.1 Authentication method", "as_of": "2026-10-08", "source": { "id": "SRC-a5c92698de", "title": "I.AM Identity Provider – Tech Specs v1.4", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/73c34e477b3b24ae14866882b24506e84f78a948/i-am-idp-cookbook-v1-4.pdf", "published": "2025-10-14" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-3138a3bd", "statement": "De eHealth IDP steunt voor de authenticatie van gebruikers op de BOSA FAS.", "kind": "fact", "kind_label": "fait", "locator": "p. 8, §4.1", "as_of": "2026-10-07", "source": { "id": "SRC-a5c92698de", "title": "I.AM Identity Provider – Tech Specs v1.4", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/73c34e477b3b24ae14866882b24506e84f78a948/i-am-idp-cookbook-v1-4.pdf", "published": "2025-10-14" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-9a00446a", "statement": "Selon la spécification IDP (version 1.4), en production, la plupart des applications sont configurées pour une authentification via CSAM FAS, l'utilisateur étant automatiquement redirigé vers le FAS.", "kind": "fact", "kind_label": "fait", "locator": "p. 11, 4.2", "as_of": "2026-10-08", "source": { "id": "SRC-a5c92698de", "title": "I.AM Identity Provider – Tech Specs v1.4", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/73c34e477b3b24ae14866882b24506e84f78a948/i-am-idp-cookbook-v1-4.pdf", "published": "2025-10-14" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-f3bce076", "statement": "La spécification IDP (version 1.4) annonce que le « Belgian citizen token » (carte comportant 24 codes personnels) sera prochainement retiré de la liste des méthodes d'authentification disponibles (spécification du 14/10/2025; le moment effectif n'a pas été trouvé).", "kind": "fact", "kind_label": "fait", "locator": "p. 11, 4.1.6 Belgian citizen token", "as_of": "2026-10-08", "source": { "id": "SRC-a5c92698de", "title": "I.AM Identity Provider – Tech Specs v1.4", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/73c34e477b3b24ae14866882b24506e84f78a948/i-am-idp-cookbook-v1-4.pdf", "published": "2025-10-14" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-1e4fad67", "statement": "Après une authentification par eID, itsme ou TOTP, I.AM applique les règles d'accès de l'application et autorise ou non l'accès sur cette base.", "kind": "fact", "kind_label": "fait", "locator": "inleiding", "as_of": "2026-09-28", "source": { "id": "SRC-e6b4005113", "title": "Geïntegreerd gebruikers- en toegangsbeheer (IAM)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/geintegreerd-gebruikers-en-toegangsbeheer-iam", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-7a3c91fe", "statement": "Selon le Welcome Pack (version 08/09/2026), les services de base de la Plate-forme eHealth sont: la coordination de processus électroniques partiels, le portail, I.AM, RN Consult, les certificats eHealth, le timestamping, le chiffrement de bout en bout, le répertoire des références (Metahub), eHealthBox et la pseudonymisation & l'anonymisation.", "kind": "fact", "kind_label": "fait", "locator": "p. 3 (inhoudstafel, rubriek 'Basisdiensten')", "as_of": "2026-09-25", "source": { "id": "SRC-6fdf93f016", "title": "Welcome Pack (eHealth-platform)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/ehealth-welcome-pack.pdf", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-2d703e64", "statement": "L'eHealth Welcome Pack décrit I.AM comme un service de base de la plate-forme eHealth, service dont l'intégration est étroitement liée aux architectures proposées par la plate-forme.", "kind": "fact", "kind_label": "fait", "locator": "p. 17, sectie '5. I.AM', 'Afhankelijkheden, aanbevelingen en waarschuwingen'", "as_of": "2026-09-26", "source": { "id": "SRC-6fdf93f016", "title": "Welcome Pack (eHealth-platform)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/ehealth-welcome-pack.pdf", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-7cdc7fdf", "statement": "Pour les applications web classiques côté serveur, l'authentification via I.AM IDP est recommandée (avec Shibboleth SP), tandis que les applications mobiles/natives et les applications REST passent par I.AM Connect.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Afhankelijkheden, aanbevelingen en waarschuwingen'", "as_of": "2026-09-26", "source": { "id": "SRC-81723a4a0f", "title": "I.AM (Identity & Access Management) | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-i.am-identity-access-management", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-7e0e1964", "statement": "Pour la sécurisation des services web SOAP, le consommateur du service s'authentifie auprès d'I.AM STS (Secure Token Service) avec un certificat eHealth ou une eID, après quoi le STS délivre un token SAML qui donne accès à plusieurs services web pendant sa période de validité.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Veiligheid - WS-Security SAML Token Profile / Holder-of-Key'", "as_of": "2026-09-26", "source": { "id": "SRC-8846f43048", "title": "Beveiliging van webservices | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/beveiliging-van-webservices", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-ed611fb8", "statement": "I.AM Connect est une solution de gestion de l'identité et de l'accès pour les applications web et les services web RESTful, basée sur la norme OIDC (OpenID Connect); l'authentification et l'autorisation des clients s'effectuent via ce service.", "kind": "fact", "kind_label": "fait", "locator": "secties 'I.AM Connect' en 'De beveiliging van REST Web Service'", "as_of": "2026-09-26", "source": { "id": "SRC-81723a4a0f", "title": "I.AM (Identity & Access Management) | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-i.am-identity-access-management", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-e471550d", "statement": "I.AM Connect utilise OpenID Connect pour l'authentification et l'autorisation des clients REST.", "kind": "fact", "kind_label": "fait", "locator": "La sécurisation de services web REST", "as_of": "2026-09-26", "source": { "id": "SRC-e00a751dd4", "title": "I.AM (Identity & Access Management)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/fr/service-i.am-identity-access-management", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-1bc4601f", "statement": "I.AM AA (Attribute Authority) permet aux partenaires de consulter les sources authentiques eHealth, dont CoBRHA (banque de données des acteurs de soins agréés) et les mandats, indépendamment de l'accès aux applications elles-mêmes.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'I.AM AA (AttributeAuthority)'", "as_of": "2026-09-26", "source": { "id": "SRC-81723a4a0f", "title": "I.AM (Identity & Access Management) | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-i.am-identity-access-management", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-9bc067d5", "statement": "I.AM AA (Attribute Authority) permet aux partenaires de consulter les sources authentiques eHealth, dont CoBRHA (données relatives aux acteurs des soins de santé) et les mandats.", "kind": "fact", "kind_label": "fait", "locator": "p. 16, 'I.AM AA (AttributeAuthority)'", "as_of": "2026-09-25", "source": { "id": "SRC-6fdf93f016", "title": "Welcome Pack (eHealth-platform)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/ehealth-welcome-pack.pdf", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-0208ef96", "statement": "Selon le cookbook STS WS Trust, la plate-forme eHealth renvoie au consommateur du service web une assertion SAML signée dans un RequestSecurityTokenResponse.", "kind": "fact", "kind_label": "fait", "locator": "p. 9, 4 Global overview, Step 2", "as_of": "2026-09-26", "source": { "id": "SRC-2c2e9d7ae5", "title": "STS – WS Trust - Cookbook", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/5f9e569e0c2436a8ed38f8fc47cd5fba93af5667/sts-ws-trust-cookbook-v1-2.pdf", "published": "2025-07-04" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-7c0c3785", "statement": "Selon le cookbook actuel « Beveiliging van webservices », le consommateur du service demande explicitement, à l'étape 1 du processus d'authentification STS, un jeton SAML 1.1 et signe à cette occasion l'appel SOAP selon la policy de sécurité X.509 SHA256.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Stap voor stap' - Stap 1", "as_of": "2026-09-26", "source": { "id": "SRC-8846f43048", "title": "Beveiliging van webservices | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/beveiliging-van-webservices", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-79851bad", "statement": "Selon le cookbook STS WS Trust (version 1.2), « SAML2 response » est une valeur acceptée pour l'élément obligatoire TokenType dans la demande d'un token.", "kind": "fact", "kind_label": "fait", "locator": "p. 11, tabel RequestSecurityToken, veld TokenType", "as_of": "2026-10-08", "source": { "id": "SRC-2c2e9d7ae5", "title": "STS – WS Trust - Cookbook", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/5f9e569e0c2436a8ed38f8fc47cd5fba93af5667/sts-ws-trust-cookbook-v1-2.pdf", "published": "2025-07-04" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-589ff844", "statement": "Selon le cookbook STS WS Trust (version 1.2), « SAML1 response » est également une valeur acceptée pour l'élément TokenType.", "kind": "fact", "kind_label": "fait", "locator": "p. 11, tabel RequestSecurityToken, veld TokenType", "as_of": "2026-10-08", "source": { "id": "SRC-2c2e9d7ae5", "title": "STS – WS Trust - Cookbook", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/5f9e569e0c2436a8ed38f8fc47cd5fba93af5667/sts-ws-trust-cookbook-v1-2.pdf", "published": "2025-07-04" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-39af4293", "statement": "Le cookbook STS WS Trust (version 1.2) contient un exemple de réponse pour le TokenType SAML2.", "kind": "fact", "kind_label": "fait", "locator": "p. 14-15, 'Reponse example for TokenType SAML2'", "as_of": "2026-10-08", "source": { "id": "SRC-2c2e9d7ae5", "title": "STS – WS Trust - Cookbook", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/5f9e569e0c2436a8ed38f8fc47cd5fba93af5667/sts-ws-trust-cookbook-v1-2.pdf", "published": "2025-07-04" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-81fe3d98", "statement": "La refactorisation technique des services TherLink (release R20252.1) touche aussi la gestion des relations thérapeutiques via Metahub et la consultation via l'Attribute Authority; elle correspond à une réécriture complète du code source de tous les composants.", "kind": "fact", "kind_label": "fait", "locator": "p. 2 (Nederlandse versie), bericht van 08/10/2025", "as_of": "2026-09-25", "source": { "id": "SRC-7fad05ed3d", "title": "Bericht aan de gebruikers van de diensten Metahub en eHealth Therapeutic Links", "publisher": "eHealth-platform (service management)", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/dbbaeb2626d0108a68c23f0b95e72bab92fd7cac/metahub-comm-09102025.pdf", "published": "2025-10-08" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-6accb34b", "statement": "Selon un message de la Plate-forme eHealth du 8 octobre 2025, la mise en production des services TherLink entièrement réécrits était, après un test d'acceptation du 5 au 25 novembre 2025, prévue le 2 décembre 2025.", "kind": "fact", "kind_label": "fait", "locator": "p. 2, bericht van 08/10/2025 (Nederlandse versie)", "as_of": "2026-09-25", "source": { "id": "SRC-7fad05ed3d", "title": "Bericht aan de gebruikers van de diensten Metahub en eHealth Therapeutic Links", "publisher": "eHealth-platform (service management)", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/dbbaeb2626d0108a68c23f0b95e72bab92fd7cac/metahub-comm-09102025.pdf", "published": "2025-10-08" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-92ad2e3a", "statement": "L'environnement Vitalink FHIR a été mis en production (message du 22 mars 2024) et se trouve à côté de l'environnement KMEHR existant.", "kind": "fact", "kind_label": "fait", "locator": "nieuwsbericht", "as_of": "2026-09-25", "source": { "id": "SRC-a7e3a494e9", "title": "Nieuwe FHIR-omgeving van Vitalink in productie!", "publisher": "Vitalink (Departement Zorg)", "url": "https://www.vitalink.be/nieuwe-fhir-omgeving-van-vitalink-in-productie", "published": "2024-03-22" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-5f8c6805", "statement": "Le nouvel environnement Vitalink utilise REST au lieu de SOAP ainsi que les services d'authentification et d'autorisation de la Plate-forme eHealth, basés sur I.AM Connect.", "kind": "fact", "kind_label": "fait", "locator": "nieuwsbericht, alinea 3", "as_of": "2026-09-25", "source": { "id": "SRC-a7e3a494e9", "title": "Nieuwe FHIR-omgeving van Vitalink in productie!", "publisher": "Vitalink (Departement Zorg)", "url": "https://www.vitalink.be/nieuwe-fhir-omgeving-van-vitalink-in-productie", "published": "2024-03-22" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-928cba95", "statement": "Vaccinnet 2.0 utilise Vitalink comme source authentique, la norme FHIR, I.AM Connect et des services eHealth comme la pseudonymisation; les couplages KMEHR existants sont restés disponibles jusqu'au déploiement définitif.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Overstap naar Vaccinnet 2.0'", "as_of": "2026-09-25", "source": { "id": "SRC-401473d268", "title": "Vaccinnet integreren in uw softwarepakket", "publisher": "Departement Zorg", "url": "https://www.zorg-en-gezondheid.be/per-domein/infectieziekten-en-vaccinaties/vaccinaties/vaccinnet/vaccinnet-integreren-in-uw-softwarepakket", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-c032dc98", "statement": "Pour l'UHMEP FHIR API, un token exchange IAM est obligatoire (I.AM Connect), de sorte que l'exploitant technique n'obtient pas de droits de pseudonymisation.", "kind": "fact", "kind_label": "fait", "locator": "p. 9 (2.3.2 Token Exchange)", "as_of": "2026-09-26", "source": { "id": "SRC-b4bdb9101a", "title": "Recip-e FHIR Cookbook (UHMEP-MedicationPrescription-Cookbook.pdf)", "publisher": "Smals / Recip-e", "url": "https://raw.githubusercontent.com/smals-belgium/shared-digital-medication-prescription/master/UHMEP-MedicationPrescription-Cookbook.pdf", "published": "2026-06-04" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-5744ac0f", "statement": "Pour les variantes REST de l'eHealthBox et de l'Addressbook, un onboarding distinct via I.AM Connect est nécessaire, avec un choix parmi des formulaires d'enregistrement de client pour « Healthcare » (prestataire de soins individuel ou application) ou « M2M » (organisation).", "kind": "fact", "kind_label": "fait", "locator": "p. 1", "as_of": "2026-09-26", "source": { "id": "SRC-771a066b18", "title": "Procedure: Onboarding IAM Connect eHealthBox - Addressbook v2.0", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/c519e44be8f41c3a3534de725dc9b2e7e906bce7/onboarding-iam-connect-ehbox-addressbook-v2-0-dd-29052024.pdf", "published": "2024-05-29" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-35abe524", "statement": "La spécification I.AM Connect 1.13 limite le flux client credentials aux clients d'organisation ou d'institution; ce flux n'authentifie aucun utilisateur final.", "kind": "fact", "kind_label": "fait", "locator": "p. 11, 4.2 Client credentials", "as_of": "2026-09-26", "source": { "id": "SRC-96b0dd314a", "title": "IAM Mobile integration — Technical specifications", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/9a7dc4d16e58378f81f999fc3a5333448bcdec8b/iam-mobile-integration-tech-specs-v1-13.pdf", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-556ba963", "statement": "Pour un client-ID d'organisation (machine-to-machine) dans I.AM Connect, une institution de soins utilise le format nihdi-\\-XXXXXXXX, où XXXXXXXX est le numéro INAMI (NIHII) de l'institution.", "kind": "fact", "kind_label": "fait", "locator": "p. 4", "as_of": "2026-09-26", "source": { "id": "SRC-771a066b18", "title": "Procedure: Onboarding IAM Connect eHealthBox - Addressbook v2.0", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/c519e44be8f41c3a3534de725dc9b2e7e906bce7/onboarding-iam-connect-ehbox-addressbook-v2-0-dd-29052024.pdf", "published": "2024-05-29" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-45f6eb96", "statement": "Dans l'API FHIR Recip-e (cookbook v1.0, 04/06/2026), les pharmaciens utilisent le realm M2M avec le client pharmacy. Les pharmacies hospitalières utilisent un client M2M propre et ne peuvent pas réutiliser le client de l'hôpital.", "kind": "fact", "kind_label": "fait", "locator": "p. 6, 2.x Authentication (I.AM Connect)", "as_of": "2026-09-26", "source": { "id": "SRC-b4bdb9101a", "title": "Recip-e FHIR Cookbook (UHMEP-MedicationPrescription-Cookbook.pdf)", "publisher": "Smals / Recip-e", "url": "https://raw.githubusercontent.com/smals-belgium/shared-digital-medication-prescription/master/UHMEP-MedicationPrescription-Cookbook.pdf", "published": "2026-06-04" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-e72751b5", "statement": "La plate-forme eHealth propose principalement deux types d'architecture: SOAP pour les applications qui tournent sur un seul appareil, et REST pour les applications qui doivent fonctionner simultanément sur plusieurs appareils (pc, smartphone, tablette); pour les nouveaux projets mobiles, REST est privilégié.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Inleiding'", "as_of": "2026-09-26", "source": { "id": "SRC-0eb97991a9", "title": "Architecturen | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-architecturen", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-aeed1d32", "statement": "La plate-forme eHealth exige que les données médicales soient sécurisées au moins au niveau du message (et pas uniquement au niveau du transport), afin que les données ne circulent pas sans protection entre les points du réseau par lesquels elles passent.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Vertrouwelijkheid'", "as_of": "2026-09-26", "source": { "id": "SRC-0eb97991a9", "title": "Architecturen | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-architecturen", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-e959b23e", "statement": "Un chiffrement end-to-end complet entre l'expéditeur initial et le destinataire final n'est pas strictement nécessaire dans tous les projets, mais la communication doit au moins être sécurisée point-to-point, de sorte que des données médicales ne soient jamais échangées sans protection entre les parties.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Vertrouwelijkheid'", "as_of": "2026-09-26", "source": { "id": "SRC-0eb97991a9", "title": "Architecturen | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-architecturen", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-a555b445", "statement": "L'ancien service STS Saml11TokenService (avec l'endpoint iamsaml11tokenservice) n'est plus utilisé depuis octobre 2023; depuis lors, les connecteurs doivent utiliser le nouvel endpoint SecurityTokenService (iamsecuritytokenservice), ce qui confronte encore certaines intégrations à l'erreur « SOA-03005 WSDL compliance failure » lorsque cette adaptation n'a pas été faite.", "kind": "fact", "kind_label": "fait", "locator": "FAQ 'Hoe pas ik de connector aan naar de nieuwe SecurityTokenService?'", "as_of": "2026-09-26", "source": { "id": "SRC-ef6afc402c", "title": "eHealth platform services connectors | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealth-platform-services-connectors", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-6abf95a5", "statement": "Le 7 juillet 2026, la plate-forme eHealth a publié un erratum à sa communication du 11 juin 2026 relative au renouvellement obligatoire des certificats/clés pour les intégrations SAML existantes (IDP/STS/AA) et pour la validation JWT dans I.AM Connect; les clients qui gèrent manuellement leurs métadonnées ou leurs truststores devaient adapter cela avant le 22/07/2026.", "kind": "fact", "kind_label": "fait", "locator": "p. 1", "as_of": "2026-09-26", "source": { "id": "SRC-2e3ed33307", "title": "eHealth Communication: Renewal of I.AM Certificates - Required Actions for SAML and I.AM Connect Integrations (07/07/2026)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/495de6aa05b964876ee1d65cf26e3c521522b1a2/ehealth-communication-renewal-of-i-am-certificat-required-actions-for-saml-and-i-am-connect-integrations.pdf", "published": "2026-07-07" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-6ae3796a", "statement": "Le message du 07/07/2026 porte le titre « ERRATUM » et indique que les corrections sont mises en évidence en jaune.", "kind": "fact", "kind_label": "fait", "locator": "p. 1, titel en inleiding", "as_of": "2026-10-08", "source": { "id": "SRC-2e3ed33307", "title": "eHealth Communication: Renewal of I.AM Certificates - Required Actions for SAML and I.AM Connect Integrations (07/07/2026)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/495de6aa05b964876ee1d65cf26e3c521522b1a2/ehealth-communication-renewal-of-i-am-certificat-required-actions-for-saml-and-i-am-connect-integrations.pdf", "published": "2026-07-07" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-d9f27bf8", "statement": "L'erratum du 07/07/2026 mentionne, aussi bien pour la gestion manuelle des métadonnées que pour la gestion manuelle du truststore des intégrations SAML, l'échéance « avant le 22/07/2026 ».", "kind": "fact", "kind_label": "fait", "locator": "p. 1, SAML-integraties", "as_of": "2026-10-08", "source": { "id": "SRC-2e3ed33307", "title": "eHealth Communication: Renewal of I.AM Certificates - Required Actions for SAML and I.AM Connect Integrations (07/07/2026)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/495de6aa05b964876ee1d65cf26e3c521522b1a2/ehealth-communication-renewal-of-i-am-certificat-required-actions-for-saml-and-i-am-connect-integrations.pdf", "published": "2026-07-07" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-1001f865", "statement": "Le message du 11/06/2026 relatif au renouvellement des certificats I.AM mentionne, pour la gestion manuelle des métadonnées des intégrations SAML, « à partir du 26/05/2026 pour ACC et 24/06 pour PRD et avant le 6/10/2026 ».", "kind": "fact", "kind_label": "fait", "locator": "p. 1, SAML-integraties, Manueel metadata-beheer", "as_of": "2026-10-08", "source": { "id": "SRC-83aa4238fd", "title": "eHealth Communication: Renewal of I.AM Certificates - Required Actions for SAML and I.AM Connect Integrations (bericht 11/06/2026)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/1b97265db93b792d41e775f131d09559d41d8008/renewal-of-i-am-certificates-required-actions-for-saml-and-i-am-connect.pdf", "published": "2026-06-11" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-343bfceb", "statement": "Le message du 11/06/2026 mentionne, pour la gestion manuelle des certificats dans le truststore, la période « à partir du 29/07/2026 et avant le 6/10/2026 » en acceptation et en production.", "kind": "fact", "kind_label": "fait", "locator": "p. 1, SAML-integraties, Manueel beheer van certificaten in de truststore", "as_of": "2026-10-08", "source": { "id": "SRC-83aa4238fd", "title": "eHealth Communication: Renewal of I.AM Certificates - Required Actions for SAML and I.AM Connect Integrations (bericht 11/06/2026)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/1b97265db93b792d41e775f131d09559d41d8008/renewal-of-i-am-certificates-required-actions-for-saml-and-i-am-connect.pdf", "published": "2026-06-11" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-1f1c9fde", "statement": "Pour le rollover de la JWT signing key d'I.AM Connect, des moments clés distincts s'appliquaient à l'environnement d'acceptation (nouvelle clé active à partir du 07/07/2026, ancienne clé supprimée le 04/08/2026) et à l'environnement de production (nouvelle clé active à partir du 28/07/2026, ancienne clé supprimée le 26/08/2026).", "kind": "fact", "kind_label": "fait", "locator": "p. 2", "as_of": "2026-09-26", "source": { "id": "SRC-2e3ed33307", "title": "eHealth Communication: Renewal of I.AM Certificates - Required Actions for SAML and I.AM Connect Integrations (07/07/2026)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/495de6aa05b964876ee1d65cf26e3c521522b1a2/ehealth-communication-renewal-of-i-am-certificat-required-actions-for-saml-and-i-am-connect-integrations.pdf", "published": "2026-07-07" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-0ed01ce5", "statement": "Le 28/07/2026, la plate-forme eHealth a annoncé qu'elle migrait sa solution IAM IDP vers une nouvelle version, avec des modifications du look-and-feel.", "kind": "fact", "kind_label": "fait", "locator": "p. 4, 'VN'-tekst", "as_of": "2026-10-08", "source": { "id": "SRC-9cac292f1a", "title": "eHealth platform communication - 28/07/2026: IDP migration (ACC)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/f0ac320472e1b3ccf800f5ef5fc35021f37267d5/ehealth-platform-communication-idp-acc.pdf", "published": "2026-07-28" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-86f257af", "statement": "Dans le message du 28/07/2026, chaque partenaire est invité à tester la nouvelle version de l'IDP en acceptation et à confirmer que le client fonctionne encore correctement, avec au minimum le login, le choix du profil, le contenu des access tokens et le logout.", "kind": "fact", "kind_label": "fait", "locator": "p. 5-6", "as_of": "2026-10-08", "source": { "id": "SRC-9cac292f1a", "title": "eHealth platform communication - 28/07/2026: IDP migration (ACC)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/f0ac320472e1b3ccf800f5ef5fc35021f37267d5/ehealth-platform-communication-idp-acc.pdf", "published": "2026-07-28" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-f1e829b3", "statement": "Selon le message du 28/07/2026, aucune modification n'est attendue de la part des intégrateurs à la suite de la migration de l'IDP dans l'environnement d'acceptation, et la planification du déploiement en production n'est pas encore fixée.", "kind": "fact", "kind_label": "fait", "locator": "p. 5", "as_of": "2026-10-08", "source": { "id": "SRC-9cac292f1a", "title": "eHealth platform communication - 28/07/2026: IDP migration (ACC)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/f0ac320472e1b3ccf800f5ef5fc35021f37267d5/ehealth-platform-communication-idp-acc.pdf", "published": "2026-07-28" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-3f8edeaf", "statement": "Le message du 28/07/2026 relatif à la migration de l'IDP en acceptation s'adresse aux clients IAM Connect; les intégrateurs de l'eHealth IAM IDP ne sont pas visés par ce message et reçoivent une communication distincte.", "kind": "fact", "kind_label": "fait", "locator": "p. 6", "as_of": "2026-10-08", "source": { "id": "SRC-9cac292f1a", "title": "eHealth platform communication - 28/07/2026: IDP migration (ACC)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/f0ac320472e1b3ccf800f5ef5fc35021f37267d5/ehealth-platform-communication-idp-acc.pdf", "published": "2026-07-28" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-8a750437", "statement": "Dans un message du 18/08/2026 adressé à tous les utilisateurs d'un service eHealth dans le domaine *.ehealth.fgov.be, la plate-forme eHealth a demandé de tester un nouveau certificat TLS dans l'environnement d'acceptation à partir du 02/09/2026; le certificat en production serait actif à partir du 13/10/2026.", "kind": "fact", "kind_label": "fait", "locator": "p. 1, punt 2 'Quand devez-vous exécuter ces actions ?'", "as_of": "2026-10-08", "source": { "id": "SRC-7100738e3f", "title": "eHealth platform communication - 18/08/2026: Replacement of the HARICA Root CA for SSL Certificates *.ehealth.fgov.be", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/2b1eb1212d86a9436c5afa34c807190b88132e14/ehealth-platform-communication-news.pdf", "published": "2026-08-18" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-29e794ae", "statement": "Le message du 18/08/2026 demande d'installer aussi bien la Root CA HARICA 2015 que HARICA 2021.", "kind": "fact", "kind_label": "fait", "locator": "p. 1", "as_of": "2026-10-08", "source": { "id": "SRC-7100738e3f", "title": "eHealth platform communication - 18/08/2026: Replacement of the HARICA Root CA for SSL Certificates *.ehealth.fgov.be", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/2b1eb1212d86a9436c5afa34c807190b88132e14/ehealth-platform-communication-news.pdf", "published": "2026-08-18" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-48ff1c55", "statement": "Le message du 18/08/2026 indique que les utilisateurs qui se servent des métadonnées TSL en ligne mentionnées dans le message pour valider la chaîne de certificats et la récupérer périodiquement n'ont rien à faire.", "kind": "fact", "kind_label": "fait", "locator": "p. 1, punt 1", "as_of": "2026-10-08", "source": { "id": "SRC-7100738e3f", "title": "eHealth platform communication - 18/08/2026: Replacement of the HARICA Root CA for SSL Certificates *.ehealth.fgov.be", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/2b1eb1212d86a9436c5afa34c807190b88132e14/ehealth-platform-communication-news.pdf", "published": "2026-08-18" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-0b11929f", "statement": "Selon une présentation publiée publiquement de la Plate-forme eHealth (30 janvier 2026), Recip-e (services web SOAP) doit passer de SAML v1 à SAML v2, parce que la Plate-forme eHealth l'exige en 2026 pour toutes les applications qui utilisent les services de base eHealth.", "kind": "fact", "kind_label": "fait", "locator": "dia 55 ('Elektronisch voorschrift van geneesmiddelen', SAMLv2-migratie, 2026)", "as_of": "2026-09-26", "source": { "id": "SRC-88e226b672", "title": "Réalisations 2025 – Perspectives 2026 (Plate-forme eHealth)", "publisher": "eHealth-platform (publieke presentatie op de persoonlijke website van de administrateur-generaal)", "url": "https://www.frankrobben.be/wp-content/uploads/2026/01/20260130a.pptx", "published": "2026-01-30" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-5dacc708", "statement": "Un certificat eHealth permet à un prestataire de soins ou à une organisation de s'authentifier en tant que prestataire de soins ou institution reconnue; il est requis dès qu'une suite logicielle souhaite accéder aux services de base eHealth via une connexion de système à système et non une application web.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Wat is een eHealth-certificaat?'", "as_of": "2026-09-26", "source": { "id": "SRC-9bfcb37059", "title": "eHealth-certificaten | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealth-certificaten", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-1ba5fb92", "statement": "Selon le Welcome Pack, l'accès à certains services REST de la plate-forme eHealth exige une intégration avec I.AM Connect; pour l'utilisation du token exchange, des règles supplémentaires et un contrat s'appliquent.", "kind": "fact", "kind_label": "fait", "locator": "p. 17, sectie '5. I.AM'", "as_of": "2026-09-26", "source": { "id": "SRC-6fdf93f016", "title": "Welcome Pack (eHealth-platform)", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/ehealth-welcome-pack.pdf", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-4ac343c7", "statement": "Pour les intégrations SOAP avec l'eHealthBox, un certificat de base (certificat eHealth) suffit, sans l'étape d'onboarding supplémentaire I.AM Connect qui est exigée pour les services REST.", "kind": "fact", "kind_label": "fait", "locator": "p. 1", "as_of": "2026-09-26", "source": { "id": "SRC-771a066b18", "title": "Procedure: Onboarding IAM Connect eHealthBox - Addressbook v2.0", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/c519e44be8f41c3a3534de725dc9b2e7e906bce7/onboarding-iam-connect-ehbox-addressbook-v2-0-dd-29052024.pdf", "published": "2024-05-29" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-a84bf904", "statement": "La plate-forme eHealth diffuse sa liste de certificats de confiance (mise à jour du trust store) selon la spécification technique ETSI relative aux listes de confiance (Trusted Lists), de sorte que les logiciels puissent mettre à jour leur trust store de manière sécurisée et automatisable.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Cookbook' - eHealth PlatformTrusted Certificates List", "as_of": "2026-09-26", "source": { "id": "SRC-9bfcb37059", "title": "eHealth-certificaten | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealth-certificaten", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-48119ef9", "statement": "Toegang tot de webservices van het eHealth-platform in de acceptatieomgeving vereist een eHealth-certificaat in acceptatie en de integratie van de connector, naast een uitgeteste computer/browser en meestal een medisch testprofiel.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Welke tools zijn vereist om de testen en demo's effectief uit te voeren?'", "as_of": "2026-09-26", "source": { "id": "SRC-5e41adfb50", "title": "Richtlijn betreffende de vernieuwing van de publieke sleutel van een certificaat. | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/de-acceptatieomgeving-van-het-ehealth-platform", "published": null }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-d0015248", "statement": "La spécification IDP (version 1.4) décrit les profils SAML 2.0 Web Browser SSO.", "kind": "fact", "kind_label": "fait", "locator": "6.1 SAML 2.0", "as_of": "2026-10-08", "source": { "id": "SRC-a5c92698de", "title": "I.AM Identity Provider – Tech Specs v1.4", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/73c34e477b3b24ae14866882b24506e84f78a948/i-am-idp-cookbook-v1-4.pdf", "published": "2025-10-14" }, "citaat": null, "figuur": null, "in_text": true, "on_page": true }, { "id": "CLM-4b8e9309", "statement": "Au 30 octobre 2026, la version française de la page eHealth sur la sécurisation des services web décrit encore que le service consumer demande un jeton SAML 1.1 à l'étape 1 du processus STS.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'Étape par étape' – Étape 1", "as_of": "2026-10-30", "source": { "id": "SRC-1c6287ee60", "title": "Sécurisation des services web | Platform eHealth", "publisher": "Plate-forme eHealth", "url": "https://www.ehealth.fgov.be/ehealthplatform/fr/securisation-des-services-web", "published": null }, "citaat": null, "figuur": null, "in_text": false, "on_page": false }, { "id": "CLM-5b389c3b", "statement": "Selon la spécification de l'I.AM Identity Provider (version 1.4), itsme est actuellement le seul partenaire reconnu qui offre, à côté des clés numériques des autorités publiques, une clé numérique permettant de se connecter aux services publics.", "kind": "fact", "kind_label": "fait", "locator": "p. 10, 4.1.2 ItsMe", "as_of": "2026-10-30", "source": { "id": "SRC-a5c92698de", "title": "I.AM Identity Provider – Tech Specs v1.4", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/73c34e477b3b24ae14866882b24506e84f78a948/i-am-idp-cookbook-v1-4.pdf", "published": "2025-10-14" }, "citaat": null, "figuur": null, "in_text": false, "on_page": false }, { "id": "CLM-5e03d5ff", "statement": "I.AM STS est destiné à l'identification auprès des services web intégrés dans les logiciels des médecins et permet de s'identifier comme médecin, spécialiste ou infirmier.", "kind": "fact", "kind_label": "fait", "locator": "sectie 'I.AM STS (Secure Token Service)'", "as_of": "2026-09-28", "source": { "id": "SRC-81723a4a0f", "title": "I.AM (Identity & Access Management) | eHealth-platform", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/nl/service-i.am-identity-access-management", "published": null }, "citaat": null, "figuur": null, "in_text": false, "on_page": false }, { "id": "CLM-5f3eeead", "statement": "Selon la spécification IDP (version 1.4), l'eHealth IDP prend en charge, pour le SSO initié par le SP, une inbound binding publiée dans l'implémentation Shibboleth des profils SAML 1.1 Web SSO.", "kind": "fact", "kind_label": "fait", "locator": "p. 27-28, 6.2 SAML 1.1", "as_of": "2026-10-08", "source": { "id": "SRC-a5c92698de", "title": "I.AM Identity Provider – Tech Specs v1.4", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/73c34e477b3b24ae14866882b24506e84f78a948/i-am-idp-cookbook-v1-4.pdf", "published": "2025-10-14" }, "citaat": null, "figuur": null, "in_text": false, "on_page": false }, { "id": "CLM-66bb1f47", "statement": "Selon la même spécification, l'échange de tokens d'I.AM STS est autorisé et pris en charge, mais sous certaines limitations.", "kind": "fact", "kind_label": "fait", "locator": "p. 9, 4.2 STS to IAM Connect", "as_of": "2026-10-30", "source": { "id": "SRC-a881336f8b", "title": "IAM STS to IDP/IAM Connect - Cookbook (SSO from fat to thin client) v1.5", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/0be0ea08d97f7ceeb2db573142df0090e4c83927/iam-sso-from-fat-to-thin-client-tech-specs-v1-5.pdf", "published": "2026-09-11" }, "citaat": null, "figuur": null, "in_text": false, "on_page": false }, { "id": "CLM-94bf1882", "statement": "Le document publié par la plate-forme eHealth au sujet de la mise à niveau du service provider Shibboleth indique qu'eHealth n'a pas encore de plans pour supprimer les profils SAML 1.1 et que ceux-ci restent pris en charge.", "kind": "fact", "kind_label": "fait", "locator": "p. 11, 4.4 SAML Protocol, Profile and Binding (optional)", "as_of": "2026-10-30", "source": { "id": "SRC-3e1616c0a1", "title": "Identity & Authorization Management (I.AM) – SP Shibboleth – Upgrade – Migration from IDP v1.3 to IDP v2", "publisher": "eHealth platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/e3e96a7608cf8fa2e29bfa4f9254b63ec709131c/ehealth-i-am-sp-shibboleth-upgrade-v1-0.pdf", "published": "2013-07-11" }, "citaat": null, "figuur": null, "in_text": false, "on_page": false }, { "id": "CLM-bbad888e", "statement": "Selon le même document, l'IDP eHealth v2 prend en charge tous les profils Web Browser SSO SAML 1.1 et SAML 2.0, de sorte qu'un service provider peut laisser sa configuration telle quelle ou choisir de passer à SAML 2.0.", "kind": "fact", "kind_label": "fait", "locator": "p. 11, 4.4 SAML Protocol, Profile and Binding (optional)", "as_of": "2026-10-30", "source": { "id": "SRC-3e1616c0a1", "title": "Identity & Authorization Management (I.AM) – SP Shibboleth – Upgrade – Migration from IDP v1.3 to IDP v2", "publisher": "eHealth platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/e3e96a7608cf8fa2e29bfa4f9254b63ec709131c/ehealth-i-am-sp-shibboleth-upgrade-v1-0.pdf", "published": "2013-07-11" }, "citaat": null, "figuur": null, "in_text": false, "on_page": false }, { "id": "CLM-f07c7dfe", "statement": "Selon le cookbook du service web Attribute Authority (version 1.9, 13/10/2026), une valeur d'attribut renvoyée par l'AA peut être pseudonymisée ou non pseudonymisée, et ce pseudonyme est généré par I.AM Connect.", "kind": "fact", "kind_label": "fait", "locator": "sectie 5.4.1 (Attribute), beschrijving van AttributeValue", "as_of": "2026-10-30", "source": { "id": "SRC-12fdf8b3ff", "title": "Attribute Authority WS – Cookbook", "publisher": "eHealth platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/66c38b07b1be651e1da00be9b1e0421c4c488dda/attribute-authority-ws-cookbook-1-9.pdf", "published": "2026-10-13" }, "citaat": null, "figuur": null, "in_text": false, "on_page": false }, { "id": "CLM-f9493a5a", "statement": "La même spécification décrit un flux permettant d'échanger un token SAML holder-of-key d'I.AM STS contre un JWT dans I.AM Connect; ce flux peut aussi servir à démarrer une session web sur la base d'une session SOAP.", "kind": "fact", "kind_label": "fait", "locator": "p. 9, 4.2 STS to IAM Connect", "as_of": "2026-10-30", "source": { "id": "SRC-a881336f8b", "title": "IAM STS to IDP/IAM Connect - Cookbook (SSO from fat to thin client) v1.5", "publisher": "eHealth-platform", "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/0be0ea08d97f7ceeb2db573142df0090e4c83927/iam-sso-from-fat-to-thin-client-tech-specs-v1-5.pdf", "published": "2026-09-11" }, "citaat": null, "figuur": null, "in_text": false, "on_page": false } ], "diagrams": [], "facets": { "type": [ "Platform" ], "jurisdiction": [ "belgie" ], "theme": [ "identiteit-en-toegang", "architectuur-en-infrastructuur" ], "lifecycle": [ "productie" ], "section": [ "platformen" ] }, "search_terms": [ "I.AM et I.AM Connect (Identity & Access Management)", "I.AM", "I.AM Connect", "I.AM IDP", "I.AM STS", "I.AM AA", "Attribute Authority", "Secure Token Service", "geïntegreerd gebruikers- en toegangsbeheer", "I.AM (Identity & Access Management)" ], "release_id": "2026.11.12-3", "license": "CC BY 4.0" }