{
 "id": "vgl-fhir-openehr-omop",
 "url": "/fr/fhir-openehr-et-omop-comparaison/",
 "md_url": "/fr/fhir-openehr-et-omop-comparaison.md",
 "json_url": "/fr/fhir-openehr-et-omop-comparaison.json",
 "claims_url": "/fr/fhir-openehr-et-omop-comparaison/beweringen/",
 "type": {
  "code": "Topic",
  "label": "Aperçu ou dossier"
 },
 "schema_type": "Thing",
 "lang": "fr",
 "translation": {
  "lang": "fr",
  "source_url": "/vgl-fhir-openehr-omop/",
  "date": "2026-10-29",
  "stale": true,
  "fields": [
   "lifecycle_note",
   "sectie:bouwstenen",
   "sectie:fase-en-verplichtingen",
   "sectie:onzekerheden-en-tegenstrijdige-informatie",
   "sectie:wat-betekent-het-voor-een-ziekenhuis",
   "sectie:wat-is-het",
   "summary",
   "title"
  ]
 },
 "title": "FHIR, openEHR et OMOP : comparaison",
 "aliases": [
  "FHIR vs openEHR vs OMOP",
  "FHIR, openEHR en OMOP CDM",
  "uitwisseling vs persistentie vs analyse"
 ],
 "names": {
  "nl": "FHIR, openEHR en OMOP: vergelijking",
  "fr": "FHIR, openEHR et OMOP : comparaison",
  "en": "FHIR, openEHR and OMOP compared",
  "de": null
 },
 "jurisdiction": [
  {
   "code": "internationaal",
   "label": "International"
  },
  {
   "code": "eu",
   "label": "Union européenne"
  },
  {
   "code": "belgie",
   "label": "Belgique (fédéral/interfédéral)"
  }
 ],
 "themes": [
  {
   "code": "architectuur-en-infrastructuur",
   "label": "Architecture et infrastructure"
  },
  {
   "code": "terminologie",
   "label": "Terminologie et codage"
  },
  {
   "code": "secundair-gebruik",
   "label": "Utilisation secondaire et registres"
  }
 ],
 "lifecycle": {
  "code": "onbekend",
  "label": "inconnu"
 },
 "lifecycle_note_html": "Sans objet : il s'agit d'une page de comparaison. Au 5 octobre 2026, FHIR→OMOP était publié à titre informatif, tandis qu'openEHR↔FHIR consistait encore en un guide de développement et des prototypes de recherche.",
 "version": null,
 "vendor": null,
 "sectors": [],
 "homologations": [],
 "links": [],
 "summary_text": "FHIR, openEHR et OMOP CDM résolvent des problèmes différents: l'échange, la modélisation clinique et la persistance, et l'analyse pour l'usage secondaire. Ils peuvent utiliser les mêmes terminologies et sont, selon les sources consultées, complémentaires, mais les conversions font perdre de l'information. L'EHDS fixera des exigences techniques pour le format européen d'échange; aucune obligation relative à openEHR ou OMOP n'a été trouvée. Pour les hôpitaux, la distinction importe dans les choix en matière d'interfaces, de stockage clinique et de données de recherche.",
 "summary_html": "<p>FHIR, openEHR et OMOP CDM résolvent des problèmes différents : l'échange, la modélisation clinique et la persistance, et l'analyse pour l'usage secondaire. Ils peuvent utiliser les mêmes terminologies et sont, selon les sources consultées, complémentaires, mais les conversions font perdre de l'information. L'EHDS fixera des exigences techniques pour le format européen d'échange ; aucune obligation relative à openEHR ou OMOP n'a été trouvée. Pour les hôpitaux, la distinction importe dans les choix en matière d'interfaces, de stockage clinique et de données de recherche.</p>",
 "last_verified": "2026-10-05",
 "verification_outdated": false,
 "sections": [
  {
   "id": "qu-est-ce-que-c-est",
   "title": "Qu'est-ce que c'est ?",
   "kind": "tekst",
   "html": "<p>Quel rôle jouent <a href=\"/fr/hl7-fhir/\">HL7 FHIR</a>, openEHR et <a href=\"/fr/omop-cdm-et-ohdsi/\">OMOP CDM</a> côte à côte, et que doit en connaître un hôpital\nflamand à la lumière de l'<a href=\"/fr/espace-europeen-des-donnees-de-sante/\">EHDS (Espace européen des données de santé)</a> ? Comme cadre, cette page utilise les trois domaines de données du guide\nd'implémentation HL7 FHIR-to-OMOP : soins cliniques et administration, échange de données et analyse longitudinale\n<sup class=\"cite\" id=\"t-CLM-cfdf8dac\" data-claims=\"CLM-cfdf8dac\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup>. Ce guide d'implémentation considère FHIR et OMOP comme complémentaires et non comme concurrents\n<sup class=\"cite\" id=\"t-CLM-2dc7d72b\" data-claims=\"CLM-2dc7d72b\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup>. Un panel d'experts aboutit à la même conclusion pour openEHR, ISO 13606 et FHIR : chacun est\nutile pour un objectif propre et ils sont utilisables ensemble<sup class=\"cite\" id=\"t-CLM-3ccf652d\" data-claims=\"CLM-3ccf652d\"><a class=\"cite-ref\" href=\"#bron-2\" aria-label=\"Source 2\">[2]</a></sup>.</p>"
  },
  {
   "id": "composantes",
   "title": "Composantes",
   "kind": "tekst",
   "html": "<table>\n<thead>\n<tr>\n<th>Dimension</th>\n<th>HL7 FHIR</th>\n<th>openEHR</th>\n<th>OMOP CDM (OHDSI)</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Objectif</td>\n<td>Échange électronique d'informations de soins<sup class=\"cite\" id=\"t-CLM-20ccab31\" data-claims=\"CLM-20ccab31\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup> ; domaine : échange de données (API REST, resources)<sup class=\"cite\" id=\"t-CLM-6c1c8ed6\" data-claims=\"CLM-6c1c8ed6\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup></td>\n<td>Séparer le stockage technique et la signification clinique, afin que les systèmes évoluent sans perte de données<sup class=\"cite\" id=\"t-CLM-75e965e1\" data-claims=\"CLM-75e965e1\"><a class=\"cite-ref\" href=\"#bron-4\" aria-label=\"Source 4\">[4]</a></sup> ; modèle de plate-forme complet pour l'enregistrement, la persistance et l'interrogation<sup class=\"cite\" id=\"t-CLM-a5de0448\" data-claims=\"CLM-a5de0448\"><a class=\"cite-ref\" href=\"#bron-2\" aria-label=\"Source 2\">[2]</a></sup></td>\n<td>Standardiser la structure et le contenu de données observationnelles pour l'analyse<sup class=\"cite\" id=\"t-CLM-0d763233\" data-claims=\"CLM-0d763233\"><a class=\"cite-ref\" href=\"#bron-5\" aria-label=\"Source 5\">[5]</a></sup> ; domaine : analyse longitudinale<sup class=\"cite\" id=\"t-CLM-e6250916\" data-claims=\"CLM-e6250916\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup></td>\n</tr>\n<tr>\n<td>Gestion</td>\n<td>HL7 International ; en Belgique, HL7 Belgium est l'affilié<sup class=\"cite\" id=\"t-CLM-6070feb3\" data-claims=\"CLM-6070feb3\"><a class=\"cite-ref\" href=\"#bron-6\" aria-label=\"Source 6\">[6]</a></sup>, des groupes de travail de HL7 Belgium élaborent des profils FHIR<sup class=\"cite\" id=\"t-CLM-cef569f6\" data-claims=\"CLM-cef569f6\"><a class=\"cite-ref\" href=\"#bron-7\" aria-label=\"Source 7\">[7]</a></sup> et la plate-forme eHealth publie des profils FHIR<sup class=\"cite\" id=\"t-CLM-43dc8f12\" data-claims=\"CLM-43dc8f12\"><a class=\"cite-ref\" href=\"#bron-8\" aria-label=\"Source 8\">[8]</a></sup></td>\n<td>openEHR International (opérationnel, depuis 2019), propriété intellectuelle auprès de la openEHR Foundation<sup class=\"cite\" id=\"t-CLM-f455020e\" data-claims=\"CLM-f455020e\"><a class=\"cite-ref\" href=\"#bron-9\" aria-label=\"Source 9\">[9]</a></sup> ; spécifications CC-BY-ND<sup class=\"cite\" id=\"t-CLM-c6ad972d\" data-claims=\"CLM-c6ad972d\"><a class=\"cite-ref\" href=\"#bron-9\" aria-label=\"Source 9\">[9]</a></sup></td>\n<td>OHDSI CDM Working Group<sup class=\"cite\" id=\"t-CLM-8016d826\" data-claims=\"CLM-8016d826\"><a class=\"cite-ref\" href=\"#bron-5\" aria-label=\"Source 5\">[5]</a></sup></td>\n</tr>\n<tr>\n<td>Granularité</td>\n<td>La resource est la brique de base<sup class=\"cite\" id=\"t-CLM-d3f779a6\" data-claims=\"CLM-d3f779a6\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup></td>\n<td>Modèle de référence stable avec des archétypes et des templates comme niveau de domaine<sup class=\"cite\" id=\"t-CLM-5472e46b\" data-claims=\"CLM-5472e46b\"><a class=\"cite-ref\" href=\"#bron-10\" aria-label=\"Source 10\">[10]</a></sup> ; les templates forment des Compositions complètes (p. ex. une lettre de sortie)<sup class=\"cite\" id=\"t-CLM-f3a32110\" data-claims=\"CLM-f3a32110\"><a class=\"cite-ref\" href=\"#bron-10\" aria-label=\"Source 10\">[10]</a></sup></td>\n<td>Centré sur la personne : toutes les tables d'événements cliniques sont reliées à PERSON<sup class=\"cite\" id=\"t-CLM-b378c72d\" data-claims=\"CLM-b378c72d\"><a class=\"cite-ref\" href=\"#bron-11\" aria-label=\"Source 11\">[11]</a></sup></td>\n</tr>\n<tr>\n<td>Interrogation</td>\n<td>L'API REST est l'une des possibilités<sup class=\"cite\" data-claims=\"CLM-6c1c8ed6\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup>, mais REST n'est pas requis pour utiliser des resources<sup class=\"cite\" id=\"t-CLM-22b16816\" data-claims=\"CLM-22b16816\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup></td>\n<td>AQL<sup class=\"cite\" id=\"t-CLM-8025c8fd\" data-claims=\"CLM-8025c8fd\"><a class=\"cite-ref\" href=\"#bron-10\" aria-label=\"Source 10\">[10]</a></sup></td>\n<td>Modèle relationnel, réalisable dans n'importe quelle base de données relationnelle (p. ex. des bases SQL)<sup class=\"cite\" id=\"t-CLM-5eaebd11\" data-claims=\"CLM-5eaebd11\"><a class=\"cite-ref\" href=\"#bron-11\" aria-label=\"Source 11\">[11]</a></sup> ; aucun langage de requête distinct trouvé dans les sources</td>\n</tr>\n<tr>\n<td>Maturité et version</td>\n<td>R5 (5.0.0) est la version actuelle<sup class=\"cite\" id=\"t-CLM-9566eb8c\" data-claims=\"CLM-9566eb8c\"><a class=\"cite-ref\" href=\"#bron-12\" aria-label=\"Source 12\">[12]</a></sup> ; R4 (4.0.1) mêle contenu normatif et STU<sup class=\"cite\" id=\"t-CLM-1badcbfb\" data-claims=\"CLM-1badcbfb\"><a class=\"cite-ref\" href=\"#bron-13\" aria-label=\"Source 13\">[13]</a></sup></td>\n<td>Architecture Overview BASE 1.2.0, statut STABLE<sup class=\"cite\" id=\"t-CLM-f00aa165\" data-claims=\"CLM-f00aa165\"><a class=\"cite-ref\" href=\"#bron-10\" aria-label=\"Source 10\">[10]</a></sup></td>\n<td>v5.5<sup class=\"cite\" data-claims=\"CLM-8016d826\"><a class=\"cite-ref\" href=\"#bron-5\" aria-label=\"Source 5\">[5]</a></sup>, uniquement des ajouts optionnels par rapport à la v5.4<sup class=\"cite\" id=\"t-CLM-ac400acb\" data-claims=\"CLM-ac400acb\"><a class=\"cite-ref\" href=\"#bron-14\" aria-label=\"Source 14\">[14]</a></sup></td>\n</tr>\n<tr>\n<td>Rôle de la terminologie</td>\n<td>Module de terminologie avec CodeSystem, ValueSet, ConceptMap<sup class=\"cite\" id=\"t-CLM-81841f02\" data-claims=\"CLM-81841f02\"><a class=\"cite-ref\" href=\"#bron-15\" aria-label=\"Source 15\">[15]</a></sup> ; chaque système de codes a une URL (p. ex. LOINC, SNOMED)<sup class=\"cite\" id=\"t-CLM-89c84b92\" data-claims=\"CLM-89c84b92\"><a class=\"cite-ref\" href=\"#bron-16\" aria-label=\"Source 16\">[16]</a></sup></td>\n<td>Archétypes et templates comme porte d'entrée sémantique vers les terminologies<sup class=\"cite\" id=\"t-CLM-19680c4c\" data-claims=\"CLM-19680c4c\"><a class=\"cite-ref\" href=\"#bron-10\" aria-label=\"Source 10\">[10]</a></sup></td>\n<td>Standardized Vocabularies au centre<sup class=\"cite\" id=\"t-CLM-5068e15a\" data-claims=\"CLM-5068e15a\"><a class=\"cite-ref\" href=\"#bron-5\" aria-label=\"Source 5\">[5]</a></sup> ; un seul Standard Concept par événement, SNOMED pour les affections<sup class=\"cite\" id=\"t-CLM-8b25e1f2\" data-claims=\"CLM-8b25e1f2\"><a class=\"cite-ref\" href=\"#bron-17\" aria-label=\"Source 17\">[17]</a></sup></td>\n</tr>\n<tr>\n<td>Usage en Belgique</td>\n<td>Norme privilégiée pour les nouveaux flux (depuis l'Actieplan e-Gezondheid 2019-2021)<sup class=\"cite\" id=\"t-CLM-a8067de8\" data-claims=\"CLM-a8067de8\"><a class=\"cite-ref\" href=\"#bron-18\" aria-label=\"Source 18\">[18]</a></sup> ; <a href=\"/fr/guides-d-implementation-fhir-belges/\">guides d'implémentation belges</a> en R4<sup class=\"cite\" id=\"t-CLM-4c97a5a4\" data-claims=\"CLM-4c97a5a4\"><a class=\"cite-ref\" href=\"#bron-19\" aria-label=\"Source 19\">[19]</a></sup></td>\n<td>Non trouvé (lacune ; cela ne signifie pas que cela n'existe pas)</td>\n<td>Nœud OHDSI belge issu de la communauté EHDEN<sup class=\"cite\" id=\"t-CLM-ba340bd5\" data-claims=\"CLM-ba340bd5\"><a class=\"cite-ref\" href=\"#bron-20\" aria-label=\"Source 20\">[20]</a></sup> ; 14 partenaires de données EHDEN belges<sup class=\"cite\" id=\"t-CLM-23727b49\" data-claims=\"CLM-23727b49\"><a class=\"cite-ref\" href=\"#bron-21\" aria-label=\"Source 21\">[21]</a></sup></td>\n</tr>\n</tbody>\n</table>\n<p>Selon un article du JMIR (2025), FHIR et OMOP utilisent les mêmes terminologies internationales, et OMOP convient mieux à l'analyse qu'à l'échange opérationnel<sup class=\"cite\" id=\"t-CLM-85e934d1\" data-claims=\"CLM-85e934d1\"><a class=\"cite-ref\" href=\"#bron-22\" aria-label=\"Source 22\">[22]</a></sup>. Dans les profils FHIR belges, <a href=\"/fr/snomed-ct/\">SNOMED CT</a> est le codage privilégié<sup class=\"cite\" id=\"t-CLM-530b635f\" data-claims=\"CLM-530b635f\"><a class=\"cite-ref\" href=\"#bron-23\" aria-label=\"Source 23\">[23]</a></sup>, et dans le guide d'implémentation FHIR belge pour les résultats de laboratoire (v1.0.0, trial use), la plupart des mesures de laboratoire courantes doivent être codées en <a href=\"/fr/loinc-et-le-sous-ensemble-belge-retam/\">LOINC</a> selon le sous-ensemble du SPF<sup class=\"cite\" id=\"t-CLM-e0e48933\" data-claims=\"CLM-e0e48933\"><a class=\"cite-ref\" href=\"#bron-24\" aria-label=\"Source 24\">[24]</a></sup>. La classification d'enregistrement <a href=\"/fr/icd-10-be/\">ICD-10-BE</a> se situe en dehors de ces trois modèles ; dans OMOP, les codes ICD sont mappés, comme codes sources, sur des concepts standard SNOMED<sup class=\"cite\" id=\"t-CLM-71837b87\" data-claims=\"CLM-8b25e1f2 CLM-71837b87\"><a class=\"cite-ref\" href=\"#bron-17\" aria-label=\"Source 17\">[17]</a></sup>.</p>\n<h3>Mappings et perte d'information</h3>\n<ul>\n<li><strong>FHIR → OMOP</strong> : le HL7 Vulcan FHIR-to-OMOP IG v1.0.0 (Informative, FHIR R5) ne traite que ce sens, pour un noyau IPA ainsi que Encounter et Procedure (US Core), avec le CDM v5.4 pour cible<sup class=\"cite\" id=\"t-CLM-77f1c57f\" data-claims=\"CLM-77f1c57f\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup>. Un ballot 2.0.0 est en ligne comme continuous build (projet)<sup class=\"cite\" id=\"t-CLM-2eb05c91\" data-claims=\"CLM-2eb05c91\"><a class=\"cite-ref\" href=\"#bron-25\" aria-label=\"Source 25\">[25]</a></sup>. Ce guide d'implémentation indique que la transformation ne peut pas être sans perte et distingue les pertes de fidélité, d'information, de relations et d'exactitude<sup class=\"cite\" id=\"t-CLM-cd749309\" data-claims=\"CLM-cd749309\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup>.</li>\n<li><strong>openEHR ↔ FHIR</strong> : un guide d'implémentation qui mappe les types de données openEHR sur les types de données FHIR est en développement (R5 ; sur GitHub dans l'organisation openehr-fhir, configuré comme IG HL7 FHIR avec publisher HL7 FHIR Infrastructure ; une publication formelle de HL7 n'a pas été constatée)<sup class=\"cite\" id=\"t-CLM-4d28e36b\" data-claims=\"CLM-4d28e36b\"><a class=\"cite-ref\" href=\"#bron-26\" aria-label=\"Source 26\">[26]</a></sup>. FHIRconnect est une proposition de recherche (preprint 2025) qui a mappé 24 archétypes vers 15 profils FHIR<sup class=\"cite\" id=\"t-CLM-dc514fc0\" data-claims=\"CLM-dc514fc0\"><a class=\"cite-ref\" href=\"#bron-27\" aria-label=\"Source 27\">[27]</a></sup>.</li>\n<li><strong>openEHR ↔ OMOP</strong> : aucune norme de mapping officielle trouvée (lacune).</li>\n</ul>"
  },
  {
   "id": "phase-et-obligations",
   "title": "Phase et obligations",
   "kind": "tekst",
   "html": "<ul>\n<li><strong>Dates d'application</strong> : le règlement est d'application à partir du 26 mars 2027<sup class=\"cite\" id=\"t-CLM-96d3720e\" data-claims=\"CLM-96d3720e\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup>. Les\n  dispositions sur l'enregistrement et l'échange (art. 3-15) s'appliquent à partir du 26 mars 2029 pour le résumé\n  patient, la e-prescription et la e-délivrance, et à partir du 26 mars 2031 pour l'imagerie, les résultats de\n  tests et les rapports de sortie<span class=\"cite-anchor\" id=\"t-CLM-c01f0160\"></span><sup class=\"cite\" id=\"t-CLM-14501017\" data-claims=\"CLM-14501017 CLM-c01f0160\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup>. Le chapitre IV (utilisation secondaire)\n  s'applique à partir du 26 mars 2029<sup class=\"cite\" id=\"t-CLM-943c06f1\" data-claims=\"CLM-943c06f1\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup>, certaines catégories de l'art. 51(1) seulement à partir\n  du 26 mars 2031<sup class=\"cite\" id=\"t-CLM-4a614894\" data-claims=\"CLM-4a614894\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup>.</li>\n<li><strong>Oui (avec ces dates d'application)</strong> : la Commission fixe pour le 26 mars 2027 les spécifications techniques\n  du <a href=\"/fr/format-europeen-d-echange-des-dossiers-de-sante-informatises/\">EEHRxF</a><sup class=\"cite\" id=\"t-CLM-14a07bfc\" data-claims=\"CLM-14a07bfc\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup> ; les prestataires de soins devront enregistrer des données prioritaires dans un système de DME<sup class=\"cite\" id=\"t-CLM-08580fc7\" data-claims=\"CLM-08580fc7\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup> ; les détenteurs de données devront notamment mettre des données de DME à disposition pour l'utilisation secondaire<sup class=\"cite\" id=\"t-CLM-eb2f08a7\" data-claims=\"CLM-eb2f08a7\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup>.</li>\n<li><strong>Orientation FHIR</strong> : HL7 Europe a publié des guides d'implémentation FHIR Base et Core à l'appui de l'EHDS\n<sup class=\"cite\" id=\"t-CLM-c6b73f2f\" data-claims=\"CLM-c6b73f2f\"><a class=\"cite-ref\" href=\"#bron-29\" aria-label=\"Source 29\">[29]</a></sup> ; la Belgique plaide pour une seule norme FHIR européenne par type de message<sup class=\"cite\" id=\"t-CLM-c444a1e8\" data-claims=\"CLM-c444a1e8\"><a class=\"cite-ref\" href=\"#bron-30\" aria-label=\"Source 30\">[30]</a></sup>.\n  Il s'agit d'une position belge, pas d'une décision de l'UE.</li>\n<li><strong>Non (trouvé)</strong> : fin 2023, un panel d'experts affirmait, à propos de la proposition d'EHDS de l'époque, que\n  l'EHDS ne règle pas de standards concrets<sup class=\"cite\" id=\"t-CLM-2906b45d\" data-claims=\"CLM-2906b45d\"><a class=\"cite-ref\" href=\"#bron-2\" aria-label=\"Source 2\">[2]</a></sup> ; le règlement définitif délègue bien les\n  spécifications techniques de l'EEHRxF à des actes d'exécution<sup class=\"cite\" data-claims=\"CLM-14a07bfc\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup>, qui peuvent contenir des\n  standards concrets (interprétation). Dans le <a href=\"/fr/donneessante-ue/\">projet pilote DonnéesDeSanté@UE</a>, OMOP était une\n  option, pas une obligation<sup class=\"cite\" id=\"t-CLM-c4f61547\" data-claims=\"CLM-c4f61547\"><a class=\"cite-ref\" href=\"#bron-31\" aria-label=\"Source 31\">[31]</a></sup> ; un cadre académique cite OMOP comme standard, mais c'est une\n  proposition<sup class=\"cite\" id=\"t-CLM-f8e9a39f\" data-claims=\"CLM-f8e9a39f\"><a class=\"cite-ref\" href=\"#bron-22\" aria-label=\"Source 22\">[22]</a></sup>. Pour openEHR, aucune référence à l'EHDS n'a été trouvée (lacune).</li>\n</ul>"
  },
  {
   "id": "qu-est-ce-que-cela-signifie-pour-un-hopital",
   "title": "Qu'est-ce que cela signifie pour un hôpital ?",
   "kind": "tekst",
   "html": "<ul>\n<li><strong>Obligation (UE, future)</strong> : enregistrer des données prioritaires dans un système de DME et les échanger dans\n  l'EEHRxF, par phases à partir du 26 mars 2029 (résumé patient, e-prescription, e-délivrance) et du 26 mars 2031\n  (imagerie, résultats de tests, rapports de sortie)<sup class=\"cite\" data-claims=\"CLM-08580fc7 CLM-14a07bfc CLM-14501017 CLM-c01f0160\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup>.\n  Le format technique sera fixé par des actes d'exécution ; que ce soit FHIR n'est pas confirmé.</li>\n<li><strong>Choix politique Belgique</strong> : des champs de l'EEHRxF sont aussi utilisés dans les CareSets belges<sup class=\"cite\" id=\"t-CLM-57376d36\" data-claims=\"CLM-57376d36\"><a class=\"cite-ref\" href=\"#bron-30\" aria-label=\"Source 30\">[30]</a></sup>.</li>\n<li><strong>Réseau</strong> : il existe un nœud OHDSI belge, issu de la communauté EHDEN<sup class=\"cite\" data-claims=\"CLM-ba340bd5\"><a class=\"cite-ref\" href=\"#bron-20\" aria-label=\"Source 20\">[20]</a></sup>.\n  <strong>Recommandation :</strong> envisager une participation OMOP via EHDEN ou le nœud OHDSI belge en cas de question de\n  recherche concrète.</li>\n<li>\n<p class=\"aanbeveling\"><strong>Recommandation</strong> : voir Conclusion.</p>\n</li>\n<li>\n<p class=\"aanbeveling\"><strong>Recommandation</strong> : traiter les profils FHIR comme couche d'échange, suivre les actes d'exécution relatifs à\n  l'EEHRxF et évaluer séparément openEHR et OMOP comme choix pour le stockage clinique et la recherche. Conserver\n  les données sources comme référence, car la conversion vers OMOP peut faire perdre de l'information.</p>\n</li>\n</ul>\n<h3>Conditions d'implémentation et limites</h3>\n<p>Les guides d'implémentation belges sont en R4, alors que le guide d'implémentation FHIR-to-OMOP repose sur R5 et\nUS Core<sup class=\"cite\" data-claims=\"CLM-4c97a5a4 CLM-77f1c57f\"><a class=\"cite-ref\" href=\"#bron-19\" aria-label=\"Source 19\">[19]</a><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup> ; une application directe demande donc une traduction. Pour l'utilisation\nde SNOMED CT dans les profils core-clinical belges, une licence Affiliate est nécessaire<sup class=\"cite\" id=\"t-CLM-ac8d824b\" data-claims=\"CLM-ac8d824b\"><a class=\"cite-ref\" href=\"#bron-32\" aria-label=\"Source 32\">[32]</a></sup>.</p>"
  },
  {
   "id": "incertitudes-et-informations-contradictoires",
   "title": "Incertitudes et informations contradictoires",
   "kind": "tekst",
   "html": "<ul>\n<li>Le guide d'implémentation FHIR-to-OMOP vise le CDM v5.4, alors qu'OHDSI cite v5.5 comme version actuelle ; v5.5\n  est compatible avec v5.4, il s'agit donc d'un décalage dans le temps<sup class=\"cite\" data-claims=\"CLM-77f1c57f CLM-8016d826 CLM-ac400acb\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a><a class=\"cite-ref\" href=\"#bron-5\" aria-label=\"Source 5\">[5]</a><a class=\"cite-ref\" href=\"#bron-14\" aria-label=\"Source 14\">[14]</a></sup>.</li>\n<li>Les actes d'exécution relatifs à l'EEHRxF ne sont attendus que début 2027<sup class=\"cite\" data-claims=\"CLM-c6b73f2f\"><a class=\"cite-ref\" href=\"#bron-29\" aria-label=\"Source 29\">[29]</a></sup> ; savoir s'ils\n  prescriront FHIR de manière normative reste ouvert.</li>\n<li>L'usage d'openEHR en Belgique n'a pas été trouvé.</li>\n<li>L'affirmation selon laquelle l'EHDS ne règle pas de standards concrets<sup class=\"cite\" data-claims=\"CLM-2906b45d\"><a class=\"cite-ref\" href=\"#bron-2\" aria-label=\"Source 2\">[2]</a></sup> date de décembre 2023 et\n  porte sur la proposition de l'époque ; le règlement définitif délègue les spécifications techniques à des actes\n  d'exécution<sup class=\"cite\" data-claims=\"CLM-14a07bfc\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup>. Les deux affirmations ne sont pas contradictoires, mais la première est datée.</li>\n</ul>"
  }
 ],
 "relation_groups": [
  {
   "type": "about",
   "direction": "uit",
   "label": "porte sur",
   "relations": [
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "fhir",
      "title": "HL7 FHIR",
      "url": "/fr/hl7-fhir/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      1,
      3
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "openehr",
      "title": "openEHR",
      "url": "/fr/openehr/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      2,
      4
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "omop-cdm",
      "title": "OMOP CDM et OHDSI",
      "url": "/fr/omop-cdm-et-ohdsi/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      1,
      5
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "snomed-ct",
      "title": "SNOMED CT",
      "url": "/fr/snomed-ct/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      22,
      17
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "loinc",
      "title": "LOINC et le sous-ensemble belge (ReTaM)",
      "url": "/fr/loinc-et-le-sous-ensemble-belge-retam/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      22,
      16
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "ehds",
      "title": "EHDS (Espace européen des données de santé)",
      "url": "/fr/espace-europeen-des-donnees-de-sante/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": "De EHDS laat de technische specificaties van het uitwisselingsformaat via uitvoeringshandelingen vastleggen; voor persistentie- of analysemodellen werd geen EHDS-verplichting gevonden.",
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      28,
      2
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "be-fhir-igs",
      "title": "Guides d'implémentation FHIR belges",
      "url": "/fr/guides-d-implementation-fhir-belges/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      19,
      23
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "eehrxf",
      "title": "EEHRxF (format européen d'échange des dossiers de santé informatisés)",
      "url": "/fr/format-europeen-d-echange-des-dossiers-de-sante-informatises/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      28
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "healthdata-at-eu",
      "title": "DonnéesDeSanté@UE",
      "url": "/fr/donneessante-ue/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": "OMOP was in de HealthData@EU-pilot een optie, geen verplichting.",
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      31
     ]
    }
   ]
  },
  {
   "type": "comparedWith",
   "direction": "in",
   "label": "est comparé à (entrant)",
   "relations": [
    {
     "direction": "in",
     "type": "comparedWith",
     "label": "est comparé à (entrant)",
     "other": {
      "id": "omop-cdm",
      "title": "OMOP CDM et OHDSI",
      "url": "/fr/omop-cdm-et-ohdsi/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      1
     ]
    },
    {
     "direction": "in",
     "type": "comparedWith",
     "label": "est comparé à (entrant)",
     "other": {
      "id": "openehr",
      "title": "openEHR",
      "url": "/fr/openehr/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      2
     ]
    }
   ]
  }
 ],
 "relation_count": 11,
 "hypothesis_count": 0,
 "neighbours": [
  {
   "id": "fhir",
   "title": "HL7 FHIR",
   "url": "/fr/hl7-fhir/",
   "type": {
    "code": "Specification",
    "label": "Norme ou spécification"
   },
   "status": "established"
  },
  {
   "id": "openehr",
   "title": "openEHR",
   "url": "/fr/openehr/",
   "type": {
    "code": "Specification",
    "label": "Norme ou spécification"
   },
   "status": "established"
  },
  {
   "id": "omop-cdm",
   "title": "OMOP CDM et OHDSI",
   "url": "/fr/omop-cdm-et-ohdsi/",
   "type": {
    "code": "Specification",
    "label": "Norme ou spécification"
   },
   "status": "established"
  },
  {
   "id": "snomed-ct",
   "title": "SNOMED CT",
   "url": "/fr/snomed-ct/",
   "type": {
    "code": "Terminology",
    "label": "Terminologie ou classification"
   },
   "status": "established"
  },
  {
   "id": "loinc",
   "title": "LOINC et le sous-ensemble belge (ReTaM)",
   "url": "/fr/loinc-et-le-sous-ensemble-belge-retam/",
   "type": {
    "code": "Terminology",
    "label": "Terminologie ou classification"
   },
   "status": "established"
  },
  {
   "id": "ehds",
   "title": "EHDS (Espace européen des données de santé)",
   "url": "/fr/espace-europeen-des-donnees-de-sante/",
   "type": {
    "code": "LegalAct",
    "label": "Acte législatif"
   },
   "status": "established"
  },
  {
   "id": "be-fhir-igs",
   "title": "Guides d'implémentation FHIR belges",
   "url": "/fr/guides-d-implementation-fhir-belges/",
   "type": {
    "code": "Specification",
    "label": "Norme ou spécification"
   },
   "status": "established"
  },
  {
   "id": "eehrxf",
   "title": "EEHRxF (format européen d'échange des dossiers de santé informatisés)",
   "url": "/fr/format-europeen-d-echange-des-dossiers-de-sante-informatises/",
   "type": {
    "code": "Specification",
    "label": "Norme ou spécification"
   },
   "status": "established"
  },
  {
   "id": "healthdata-at-eu",
   "title": "DonnéesDeSanté@UE",
   "url": "/fr/donneessante-ue/",
   "type": {
    "code": "Platform",
    "label": "Plateforme ou service"
   },
   "status": "established"
  }
 ],
 "open_questions_html": [
  "Welke Belgische of Europese referentiearchitectuur combineert FHIR, openEHR en OMOP expliciet (bv. richtlijnen van de Health Data Agency)?",
  "Wanneer volgt de HL7 FHIR-to-OMOP IG op OMOP CDM v5.5, en komt er een R4-variant die aansluit op de Belgische R4-IG's?",
  "Wordt openEHR in België gebruikt door ziekenhuizen of EPD-leveranciers? Niet gevonden.",
  "Bestaat er een officiële mappingstandaard openEHR↔OMOP? Niet gevonden.",
  "Verwijzen de EEHRxF-uitvoeringshandelingen (verwacht begin 2027) normatief naar FHIR?",
  "Komt er een Atlas-conceptpagina voor openEHR (relatie nu naar een nog aan te maken concept)?"
 ],
 "open_questions": [
  {
   "id": "oq-b2207a",
   "html": "Welke Belgische of Europese referentiearchitectuur combineert FHIR, openEHR en OMOP expliciet (bv. richtlijnen van de Health Data Agency)?",
   "text": "Welke Belgische of Europese referentiearchitectuur combineert FHIR, openEHR en OMOP expliciet (bv. richtlijnen van de Health Data Agency)?"
  },
  {
   "id": "oq-af3637",
   "html": "Wanneer volgt de HL7 FHIR-to-OMOP IG op OMOP CDM v5.5, en komt er een R4-variant die aansluit op de Belgische R4-IG's?",
   "text": "Wanneer volgt de HL7 FHIR-to-OMOP IG op OMOP CDM v5.5, en komt er een R4-variant die aansluit op de Belgische R4-IG's?"
  },
  {
   "id": "oq-3f16b8",
   "html": "Wordt openEHR in België gebruikt door ziekenhuizen of EPD-leveranciers? Niet gevonden.",
   "text": "Wordt openEHR in België gebruikt door ziekenhuizen of EPD-leveranciers? Niet gevonden."
  },
  {
   "id": "oq-dd36c7",
   "html": "Bestaat er een officiële mappingstandaard openEHR↔OMOP? Niet gevonden.",
   "text": "Bestaat er een officiële mappingstandaard openEHR↔OMOP? Niet gevonden."
  },
  {
   "id": "oq-493197",
   "html": "Verwijzen de EEHRxF-uitvoeringshandelingen (verwacht begin 2027) normatief naar FHIR?",
   "text": "Verwijzen de EEHRxF-uitvoeringshandelingen (verwacht begin 2027) normatief naar FHIR?"
  },
  {
   "id": "oq-415aee",
   "html": "Komt er een Atlas-conceptpagina voor openEHR (relatie nu naar een nog aan te maken concept)?",
   "text": "Komt er een Atlas-conceptpagina voor openEHR (relatie nu naar een nog aan te maken concept)?"
  }
 ],
 "exchanges": [],
 "sources": [
  {
   "n": 1,
   "id": "SRC-4762fc1944",
   "title": "Vulcan FHIR to OMOP FHIR Implementation Guide",
   "publisher": "HL7 International / Biomedical Research and Regulation",
   "url": "https://hl7.org/fhir/uv/omop/en/index.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:23+00:00",
   "last_checked": "2026-09-26T05:59:20+00:00",
   "content_sha256": "99216bdc130a3b77ab7741f5d19a4676b50144790b4f7d2b39367b890761540e",
   "link_unreachable_since": null
  },
  {
   "n": 2,
   "id": "SRC-b22ee5ef19",
   "title": "Can OpenEHR, ISO 13606, and HL7 FHIR Work Together? An Agnostic Approach for the Selection and Application of Electronic Health Record Standards to the Next-Generation Health Data Spaces",
   "publisher": "JMIR Medical Informatics (Pedrera-Jiménez et al.)",
   "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC10784985/",
   "published": "2023-12-28",
   "first_retrieved": "2026-09-25T20:37:30+00:00",
   "last_checked": "2026-09-26T05:59:33+00:00",
   "content_sha256": "9f357748e628d69696d5db5db5f055822ae320cccb50df7488a5626757375edd",
   "link_unreachable_since": null
  },
  {
   "n": 3,
   "id": "SRC-8086ca6f2b",
   "title": "FHIR Overview (R4)",
   "publisher": "HL7 International",
   "url": "https://hl7.org/fhir/R4/overview.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:25+00:00",
   "last_checked": "2026-09-26T05:59:22+00:00",
   "content_sha256": "8b345c83b3da8aa4ea184a65e0f5c8e141cabcff927cdc3ec571bc644b8c8daa",
   "link_unreachable_since": null
  },
  {
   "n": 4,
   "id": "SRC-d2e10204e3",
   "title": "What is openEHR?",
   "publisher": "openEHR International",
   "url": "https://openehr.org/what-is-openehr/",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:20+00:00",
   "last_checked": "2026-09-26T05:59:16+00:00",
   "content_sha256": "c006e5b97f61bd7f436cb6249fe1ce9d74f3663698eb662ad6bab11995f2aa02",
   "link_unreachable_since": null
  },
  {
   "n": 5,
   "id": "SRC-51838ad661",
   "title": "OMOP Common Data Model",
   "publisher": "OHDSI CDM Working Group",
   "url": "https://ohdsi.github.io/CommonDataModel/",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:20+00:00",
   "last_checked": "2026-09-26T05:59:12+00:00",
   "content_sha256": "6fe8d89ada407d6817de8175f2e1f15e5ef18e7ea99c26bf640c5d12d862e992",
   "link_unreachable_since": null
  },
  {
   "n": 6,
   "id": "SRC-5d260b906d",
   "title": "HL7 Belgium",
   "publisher": "Agoria",
   "url": "https://www.agoria.be/en/hl7-belgium",
   "published": null,
   "first_retrieved": "2026-09-25T20:18:57+00:00",
   "last_checked": "2026-09-26T05:57:33+00:00",
   "content_sha256": "63b1b0d02a599293607227bb551e2be8c57666dc941ef1d08d322ba1dc805413",
   "link_unreachable_since": null
  },
  {
   "n": 7,
   "id": "SRC-f0063a5aab",
   "title": "HL7 FHIR Governance",
   "publisher": "eHealth-platform",
   "url": "https://www.ehealth.fgov.be/standards/kmehr/en/page/hl7-fhir-governance",
   "published": null,
   "first_retrieved": "2026-09-25T20:18:15+00:00",
   "last_checked": "2026-09-25T21:07:23+00:00",
   "content_sha256": "5b351ed6cd75b317183d83eb16907f2bebed48bec9467040ea96aab21bc35462",
   "link_unreachable_since": null
  },
  {
   "n": 8,
   "id": "SRC-8aef25830b",
   "title": "eHealth Standard FHIR - FHIR Implementation Guides",
   "publisher": "eHealth-platform",
   "url": "https://www.ehealth.fgov.be/standards/fhir/",
   "published": null,
   "first_retrieved": "2026-09-25T20:18:20+00:00",
   "last_checked": "2026-09-26T05:59:07+00:00",
   "content_sha256": "f6e363654537314c2cb0e66f88b308b34a2247e7fc93af942489e9387fc0cbe5",
   "link_unreachable_since": null
  },
  {
   "n": 9,
   "id": "SRC-bd6b94de2d",
   "title": "openEHR governance",
   "publisher": "openEHR International",
   "url": "https://openehr.org/governance/",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:22+00:00",
   "last_checked": "2026-09-26T05:59:18+00:00",
   "content_sha256": "2d84b9f488886117874d560ccdb911737ed79c0e9672fa578508938f8602e8d5",
   "link_unreachable_since": null
  },
  {
   "n": 10,
   "id": "SRC-33f54a15dd",
   "title": "openEHR Architecture Overview",
   "publisher": "openEHR Specification Program",
   "url": "https://specifications.openehr.org/releases/BASE/latest/architecture_overview.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:27+00:00",
   "last_checked": "2026-09-26T05:59:25+00:00",
   "content_sha256": "924316a34e4d3cfb6b0bdc193b1bfe51f1dd23d5ca439e3a3dfa59b1f7da396f",
   "link_unreachable_since": null
  },
  {
   "n": 11,
   "id": "SRC-277609bbe8",
   "title": "The Book of OHDSI - Chapter 4 The Common Data Model",
   "publisher": "OHDSI",
   "url": "https://ohdsi.github.io/TheBookOfOhdsi/CommonDataModel.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:23+00:00",
   "last_checked": "2026-09-26T05:59:19+00:00",
   "content_sha256": "d73621818f61e52fcfb5460acf5bdd863b943afa3e7f509609bbebe6fba24add",
   "link_unreachable_since": null
  },
  {
   "n": 12,
   "id": "SRC-ec315cc0fc",
   "title": "FHIR R5 (v5.0.0)",
   "publisher": "HL7 International",
   "url": "https://hl7.org/fhir/R5/index.html",
   "published": "2023-03-26",
   "first_retrieved": "2026-09-25T20:18:59+00:00",
   "last_checked": "2026-09-26T05:59:06+00:00",
   "content_sha256": "a3f30ce6ad0ea77b07d8654cf571de51d96e413a0c4f2174d87fa8e088bc1a74",
   "link_unreachable_since": null
  },
  {
   "n": 13,
   "id": "SRC-ec16ae26c1",
   "title": "FHIR R4 (v4.0.1)",
   "publisher": "HL7 International",
   "url": "https://hl7.org/fhir/R4/index.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:18:58+00:00",
   "last_checked": "2026-09-26T05:59:08+00:00",
   "content_sha256": "928d5f5069319624ba4864ffcb00f5d221bd5caf2a2f72237e9c2501abdd6c7d",
   "link_unreachable_since": null
  },
  {
   "n": 14,
   "id": "SRC-cf9241837b",
   "title": "CDM v5.5 (release v5.5.0)",
   "publisher": "OHDSI",
   "url": "https://github.com/OHDSI/CommonDataModel/releases/tag/v5.5.0",
   "published": "2026-08-25",
   "first_retrieved": "2026-09-25T20:37:23+00:00",
   "last_checked": "2026-09-26T05:59:21+00:00",
   "content_sha256": "ac2b47ef00edbe13dca6bde5a90067ea8e074addc2f8a86b23d9383d1a0b7f4e",
   "link_unreachable_since": null
  },
  {
   "n": 15,
   "id": "SRC-ddc1f2b720",
   "title": "FHIR Terminology Module (R4)",
   "publisher": "HL7 International, Vocabulary Work Group",
   "url": "https://hl7.org/fhir/R4/terminology-module.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:27+00:00",
   "last_checked": "2026-09-26T05:59:26+00:00",
   "content_sha256": "fe9b9dc3a9d63948824ecd44779b570eb368b32e3e598c608c49d3e3eac2e08e",
   "link_unreachable_since": null
  },
  {
   "n": 16,
   "id": "SRC-6f62e628f5",
   "title": "Using Codes in resources (R4)",
   "publisher": "HL7 International",
   "url": "https://hl7.org/fhir/R4/terminologies.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:29+00:00",
   "last_checked": "2026-09-26T05:59:29+00:00",
   "content_sha256": "c4d1a62631a2179224ae7123a144ef5c9c37fe5669240da70e16ad612bebe718",
   "link_unreachable_since": null
  },
  {
   "n": 17,
   "id": "SRC-9a557cfa23",
   "title": "The Book of OHDSI - Chapter 5 Standardized Vocabularies",
   "publisher": "OHDSI",
   "url": "https://ohdsi.github.io/TheBookOfOhdsi/StandardizedVocabularies.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:25+00:00",
   "last_checked": "2026-09-26T05:59:23+00:00",
   "content_sha256": "b5fa0ffe012907533944e35e1578706181941a6b4392fd54ed323268ca0a8da8",
   "link_unreachable_since": null
  },
  {
   "n": 18,
   "id": "SRC-bd069bf1c8",
   "title": "eHealth Platform Standards - Home (KMEHR)",
   "publisher": "eHealth-platform",
   "url": "https://www.ehealth.fgov.be/standards/kmehr/en",
   "published": null,
   "first_retrieved": "2026-09-25T20:18:06+00:00",
   "last_checked": "2026-09-25T21:07:13+00:00",
   "content_sha256": "31d7759c5f189a49bdc0f24c370693d1ad8fe80070429fb67bbd5ca3b586cae1",
   "link_unreachable_since": null
  },
  {
   "n": 19,
   "id": "SRC-c0c4b77571",
   "title": "BE Medication - Home",
   "publisher": "eHealth-platform",
   "url": "https://www.ehealth.fgov.be/standards/fhir/medication/en/index.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:18:36+00:00",
   "last_checked": "2026-09-25T21:07:40+00:00",
   "content_sha256": "2d52539b2c62b81502e1b821f0ff49c0844d9ed816a30f89ce6045eabf49fa1d",
   "link_unreachable_since": null
  },
  {
   "n": 20,
   "id": "SRC-8af9dba3d7",
   "title": "OHDSI Belgium - national node",
   "publisher": "OHDSI Europe",
   "url": "https://www.ohdsi-europe.org/index.php/national-nodes/belgium",
   "published": null,
   "first_retrieved": "2026-09-25T20:19:52+00:00",
   "last_checked": "2026-09-26T05:58:45+00:00",
   "content_sha256": "456efd283d0e2f54c444424a58c2c87f34b9c8d43c096c7633502b0546d8297d",
   "link_unreachable_since": null
  },
  {
   "n": 21,
   "id": "SRC-88258db489",
   "title": "Data Partners – EHDEN Foundation",
   "publisher": "EHDEN Foundation",
   "url": "https://www.ehden.eu/datapartners/",
   "published": null,
   "first_retrieved": "2026-09-25T20:19:52+00:00",
   "last_checked": "2026-09-26T05:59:05+00:00",
   "content_sha256": "2ac163c8f115082905a356a8d898cbc644539ffd022c83cca83bba4795bb5587",
   "link_unreachable_since": null
  },
  {
   "n": 22,
   "id": "SRC-55ef771c33",
   "title": "Interoperability Framework of the European Health Data Space for the Secondary Use of Data: Interactive European Interoperability Framework-Based Standards Compliance Toolkit for AI-Driven Projects",
   "publisher": "Journal of Medical Internet Research",
   "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC12059490/",
   "published": "2025",
   "first_retrieved": "2026-09-25T20:37:33+00:00",
   "last_checked": "2026-09-26T05:59:37+00:00",
   "content_sha256": "f4a7fb2c94de8f80d567d5cc5c10d71607c6e8eff3378691572bd242e59459c1",
   "link_unreachable_since": null
  },
  {
   "n": 23,
   "id": "SRC-4688612825",
   "title": "Guidance - eHealth Platform Federal Core Profiles v2.1.1",
   "publisher": "eHealth-platform",
   "url": "https://www.ehealth.fgov.be/standards/fhir/core/2.1.1/guidance.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:19:50+00:00",
   "last_checked": "2026-09-26T05:58:40+00:00",
   "content_sha256": "f42af07f72452e17e60f669fee2a0c5e2a22316c6d3bbdaf568012ad9c94b1b4",
   "link_unreachable_since": null
  },
  {
   "n": 24,
   "id": "SRC-fb93029bf0",
   "title": "HL7 Belgium FHIR IG - Lab related profiles: Guidance",
   "publisher": "eHealth-platform / HL7 Belgium",
   "url": "https://www.ehealth.fgov.be/standards/fhir/lab/guidance.html",
   "published": "2022-09-08",
   "first_retrieved": "2026-09-25T20:19:49+00:00",
   "last_checked": "2026-09-26T05:58:38+00:00",
   "content_sha256": "ffaa38773ca23656b6f83cb7b69d3956895028661c49bffc3a47681699195094",
   "link_unreachable_since": null
  },
  {
   "n": 25,
   "id": "SRC-5f6318ee1a",
   "title": "FHIR to OMOP FHIR IG (continuous build 2.0.0-ballot)",
   "publisher": "HL7 International / Biomedical Research and Regulation",
   "url": "https://build.fhir.org/ig/HL7/fhir-omop-ig/",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:24+00:00",
   "last_checked": "2026-09-26T05:59:22+00:00",
   "content_sha256": "4c407afe3f967c32a95418fec31f1ec43d1c95d3eaf0adfac905c2a8bb242761",
   "link_unreachable_since": null
  },
  {
   "n": 26,
   "id": "SRC-c911dbe4d4",
   "title": "openEHR-FHIR Data Type Mapping IG (broncode)",
   "publisher": "openehr-fhir (GitHub)",
   "url": "https://github.com/openehr-fhir/data-type-mapping-ig",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:31+00:00",
   "last_checked": "2026-09-26T05:59:36+00:00",
   "content_sha256": "a3218f26e6f68ded0c32003ea9583d791e109fb9aadd64dedba6697aa7125b14",
   "link_unreachable_since": null
  },
  {
   "n": 27,
   "id": "SRC-36bd69feaa",
   "title": "FHIRconnect: Towards a seamless integration of openEHR and FHIR",
   "publisher": "arXiv (preprint)",
   "url": "https://arxiv.org/abs/2511.14618",
   "published": "2025-11-18",
   "first_retrieved": "2026-09-25T20:37:29+00:00",
   "last_checked": "2026-09-26T05:59:28+00:00",
   "content_sha256": "f2315566b00641dcc5e2f19ad94628606975d4697682ab3b13e184005b763026",
   "link_unreachable_since": null
  },
  {
   "n": 28,
   "id": "SRC-af26b6d770",
   "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
   "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
   "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
   "published": "2025-03-05",
   "first_retrieved": "2026-09-25T20:37:19+00:00",
   "last_checked": "2026-09-26T06:04:07+00:00",
   "content_sha256": "87d9f6722e7949ce9b443204467cfd3bd9d0d1137b5e3ba6b705ea39800439d3",
   "link_unreachable_since": null
  },
  {
   "n": 29,
   "id": "SRC-f046cd4082",
   "title": "New HL7 Europe FHIR Implementation Guides to support the European Health Data Space",
   "publisher": "HL7 International (HL7 News)",
   "url": "https://hl7news.hl7.org/2026/01/02/new-hl7-europe-fhir-implementation-guides-to-support-the-european-health-data-space/",
   "published": "2026-01-02",
   "first_retrieved": "2026-09-25T20:37:29+00:00",
   "last_checked": "2026-09-26T05:59:31+00:00",
   "content_sha256": "8af576865dbdb03044ea21749b2771424be2259cb957951ed2da4d290b992901",
   "link_unreachable_since": null
  },
  {
   "n": 30,
   "id": "SRC-41ee539e0b",
   "title": "EHDS (European Health Data Space) - De Europese Verordening betreffende de Europese ruimte voor gezondheidsgegevens",
   "publisher": "eHealth-platform",
   "url": "https://www.ehealth.fgov.be/nl/page/ehds-european-health-data-space-de-europese-verordening-betreffende-de-europese-ruimte-voor-gezondheidsgegevens",
   "published": null,
   "first_retrieved": "2026-09-25T20:37:20+00:00",
   "last_checked": "2026-09-26T05:59:11+00:00",
   "content_sha256": "528e11d81be69835077c2d38f4c820a35a1ffea7993ebde3794d59759ac10064",
   "link_unreachable_since": null
  },
  {
   "n": 31,
   "id": "SRC-b280053090",
   "title": "The European Health Data Space in communicable diseases surveillance and monitoring of medicines and vaccines: achievements of a pilot project examining the user journey",
   "publisher": "European Journal of Public Health",
   "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC12420905/",
   "published": "2025",
   "first_retrieved": "2026-09-25T20:37:31+00:00",
   "last_checked": "2026-09-26T05:59:35+00:00",
   "content_sha256": "299c7d270302c921ce0bd293c193db467cbd7cd6810b0e8c6d1bd43e930abb3e",
   "link_unreachable_since": null
  },
  {
   "n": 32,
   "id": "SRC-854e8cb270",
   "title": "HL7 Belgium FHIR IG - core-clinical profiles: Home",
   "publisher": "eHealth-platform / HL7 Belgium",
   "url": "https://www.ehealth.fgov.be/standards/fhir/core-clinical/en/index.html",
   "published": null,
   "first_retrieved": "2026-09-25T20:19:54+00:00",
   "last_checked": "2026-09-26T05:58:55+00:00",
   "content_sha256": "8902deb6ebf26e8b85a19d9145f2a2ef94fcd97546539f40e79ba15d3ba4aed4",
   "link_unreachable_since": null
  }
 ],
 "claims": [
  {
   "id": "CLM-cfdf8dac",
   "statement": "De IG onderscheidt drie datadomeinen: klinische zorg en administratie, data-uitwisseling, en longitudinale analyse. Dat is het kader voor de vergelijking.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Home, sectie over ontwerpdomeinen",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-4762fc1944",
    "title": "Vulcan FHIR to OMOP FHIR Implementation Guide",
    "publisher": "HL7 International / Biomedical Research and Regulation",
    "url": "https://hl7.org/fhir/uv/omop/en/index.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-2dc7d72b",
   "statement": "De IG ziet FHIR en OMOP als complementair, niet concurrerend.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Home",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-4762fc1944",
    "title": "Vulcan FHIR to OMOP FHIR Implementation Guide",
    "publisher": "HL7 International / Biomedical Research and Regulation",
    "url": "https://hl7.org/fhir/uv/omop/en/index.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-3ccf652d",
   "statement": "Het panel besluit dat openEHR, ISO 13606 en FHIR elk nuttig zijn voor hun eigen doel en functioneel en technisch samen inzetbaar zijn.",
   "kind": "research-finding",
   "kind_label": "résultat de recherche",
   "locator": "Conclusions",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-b22ee5ef19",
    "title": "Can OpenEHR, ISO 13606, and HL7 FHIR Work Together? An Agnostic Approach for the Selection and Application of Electronic Health Record Standards to the Next-Generation Health Data Spaces",
    "publisher": "JMIR Medical Informatics (Pedrera-Jiménez et al.)",
    "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC10784985/",
    "published": "2023-12-28"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-20ccab31",
   "statement": "FHIR est une norme pour l'échange électronique d'informations de santé.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Overview, alinea 1",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-8086ca6f2b",
    "title": "FHIR Overview (R4)",
    "publisher": "HL7 International",
    "url": "https://hl7.org/fhir/R4/overview.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-6c1c8ed6",
   "statement": "De Vulcan-IG plaatst FHIR in het domein van data-uitwisseling (REST-API, resources, rijke lokale terminologie).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Home, sectie over ontwerpdomeinen",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-4762fc1944",
    "title": "Vulcan FHIR to OMOP FHIR Implementation Guide",
    "publisher": "HL7 International / Biomedical Research and Regulation",
    "url": "https://hl7.org/fhir/uv/omop/en/index.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-75e965e1",
   "statement": "openEHR richt zich via 'multi-level modeling' op het scheiden van de technische opslag van de klinische betekenis, zodat systemen kunnen evolueren zonder dataverlies.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'What makes openEHR different?'",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-d2e10204e3",
    "title": "What is openEHR?",
    "publisher": "openEHR International",
    "url": "https://openehr.org/what-is-openehr/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-a5de0448",
   "statement": "Een expertpanel (JMIR Med Inform 2023) stelt dat openEHR een volledig platformmodel biedt voor registratie, persistentie en querying, terwijl FHIR en ISO 13606 daarvoor externe ontwikkelingen nodig hebben en zich op uitwisseling richten.",
   "kind": "research-finding",
   "kind_label": "résultat de recherche",
   "locator": "sectie Results/Discussion",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-b22ee5ef19",
    "title": "Can OpenEHR, ISO 13606, and HL7 FHIR Work Together? An Agnostic Approach for the Selection and Application of Electronic Health Record Standards to the Next-Generation Health Data Spaces",
    "publisher": "JMIR Medical Informatics (Pedrera-Jiménez et al.)",
    "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC10784985/",
    "published": "2023-12-28"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-0d763233",
   "statement": "De OMOP CDM is een open community-datastandaard om structuur en inhoud van observationele data te standaardiseren voor efficiënte analyses met betrouwbare evidentie.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Home",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-51838ad661",
    "title": "OMOP Common Data Model",
    "publisher": "OHDSI CDM Working Group",
    "url": "https://ohdsi.github.io/CommonDataModel/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-e6250916",
   "statement": "Volgens dezelfde IG hoort OMOP in het domein van longitudinale analyse: relationeel, patiëntgericht, met OHDSI Standardized Vocabularies en vergelijkbaarheid tussen sites boven bronfideliteit.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Home, sectie over ontwerpdomeinen",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-4762fc1944",
    "title": "Vulcan FHIR to OMOP FHIR Implementation Guide",
    "publisher": "HL7 International / Biomedical Research and Regulation",
    "url": "https://hl7.org/fhir/uv/omop/en/index.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-6070feb3",
   "statement": "HL7 Belgium is de Belgische affiliate van HL7 International, opgericht in juni 2019 en erkend in april 2020.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "pagina HL7 Belgium",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-5d260b906d",
    "title": "HL7 Belgium",
    "publisher": "Agoria",
    "url": "https://www.agoria.be/en/hl7-belgium",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-cef569f6",
   "statement": "In stap 3.2 van de governance werken HL7 Belgium-werkgroepen het datamodel en de FHIR-profielen uit.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Step 3.2",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-f0063a5aab",
    "title": "HL7 FHIR Governance",
    "publisher": "eHealth-platform",
    "url": "https://www.ehealth.fgov.be/standards/kmehr/en/page/hl7-fhir-governance",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-43dc8f12",
   "statement": "La plate-forme eHealth publie, lorsque c'est nécessaire, des profils FHIR et des guides d'implémentation spécifiques pour des initiatives fédérales sur ehealth.fgov.be/standards/fhir.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "intro 'FHIR profiles'",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-8aef25830b",
    "title": "eHealth Standard FHIR - FHIR Implementation Guides",
    "publisher": "eHealth-platform",
    "url": "https://www.ehealth.fgov.be/standards/fhir/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-f455020e",
   "statement": "openEHR International (openEHR CIC) is een Britse not-for-profit ledenvennootschap die sinds 10 mei 2019 het operationeel beheer voert; de openEHR Foundation houdt het intellectueel eigendom.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Organisational structure'",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-bd6b94de2d",
    "title": "openEHR governance",
    "publisher": "openEHR International",
    "url": "https://openehr.org/governance/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-c6ad972d",
   "statement": "Specificaties, software en klinische modellen (archetypes, templates) zijn kosteloos en ook commercieel bruikbaar; de specificaties vallen onder CC-BY-ND.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie Principles",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-bd6b94de2d",
    "title": "openEHR governance",
    "publisher": "openEHR International",
    "url": "https://openehr.org/governance/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-8016d826",
   "statement": "De huidige OMOP CDM-versie is v5.5 (release v5.5.0 op GitHub, 25 augustus 2026); de CDM wordt beheerd door de OHDSI CDM Working Group.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Current CDM Version'",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-51838ad661",
    "title": "OMOP Common Data Model",
    "publisher": "OHDSI CDM Working Group",
    "url": "https://ohdsi.github.io/CommonDataModel/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-d3f779a6",
   "statement": "La ressource est la brique de base: tout contenu échangeable est une ressource. REST est courant, mais n'est pas obligatoire pour utiliser des ressources.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Overview",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-8086ca6f2b",
    "title": "FHIR Overview (R4)",
    "publisher": "HL7 International",
    "url": "https://hl7.org/fhir/R4/overview.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-5472e46b",
   "statement": "Bij multi-level modelling is het referentiemodel een stabiel objectmodel waarop software en data worden gebouwd; archetypes en templates vormen het domeinniveau.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Archetypes and Templates'",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-33f54a15dd",
    "title": "openEHR Architecture Overview",
    "publisher": "openEHR Specification Program",
    "url": "https://specifications.openehr.org/releases/BASE/latest/architecture_overview.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-f3a32110",
   "statement": "Templates combineren archetypes tot volledige Compositions (bv. ontslagbrief) en zijn meestal lokaal, terwijl archetypes breed hergebruikt worden.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Archetypes and Templates'",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-33f54a15dd",
    "title": "openEHR Architecture Overview",
    "publisher": "openEHR Specification Program",
    "url": "https://specifications.openehr.org/releases/BASE/latest/architecture_overview.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-b378c72d",
   "statement": "De CDM is een persoonsgericht model: alle klinische event-tabellen hangen aan de PERSON-tabel voor een longitudinaal beeld.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "hoofdstuk 4.1",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-277609bbe8",
    "title": "The Book of OHDSI - Chapter 4 The Common Data Model",
    "publisher": "OHDSI",
    "url": "https://ohdsi.github.io/TheBookOfOhdsi/CommonDataModel.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-22b16816",
   "statement": "Volgens de FHIR R4-specificatie hoeft men geen REST te gebruiken om FHIR-resources te gebruiken.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Overview, sectie resources",
   "as_of": "2026-09-26",
   "source": {
    "id": "SRC-8086ca6f2b",
    "title": "FHIR Overview (R4)",
    "publisher": "HL7 International",
    "url": "https://hl7.org/fhir/R4/overview.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-8025c8fd",
   "statement": "Queries gebeuren in AQL (Archetype Query Language), een synthese van SQL en XPath-achtige paden uit archetypes.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie over querying",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-33f54a15dd",
    "title": "openEHR Architecture Overview",
    "publisher": "openEHR Specification Program",
    "url": "https://specifications.openehr.org/releases/BASE/latest/architecture_overview.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-5eaebd11",
   "statement": "De OMOP CDM schrijft geen specifieke technologie voor; ze kan in elke relationele database (bv. Oracle, SQL Server) of als SAS-analysedatasets worden gerealiseerd.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 4.1 (design principles, technology neutrality)",
   "as_of": "2026-09-26",
   "source": {
    "id": "SRC-277609bbe8",
    "title": "The Book of OHDSI - Chapter 4 The Common Data Model",
    "publisher": "OHDSI",
    "url": "https://ohdsi.github.io/TheBookOfOhdsi/CommonDataModel.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-9566eb8c",
   "statement": "FHIR R5 (v5.0.0) a été publié le 26 mars 2023 et constitue la version actuellement publiée de FHIR (statut STU).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "voettekst",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-ec315cc0fc",
    "title": "FHIR R5 (v5.0.0)",
    "publisher": "HL7 International",
    "url": "https://hl7.org/fhir/R5/index.html",
    "published": "2023-03-26"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-1badcbfb",
   "statement": "FHIR R4 (v4.0.1, Technical Correction #1) est un mélange de contenu normatif et de contenu STU; la publication 4.0.1 date du 1er novembre 2019.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "voettekst",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-ec16ae26c1",
    "title": "FHIR R4 (v4.0.1)",
    "publisher": "HL7 International",
    "url": "https://hl7.org/fhir/R4/index.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-f00aa165",
   "statement": "De geraadpleegde Architecture Overview is BASE Release-1.2.0 met status STABLE.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "documentkop",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-33f54a15dd",
    "title": "openEHR Architecture Overview",
    "publisher": "openEHR Specification Program",
    "url": "https://specifications.openehr.org/releases/BASE/latest/architecture_overview.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-ac400acb",
   "statement": "v5.5 voegt enkel niet-verplichte velden en vocabulariummetadatatabellen toe; er werd niets verwijderd of hernoemd ten opzichte van v5.4.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie Summary",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-cf9241837b",
    "title": "CDM v5.5 (release v5.5.0)",
    "publisher": "OHDSI",
    "url": "https://github.com/OHDSI/CommonDataModel/releases/tag/v5.5.0",
    "published": "2026-08-25"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-81841f02",
   "statement": "Le module de terminologie (CodeSystem, ValueSet, ConceptMap, services de terminologie) permet d'exprimer et de communiquer des données codées en FHIR.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Introduction",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-ddc1f2b720",
    "title": "FHIR Terminology Module (R4)",
    "publisher": "HL7 International, Vocabulary Work Group",
    "url": "https://hl7.org/fhir/R4/terminology-module.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-89c84b92",
   "statement": "Pour l'échange, chaque système de codes reçoit une URL (p. ex. http://loinc.org, http://snomed.info/sct), de sorte que l'origine de chaque code soit explicite.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie over code systems en value sets",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-6f62e628f5",
    "title": "Using Codes in resources (R4)",
    "publisher": "HL7 International",
    "url": "https://hl7.org/fhir/R4/terminologies.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-19680c4c",
   "statement": "Archetypes en templates vormen de semantische toegangspoort naar terminologieën en classificaties.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 4.1.1 Multi-level Modelling and Archetypes",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-33f54a15dd",
    "title": "openEHR Architecture Overview",
    "publisher": "openEHR Specification Program",
    "url": "https://specifications.openehr.org/releases/BASE/latest/architecture_overview.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-5068e15a",
   "statement": "De OHDSI Standardized Vocabularies zijn een centraal onderdeel van de OMOP CDM.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Home",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-51838ad661",
    "title": "OMOP Common Data Model",
    "publisher": "OHDSI CDM Working Group",
    "url": "https://ohdsi.github.io/CommonDataModel/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-8b25e1f2",
   "statement": "Per klinisch event wordt één Standard Concept gekozen; bij aandoeningen is dat SNOMED, en ICD- of andere broncodes worden erop gemapt.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 5.2.6 Standard Concepts",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-9a557cfa23",
    "title": "The Book of OHDSI - Chapter 5 Standardized Vocabularies",
    "publisher": "OHDSI",
    "url": "https://ohdsi.github.io/TheBookOfOhdsi/StandardizedVocabularies.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-a8067de8",
   "statement": "Dans le cadre du plan d'action e-Santé 2019-2021 (cluster 0.5), HL7 FHIR est la norme préférentielle en Belgique: les nouveaux flux de données utilisent de préférence FHIR, les nouvelles interfaces de préférence FHIR REST.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'concerning FHIR'",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-bd069bf1c8",
    "title": "eHealth Platform Standards - Home (KMEHR)",
    "publisher": "eHealth-platform",
    "url": "https://www.ehealth.fgov.be/standards/kmehr/en",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-4c97a5a4",
   "statement": "Les IG belges sont des IG R4 également utilisables avec des systèmes R4B; des paquets R4 et R4B sont proposés. Aucun IG belge publié n'est basé sur FHIR R5; les éléments R5 sont utilisés dans R4 au moyen d'extensions cross-version.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie cross-version analysis / dependencies",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-c0c4b77571",
    "title": "BE Medication - Home",
    "publisher": "eHealth-platform",
    "url": "https://www.ehealth.fgov.be/standards/fhir/medication/en/index.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-ba340bd5",
   "statement": "De Belgische OHDSI-node ontstond spontaan uit de Belgische EHDEN-gemeenschap en behoort tot de meest actieve in Europa.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "inleiding",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-8af9dba3d7",
    "title": "OHDSI Belgium - national node",
    "publisher": "OHDSI Europe",
    "url": "https://www.ohdsi-europe.org/index.php/national-nodes/belgium",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-23727b49",
   "statement": "EHDEN lijst 14 Belgische datapartners (Brussel en Vlaanderen): overwegend ziekenhuizen, aangevuld met enkele bedrijven en een universitair MS-centrum.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "lijst BENELUX > Belgium (14)",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-88258db489",
    "title": "Data Partners – EHDEN Foundation",
    "publisher": "EHDEN Foundation",
    "url": "https://www.ehden.eu/datapartners/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-85e934d1",
   "statement": "Volgens een JMIR-artikel (2025) gebruiken FHIR (CodeSystems) en OMOP (OHDSI-vocabularia) dezelfde internationale terminologieën; OMOP past beter bij analyse dan bij operationele uitwisseling.",
   "kind": "research-finding",
   "kind_label": "résultat de recherche",
   "locator": "sectie Discussion (FHIR vs OMOP)",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-55ef771c33",
    "title": "Interoperability Framework of the European Health Data Space for the Secondary Use of Data: Interactive European Interoperability Framework-Based Standards Compliance Toolkit for AI-Driven Projects",
    "publisher": "Journal of Medical Internet Research",
    "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC12059490/",
    "published": "2025"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-530b635f",
   "statement": "Selon la guidance des profils FHIR fédéraux (Federal Core Profiles v2.1.1) de la Plate-forme eHealth, SNOMED CT est le codage préférentiel dans le contexte belge, soutenu par le SPF Santé publique.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie SNOMED-CT",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-4688612825",
    "title": "Guidance - eHealth Platform Federal Core Profiles v2.1.1",
    "publisher": "eHealth-platform",
    "url": "https://www.ehealth.fgov.be/standards/fhir/core/2.1.1/guidance.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-e0e48933",
   "statement": "Dans le Lab-IG FHIR belge (v1.0.0, Trial Use), les résultats de laboratoire doivent (SHALL) être codés en LOINC selon le sous-ensemble du SPF Santé publique; sinon des codes Albert.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie codering observaties",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-fb93029bf0",
    "title": "HL7 Belgium FHIR IG - Lab related profiles: Guidance",
    "publisher": "eHealth-platform / HL7 Belgium",
    "url": "https://www.ehealth.fgov.be/standards/fhir/lab/guidance.html",
    "published": "2022-09-08"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-71837b87",
   "statement": "De omzetting van bronconcepten naar Standard Concepts heet 'mapping'; niet-standaardconcepten blijven als 'source concepts' in de vocabularia.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 5.2.7 Non-Standard Concepts",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-9a557cfa23",
    "title": "The Book of OHDSI - Chapter 5 Standardized Vocabularies",
    "publisher": "OHDSI",
    "url": "https://ohdsi.github.io/TheBookOfOhdsi/StandardizedVocabularies.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-77f1c57f",
   "statement": "De Vulcan FHIR-to-OMOP IG v1.0.0 (Informative, FHIR R5) behandelt enkel de richting FHIR→OMOP, voor een IPA-kern plus Encounter en Procedure (US Core), met OMOP CDM v5.4 als doel.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Home, sectie Scope",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-4762fc1944",
    "title": "Vulcan FHIR to OMOP FHIR Implementation Guide",
    "publisher": "HL7 International / Biomedical Research and Regulation",
    "url": "https://hl7.org/fhir/uv/omop/en/index.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-2eb05c91",
   "statement": "Een volgende versie van de FHIR-to-OMOP IG (2.0.0-ballot) staat als continuous build op build.fhir.org (ontwerp).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "publicatiebanner",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-5f6318ee1a",
    "title": "FHIR to OMOP FHIR IG (continuous build 2.0.0-ballot)",
    "publisher": "HL7 International / Biomedical Research and Regulation",
    "url": "https://build.fhir.org/ig/HL7/fhir-omop-ig/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-cd749309",
   "statement": "Een FHIR-naar-OMOP-transformatie kan niet verliesvrij zijn; de IG noemt vier soorten verlies: fideliteit, informatie, relaties en accuraatheid.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Home, sectie over informatieverlies",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-4762fc1944",
    "title": "Vulcan FHIR to OMOP FHIR Implementation Guide",
    "publisher": "HL7 International / Biomedical Research and Regulation",
    "url": "https://hl7.org/fhir/uv/omop/en/index.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-4d28e36b",
   "statement": "Er is een HL7-implementatiegids in ontwikkeling (broncode op GitHub, FHIR R5, HL7 FHIR Infrastructure) die openEHR-datatypes op FHIR-datatypes mapt voor uitwisseling en persistentie zonder betekenisverlies.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "README",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-c911dbe4d4",
    "title": "openEHR-FHIR Data Type Mapping IG (broncode)",
    "publisher": "openehr-fhir (GitHub)",
    "url": "https://github.com/openehr-fhir/data-type-mapping-ig",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-dc514fc0",
   "statement": "Het onderzoeksvoorstel FHIRconnect (preprint 2025) biedt een DSL en open-source engine (openFHIR) voor bidirectionele openEHR-FHIR-transformatie en mapte 24 archetypes naar 15 FHIR-profielen.",
   "kind": "research-finding",
   "kind_label": "résultat de recherche",
   "locator": "Abstract",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-36bd69feaa",
    "title": "FHIRconnect: Towards a seamless integration of openEHR and FHIR",
    "publisher": "arXiv (preprint)",
    "url": "https://arxiv.org/abs/2511.14618",
    "published": "2025-11-18"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-96d3720e",
   "statement": "Le règlement est applicable à partir du 26 mars 2027; l'art. 105 y apporte une exception: les articles 3 à 15,\nl'art. 23(2) à (6) et les articles 25, 26, 27, 47, 48 et 49 s'appliquent de manière échelonnée par catégorie\n(26 mars 2029 pour l'art. 14(1)(a)-(c), 26 mars 2031 pour l'art. 14(1)(d)-(f)).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "art. 105, derde alinea",
   "as_of": "2026-09-26",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-14501017",
   "statement": "Les articles 3 à 15 (dont l'obligation d'enregistrement de l'art. 13 et l'EEHRxF de l'art. 15) s'appliquent à partir du\n26 mars 2029 au résumé patient, à l'e-prescription et à l'e-dispensation, ainsi qu'aux systèmes de DME que le fabricant\ndestine à ces catégories; pour l'imagerie, les résultats de tests et les rapports de sortie, à partir du 26 mars 2031.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "art. 105, derde alinea, punt (a)",
   "as_of": "2026-09-26",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-c01f0160",
   "statement": "Pour le deuxième groupe de catégories prioritaires (art. 14(1) d-f: imagerie médicale avec comptes rendus, résultats de\ntests y compris de laboratoire, rapports de sortie), ces dispositions s'appliquent à partir du 26 mars 2031.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "artikel 105, derde alinea, punt (b)",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-943c06f1",
   "statement": "Le chapitre IV (utilisation secondaire) est applicable à partir du 26 mars 2029, certaines dispositions (dont l'art. 75(1)\nsur les points de contact DonnéesDeSanté@UE) l'étant déjà à partir du 26 mars 2027.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "artikel 105",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-4a614894",
   "statement": "Volgens de verordening is art. 75(5) (aansluiting van derde landen/internationale organisaties op HealthData@EU) pas van toepassing vanaf 26 maart 2035.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "art. 105, zesde alinea",
   "as_of": "2026-09-26",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-14a07bfc",
   "statement": "Au plus tard le 26 mars 2027, la Commission doit fixer par des actes d'exécution, pour les catégories prioritaires, les spécifications techniques qui forment ensemble le format européen d'échange des dossiers médicaux électroniques (EEHRxF).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "artikel 15(1)",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-08580fc7",
   "statement": "Les prestataires de soins doivent enregistrer sous forme électronique, dans un système de DME, les données qui relèvent\n(en partie) des catégories prioritaires.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "artikel 13(1)",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-eb2f08a7",
   "statement": "Les détenteurs de données (dont les hôpitaux, sauf exemption) doivent mettre au minimum certaines catégories à disposition\npour l'utilisation secondaire, en commençant par les données de santé électroniques issues des DME.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "artikel 51(1)(a)",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-c6b73f2f",
   "statement": "À l'automne 2025, HL7 Europe a publié des IG FHIR Base et Core (STU, R4 et R5) et un paquet Extensions à l'appui de l'EHDS; les actes d'exécution relatifs à l'EEHRxF sont attendus début 2027.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "alinea's 1 en 5",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-f046cd4082",
    "title": "New HL7 Europe FHIR Implementation Guides to support the European Health Data Space",
    "publisher": "HL7 International (HL7 News)",
    "url": "https://hl7news.hl7.org/2026/01/02/new-hl7-europe-fhir-implementation-guides-to-support-the-european-health-data-space/",
    "published": "2026-01-02"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-c444a1e8",
   "statement": "La Belgique plaide pour un seul standard technique FHIR européen par type de message (résumé patient, e-prescription,\ne-dispensation, imagerie, résultats de tests, rapports de sortie).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Organisatie in België'",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-41ee539e0b",
    "title": "EHDS (European Health Data Space) - De Europese Verordening betreffende de Europese ruimte voor gezondheidsgegevens",
    "publisher": "eHealth-platform",
    "url": "https://www.ehealth.fgov.be/nl/page/ehds-european-health-data-space-de-europese-verordening-betreffende-de-europese-ruimte-voor-gezondheidsgegevens",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-2906b45d",
   "statement": "Selon un panel d'experts (JMIR Med Inform, 2023), l'EHDS vise l'harmonisation et la réutilisation sans régler les normes\nconcrètes à utiliser.",
   "kind": "research-finding",
   "kind_label": "résultat de recherche",
   "locator": "sectie Discussion/Conclusions",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-b22ee5ef19",
    "title": "Can OpenEHR, ISO 13606, and HL7 FHIR Work Together? An Agnostic Approach for the Selection and Application of Electronic Health Record Standards to the Next-Generation Health Data Spaces",
    "publisher": "JMIR Medical Informatics (Pedrera-Jiménez et al.)",
    "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC10784985/",
    "published": "2023-12-28"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-c4f61547",
   "statement": "In de EMA-use case van de pilot gebruikte DARWIN EU de OMOP CDM; andere knooppunten mochten kiezen tussen analyse op brondata of conversie naar OMOP. OMOP was dus een optie in de pilot, geen verplichting.",
   "kind": "research-finding",
   "kind_label": "résultat de recherche",
   "locator": "sectie 'Summary of the EMA use case'",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-b280053090",
    "title": "The European Health Data Space in communicable diseases surveillance and monitoring of medicines and vaccines: achievements of a pilot project examining the user journey",
    "publisher": "European Journal of Public Health",
    "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC12420905/",
    "published": "2025"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-f8e9a39f",
   "statement": "Een interoperabiliteitsraamwerk voor EHDS-secundair gebruik (JMIR 2025) noemt OMOP CDM als standaard voor semantische interoperabiliteit (academisch voorstel, geen EU-besluit).",
   "kind": "research-finding",
   "kind_label": "résultat de recherche",
   "locator": "sectie Results, semantische laag",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-55ef771c33",
    "title": "Interoperability Framework of the European Health Data Space for the Secondary Use of Data: Interactive European Interoperability Framework-Based Standards Compliance Toolkit for AI-Driven Projects",
    "publisher": "Journal of Medical Internet Research",
    "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC12059490/",
    "published": "2025"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-57376d36",
   "statement": "La Belgique choisit d'utiliser aussi les champs des types de messages européens dans les caresets belges; un message\ntransfrontalier est créé le plus près possible de la source, pour les informations se trouvant dans le DPI par le logiciel\ndu DPI.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Organisatie in België'",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-41ee539e0b",
    "title": "EHDS (European Health Data Space) - De Europese Verordening betreffende de Europese ruimte voor gezondheidsgegevens",
    "publisher": "eHealth-platform",
    "url": "https://www.ehealth.fgov.be/nl/page/ehds-european-health-data-space-de-europese-verordening-betreffende-de-europese-ruimte-voor-gezondheidsgegevens",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-ac8d824b",
   "statement": "Les implémenteurs des spécifications FHIR core-clinical belges doivent disposer d'une licence SNOMED CT Affiliate.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie IP statements",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-854e8cb270",
    "title": "HL7 Belgium FHIR IG - core-clinical profiles: Home",
    "publisher": "eHealth-platform / HL7 Belgium",
    "url": "https://www.ehealth.fgov.be/standards/fhir/core-clinical/en/index.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-0537aba1",
   "statement": "Voor primair gebruik legt de EHDS geen persistentiemodel op, alleen het uitwisselingsformaat (EEHRxF) voor de prioritaire categorieën, en België vraagt daarvoor één FHIR-standaard. Voor een Belgisch ziekenhuis is FHIR (EU-/BE-profielen met SNOMED CT/LOINC) daarom de directe verplichting. openEHR en OMOP zijn architectuurkeuzes en worden niet door de EHDS opgelegd.",
   "kind": "interpretation",
   "kind_label": "interprétation",
   "locator": "synthese van eehrxf-01/02, ehds-12/13/15, ehds-16",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": false
  },
  {
   "id": "CLM-1e57ae00",
   "statement": "Synthese: FHIR is een uitwisselingsstandaard (API/berichten, EEHRxF-richting), openEHR een standaard voor klinische modellering en persistentie in het EPD, OMOP CDM een analysemodel voor secundair gebruik; SNOMED CT en LOINC zijn de gedeelde semantische laag die in alle drie wordt gebruikt (FHIR via CodeSystem/ValueSet-binding, openEHR via terminologiebinding in archetypes, OMOP als Standard Concepts). Ze zijn complementair: een ziekenhuis kan intern openEHR of een leveranciersmodel gebruiken, extern FHIR aanbieden en een OMOP-kopie voeden voor onderzoek.",
   "kind": "interpretation",
   "kind_label": "interprétation",
   "locator": "synthese van vgl-01..10, openehr-03/06, omop-cdm-07, fhir-03/04",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-4762fc1944",
    "title": "Vulcan FHIR to OMOP FHIR Implementation Guide",
    "publisher": "HL7 International / Biomedical Research and Regulation",
    "url": "https://hl7.org/fhir/uv/omop/en/index.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": false
  },
  {
   "id": "CLM-9933480b",
   "statement": "Onder de EHDS wordt deelname aan MyHealth@EU, dat vroeger vrijwillig was, verplicht voor de lidstaten.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "overweging 33",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": true
  },
  {
   "id": "CLM-23e1f00b",
   "statement": "HealthData@EU is de grensoverschrijdende infrastructuur voor secundair gebruik; nationale contactpunten voor secundair gebruik en de Union health data access service moeten erop aansluiten.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "artikel 75(3)",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": true
  },
  {
   "id": "CLM-1a78183e",
   "statement": "Elk nationaal contactpunt voor digitale gezondheid maakt de uitwisseling van de persoonlijke elektronische gezondheidsgegevens van artikel 14(1) met de contactpunten van andere lidstaten via MyHealth@EU mogelijk; die uitwisseling steunt op het EEHRxF.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "artikel 23(3)",
   "as_of": "2026-09-25",
   "source": {
    "id": "SRC-af26b6d770",
    "title": "Regulation (EU) 2025/327 of the European Parliament and of the Council of 11 February 2025 on the European Health Data Space and amending Directive 2011/24/EU and Regulation (EU) 2024/2847",
    "publisher": "Europees Parlement en Raad van de EU (EUR-Lex)",
    "url": "https://eur-lex.europa.eu/eli/reg/2025/327/oj/eng",
    "published": "2025-03-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": true
  }
 ],
 "diagrams": [
  {
   "id": "fhir-openehr-omop-terminologie",
   "kind": "lagen",
   "title": "FHIR, openEHR, OMOP en terminologieën: conceptueel model",
   "alt": "Drie lagen: de Europese laag (EHDS, EEHRxF, MyHealth@EU, HealthData@EU), de modellen voor uitwisseling, klinische modellering en analyse (HL7 FHIR, Belgische FHIR-IG's, openEHR, OMOP CDM) en de semantische laag (SNOMED CT, LOINC, ICD-10-BE), met veertien genummerde verbanden.",
   "note": "Toont de verhouding tussen standaarden volgens de bronnen; geen ziekenhuisarchitectuur en geen bewezen operationele koppelingen. Gestippeld = ontwerp, voorstel of standpunt.",
   "layers": [
    {
     "title": "Europese laag",
     "subtitle": "EHDS",
     "nodes": [
      {
       "id": "ehds",
       "label": "EHDS",
       "sublabel": "Verordening (EU) 2025/327",
       "type": {
        "code": "LegalAct",
        "label": "Acte législatif"
       },
       "url": "/fr/espace-europeen-des-donnees-de-sante/",
       "title": "EHDS (Verordening (EU) 2025/327)"
      },
      {
       "id": "eehrxf",
       "label": "EEHRxF",
       "sublabel": "Europees uitwisselingsformaat",
       "type": {
        "code": "Specification",
        "label": "Norme ou spécification"
       },
       "url": "/fr/format-europeen-d-echange-des-dossiers-de-sante-informatises/",
       "title": "EEHRxF (Europees uitwisselingsformaat)"
      },
      {
       "id": "mh",
       "label": "MyHealth@EU",
       "sublabel": "BE-NCPeH: eHealth-platform",
       "type": {
        "code": "Platform",
        "label": "Plateforme ou service"
       },
       "url": "/fr/masante-ue/",
       "title": "MyHealth@EU (BE-NCPeH: eHealth-platform)"
      },
      {
       "id": "hd",
       "label": "HealthData@EU",
       "sublabel": "BE: Health Data Agency",
       "type": {
        "code": "Platform",
        "label": "Plateforme ou service"
       },
       "url": "/fr/donneessante-ue/",
       "title": "HealthData@EU (BE: Health Data Agency)"
      }
     ]
    },
    {
     "title": "Modellen",
     "subtitle": "uitwisseling · klinische modellering · analyse",
     "nodes": [
      {
       "id": "fhir",
       "label": "HL7 FHIR",
       "sublabel": "uitwisseling",
       "type": {
        "code": "Specification",
        "label": "Norme ou spécification"
       },
       "url": "/fr/hl7-fhir/",
       "title": "HL7 FHIR (uitwisseling)"
      },
      {
       "id": "beig",
       "label": "Belgische FHIR-IG's",
       "sublabel": "R4 4.0.1",
       "type": {
        "code": "Specification",
        "label": "Norme ou spécification"
       },
       "url": "/fr/guides-d-implementation-fhir-belges/",
       "title": "Belgische FHIR-IG's (R4 4.0.1)"
      },
      {
       "id": "oehr",
       "label": "openEHR",
       "sublabel": "klinische modellering, archetypes",
       "type": null,
       "url": null,
       "title": "openEHR (klinische modellering, archetypes)"
      },
      {
       "id": "omop",
       "label": "OMOP CDM v5.5",
       "sublabel": "analyse en onderzoek",
       "type": {
        "code": "Specification",
        "label": "Norme ou spécification"
       },
       "url": "/fr/omop-cdm-et-ohdsi/",
       "title": "OMOP CDM v5.5 (analyse en onderzoek)"
      }
     ]
    },
    {
     "title": "Semantische laag",
     "subtitle": "terminologie en classificatie",
     "nodes": [
      {
       "id": "snomed",
       "label": "SNOMED CT",
       "sublabel": "Belgian Edition",
       "type": {
        "code": "Terminology",
        "label": "Terminologie ou classification"
       },
       "url": "/fr/snomed-ct/",
       "title": "SNOMED CT (Belgian Edition)"
      },
      {
       "id": "loinc",
       "label": "LOINC",
       "sublabel": "Belgische subset",
       "type": {
        "code": "Terminology",
        "label": "Terminologie ou classification"
       },
       "url": "/fr/loinc-et-le-sous-ensemble-belge-retam/",
       "title": "LOINC (Belgische subset)"
      },
      {
       "id": "icd",
       "label": "ICD-10-BE",
       "sublabel": null,
       "type": {
        "code": "Terminology",
        "label": "Terminologie ou classification"
       },
       "url": "/fr/icd-10-be/",
       "title": "ICD-10-BE"
      }
     ]
    }
   ],
   "participants": [],
   "edges": [
    {
     "n": "1",
     "source": "ehds",
     "target": "eehrxf",
     "text": "EHDS: de Commissie legt de EEHRxF-specificaties vast (tegen 26/3/2027)",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-14a07bfc"
     ],
     "refs": [
      28
     ]
    },
    {
     "n": "2",
     "source": "ehds",
     "target": "mh",
     "text": "EHDS: deelname aan MyHealth@EU verplicht voor lidstaten",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-9933480b"
     ],
     "refs": [
      28
     ]
    },
    {
     "n": "3",
     "source": "ehds",
     "target": "hd",
     "text": "EHDS: secundair gebruik via HealthData@EU; OMOP enkel een optie in de pilot",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-23e1f00b",
      "CLM-c4f61547"
     ],
     "refs": [
      28,
      31
     ]
    },
    {
     "n": "4",
     "source": "mh",
     "target": "eehrxf",
     "text": "MyHealth@EU-uitwisseling steunt op EEHRxF",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-1a78183e"
     ],
     "refs": [
      28
     ]
    },
    {
     "n": "5",
     "source": "eehrxf",
     "target": "fhir",
     "text": "HL7 Europe Base/Core-IG's (STU); uitvoeringshandelingen verwacht begin 2027",
     "status": "hypothesis",
     "reply": false,
     "claims": [
      "CLM-c6b73f2f"
     ],
     "refs": [
      29
     ]
    },
    {
     "n": "6",
     "source": "beig",
     "target": "fhir",
     "text": "Belgische IG's profileren FHIR R4 (geen R5)",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-4c97a5a4"
     ],
     "refs": [
      19
     ]
    },
    {
     "n": "7",
     "source": "beig",
     "target": "eehrxf",
     "text": "EU-velden ook in Belgische CareSets (Belgisch standpunt)",
     "status": "hypothesis",
     "reply": false,
     "claims": [
      "CLM-57376d36"
     ],
     "refs": [
      30
     ]
    },
    {
     "n": "8",
     "source": "beig",
     "target": "snomed",
     "text": "SNOMED CT als voorkeurscodering in Belgische IG's",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-530b635f"
     ],
     "refs": [
      23
     ]
    },
    {
     "n": "9",
     "source": "beig",
     "target": "loinc",
     "text": "BE Lab-IG: LOINC verplicht (FOD-subset)",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-e0e48933"
     ],
     "refs": [
      24
     ]
    },
    {
     "n": "10",
     "source": "oehr",
     "target": "snomed",
     "text": "openEHR: terminologiebinding via archetypes (SNOMED CT als voorbeeld is een interpretatie)",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-19680c4c"
     ],
     "refs": [
      10
     ]
    },
    {
     "n": "11",
     "source": "oehr",
     "target": "fhir",
     "text": "Een openEHR↔FHIR-IG voor datatype-mapping is in ontwikkeling",
     "status": "hypothesis",
     "reply": false,
     "claims": [
      "CLM-4d28e36b"
     ],
     "refs": [
      26
     ]
    },
    {
     "n": "12",
     "source": "fhir",
     "target": "omop",
     "text": "HL7 Vulcan FHIR-to-OMOP IG v1.0.0 (Informative; CDM v5.4); niet verliesvrij",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-77f1c57f",
      "CLM-cd749309"
     ],
     "refs": [
      1
     ]
    },
    {
     "n": "13",
     "source": "omop",
     "target": "snomed",
     "text": "OMOP: SNOMED CT als standaardconcept voor aandoeningen",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-8b25e1f2"
     ],
     "refs": [
      17
     ]
    },
    {
     "n": "14",
     "source": "icd",
     "target": "omop",
     "text": "ICD als broncode, gemapt op een standaardconcept (ICD-10-BE specifiek is een interpretatie)",
     "status": "established",
     "reply": false,
     "claims": [
      "CLM-8b25e1f2",
      "CLM-71837b87"
     ],
     "refs": [
      17
     ]
    }
   ],
   "footer": null
  }
 ],
 "facets": {
  "type": [
   "Topic"
  ],
  "jurisdiction": [
   "internationaal",
   "eu",
   "belgie"
  ],
  "theme": [
   "architectuur-en-infrastructuur",
   "terminologie",
   "secundair-gebruik"
  ],
  "lifecycle": [
   "onbekend"
  ],
  "section": [
   "terminologie",
   "europa"
  ]
 },
 "search_terms": [
  "FHIR, openEHR et OMOP : comparaison",
  "FHIR vs openEHR vs OMOP",
  "FHIR, openEHR en OMOP CDM",
  "uitwisseling vs persistentie vs analyse",
  "FHIR, openEHR en OMOP: vergelijking",
  "FHIR, openEHR and OMOP compared"
 ],
 "release_id": "2026.11.12-3",
 "license": "CC BY 4.0"
}
