{
 "id": "integratie-engine",
 "url": "/fr/moteur-d-integration/",
 "md_url": "/fr/moteur-d-integration.md",
 "json_url": "/fr/moteur-d-integration.json",
 "claims_url": "/fr/moteur-d-integration/beweringen/",
 "type": {
  "code": "Topic",
  "label": "Aperçu ou dossier"
 },
 "schema_type": "Thing",
 "lang": "fr",
 "translation": {
  "lang": "fr",
  "source_url": "/integratie-engine/",
  "date": "2026-10-15",
  "stale": true,
  "fields": [
   "in_het_kort",
   "lifecycle_note",
   "sectie:belgische-context",
   "sectie:conclusie",
   "sectie:implementatievoorwaarden-en-beperkingen",
   "sectie:onzekerheden-en-tegenstrijdige-informatie",
   "sectie:praktische-betekenis-voor-ziekenhuizen",
   "sectie:vergelijking",
   "sectie:vraag-of-patroon",
   "summary",
   "title"
  ]
 },
 "title": "Moteur d'intégration (interface engine)",
 "aliases": [
  "interface engine",
  "integration engine",
  "communicatieserver",
  "HL7-integratie-engine",
  "interfacemotor",
  "moteur d'intégration"
 ],
 "names": {
  "nl": "Integratie-engine",
  "fr": "Moteur d'intégration",
  "en": "Integration engine",
  "de": "Kommunikationsserver"
 },
 "jurisdiction": [
  {
   "code": "internationaal",
   "label": "International"
  },
  {
   "code": "belgie",
   "label": "Belgique (fédéral/interfédéral)"
  }
 ],
 "themes": [
  {
   "code": "architectuur-en-infrastructuur",
   "label": "Architecture et infrastructure"
  },
  {
   "code": "softwaremarkt",
   "label": "Marché logiciel et homologation"
  },
  {
   "code": "standaardisatie-en-governance",
   "label": "Normalisation et gouvernance"
  }
 ],
 "lifecycle": {
  "code": "onbekend",
  "label": "inconnu"
 },
 "lifecycle_note_html": "Sans objet (page de patron) ; le statut par produit figure dans le tableau comparatif et sur les pages propres.",
 "version": null,
 "vendor": null,
 "sectors": [],
 "homologations": [],
 "links": [],
 "summary_text": "Un moteur d'intégration (interface engine, aussi appelé « serveur de communication ») est un serveur qui reçoit, filtre, transforme et route des messages entre applications de soins, par exemple entre les formats HL7 v2, FHIR, DICOM et XML. Les moteurs ajoutent au transport des files d'attente persistantes, de nouvelles tentatives et un monitoring; un message broker (Kafka, ActiveMQ) fournit le transport et le stockage des messages, une bibliothèque ou un framework (HAPI, Apache Camel) des briques pour du code propre, selon leur propre description. En Belgique, NextGen Connect (Mirth Connect) est le moteur de HD4DP v2 de healthdata.be; pour la technologie InterSystems, seul un avis de marché portant sur le DPI d'un seul hôpital a été trouvé.",
 "summary_html": "<p>Un moteur d'intégration (interface engine, aussi appelé « serveur de communication ») est un serveur qui reçoit, filtre, transforme et route des messages entre applications de soins, par exemple entre les formats HL7 v2, FHIR, DICOM et XML. Les moteurs ajoutent au transport des files d'attente persistantes, de nouvelles tentatives et un monitoring ; un message broker (Kafka, ActiveMQ) fournit le transport et le stockage des messages, une bibliothèque ou un framework (HAPI, Apache Camel) des briques pour du code propre, selon leur propre description. En Belgique, NextGen Connect (Mirth Connect) est le moteur de HD4DP v2 de healthdata.be ; pour la technologie InterSystems, seul un avis de marché portant sur le DPI d'un seul hôpital a été trouvé.</p>",
 "last_verified": "2026-10-08",
 "verification_outdated": false,
 "sections": [
  {
   "id": "en-bref",
   "title": "En bref",
   "kind": "tekst",
   "html": "<ul>\n<li>Un moteur d'intégration reçoit des messages, les filtre, les transforme et les route vers le format et la destination exigés par le système récepteur ; healthdata.be qualifie le filtrage, la transformation, l'extraction et le routage de fonctions principales.<sup class=\"cite\" id=\"t-CLM-dba676c9\" data-claims=\"CLM-dba676c9\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup><sup class=\"cite\" id=\"t-CLM-334477b1\" data-claims=\"CLM-334477b1\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup></li>\n<li>Pour HL7 v2 sur le réseau, IHE prescrit le Minimal Lower Layer Protocol (MLLP), avec des messages ACK qui signalent les erreurs applicatives à l'expéditeur.<sup class=\"cite\" id=\"t-CLM-17193907\" data-claims=\"CLM-17193907\"><a class=\"cite-ref\" href=\"#bron-2\" aria-label=\"Source 2\">[2]</a></sup><sup class=\"cite\" id=\"t-CLM-0900d5b9\" data-claims=\"CLM-0900d5b9\"><a class=\"cite-ref\" href=\"#bron-2\" aria-label=\"Source 2\">[2]</a></sup></li>\n<li>Les moteurs conservent les messages de manière persistante pendant le traitement, les placent dans des files d'attente et réessaient en cas d'erreur (livraison garantie).<sup class=\"cite\" id=\"t-CLM-389decff\" data-claims=\"CLM-389decff\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup><sup class=\"cite\" id=\"t-CLM-b4bfb612\" data-claims=\"CLM-b4bfb612\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup><sup class=\"cite\" id=\"t-CLM-49dd434f\" data-claims=\"CLM-49dd434f\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup></li>\n<li>Un message broker généraliste comme Apache ActiveMQ ou Kafka fournit le transport et le stockage des messages, mais pas de fonctions spécifiques aux soins.<sup class=\"cite\" id=\"t-CLM-c3fb6bfb\" data-claims=\"CLM-c3fb6bfb\"><a class=\"cite-ref\" href=\"#bron-4\" aria-label=\"Source 4\">[4]</a></sup><sup class=\"cite\" id=\"t-CLM-11a0abcc\" data-claims=\"CLM-11a0abcc\"><a class=\"cite-ref\" href=\"#bron-5\" aria-label=\"Source 5\">[5]</a></sup><sup class=\"cite\" id=\"t-CLM-41b3e598\" data-claims=\"CLM-41b3e598\"><a class=\"cite-ref\" href=\"#bron-5\" aria-label=\"Source 5\">[5]</a></sup></li>\n<li>Les bibliothèques et frameworks comme HAPI et Apache Camel s'intègrent dans du code Java propre et ne constituent pas un moteur autonome doté d'une interface de gestion.<sup class=\"cite\" id=\"t-CLM-5ec7787f\" data-claims=\"CLM-5ec7787f\"><a class=\"cite-ref\" href=\"#bron-6\" aria-label=\"Source 6\">[6]</a></sup><sup class=\"cite\" id=\"t-CLM-645cdbfe\" data-claims=\"CLM-645cdbfe\"><a class=\"cite-ref\" href=\"#bron-7\" aria-label=\"Source 7\">[7]</a></sup></li>\n<li>En Belgique, NextGen Connect est le moteur d'intégration de <a href=\"/fr/hd4dp-v2/\">HD4DP v2</a> ; l'intégrateur <a href=\"/fr/amaron/\">Amaron</a> affirme construire des connexions eHealth sur Mirth Connect (affirmation du fournisseur).<sup class=\"cite\" id=\"t-CLM-45aa1fa7\" data-claims=\"CLM-45aa1fa7\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup><sup class=\"cite\" id=\"t-CLM-936a6917\" data-claims=\"CLM-936a6917\"><a class=\"cite-ref\" href=\"#bron-8\" aria-label=\"Source 8\">[8]</a></sup></li>\n</ul>"
  },
  {
   "id": "question-ou-modele",
   "title": "Question ou modèle",
   "kind": "tekst",
   "html": "<p>Cette page décrit le modèle d'architecture « moteur d'intégration » : un serveur central et géré, unique, qui transmet et convertit les messages entre applications de soins. La documentation de healthdata.be décrit NextGen Connect comme un moteur d'intégration pour les soins de santé, qui traduit des normes de messages (entre autres HL7, DICOM, ANSI X12, ASCII et XML) vers la norme exigée par le système destinataire.<sup class=\"cite\" data-claims=\"CLM-dba676c9\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup> La proposition Eclipse pour Open Integration Engine décrit un tel moteur comme un serveur basé sur Java qui reçoit, transforme, filtre, route et délivre des messages cliniques et administratifs entre des systèmes de soins hétérogènes.<sup class=\"cite\" id=\"t-CLM-fe5d52d0\" data-claims=\"CLM-fe5d52d0\"><a class=\"cite-ref\" href=\"#bron-9\" aria-label=\"Source 9\">[9]</a></sup> D'autres appellations sont « interface engine » et « serveur de communication » ; ainsi, Enovation décrit Infor Cloverleaf comme un serveur de communication qui rassemble des données provenant de différents systèmes d'information.<sup class=\"cite\" id=\"t-CLM-20acebff\" data-claims=\"CLM-20acebff\"><a class=\"cite-ref\" href=\"#bron-10\" aria-label=\"Source 10\">[10]</a></sup></p>\n<h3>Que fait un moteur d'intégration ?</h3>\n<ul>\n<li><strong>Connecteurs et transport.</strong> Un moteur parle de nombreux protocoles de transport ; la proposition OIE cite HTTP/S, TCP/MLLP, FTP/SFTP, SMTP, le système de fichiers, JMS et la connectivité directe aux bases de données via JDBC.<sup class=\"cite\" id=\"t-CLM-11f35873\" data-claims=\"CLM-11f35873\"><a class=\"cite-ref\" href=\"#bron-9\" aria-label=\"Source 9\">[9]</a></sup> Pour HL7 v2 sur le réseau, IHE prescrit le Minimal Lower Layer Protocol (MLLP) de l'annexe C du HL7 Implementation Guide.<sup class=\"cite\" data-claims=\"CLM-17193907\"><a class=\"cite-ref\" href=\"#bron-2\" aria-label=\"Source 2\">[2]</a></sup></li>\n<li><strong>Canaux.</strong> Dans Mirth Connect et OIE, un canal constitue une seule intégration : il détermine d'où viennent les messages, ce qu'il advient d'eux en route et où ils vont.<sup class=\"cite\" id=\"t-CLM-3e9fe0f5\" data-claims=\"CLM-3e9fe0f5\"><a class=\"cite-ref\" href=\"#bron-9\" aria-label=\"Source 9\">[9]</a></sup></li>\n<li><strong>Parsing et validation.</strong> Les produits InterSystems peuvent transmettre des messages HL7 sans schéma, mais, avec un schéma associé, ils peuvent analyser des champs en vue de transformations et de règles de routage et valider des messages.<sup class=\"cite\" id=\"t-CLM-eae96652\" data-claims=\"CLM-eae96652\"><a class=\"cite-ref\" href=\"#bron-11\" aria-label=\"Source 11\">[11]</a></sup> Pour HL7 v2, Mirth Connect utilise la bibliothèque open source HAPI.<sup class=\"cite\" id=\"t-CLM-2fa36873\" data-claims=\"CLM-2fa36873\"><a class=\"cite-ref\" href=\"#bron-12\" aria-label=\"Source 12\">[12]</a></sup></li>\n<li><strong>Transformation et mapping.</strong> Un moteur convertit le format entrant en un autre, par exemple HL7 vers XML.<sup class=\"cite\" id=\"t-CLM-c2efda59\" data-claims=\"CLM-c2efda59\"><a class=\"cite-ref\" href=\"#bron-13\" aria-label=\"Source 13\">[13]</a></sup> InterSystems Health Connect contient des transformations intégrées entre FHIR et HL7 v2 ou C-CDA, et utilise un format intermédiaire propre (SDA) lors de telles conversions.<sup class=\"cite\" id=\"t-CLM-dc9fc31d\" data-claims=\"CLM-dc9fc31d\"><a class=\"cite-ref\" href=\"#bron-14\" aria-label=\"Source 14\">[14]</a></sup><sup class=\"cite\" id=\"t-CLM-44b9fbcf\" data-claims=\"CLM-44b9fbcf\"><a class=\"cite-ref\" href=\"#bron-14\" aria-label=\"Source 14\">[14]</a></sup> Dans HD4DP v2, NextGen Connect convertit des données provenant d'une API HL7 FHIR et de fichiers CSV vers l'API du serveur de formulaires.<sup class=\"cite\" id=\"t-CLM-d31dfbfd\" data-claims=\"CLM-d31dfbfd\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup><sup class=\"cite\" id=\"t-CLM-33972230\" data-claims=\"CLM-33972230\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup> Pour KMEHR, Amaron décrit que des messages sont horodatés au moyen de Mirth Connect via le service de timestamping d'eHealth, le plus souvent sur la base d'un message KMEHR-XML provenant des systèmes sources (affirmation du fournisseur).<sup class=\"cite\" id=\"t-CLM-7efd81d7\" data-claims=\"CLM-7efd81d7\"><a class=\"cite-ref\" href=\"#bron-8\" aria-label=\"Source 8\">[8]</a></sup> Aucun mapping public et réutilisable entre HL7 v2, FHIR et <a href=\"/fr/kmehr/\">KMEHR</a> sur un moteur d'intégration n'a été trouvé (lacune).</li>\n<li><strong>Routage et filtrage.</strong> Un filtre lit des paramètres de message et laisse passer un message vers la phase de transformation ou le retient.<sup class=\"cite\" id=\"t-CLM-1358fd23\" data-claims=\"CLM-1358fd23\"><a class=\"cite-ref\" href=\"#bron-13\" aria-label=\"Source 13\">[13]</a></sup> En tant que routing engine, les produits InterSystems peuvent transférer des messages HL7 v2 d'une application vers une autre.<sup class=\"cite\" id=\"t-CLM-78eaf1dd\" data-claims=\"CLM-78eaf1dd\"><a class=\"cite-ref\" href=\"#bron-11\" aria-label=\"Source 11\">[11]</a></sup></li>\n<li><strong>Files d'attente, store-and-forward et relivraison.</strong> Mirth Connect persiste les messages pendant le traitement, de sorte qu'après une panne du système ou l'arrêt d'un canal, leur traitement reprend là où il s'était interrompu.<sup class=\"cite\" data-claims=\"CLM-389decff\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup> Chaque destination connector peut utiliser une file d'attente stockée dans la base de données.<sup class=\"cite\" data-claims=\"CLM-b4bfb612\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup> Dans HD4DP v2, NextGen Connect livre les données en « guaranteed delivery », si nécessaire avec de nouvelles tentatives après une erreur.<sup class=\"cite\" data-claims=\"CLM-49dd434f\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup> Dans Apache Camel, un message qui ne peut pas être traité ou envoyé part vers une dead letter queue.<sup class=\"cite\" id=\"t-CLM-8f7e1ce5\" data-claims=\"CLM-8f7e1ce5\"><a class=\"cite-ref\" href=\"#bron-15\" aria-label=\"Source 15\">[15]</a></sup></li>\n<li><strong>Accusés de réception (ACK).</strong> IHE prend en charge les deux modes d'accusé de réception de HL7 v2.5, Original et Enhanced Acknowledgement Mode.<sup class=\"cite\" id=\"t-CLM-d2b0f504\" data-claims=\"CLM-d2b0f504\"><a class=\"cite-ref\" href=\"#bron-2\" aria-label=\"Source 2\">[2]</a></sup> Dans l'Original Mode, le message ACK rapporte à l'expéditeur les erreurs applicatives du destinataire.<sup class=\"cite\" data-claims=\"CLM-0900d5b9\"><a class=\"cite-ref\" href=\"#bron-2\" aria-label=\"Source 2\">[2]</a></sup> Avec une source queue, Mirth Connect peut d'abord accuser réception des messages et ne les traiter qu'ensuite à son propre rythme (« ACK now, process later »).<sup class=\"cite\" id=\"t-CLM-96d1e5f0\" data-claims=\"CLM-96d1e5f0\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup> Le composant MLLP de Camel crée automatiquement les accusés de réception HL7 et contrôle les accusés de réception reçus.<sup class=\"cite\" id=\"t-CLM-6cc97ad8\" data-claims=\"CLM-6cc97ad8\"><a class=\"cite-ref\" href=\"#bron-16\" aria-label=\"Source 16\">[16]</a></sup></li>\n<li><strong>Monitoring, journalisation et audit.</strong> Mirth Connect affiche des statistiques par canal et par connecteur et conserve par canal un stockage de messages consultable.<sup class=\"cite\" id=\"t-CLM-dca55b1c\" data-claims=\"CLM-dca55b1c\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup><sup class=\"cite\" id=\"t-CLM-135d02c8\" data-claims=\"CLM-135d02c8\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup> La proposition OIE cite une application de gestion pour la création et le déploiement de canaux, le monitoring opérationnel et l'audit des messages.<sup class=\"cite\" id=\"t-CLM-f4b4a42b\" data-claims=\"CLM-f4b4a42b\"><a class=\"cite-ref\" href=\"#bron-9\" aria-label=\"Source 9\">[9]</a></sup> Selon InterSystems, la détection d'événements, les alertes et le monitoring dans Health Connect font que des messages ne se perdent pas (affirmation du fournisseur).<sup class=\"cite\" id=\"t-CLM-2a0d3143\" data-claims=\"CLM-2a0d3143\"><a class=\"cite-ref\" href=\"#bron-14\" aria-label=\"Source 14\">[14]</a></sup></li>\n</ul>\n<h3>Moteur, message broker ou bibliothèque</h3>\n<p>Trois types de logiciels sont mentionnés indifféremment dans les projets d'intégration. La distinction ci-dessous est une <strong>interprétation</strong> de l'Atlas ; chaque phrase s'appuie sur la description citée qu'en donnent leurs créateurs.</p>\n<ul>\n<li><strong>Message broker générique.</strong> Apache ActiveMQ est un message broker générique, basé sur Java, qui prend en charge plusieurs protocoles (entre autres AMQP, STOMP, MQTT, JMS).<sup class=\"cite\" data-claims=\"CLM-c3fb6bfb\"><a class=\"cite-ref\" href=\"#bron-4\" aria-label=\"Source 4\">[4]</a></sup> Apache Kafka est une plate-forme d'event streaming permettant de publier des flux d'événements, de s'y abonner et de les stocker durablement.<sup class=\"cite\" data-claims=\"CLM-11a0abcc\"><a class=\"cite-ref\" href=\"#bron-5\" aria-label=\"Source 5\">[5]</a></sup><sup class=\"cite\" data-claims=\"CLM-41b3e598\"><a class=\"cite-ref\" href=\"#bron-5\" aria-label=\"Source 5\">[5]</a></sup> Dans leur propre description, aucun des deux produits ne mentionne de parsing HL7 ni de mapping spécifique aux soins de santé ; un broker peut toutefois servir de couche de transport sous un moteur ou à côté de celui-ci, comme le montre le connecteur JMS dans la base de code de Mirth.<sup class=\"cite\" data-claims=\"CLM-c3fb6bfb\"><a class=\"cite-ref\" href=\"#bron-4\" aria-label=\"Source 4\">[4]</a></sup><sup class=\"cite\" data-claims=\"CLM-11f35873\"><a class=\"cite-ref\" href=\"#bron-9\" aria-label=\"Source 9\">[9]</a></sup></li>\n<li><strong>Bibliothèque ou framework.</strong> HAPI est un parseur HL7 2.x open source et orienté objet pour Java.<sup class=\"cite\" data-claims=\"CLM-5ec7787f\"><a class=\"cite-ref\" href=\"#bron-6\" aria-label=\"Source 6\">[6]</a></sup> HAPI FHIR est une API Java pour clients et serveurs FHIR.<sup class=\"cite\" id=\"t-CLM-663912f1\" data-claims=\"CLM-663912f1\"><a class=\"cite-ref\" href=\"#bron-17\" aria-label=\"Source 17\">[17]</a></sup> Apache Camel est un framework d'intégration fondé sur les Enterprise Integration Patterns et une petite bibliothèque que l'on intègre dans une application Java.<sup class=\"cite\" id=\"t-CLM-b5098d65\" data-claims=\"CLM-b5098d65\"><a class=\"cite-ref\" href=\"#bron-7\" aria-label=\"Source 7\">[7]</a></sup><sup class=\"cite\" data-claims=\"CLM-645cdbfe\"><a class=\"cite-ref\" href=\"#bron-7\" aria-label=\"Source 7\">[7]</a></sup> Qui utilise un tel composant écrit lui-même les routes et la couche de gestion.</li>\n<li><strong>Moteur d'intégration.</strong> Un moteur regroupe connecteurs, transformation, routage, files d'attente et monitoring dans un seul serveur doté d'une interface de gestion ; le Mirth Connect Server contient à la fois le back-end de l'interface de gestion et le moteur proprement dit, qui filtre, transforme et envoie les messages.<sup class=\"cite\" id=\"t-CLM-617f2bee\" data-claims=\"CLM-617f2bee\"><a class=\"cite-ref\" href=\"#bron-18\" aria-label=\"Source 18\">[18]</a></sup> Les moteurs s'appuient souvent eux-mêmes sur des bibliothèques : Mirth Connect utilise HAPI pour HL7 v2, et le composant HL7 de Camel fonctionne également avec HAPI.<sup class=\"cite\" data-claims=\"CLM-2fa36873\"><a class=\"cite-ref\" href=\"#bron-12\" aria-label=\"Source 12\">[12]</a></sup><sup class=\"cite\" id=\"t-CLM-c273ba2b\" data-claims=\"CLM-c273ba2b\"><a class=\"cite-ref\" href=\"#bron-19\" aria-label=\"Source 19\">[19]</a></sup></li>\n</ul>\n<p>Il existe en outre des services de conversion dans le cloud. Pour la conversion de données de santé vers FHIR avec $convert-data dans le service FHIR d'Azure, Microsoft recommande, pour le workflow complet, un pipeline ETL (extract, transform, load) avec un moteur ETL ; Azure Logic Apps ou Azure Data Factory sont cités (description du fournisseur) ; en cas de succès, le service renvoie un bundle FHIR en R4.<sup class=\"cite\" id=\"t-CLM-5f6f3c45\" data-claims=\"CLM-5f6f3c45\"><a class=\"cite-ref\" href=\"#bron-20\" aria-label=\"Source 20\">[20]</a></sup><sup class=\"cite\" id=\"t-CLM-52ee955e\" data-claims=\"CLM-52ee955e\"><a class=\"cite-ref\" href=\"#bron-20\" aria-label=\"Source 20\">[20]</a></sup><sup class=\"cite\" id=\"t-CLM-1c217489\" data-claims=\"CLM-1c217489\"><a class=\"cite-ref\" href=\"#bron-20\" aria-label=\"Source 20\">[20]</a></sup> Microsoft livre les templates standard correspondants sous licence MIT, mais ne les prend pas en charge et les destine uniquement à servir de point de départ.<sup class=\"cite\" id=\"t-CLM-16aeb194\" data-claims=\"CLM-16aeb194\"><a class=\"cite-ref\" href=\"#bron-20\" aria-label=\"Source 20\">[20]</a></sup></p>"
  },
  {
   "id": "comparaison",
   "title": "Comparaison",
   "kind": "tekst",
   "html": "<p>Comparaison neutre, sans classement ni recommandation. « Non trouvé » signifie que l'Atlas n'a trouvé aucune source, non qu'il n'y a pas d'utilisation.</p>\n<table>\n<thead>\n<tr>\n<th>Produit</th>\n<th>Type</th>\n<th>Producteur</th>\n<th>Licence</th>\n<th>HL7 v2 / FHIR</th>\n<th>Utilisation en Belgique</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><a href=\"/fr/mirth-connect/\">Mirth Connect (NextGen Connect)</a> (NextGen Connect)</td>\n<td>moteur</td>\n<td>NextGen Healthcare<sup class=\"cite\" id=\"t-CLM-8154aa5f\" data-claims=\"CLM-8154aa5f\"><a class=\"cite-ref\" href=\"#bron-21\" aria-label=\"Source 21\">[21]</a></sup></td>\n<td>MPL 2.0 jusqu'à 4.5.2 inclus ; propriétaire à partir de 4.6 (mars 2025)<sup class=\"cite\" id=\"t-CLM-0c95a7ee\" data-claims=\"CLM-0c95a7ee\"><a class=\"cite-ref\" href=\"#bron-13\" aria-label=\"Source 13\">[13]</a></sup><sup class=\"cite\" id=\"t-CLM-52d16276\" data-claims=\"CLM-52d16276\"><a class=\"cite-ref\" href=\"#bron-22\" aria-label=\"Source 22\">[22]</a></sup></td>\n<td>HL7 v2 via HAPI ; extension FHIR, notamment R4<sup class=\"cite\" data-claims=\"CLM-2fa36873\"><a class=\"cite-ref\" href=\"#bron-12\" aria-label=\"Source 12\">[12]</a></sup><sup class=\"cite\" id=\"t-CLM-e54a354d\" data-claims=\"CLM-e54a354d\"><a class=\"cite-ref\" href=\"#bron-23\" aria-label=\"Source 23\">[23]</a></sup></td>\n<td>HD4DP v2<sup class=\"cite\" data-claims=\"CLM-45aa1fa7\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup> ; Amaron (affirmation du fournisseur)<sup class=\"cite\" data-claims=\"CLM-936a6917\"><a class=\"cite-ref\" href=\"#bron-8\" aria-label=\"Source 8\">[8]</a></sup></td>\n</tr>\n<tr>\n<td>Open Integration Engine</td>\n<td>moteur (fork de Mirth)</td>\n<td>communauté, incubation Eclipse<sup class=\"cite\" id=\"t-CLM-ea0fa5c0\" data-claims=\"CLM-ea0fa5c0\"><a class=\"cite-ref\" href=\"#bron-24\" aria-label=\"Source 24\">[24]</a></sup><sup class=\"cite\" id=\"t-CLM-da3a8bb6\" data-claims=\"CLM-da3a8bb6\"><a class=\"cite-ref\" href=\"#bron-25\" aria-label=\"Source 25\">[25]</a></sup></td>\n<td>MPL 2.0<sup class=\"cite\" id=\"t-CLM-00eeeca6\" data-claims=\"CLM-00eeeca6\"><a class=\"cite-ref\" href=\"#bron-24\" aria-label=\"Source 24\">[24]</a></sup></td>\n<td>HL7 v2.x, FHIR, DICOM, CDA (selon la proposition)<sup class=\"cite\" id=\"t-CLM-dcb67e02\" data-claims=\"CLM-dcb67e02\"><a class=\"cite-ref\" href=\"#bron-9\" aria-label=\"Source 9\">[9]</a></sup></td>\n<td>non trouvé</td>\n</tr>\n<tr>\n<td>BridgeLink</td>\n<td>moteur (fork de Mirth)</td>\n<td>Innovar Healthcare et la communauté<sup class=\"cite\" id=\"t-CLM-322e5f30\" data-claims=\"CLM-322e5f30\"><a class=\"cite-ref\" href=\"#bron-26\" aria-label=\"Source 26\">[26]</a></sup></td>\n<td>MPL 2.0<sup class=\"cite\" id=\"t-CLM-05fdc8d6\" data-claims=\"CLM-05fdc8d6\"><a class=\"cite-ref\" href=\"#bron-27\" aria-label=\"Source 27\">[27]</a></sup></td>\n<td>pas établi séparément</td>\n<td>non trouvé</td>\n</tr>\n<tr>\n<td><a href=\"/fr/apache-camel/\">Apache Camel</a> (+ IPF)</td>\n<td>framework/bibliothèque</td>\n<td>Apache Software Foundation<sup class=\"cite\" id=\"t-CLM-6a60adeb\" data-claims=\"CLM-6a60adeb\"><a class=\"cite-ref\" href=\"#bron-7\" aria-label=\"Source 7\">[7]</a></sup></td>\n<td>Apache 2.0<sup class=\"cite\" data-claims=\"CLM-6a60adeb\"><a class=\"cite-ref\" href=\"#bron-7\" aria-label=\"Source 7\">[7]</a></sup><sup class=\"cite\" id=\"t-CLM-edba5f7e\" data-claims=\"CLM-edba5f7e\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup></td>\n<td>HL7 v2/MLLP via HAPI ; FHIR via HAPI FHIR ; IPF pour les profils IHE<sup class=\"cite\" data-claims=\"CLM-c273ba2b\"><a class=\"cite-ref\" href=\"#bron-19\" aria-label=\"Source 19\">[19]</a></sup><sup class=\"cite\" id=\"t-CLM-d4e1052b\" data-claims=\"CLM-d4e1052b\"><a class=\"cite-ref\" href=\"#bron-29\" aria-label=\"Source 29\">[29]</a></sup><sup class=\"cite\" id=\"t-CLM-d70d208d\" data-claims=\"CLM-d70d208d\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup></td>\n<td>non trouvé</td>\n</tr>\n<tr>\n<td>HAPI HL7v2 / HAPI FHIR</td>\n<td>bibliothèque</td>\n<td>projet open source, non lié à l'organisation HL7<sup class=\"cite\" id=\"t-CLM-f7180413\" data-claims=\"CLM-f7180413\"><a class=\"cite-ref\" href=\"#bron-6\" aria-label=\"Source 6\">[6]</a></sup></td>\n<td>MPL ou GPL (HL7v2) ; Apache 2.0 (FHIR)<sup class=\"cite\" id=\"t-CLM-16175437\" data-claims=\"CLM-16175437\"><a class=\"cite-ref\" href=\"#bron-30\" aria-label=\"Source 30\">[30]</a></sup><sup class=\"cite\" data-claims=\"CLM-663912f1\"><a class=\"cite-ref\" href=\"#bron-17\" aria-label=\"Source 17\">[17]</a></sup></td>\n<td>parseur HL7 v2 ; API FHIR<sup class=\"cite\" data-claims=\"CLM-5ec7787f\"><a class=\"cite-ref\" href=\"#bron-6\" aria-label=\"Source 6\">[6]</a></sup><sup class=\"cite\" data-claims=\"CLM-663912f1\"><a class=\"cite-ref\" href=\"#bron-17\" aria-label=\"Source 17\">[17]</a></sup></td>\n<td>directement non trouvé ; intégré dans Mirth Connect<sup class=\"cite\" data-claims=\"CLM-2fa36873\"><a class=\"cite-ref\" href=\"#bron-12\" aria-label=\"Source 12\">[12]</a></sup></td>\n</tr>\n<tr>\n<td>InterSystems Health Connect</td>\n<td>moteur</td>\n<td>InterSystems<sup class=\"cite\" id=\"t-CLM-d3f47764\" data-claims=\"CLM-d3f47764\"><a class=\"cite-ref\" href=\"#bron-14\" aria-label=\"Source 14\">[14]</a></sup></td>\n<td>commercial, clé de licence par instance IRIS<sup class=\"cite\" id=\"t-CLM-4866354d\" data-claims=\"CLM-4866354d\"><a class=\"cite-ref\" href=\"#bron-31\" aria-label=\"Source 31\">[31]</a></sup></td>\n<td>routage HL7 v2 ; client/serveur FHIR et transformations<sup class=\"cite\" data-claims=\"CLM-78eaf1dd\"><a class=\"cite-ref\" href=\"#bron-11\" aria-label=\"Source 11\">[11]</a></sup><sup class=\"cite\" data-claims=\"CLM-dc9fc31d\"><a class=\"cite-ref\" href=\"#bron-14\" aria-label=\"Source 14\">[14]</a></sup></td>\n<td>Health Connect lui-même non trouvé ; IRIS for Health et Ensemble dans l'application DPI d'un seul hôpital (avis de marché)<sup class=\"cite\" id=\"t-CLM-4cadafc8\" data-claims=\"CLM-4cadafc8\"><a class=\"cite-ref\" href=\"#bron-32\" aria-label=\"Source 32\">[32]</a></sup></td>\n</tr>\n<tr>\n<td>Rhapsody (incl. Corepoint)</td>\n<td>moteur</td>\n<td>Rhapsody, auparavant Lyniate<sup class=\"cite\" id=\"t-CLM-c4b57282\" data-claims=\"CLM-c4b57282\"><a class=\"cite-ref\" href=\"#bron-33\" aria-label=\"Source 33\">[33]</a></sup></td>\n<td>commercial ; SaaS, infrastructure propre ou iPaaS<sup class=\"cite\" id=\"t-CLM-d3e120af\" data-claims=\"CLM-d3e120af\"><a class=\"cite-ref\" href=\"#bron-34\" aria-label=\"Source 34\">[34]</a></sup></td>\n<td>HL7 et FHIR (affirmation du fournisseur)<sup class=\"cite\" id=\"t-CLM-4f288ded\" data-claims=\"CLM-4f288ded\"><a class=\"cite-ref\" href=\"#bron-35\" aria-label=\"Source 35\">[35]</a></sup></td>\n<td>non trouvé ; 31 pays sans ventilation<sup class=\"cite\" id=\"t-CLM-65ff6420\" data-claims=\"CLM-65ff6420\"><a class=\"cite-ref\" href=\"#bron-34\" aria-label=\"Source 34\">[34]</a></sup></td>\n</tr>\n<tr>\n<td>Infor Cloverleaf</td>\n<td>moteur</td>\n<td>Infor<sup class=\"cite\" id=\"t-CLM-13605c49\" data-claims=\"CLM-13605c49\"><a class=\"cite-ref\" href=\"#bron-36\" aria-label=\"Source 36\">[36]</a></sup></td>\n<td>pas établi</td>\n<td>HL7v2, FHIR, CDA, X12 (affirmation du fournisseur)<sup class=\"cite\" data-claims=\"CLM-13605c49\"><a class=\"cite-ref\" href=\"#bron-36\" aria-label=\"Source 36\">[36]</a></sup></td>\n<td>non trouvé ; proposé aux Pays-Bas via Enovation<sup class=\"cite\" data-claims=\"CLM-20acebff\"><a class=\"cite-ref\" href=\"#bron-10\" aria-label=\"Source 10\">[10]</a></sup></td>\n</tr>\n</tbody>\n</table>\n<p>Précisions sur le tableau :\n- Les deux forks de Mirth sont nés après que NextGen a modifié la licence de Mirth Connect ; les détails figurent sur <a href=\"/fr/mirth-connect/\">Mirth Connect (NextGen Connect)</a>.<sup class=\"cite\" data-claims=\"CLM-ea0fa5c0\"><a class=\"cite-ref\" href=\"#bron-24\" aria-label=\"Source 24\">[24]</a></sup><sup class=\"cite\" data-claims=\"CLM-322e5f30\"><a class=\"cite-ref\" href=\"#bron-26\" aria-label=\"Source 26\">[26]</a></sup>\n- IPF (Open eHealth Integration Platform) est une extension d'Apache Camel pour les soins de santé, sous Apache License 2.0, avec des composants pour des profils IHE comme XDS, PIX, PDQ et XCPD.<sup class=\"cite\" data-claims=\"CLM-edba5f7e\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup><sup class=\"cite\" data-claims=\"CLM-d70d208d\"><a class=\"cite-ref\" href=\"#bron-28\" aria-label=\"Source 28\">[28]</a></sup>\n- InterSystems décrit Health Connect comme un moteur d'intégration pour de grands volumes de transactions, avec gestion des processus et monitoring continu (affirmation du fournisseur) ; la page de l'entreprise est <a href=\"/intersystems/\">InterSystems</a>.<sup class=\"cite\" data-claims=\"CLM-d3f47764\"><a class=\"cite-ref\" href=\"#bron-14\" aria-label=\"Source 14\">[14]</a></sup>\n- Rhapsody affirme construire des intégrations de n'importe quelle source vers n'importe quelle destination, à travers FHIR, les API, HL7 et MCP (affirmation du fournisseur).<sup class=\"cite\" id=\"t-CLM-f68daa0c\" data-claims=\"CLM-f68daa0c\"><a class=\"cite-ref\" href=\"#bron-34\" aria-label=\"Source 34\">[34]</a></sup> Selon Rhapsody, le moteur convertit aussi entre FHIR XML et JSON et établit des mappings entre FHIR et d'autres normes ; une utilisation en Belgique n'est pas démontrée.<sup class=\"cite\" id=\"t-CLM-bb2d829f\" data-claims=\"CLM-bb2d829f\"><a class=\"cite-ref\" href=\"#bron-37\" aria-label=\"Source 37\">[37]</a></sup>\n- <strong>Autre fonction : passerelle FHIR.</strong> Une passerelle ou façade FHIR comme <a href=\"/fr/fhir-station-amaron/\">FHIR Station</a> d'Amaron interroge des sources existantes de manière conforme à FHIR sans router elle-même des messages ni stocker des données (affirmation du fournisseur) ; les fonctions FHIR d'un moteur constituent une alternative à cela.<sup class=\"cite\" id=\"t-CLM-cf49678a\" data-claims=\"CLM-cf49678a\"><a class=\"cite-ref\" href=\"#bron-38\" aria-label=\"Source 38\">[38]</a></sup><sup class=\"cite\" id=\"t-CLM-ae15ffec\" data-claims=\"CLM-ae15ffec\"><a class=\"cite-ref\" href=\"#bron-14\" aria-label=\"Source 14\">[14]</a></sup>\n- Selon Infor, Infor Cloverleaf peut fonctionner dans le cloud, on-premises ou en mode hybride avec des conteneurs Docker (affirmation du fournisseur).<sup class=\"cite\" id=\"t-CLM-e7d74439\" data-claims=\"CLM-e7d74439\"><a class=\"cite-ref\" href=\"#bron-36\" aria-label=\"Source 36\">[36]</a></sup> Infor renvoie à un rapport Black Book de 2026 qui classe Infor comme fournisseur de premier plan de plates-formes d'intégration de données cliniques ; il s'agit là d'une affirmation du fournisseur que l'Atlas n'a pas pu vérifier.<sup class=\"cite\" id=\"t-CLM-95776dab\" data-claims=\"CLM-95776dab\"><a class=\"cite-ref\" href=\"#bron-36\" aria-label=\"Source 36\">[36]</a></sup></p>"
  },
  {
   "id": "contexte-belge",
   "title": "Contexte belge",
   "kind": "tekst",
   "html": "<ul>\n<li><strong>HD4DP v2 (healthdata.be).</strong> HD4DP v2 Local se compose de NextGen Connect (moteur d'intégration), de Form.io, de HD Connect et d'un entrepôt de données local.<sup class=\"cite\" data-claims=\"CLM-45aa1fa7\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup> NextGen Connect y traite toutes les intégrations, tant au sein de HD4DP qu'avec le monde extérieur.<sup class=\"cite\" id=\"t-CLM-166c1f66\" data-claims=\"CLM-166c1f66\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup> Pour chaque enregistrement de données, le composant détermine la destination, la transformation et la scission, avec livraison garantie.<sup class=\"cite\" data-claims=\"CLM-49dd434f\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup> Les systèmes maîtres des data providers n'adressent pas directement l'API des formulaires, mais passent par l'API que propose NextGen Connect.<sup class=\"cite\" id=\"t-CLM-ebfb4c34\" data-claims=\"CLM-ebfb4c34\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup> Voir <a href=\"/fr/hd4dp-v2/\">HD4DP v2 (healthdata.be)</a>.</li>\n<li><strong>Connexions eHealth (affirmations du fournisseur Amaron).</strong> L'intégrateur belge <a href=\"/fr/amaron/\">Amaron</a> déclare utiliser Mirth Connect pour ses connexions eHealth.<sup class=\"cite\" data-claims=\"CLM-936a6917\"><a class=\"cite-ref\" href=\"#bron-8\" aria-label=\"Source 8\">[8]</a></sup> Pour le Centraal Traceerbaarheidsregister, Amaron utilise un service web dans Mirth Connect, avec authentification et chiffrement via des certificats eHealth.<sup class=\"cite\" id=\"t-CLM-341a8ece\" data-claims=\"CLM-341a8ece\"><a class=\"cite-ref\" href=\"#bron-8\" aria-label=\"Source 8\">[8]</a></sup> Deux services web REST dans Mirth Connect reçoivent des données HD4DP et les envoient via une application <a href=\"/fr/ehealthbox-boite-aux-lettres-electronique-securisee/\">eHealthBox</a>.<sup class=\"cite\" id=\"t-CLM-70361611\" data-claims=\"CLM-70361611\"><a class=\"cite-ref\" href=\"#bron-8\" aria-label=\"Source 8\">[8]</a></sup></li>\n<li><strong>InterSystems.</strong> Un avis de marché européen décrit une programmation IRIS for Health et Ensemble pour l'intégration de l'application DPI Clinicom d'un seul hôpital avec d'autres logiciels.<sup class=\"cite\" data-claims=\"CLM-4cadafc8\"><a class=\"cite-ref\" href=\"#bron-32\" aria-label=\"Source 32\">[32]</a></sup> Cela ne prouve pas une utilisation par d'autres parties ; l'utilisation en Belgique de Health Connect lui-même n'a pas été trouvée. Selon un communiqué de presse, ZORGI est devenu en 2026 partenaire d'implémentation belge d'InterSystems pour HealthShare (affirmation du fournisseur).<sup class=\"cite\" id=\"t-CLM-77f38a9a\" data-claims=\"CLM-77f38a9a\"><a class=\"cite-ref\" href=\"#bron-39\" aria-label=\"Source 39\">[39]</a></sup></li>\n<li><strong>Ce qu'exige une connexion aux services eHealth</strong> (certificats, I.AM/STS, ETEE, connecteurs, tests d'enregistrement) figure par service cible sur <a href=\"/fr/integration-technique-avec-l-infrastructure-ehealth/\">Intégration technique avec l'infrastructure eHealth</a> ; les <a href=\"/fr/connecteurs-ehealth/\">connecteurs eHealth</a> sont des bibliothèques que l'on intègre dans des logiciels. La question de savoir si et comment les hôpitaux logent ces composants dans un moteur d'intégration n'est pas documentée en dehors des exemples d'Amaron (lacune). Le connecteur eHealth V4 (guide 1.10, 27 novembre 2025) est disponible comme bibliothèque Java (JAR) et comme version .NET (DLL) pour les développeurs qui l'intègrent dans leur propre application ; aucune mention d'un moteur d'intégration n'a été trouvée dans le guide (lacune).<sup class=\"cite\" id=\"t-CLM-b887c30d\" data-claims=\"CLM-b887c30d\"><a class=\"cite-ref\" href=\"#bron-40\" aria-label=\"Source 40\">[40]</a></sup></li>\n</ul>\n<p>Aucune utilisation en Belgique d'Open Integration Engine, de BridgeLink, d'Apache Camel/IPF, de Rhapsody ou d'Infor Cloverleaf n'a été trouvée ; c'est une lacune, non une preuve d'absence.</p>"
  },
  {
   "id": "conclusion",
   "title": "Conclusion",
   "kind": "tekst",
   "html": "<p><strong>Constats (avec source) :</strong>\n- Les fonctions essentielles d'un moteur d'intégration sont le filtrage, la transformation, l'extraction et le routage, complétés par des files d'attente persistantes, la relivraison et le monitoring.<sup class=\"cite\" data-claims=\"CLM-334477b1\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup><sup class=\"cite\" data-claims=\"CLM-389decff\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup><sup class=\"cite\" data-claims=\"CLM-dca55b1c\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup>\n- Pour HL7 v2, IHE prescrit MLLP, et les moteurs comme les frameworks prennent en charge MLLP et le traitement des ACK.<sup class=\"cite\" data-claims=\"CLM-17193907\"><a class=\"cite-ref\" href=\"#bron-2\" aria-label=\"Source 2\">[2]</a></sup><sup class=\"cite\" data-claims=\"CLM-96d1e5f0\"><a class=\"cite-ref\" href=\"#bron-3\" aria-label=\"Source 3\">[3]</a></sup><sup class=\"cite\" data-claims=\"CLM-6cc97ad8\"><a class=\"cite-ref\" href=\"#bron-16\" aria-label=\"Source 16\">[16]</a></sup>\n- Le marché comprend des moteurs open source (forks de Mirth sous MPL 2.0), un moteur passé de l'open source au propriétaire (Mirth Connect 4.6), des moteurs commerciaux (InterSystems, Rhapsody, Infor) et des frameworks open source (Camel, IPF, HAPI).<sup class=\"cite\" data-claims=\"CLM-00eeeca6\"><a class=\"cite-ref\" href=\"#bron-24\" aria-label=\"Source 24\">[24]</a></sup><sup class=\"cite\" data-claims=\"CLM-05fdc8d6\"><a class=\"cite-ref\" href=\"#bron-27\" aria-label=\"Source 27\">[27]</a></sup><sup class=\"cite\" data-claims=\"CLM-52d16276\"><a class=\"cite-ref\" href=\"#bron-22\" aria-label=\"Source 22\">[22]</a></sup><sup class=\"cite\" data-claims=\"CLM-4866354d\"><a class=\"cite-ref\" href=\"#bron-31\" aria-label=\"Source 31\">[31]</a></sup><sup class=\"cite\" data-claims=\"CLM-d3e120af\"><a class=\"cite-ref\" href=\"#bron-34\" aria-label=\"Source 34\">[34]</a></sup><sup class=\"cite\" data-claims=\"CLM-6a60adeb\"><a class=\"cite-ref\" href=\"#bron-7\" aria-label=\"Source 7\">[7]</a></sup></p>\n<p class=\"aanbeveling\"><strong>Recommandation (propre) :</strong> évaluez un moteur d'intégration non seulement sur ses fonctions, mais aussi sur la politique de licence et de correctifs, la disponibilité d'intégrateurs expérimentés en Belgique, la prise en charge de MLLP/ACK, de FHIR et de KMEHR, et la possibilité de suivre les messages et de les soumettre à nouveau. L'Atlas ne recommande aucun produit.</p>"
  },
  {
   "id": "signification-pratique-pour-les-hopitaux",
   "title": "Signification pratique pour les hôpitaux",
   "kind": "tekst",
   "html": "<p>Les organisations qui font tourner HD4DP v2 Local disposent déjà d'un moteur d'intégration (NextGen Connect) dans leur infrastructure.<sup class=\"cite\" data-claims=\"CLM-45aa1fa7\"><a class=\"cite-ref\" href=\"#bron-1\" aria-label=\"Source 1\">[1]</a></sup> Pour les versions open source de Mirth jusqu'à 4.5.2 incluse, NextGen ne fournit plus de correctifs de sécurité ; voir <a href=\"/fr/mirth-connect/\">Mirth Connect (NextGen Connect)</a>.<sup class=\"cite\" id=\"t-CLM-0f9a2ba2\" data-claims=\"CLM-0f9a2ba2\"><a class=\"cite-ref\" href=\"#bron-41\" aria-label=\"Source 41\">[41]</a></sup></p>\n<p class=\"aanbeveling\"><strong>Recommandation (propre) :</strong> tenez un inventaire de tous les moteurs d'intégration et des moteurs intégrés dans les logiciels livrés (y compris ceux de HD4DP), avec la version, la licence et l'indication de qui porte la gestion des correctifs. Lors des marchés publics, précisez explicitement si une couche d'intégration est livrée comme moteur, comme framework avec du code propre ou comme service d'un intégrateur.</p>"
  },
  {
   "id": "conditions-de-mise-en-uvre-et-limites",
   "title": "Conditions de mise en œuvre et limites",
   "kind": "tekst",
   "html": "<ul>\n<li><strong>Licence et coûts :</strong> pour Mirth Connect 4.6 et les versions ultérieures, une licence de NextGen est nécessaire ; InterSystems demande une clé de licence par instance IRIS.<sup class=\"cite\" id=\"t-CLM-68a758b3\" data-claims=\"CLM-68a758b3\"><a class=\"cite-ref\" href=\"#bron-42\" aria-label=\"Source 42\">[42]</a></sup><sup class=\"cite\" data-claims=\"CLM-4866354d\"><a class=\"cite-ref\" href=\"#bron-31\" aria-label=\"Source 31\">[31]</a></sup></li>\n<li><strong>Capacité de développement :</strong> des frameworks comme Camel demandent du développement Java, parce que les routes s'écrivent dans des DSL (Java, XML, YAML).<sup class=\"cite\" data-claims=\"CLM-645cdbfe\"><a class=\"cite-ref\" href=\"#bron-7\" aria-label=\"Source 7\">[7]</a></sup> Dans Mirth Connect également, les filtres et les transformers s'écrivent en JavaScript.<sup class=\"cite\" id=\"t-CLM-1f63c184\" data-claims=\"CLM-1f63c184\"><a class=\"cite-ref\" href=\"#bron-43\" aria-label=\"Source 43\">[43]</a></sup></li>\n<li><strong>Cycle de maintenance :</strong> Camel publie une release presque chaque mois ; les versions LTS reçoivent jusqu'à un an de corrections de bogues et de sécurité.<sup class=\"cite\" id=\"t-CLM-9605ff05\" data-claims=\"CLM-9605ff05\"><a class=\"cite-ref\" href=\"#bron-44\" aria-label=\"Source 44\">[44]</a></sup></li>\n<li><strong>Templates de conversion :</strong> les templates standard d'Azure $convert-data ne sont pas pris en charge par Microsoft.<sup class=\"cite\" data-claims=\"CLM-16aeb194\"><a class=\"cite-ref\" href=\"#bron-20\" aria-label=\"Source 20\">[20]</a></sup></li>\n</ul>"
  },
  {
   "id": "incertitudes-et-informations-contradictoires",
   "title": "Incertitudes et informations contradictoires",
   "kind": "tekst",
   "html": "<ul>\n<li><strong>Pas de définition neutre :</strong> aucune définition d'« integration engine » par HL7 International, IHE ou l'ISO n'a été trouvée ; cette page s'appuie sur des descriptions données par les créateurs et par healthdata.be (lacune).</li>\n<li><strong>Affirmations des fournisseurs :</strong> les déclarations d'InterSystems, de Rhapsody, d'Infor et d'Enovation sur les fonctions, la diffusion et le classement n'ont pas été vérifiées de manière indépendante.<sup class=\"cite\" data-claims=\"CLM-2a0d3143\"><a class=\"cite-ref\" href=\"#bron-14\" aria-label=\"Source 14\">[14]</a></sup><sup class=\"cite\" data-claims=\"CLM-65ff6420\"><a class=\"cite-ref\" href=\"#bron-34\" aria-label=\"Source 34\">[34]</a></sup><sup class=\"cite\" data-claims=\"CLM-95776dab\"><a class=\"cite-ref\" href=\"#bron-36\" aria-label=\"Source 36\">[36]</a></sup></li>\n<li><strong>Part de marché en Belgique :</strong> en dehors des affirmations du fournisseur Amaron, aucun chiffre n'a été trouvé sur les moteurs qu'utilisent les organisations de soins belges (lacune).</li>\n<li><strong>Nom dans HD4DP :</strong> healthdata.be parle de « NextGen Connect » ; la version et la licence livrées avec HD4DP v2 ne sont pas documentées (voir <a href=\"/fr/mirth-connect/\">Mirth Connect (NextGen Connect)</a>).<sup class=\"cite\" id=\"t-CLM-3ace548d\" data-claims=\"CLM-3ace548d\"><a class=\"cite-ref\" href=\"#bron-45\" aria-label=\"Source 45\">[45]</a></sup></li>\n</ul>"
  }
 ],
 "relation_groups": [
  {
   "type": "about",
   "direction": "uit",
   "label": "porte sur",
   "relations": [
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "mirth-connect",
      "title": "Mirth Connect (NextGen Connect)",
      "url": "/fr/mirth-connect/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": "Voorbeeld van een integratie-engine; open source (MPL 2.0) t/m 4.5.2, commercieel vanaf 4.6.",
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      1,
      18,
      9
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "intersystems-iris-for-health",
      "title": "InterSystems IRIS for Health et HealthShare",
      "url": "/fr/intersystems-iris-for-health-et-healthshare/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": "InterSystems Health Connect als commerciële integratie-engine (leveranciersomschrijving); een aanbestedingsbericht van één ziekenhuis beschrijft IRIS for Health- en Ensemble-programmering voor de integratie van zijn EPD-toepassing.",
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      14,
      11
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "apache-camel",
      "title": "Apache Camel",
      "url": "/fr/apache-camel/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": "Integratieframework en bibliotheek, geen kant-en-klare engine met beheerinterface; Belgisch gebruik niet gevonden.",
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      7,
      19
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "fhir",
      "title": "HL7 FHIR",
      "url": "/fr/hl7-fhir/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": "Transformaties van en naar FHIR (FHIR-API van HD4DP, Health Connect, Camel FHIR-component, Azure $convert-data).",
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      1,
      14,
      29,
      20
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "healthdata-hd4dp",
      "title": "HD4DP v2 (healthdata.be)",
      "url": "/fr/hd4dp-v2/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": "Belgisch voorbeeld van het patroon (transformatie, routering, gegarandeerde aflevering).",
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      1
     ]
    },
    {
     "direction": "uit",
     "type": "about",
     "label": "porte sur",
     "other": {
      "id": "amaron",
      "title": "Amaron",
      "url": "/fr/amaron/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": "Leveranciersclaim: Belgische integrator die eHealth-koppelingen op Mirth Connect bouwt.",
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      8
     ]
    }
   ]
  },
  {
   "type": "comparedWith",
   "direction": "in",
   "label": "est comparé à (entrant)",
   "relations": [
    {
     "direction": "in",
     "type": "comparedWith",
     "label": "est comparé à (entrant)",
     "other": {
      "id": "amaron-fhir-station",
      "title": "FHIR Station (Amaron)",
      "url": "/fr/fhir-station-amaron/"
     },
     "status": "hypothesis",
     "status_label": "hypothèse",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      14,
      37,
      23
     ]
    }
   ]
  },
  {
   "type": "seeAlso",
   "direction": "in",
   "label": "voir aussi (entrant)",
   "relations": [
    {
     "direction": "in",
     "type": "seeAlso",
     "label": "voir aussi (entrant)",
     "other": {
      "id": "apache-camel",
      "title": "Apache Camel",
      "url": "/fr/apache-camel/"
     },
     "status": "established",
     "status_label": "établi",
     "note_html": null,
     "valid_from": null,
     "valid_to": null,
     "historical": false,
     "refs": [
      7
     ]
    }
   ]
  }
 ],
 "relation_count": 8,
 "hypothesis_count": 1,
 "neighbours": [
  {
   "id": "mirth-connect",
   "title": "Mirth Connect (NextGen Connect)",
   "url": "/fr/mirth-connect/",
   "type": {
    "code": "Product",
    "label": "Produit logiciel"
   },
   "status": "established"
  },
  {
   "id": "intersystems-iris-for-health",
   "title": "InterSystems IRIS for Health et HealthShare",
   "url": "/fr/intersystems-iris-for-health-et-healthshare/",
   "type": {
    "code": "Product",
    "label": "Produit logiciel"
   },
   "status": "established"
  },
  {
   "id": "apache-camel",
   "title": "Apache Camel",
   "url": "/fr/apache-camel/",
   "type": {
    "code": "Product",
    "label": "Produit logiciel"
   },
   "status": "established"
  },
  {
   "id": "fhir",
   "title": "HL7 FHIR",
   "url": "/fr/hl7-fhir/",
   "type": {
    "code": "Specification",
    "label": "Norme ou spécification"
   },
   "status": "established"
  },
  {
   "id": "healthdata-hd4dp",
   "title": "HD4DP v2 (healthdata.be)",
   "url": "/fr/hd4dp-v2/",
   "type": {
    "code": "Platform",
    "label": "Plateforme ou service"
   },
   "status": "established"
  },
  {
   "id": "amaron",
   "title": "Amaron",
   "url": "/fr/amaron/",
   "type": {
    "code": "Organization",
    "label": "Organisation"
   },
   "status": "established"
  },
  {
   "id": "amaron-fhir-station",
   "title": "FHIR Station (Amaron)",
   "url": "/fr/fhir-station-amaron/",
   "type": {
    "code": "Product",
    "label": "Produit logiciel"
   },
   "status": "hypothesis"
  }
 ],
 "open_questions_html": [
  "Welke integratie-engines gebruiken Belgische ziekenhuizen, labo's en woonzorgcentra? Buiten leveranciersclaims werden geen marktcijfers gevonden.",
  "Worden Open Integration Engine, BridgeLink, Rhapsody, Infor Cloverleaf, Apache Camel/IPF of Azure-conversiediensten in de Belgische zorg gebruikt? Geen bron gevonden.",
  "Bestaan er publieke, herbruikbare kanalen of mappings voor KMEHR, hubs/metahub, MyCareNet of de eHealth-connectoren op een integratie-engine?",
  "Welke rol spelen integratie-engines in de Belgische FHIR-transitie (FHIR-facades vóór bestaande HL7 v2- en KMEHR-stromen)?",
  "Bestaat er een neutrale definitie (HL7 International, IHE, ISO) van 'integration engine' of 'interface engine'? Niet gevonden (geraadpleegd 2026-10-08)."
 ],
 "open_questions": [
  {
   "id": "oq-884f04",
   "html": "Welke integratie-engines gebruiken Belgische ziekenhuizen, labo's en woonzorgcentra? Buiten leveranciersclaims werden geen marktcijfers gevonden.",
   "text": "Welke integratie-engines gebruiken Belgische ziekenhuizen, labo's en woonzorgcentra? Buiten leveranciersclaims werden geen marktcijfers gevonden."
  },
  {
   "id": "oq-792394",
   "html": "Worden Open Integration Engine, BridgeLink, Rhapsody, Infor Cloverleaf, Apache Camel/IPF of Azure-conversiediensten in de Belgische zorg gebruikt? Geen bron gevonden.",
   "text": "Worden Open Integration Engine, BridgeLink, Rhapsody, Infor Cloverleaf, Apache Camel/IPF of Azure-conversiediensten in de Belgische zorg gebruikt? Geen bron gevonden."
  },
  {
   "id": "oq-7ec7b7",
   "html": "Bestaan er publieke, herbruikbare kanalen of mappings voor KMEHR, hubs/metahub, MyCareNet of de eHealth-connectoren op een integratie-engine?",
   "text": "Bestaan er publieke, herbruikbare kanalen of mappings voor KMEHR, hubs/metahub, MyCareNet of de eHealth-connectoren op een integratie-engine?"
  },
  {
   "id": "oq-cce39a",
   "html": "Welke rol spelen integratie-engines in de Belgische FHIR-transitie (FHIR-facades vóór bestaande HL7 v2- en KMEHR-stromen)?",
   "text": "Welke rol spelen integratie-engines in de Belgische FHIR-transitie (FHIR-facades vóór bestaande HL7 v2- en KMEHR-stromen)?"
  },
  {
   "id": "oq-3b7f6f",
   "html": "Bestaat er een neutrale definitie (HL7 International, IHE, ISO) van 'integration engine' of 'interface engine'? Niet gevonden (geraadpleegd 2026-10-08).",
   "text": "Bestaat er een neutrale definitie (HL7 International, IHE, ISO) van 'integration engine' of 'interface engine'? Niet gevonden (geraadpleegd 2026-10-08)."
  }
 ],
 "exchanges": [],
 "sources": [
  {
   "n": 1,
   "id": "SRC-cd9b7aab6e",
   "title": "General description of the HD4DP v2 application",
   "publisher": "healthdata.be (HDA)",
   "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/general-description-hd4dp-v2-application",
   "published": null,
   "first_retrieved": "2026-09-26T10:36:17+00:00",
   "last_checked": "2026-09-26T10:36:17+00:00",
   "content_sha256": "599ccfc7d6dc170e59af4513983419ed276e727dde082570f780c4859caad286",
   "link_unreachable_since": null
  },
  {
   "n": 2,
   "id": "SRC-b116a29d8b",
   "title": "IHE ITI Technical Framework Volume 2 - Appendix C: HL7 Profiling Conventions",
   "publisher": "IHE International",
   "url": "https://profiles.ihe.net/ITI/TF/Volume2/ch-C.html",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:20+00:00",
   "last_checked": "2026-09-28T13:34:20+00:00",
   "content_sha256": "f1434b0c9461427e0d6c4afa6b7a20bb8b0ed98967f5a1f6b4a27d4183fc4b16",
   "link_unreachable_since": null
  },
  {
   "n": 3,
   "id": "SRC-c89553889f",
   "title": "Mirth Connect wiki - 3.0.0 What's New",
   "publisher": "NextGen Healthcare",
   "url": "https://github.com/nextgenhealthcare/connect/wiki/3.0.0---What's-New",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:20+00:00",
   "last_checked": "2026-09-28T13:34:20+00:00",
   "content_sha256": "cb36c70a2b64004da2c207edc707cb62bb9bd6fe2965e2800b93ce27903cd463",
   "link_unreachable_since": null
  },
  {
   "n": 4,
   "id": "SRC-aa08148984",
   "title": "Apache ActiveMQ",
   "publisher": "The Apache Software Foundation",
   "url": "https://activemq.apache.org/",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:31+00:00",
   "last_checked": "2026-09-28T13:34:31+00:00",
   "content_sha256": "8bca77e87aa1534e76344916ba27887e5ae4e2b6d7361acbe468fe8ebbd09d64",
   "link_unreachable_since": null
  },
  {
   "n": 5,
   "id": "SRC-4b6feb6916",
   "title": "Apache Kafka - Introduction",
   "publisher": "The Apache Software Foundation",
   "url": "https://kafka.apache.org/intro/",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:31+00:00",
   "last_checked": "2026-09-28T13:34:31+00:00",
   "content_sha256": "4a020f5db3a31ab70aa3c3332620d73b77a8c6e7904b94dac04476d5907b6f20",
   "link_unreachable_since": null
  },
  {
   "n": 6,
   "id": "SRC-aa061878d4",
   "title": "HAPI - The Open Source HL7 API for Java",
   "publisher": "HAPI-project (University Health Network)",
   "url": "https://hapifhir.github.io/hapi-hl7v2/",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:20+00:00",
   "last_checked": "2026-09-28T13:34:20+00:00",
   "content_sha256": "77092b2a94146e6bf83b93571acb27520c86af09e261a0880ab8f81c5d791107",
   "link_unreachable_since": null
  },
  {
   "n": 7,
   "id": "SRC-9bc6ac0a7f",
   "title": "What is Camel?",
   "publisher": "The Apache Software Foundation",
   "url": "https://camel.apache.org/manual/faq/what-is-camel.html",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:23+00:00",
   "last_checked": "2026-09-28T13:34:23+00:00",
   "content_sha256": "98f4e85076bdcc033b438f535006e17d0edea5c21359bc129feb3af8577b6699",
   "link_unreachable_since": null
  },
  {
   "n": 8,
   "id": "SRC-268611b7ba",
   "title": "Interactie met externe platformen (e-health)",
   "publisher": "Amaron",
   "url": "https://amaron.be/ehealth/",
   "published": null,
   "first_retrieved": "2026-09-26T11:14:31+00:00",
   "last_checked": "2026-09-26T11:14:31+00:00",
   "content_sha256": "ac8129398e0ab8e61a2401c79c67c793051731a0f2f2bfbba3dabac7ffbaaed7",
   "link_unreachable_since": null
  },
  {
   "n": 9,
   "id": "SRC-516352689e",
   "title": "Eclipse Open Integration Engine (projectvoorstel)",
   "publisher": "Eclipse Foundation",
   "url": "https://projects.eclipse.org/proposals/eclipse-open-integration-engine",
   "published": null,
   "first_retrieved": "2026-09-28T13:06:22+00:00",
   "last_checked": "2026-09-28T13:06:22+00:00",
   "content_sha256": "acbf50d688c20e91d148e9cbfe7e1c4d63c355a505ba6364564cb89eb19a7915",
   "link_unreachable_since": null
  },
  {
   "n": 10,
   "id": "SRC-dd2b781f48",
   "title": "Cloverleaf - Enovation",
   "publisher": "Enovation",
   "url": "https://enovationgroup.com/en/cloverleaf/",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:34+00:00",
   "last_checked": "2026-09-28T13:34:34+00:00",
   "content_sha256": "758976352f82d5eec171cc3341d9a52679af7973c740e93f7711d0af825a4fef",
   "link_unreachable_since": null
  },
  {
   "n": 11,
   "id": "SRC-f7ca717425",
   "title": "Introduction to HL7 Version 2 (Routing HL7 Version 2 Messages in Productions)",
   "publisher": "InterSystems",
   "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=EHL72_intro",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:34+00:00",
   "last_checked": "2026-09-28T13:34:34+00:00",
   "content_sha256": "fa9255aa520ff56080217ced31f51e4277efac1363e467d6cc0b702f1ac6c00d",
   "link_unreachable_since": null
  },
  {
   "n": 12,
   "id": "SRC-25769bece9",
   "title": "Mirth Connect wiki - 3.12.0 What's New",
   "publisher": "NextGen Healthcare",
   "url": "https://github.com/nextgenhealthcare/connect/wiki/3.12.0---What's-New",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:29+00:00",
   "last_checked": "2026-09-28T13:34:29+00:00",
   "content_sha256": "ab72e3856922ca74dfd4ad87e65ae6d2062733e33fa9905a4f84993aa5966d49",
   "link_unreachable_since": null
  },
  {
   "n": 13,
   "id": "SRC-8da1ea8396",
   "title": "Mirth® Connect by NextGen Healthcare (GitHub-repository, README)",
   "publisher": "NextGen Healthcare (GitHub)",
   "url": "https://github.com/nextgenhealthcare/connect",
   "published": null,
   "first_retrieved": "2026-09-28T13:06:13+00:00",
   "last_checked": "2026-09-28T13:06:13+00:00",
   "content_sha256": "38d71188fc324566c845eae41ecb0a1c8c4bc5da308a9d03cd995d5f72c6615e",
   "link_unreachable_since": null
  },
  {
   "n": 14,
   "id": "SRC-b870d6655c",
   "title": "InterSystems Health Connect Overview",
   "publisher": "InterSystems",
   "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=AHXHCOVW",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:32+00:00",
   "last_checked": "2026-09-28T13:34:32+00:00",
   "content_sha256": "afa5d0ca23c8e198e07f9405b78043c8aa339285856cbc3c579d6bf0434f0dc7",
   "link_unreachable_since": null
  },
  {
   "n": 15,
   "id": "SRC-d3df6e5982",
   "title": "Apache Camel - Dead Letter Channel",
   "publisher": "The Apache Software Foundation",
   "url": "https://camel.apache.org/components/4.22.x/eips/dead-letter-channel.html",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:29+00:00",
   "last_checked": "2026-09-28T13:34:29+00:00",
   "content_sha256": "d77181b2c9e764e9bfab580fb0dd94e843bc35b4e73693b32024a12c813c5747",
   "link_unreachable_since": null
  },
  {
   "n": 16,
   "id": "SRC-766f18cbf7",
   "title": "Apache Camel - MLLP component",
   "publisher": "The Apache Software Foundation",
   "url": "https://camel.apache.org/components/4.22.x/mllp-component.html",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:26+00:00",
   "last_checked": "2026-09-28T13:34:26+00:00",
   "content_sha256": "a8c56be58a89cbc72b9b268b3f1ab63e458e3553a1d82eeef66eea02c9ab744d",
   "link_unreachable_since": null
  },
  {
   "n": 17,
   "id": "SRC-98bb53751c",
   "title": "HAPI FHIR - Java API for HL7 FHIR Clients and Servers (GitHub)",
   "publisher": "HAPI FHIR-project",
   "url": "https://github.com/hapifhir/hapi-fhir",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:33+00:00",
   "last_checked": "2026-09-28T13:34:33+00:00",
   "content_sha256": "e9b3feb27bca0343eefdd0f1523c9c2c53568d65fc7e2b67f5dde8ddcddc29d5",
   "link_unreachable_since": null
  },
  {
   "n": 18,
   "id": "SRC-ca89476bda",
   "title": "Frequently Asked Questions · nextgenhealthcare/connect Wiki",
   "publisher": "NextGen Healthcare (GitHub)",
   "url": "https://github.com/nextgenhealthcare/connect/wiki/Frequently-Asked-Questions",
   "published": null,
   "first_retrieved": "2026-09-28T13:06:11+00:00",
   "last_checked": "2026-09-28T13:06:11+00:00",
   "content_sha256": "d97317b389c75ba503f494ad71e9fb151c4f0f3b7e98ee04676f821e9588dfc1",
   "link_unreachable_since": null
  },
  {
   "n": 19,
   "id": "SRC-6cb214c582",
   "title": "Apache Camel - HL7 (component en dataformat)",
   "publisher": "The Apache Software Foundation",
   "url": "https://camel.apache.org/components/4.22.x/dataformats/hl7-dataformat.html",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:25+00:00",
   "last_checked": "2026-09-28T13:34:25+00:00",
   "content_sha256": "436d54d25d72f83a2de833cf7173956e66702bee16ac3c7e9a7d667942ed2584",
   "link_unreachable_since": null
  },
  {
   "n": 20,
   "id": "SRC-b98c0fb8ce",
   "title": "Convert health data with $convert-data in FHIR",
   "publisher": "Microsoft",
   "url": "https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/convert-data-overview",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:34+00:00",
   "last_checked": "2026-09-28T13:34:34+00:00",
   "content_sha256": "04b0cbc7fddba37622d7a6f10039680cccbc7e5c4a4ca17af677899f9e4423bf",
   "link_unreachable_since": null
  },
  {
   "n": 21,
   "id": "SRC-f2aa84429a",
   "title": "Healthcare Integration Engine | Mirth® Connect by NextGen Healthcare",
   "publisher": "NextGen Healthcare",
   "url": "https://www.nextgen.com/solutions/interoperability/mirth-integration-engine",
   "published": null,
   "first_retrieved": "2026-09-28T13:06:18+00:00",
   "last_checked": "2026-09-28T13:06:18+00:00",
   "content_sha256": "cc33713f26817b37ff89d6f6aa554f856c49c315978970ef8978f7ef965b4a33",
   "link_unreachable_since": null
  },
  {
   "n": 22,
   "id": "SRC-2aa07dd2b9",
   "title": "A New Era for Mirth® Connect by NextGen Healthcare",
   "publisher": "NextGen Healthcare",
   "url": "https://www.nextgen.com/blog/industry-news/a-new-era-for-mirth-connect-by-nextgen-healthcare",
   "published": "2025-03-19",
   "first_retrieved": "2026-09-28T13:06:13+00:00",
   "last_checked": "2026-09-28T13:06:13+00:00",
   "content_sha256": "d0e2dbb4c84da541aa8ecca7ac0be4d13870a74412b6e621a8af5ad7a3f84af3",
   "link_unreachable_since": null
  },
  {
   "n": 23,
   "id": "SRC-41e47a2e35",
   "title": "Mirth Connect wiki - 3.9.0 What's New",
   "publisher": "NextGen Healthcare",
   "url": "https://github.com/nextgenhealthcare/connect/wiki/3.9.0---What's-New",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:27+00:00",
   "last_checked": "2026-09-28T13:34:27+00:00",
   "content_sha256": "51d74eb42e73166bc342a358ed4c22229a2f8c8c189ffed8ecd409e8f11f4b5c",
   "link_unreachable_since": null
  },
  {
   "n": 24,
   "id": "SRC-035f231c9a",
   "title": "OpenIntegrationEngine/engine – An open source fork of the now closed-source Mirth Connect",
   "publisher": "Open Integration Engine-project (GitHub)",
   "url": "https://github.com/OpenIntegrationEngine/engine",
   "published": null,
   "first_retrieved": "2026-09-28T13:06:26+00:00",
   "last_checked": "2026-09-28T13:06:26+00:00",
   "content_sha256": "81f88f56f60a160373e072c2e4337a1646eb78ac2be98ef4c67d207ce3cc5b8e",
   "link_unreachable_since": null
  },
  {
   "n": 25,
   "id": "SRC-bcf20c768e",
   "title": "Open Integration Engine – Healthcare Integration, Free and Open Source",
   "publisher": "Open Integration Engine-project",
   "url": "https://openintegrationengine.org/",
   "published": null,
   "first_retrieved": "2026-09-28T13:06:22+00:00",
   "last_checked": "2026-09-28T13:06:22+00:00",
   "content_sha256": "7689be1c4f0b6de8ea3f606578f17694f544633af4f2d4aa4da73a5d2c323f88",
   "link_unreachable_since": null
  },
  {
   "n": 26,
   "id": "SRC-1e4f421d7e",
   "title": "A Look at BridgeLink's Fork of the Open Source Mirth Connect",
   "publisher": "Healthcare IT Today",
   "url": "https://www.healthcareittoday.com/2025/08/14/a-look-at-bridgelinks-fork-of-the-open-source-mirth-connect/",
   "published": "2025-08-14",
   "first_retrieved": "2026-09-28T13:06:22+00:00",
   "last_checked": "2026-09-28T13:06:22+00:00",
   "content_sha256": "5fbf5ca3338374502e7867abc6f76ce7f75e14785d29cedb6f3c7c89f5527692",
   "link_unreachable_since": null
  },
  {
   "n": 27,
   "id": "SRC-413a8a189a",
   "title": "Innovar-Healthcare/BridgeLink (GitHub-repository, README)",
   "publisher": "Innovar Healthcare (GitHub)",
   "url": "https://github.com/Innovar-Healthcare/BridgeLink",
   "published": null,
   "first_retrieved": "2026-09-28T13:06:32+00:00",
   "last_checked": "2026-09-28T13:06:32+00:00",
   "content_sha256": "0b2109fe96a878beac3747c01c6d564dd1809d9b79120cdf711aa4f4369d3595",
   "link_unreachable_since": null
  },
  {
   "n": 28,
   "id": "SRC-54855d801f",
   "title": "Open eHealth Integration Platform (IPF) - GitHub",
   "publisher": "Open eHealth Foundation",
   "url": "https://github.com/oehf/ipf",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:35+00:00",
   "last_checked": "2026-09-28T13:34:35+00:00",
   "content_sha256": "3663ca1a40b11ce789f1f5c7d5f2878b03333858beff72d68ec052716d35519d",
   "link_unreachable_since": null
  },
  {
   "n": 29,
   "id": "SRC-e9063759a6",
   "title": "Apache Camel - FHIR component",
   "publisher": "The Apache Software Foundation",
   "url": "https://camel.apache.org/components/4.22.x/fhir-component.html",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:28+00:00",
   "last_checked": "2026-09-28T13:34:28+00:00",
   "content_sha256": "27c0843e1b05ab19cf320452d1f9187e2375ab0dbb338b462dc8c78f0fd8c751",
   "link_unreachable_since": null
  },
  {
   "n": 30,
   "id": "SRC-c6240a0598",
   "title": "HAPI - Project License",
   "publisher": "HAPI-project",
   "url": "https://hapifhir.github.io/hapi-hl7v2/license.html",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:22+00:00",
   "last_checked": "2026-09-28T13:34:22+00:00",
   "content_sha256": "52bc60b3bf1b77890bf9f0c659475a222877868bb39b4c510aaf589c15e1aafc",
   "link_unreachable_since": null
  },
  {
   "n": 31,
   "id": "SRC-c89022e014",
   "title": "Managing InterSystems IRIS Licensing",
   "publisher": "InterSystems",
   "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=GSA_license",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:36+00:00",
   "last_checked": "2026-09-28T13:34:36+00:00",
   "content_sha256": "75ae4fa9218147ba5e3656c6a74209a26e1ec866d61826ef7897257f52ac2309",
   "link_unreachable_since": null
  },
  {
   "n": 32,
   "id": "SRC-a1e3d9ea7c",
   "title": "België – Informaticadiensten – Raamovereenkomst voor EPD consultancy, specifiek voor IRIS for Health platform ontwikkeling (UZ Gent) – 792714-2025",
   "publisher": "Publicatieblad van de EU (TED)",
   "url": "https://ted.europa.eu/nl/notice/792714-2025/html",
   "published": "2025-11-28",
   "first_retrieved": "2026-09-26T10:42:22+00:00",
   "last_checked": "2026-09-26T10:42:22+00:00",
   "content_sha256": "22425da88649380b58340c41bbdffed4b736c7da3c2762ef948df0715cb9c203",
   "link_unreachable_since": null
  },
  {
   "n": 33,
   "id": "SRC-15645f681e",
   "title": "Interoperability Platform Lyniate Rebrands as Rhapsody",
   "publisher": "HIT Consultant",
   "url": "https://hitconsultant.net/2023/04/03/lyniate-rebrands-as-rhapsody/",
   "published": "2023-04-03",
   "first_retrieved": "2026-09-28T13:34:33+00:00",
   "last_checked": "2026-09-28T13:34:33+00:00",
   "content_sha256": "d769ac465690d5bed16acfe84a2e72abb1de5c7e14449d3f9de019c73017c5db",
   "link_unreachable_since": null
  },
  {
   "n": 34,
   "id": "SRC-9559264fe8",
   "title": "Rhapsody Integration Engine for Healthcare Interoperability",
   "publisher": "Rhapsody",
   "url": "https://rhapsody.health/solutions/rhapsody/",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:32+00:00",
   "last_checked": "2026-09-28T13:34:32+00:00",
   "content_sha256": "bed1a55779abefcb74c0f62975ff05fa0e8cc38cfe75898ff99742efa0cbe758",
   "link_unreachable_since": null
  },
  {
   "n": 35,
   "id": "SRC-0c54db06e2",
   "title": "About us - Rhapsody",
   "publisher": "Rhapsody",
   "url": "https://rhapsody.health/about-us/",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:34+00:00",
   "last_checked": "2026-09-28T13:34:34+00:00",
   "content_sha256": "8632efe58400e267c20d3028c0ae99bce49f7576ad5957920565e94f4fa289ed",
   "link_unreachable_since": null
  },
  {
   "n": 36,
   "id": "SRC-f4f81515f7",
   "title": "Infor Cloverleaf healthcare integration engine",
   "publisher": "Infor",
   "url": "https://www.infor.com/products/cloverleaf",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:34+00:00",
   "last_checked": "2026-09-28T13:34:34+00:00",
   "content_sha256": "62c84d1e40de95b8a9f60ba082d7204dc92c7ed65f858a07ff12aa47cf21102f",
   "link_unreachable_since": null
  },
  {
   "n": 37,
   "id": "SRC-1dd1e122c7",
   "title": "Product brochure – Rhapsody Integration Engine (2026)",
   "publisher": "Rhapsody Health",
   "url": "https://rhapsody.health/wp-content/uploads/2023/03/rg_Product_brochure_Rhapsody-Integration-Engine_2026.pdf",
   "published": null,
   "first_retrieved": "2026-10-01T07:35:00+00:00",
   "last_checked": "2026-10-01T07:35:00+00:00",
   "content_sha256": "ac95c95a20313ddd9a64c9199214d38a442d34a7016c2fa6a865a65b064479bb",
   "link_unreachable_since": null
  },
  {
   "n": 38,
   "id": "SRC-b85fced929",
   "title": "White paper – Beginnen met FHIR: waarom en hoe pak je het aan? (© 2024-07, bestand 2024-11-28)",
   "publisher": "Amaron BV",
   "url": "https://amaron.be/wp-content/uploads/2024/12/AMARON_WhitePaper_Beginnen-met-FHIR_NL_20241128_DIGITAL.pdf",
   "published": null,
   "first_retrieved": "2026-10-01T07:34:46+00:00",
   "last_checked": "2026-10-01T07:34:46+00:00",
   "content_sha256": "5b4060824e07096c81d3787420137d0dd5c0bae3b64604da7c23bdf9a8eac1f6",
   "link_unreachable_since": null
  },
  {
   "n": 39,
   "id": "SRC-9750479a42",
   "title": "InterSystems et ZORGI renforcent leur partenariat autour des solutions HealthShare en Belgique",
   "publisher": "ZORGI",
   "url": "https://www.zorgi.be/actualites/corporate/intersystems-zorgi-renforcent-partenariat-solutions-healthshare-belgique/",
   "published": "2026-02-26",
   "first_retrieved": "2026-09-26T11:14:36+00:00",
   "last_checked": "2026-09-26T11:14:36+00:00",
   "content_sha256": "e1beebde2bc577dd612f81336f97bf77067331f548a9d5a503221ab9a7e7f3de",
   "link_unreachable_since": null
  },
  {
   "n": 40,
   "id": "SRC-6fed0ba536",
   "title": "eHealth-platform Services Connectors V4 - Guide v.1.10",
   "publisher": "eHealth-platform",
   "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/8f40846c5d1c18ead66a323e5c51200ee84df14d/eh_connectors-v4-introduction_guide-1.10.pdf",
   "published": "2025-11-27",
   "first_retrieved": "2026-10-08T16:24:39+00:00",
   "last_checked": "2026-10-08T16:24:39+00:00",
   "content_sha256": "1a13c9d128e72085c4db33f9bca67ac4dc9d29c473e4cc03d3574daa7e0c1393",
   "link_unreachable_since": null
  },
  {
   "n": 41,
   "id": "SRC-2f0d02aa2a",
   "title": "Security Policy (SECURITY.md) – nextgenhealthcare/connect",
   "publisher": "NextGen Healthcare (GitHub)",
   "url": "https://github.com/nextgenhealthcare/connect/blob/development/SECURITY.md",
   "published": null,
   "first_retrieved": "2026-09-28T13:06:15+00:00",
   "last_checked": "2026-09-28T13:06:15+00:00",
   "content_sha256": "dd7d27a57aa7eb06b0d77cc89dd44afc2689248ce78b668116a168763d47035d",
   "link_unreachable_since": null
  },
  {
   "n": 42,
   "id": "SRC-d17c49e8bc",
   "title": "Mirth Connect Distribution – New licensing model (mirth-downloads)",
   "publisher": "NextGen Healthcare",
   "url": "https://www.nextgen.com/solutions/interoperability/mirth-integration-engine/mirth-connect-downloads",
   "published": null,
   "first_retrieved": "2026-09-28T13:06:15+00:00",
   "last_checked": "2026-09-28T13:06:15+00:00",
   "content_sha256": "a712bca5339bf9c742cddd0b825d9160eecd50f3ecefb1e0cbe5e1df6e3c2660",
   "link_unreachable_since": null
  },
  {
   "n": 43,
   "id": "SRC-de53c34c4c",
   "title": "Mirth Connect wiki - 3.7.0 What's New",
   "publisher": "NextGen Healthcare",
   "url": "https://github.com/nextgenhealthcare/connect/wiki/3.7.0---What's-New",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:23+00:00",
   "last_checked": "2026-09-28T13:34:23+00:00",
   "content_sha256": "71d0b36d9e7ab8440550a9b797dc56d848bce8ace612e89ffd6cb38b175596db",
   "link_unreachable_since": null
  },
  {
   "n": 44,
   "id": "SRC-1e7e6d2774",
   "title": "Apache Camel - Downloads",
   "publisher": "The Apache Software Foundation",
   "url": "https://camel.apache.org/download/",
   "published": null,
   "first_retrieved": "2026-09-28T13:34:32+00:00",
   "last_checked": "2026-09-28T13:34:32+00:00",
   "content_sha256": "a07199b04fa60983951300a1b1f43b21ae1c3ce4cbc311df2f4f090eaa33fff2",
   "link_unreachable_since": null
  },
  {
   "n": 45,
   "id": "SRC-4df4701ab2",
   "title": "HD4DP v2 Infrastructure instructions",
   "publisher": "healthdata.be",
   "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/hd4dp-v2-infrastructure-instructions",
   "published": null,
   "first_retrieved": "2026-09-28T13:06:23+00:00",
   "last_checked": "2026-09-28T13:06:23+00:00",
   "content_sha256": "78a7e12c20503693e356d084ab319e070c29222a4ddb9f538a7588d42104b170",
   "link_unreachable_since": null
  }
 ],
 "claims": [
  {
   "id": "CLM-dba676c9",
   "statement": "De healthdata.be-documentatie omschrijft NextGen Connect als een integratie-engine voor de zorg die berichtstandaarden (o.a. HL7, DICOM, ANSI X12, ASCII en XML) vertaalt naar de standaard die het ontvangende systeem vereist.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'NextGen Connect'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-cd9b7aab6e",
    "title": "General description of the HD4DP v2 application",
    "publisher": "healthdata.be (HDA)",
    "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/general-description-hd4dp-v2-application",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-334477b1",
   "statement": "Volgens healthdata.be zijn de hoofdfuncties van die integratie-engine filteren, transformeren, extraheren en routeren.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'NextGen Connect'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-cd9b7aab6e",
    "title": "General description of the HD4DP v2 application",
    "publisher": "healthdata.be (HDA)",
    "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/general-description-hd4dp-v2-application",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-17193907",
   "statement": "IHE schrijft voor dat toepassingen HL7 v2-berichten over het netwerk uitwisselen met het Minimal Lower Layer Protocol (MLLP) uit Appendix C van de HL7 Implementation Guide.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "C.2.1 Network Guidelines",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-b116a29d8b",
    "title": "IHE ITI Technical Framework Volume 2 - Appendix C: HL7 Profiling Conventions",
    "publisher": "IHE International",
    "url": "https://profiles.ihe.net/ITI/TF/Volume2/ch-C.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-0900d5b9",
   "statement": "In de Original Acknowledgement Mode meldt het ACK-bericht eventuele applicatiefouten van de ontvangende toepassing terug aan de zender.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "C.2.3 Acknowledgement Modes",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-b116a29d8b",
    "title": "IHE ITI Technical Framework Volume 2 - Appendix C: HL7 Profiling Conventions",
    "publisher": "IHE International",
    "url": "https://profiles.ihe.net/ITI/TF/Volume2/ch-C.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-389decff",
   "statement": "Depuis la 3.0, Mirth persiste les messages pendant le traitement dans un canal, de sorte que chaque message peut, après une défaillance du système ou l'arrêt d'un canal, continuer à être traité là où il en était resté.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'System-wide Queuing & Automatic Message Recovery'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-c89553889f",
    "title": "Mirth Connect wiki - 3.0.0 What's New",
    "publisher": "NextGen Healthcare",
    "url": "https://github.com/nextgenhealthcare/connect/wiki/3.0.0---What's-New",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-b4bfb612",
   "statement": "Depuis la 3.0, une file d'attente de destination est disponible sur chaque connecteur de destination; les messages en attente sont stockés dans la base de données au lieu de fichiers de file d'attente.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Destination Queue - Now available for all destination connectors'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-c89553889f",
    "title": "Mirth Connect wiki - 3.0.0 What's New",
    "publisher": "NextGen Healthcare",
    "url": "https://github.com/nextgenhealthcare/connect/wiki/3.0.0---What's-New",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-49dd434f",
   "statement": "In HD4DP v2 bepaalt NextGen Connect per te leveren gegevensrecord de bestemming, transformatie en opsplitsing, en doet dat met gegarandeerde aflevering (guaranteed delivery), zo nodig met nieuwe pogingen na een fout.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'NextGen Connect', 'Data delivery'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-cd9b7aab6e",
    "title": "General description of the HD4DP v2 application",
    "publisher": "healthdata.be (HDA)",
    "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/general-description-hd4dp-v2-application",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-c3fb6bfb",
   "statement": "Apache ActiveMQ is een algemene, Java-gebaseerde message broker die meerdere protocollen ondersteunt (o.a. AMQP, STOMP, MQTT, JMS); het is geen zorgspecifieke integratie-engine.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "startpagina, inleiding",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-aa08148984",
    "title": "Apache ActiveMQ",
    "publisher": "The Apache Software Foundation",
    "url": "https://activemq.apache.org/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-11a0abcc",
   "statement": "Apache Kafka laat toe om stromen van events te publiceren en erop in te schrijven, inclusief continue import en export van gegevens uit andere systemen.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Apache Kafka is an event streaming platform', punt 1",
   "as_of": "2026-10-08",
   "source": {
    "id": "SRC-4b6feb6916",
    "title": "Apache Kafka - Introduction",
    "publisher": "The Apache Software Foundation",
    "url": "https://kafka.apache.org/intro/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-41b3e598",
   "statement": "Apache Kafka slaat stromen van events duurzaam en betrouwbaar op, zolang men dat wil.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Apache Kafka is an event streaming platform', punt 2",
   "as_of": "2026-10-08",
   "source": {
    "id": "SRC-4b6feb6916",
    "title": "Apache Kafka - Introduction",
    "publisher": "The Apache Software Foundation",
    "url": "https://kafka.apache.org/intro/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-5ec7787f",
   "statement": "HAPI (HL7 application programming interface) is een open-source, objectgeoriënteerde HL7 2.x-parser voor Java: een bibliotheek om HL7-functies in eigen toepassingen in te bouwen, geen zelfstandige engine.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Welcome'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-aa061878d4",
    "title": "HAPI - The Open Source HL7 API for Java",
    "publisher": "HAPI-project (University Health Network)",
    "url": "https://hapifhir.github.io/hapi-hl7v2/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-645cdbfe",
   "statement": "Camel is een kleine bibliotheek die in eender welke Java-toepassing wordt ingebouwd; routerings- en mediatieregels worden in DSL's (Java, XML, YAML) geschreven, niet in een grafische engine.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "What is Camel?",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-9bc6ac0a7f",
    "title": "What is Camel?",
    "publisher": "The Apache Software Foundation",
    "url": "https://camel.apache.org/manual/faq/what-is-camel.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-45aa1fa7",
   "statement": "HD4DP v2 se compose de NextGen Connect (moteur d'intégration), Form.io, HD Connect et d'un datawarehouse local (PostgreSQL).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Components and features",
   "as_of": "2026-09-26",
   "source": {
    "id": "SRC-cd9b7aab6e",
    "title": "General description of the HD4DP v2 application",
    "publisher": "healthdata.be (HDA)",
    "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/general-description-hd4dp-v2-application",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-936a6917",
   "statement": "Amaron déclare utiliser Mirth Connect pour ses couplages eHealth.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "Welke koppelingen ondersteunen we?",
   "as_of": "2026-09-26",
   "source": {
    "id": "SRC-268611b7ba",
    "title": "Interactie met externe platformen (e-health)",
    "publisher": "Amaron",
    "url": "https://amaron.be/ehealth/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-fe5d52d0",
   "statement": "La proposition Eclipse pour Open Integration Engine (qui poursuit la base de code open source de Mirth) décrit le moteur comme multiplateforme et basé sur Java, et comme recevant, transformant, filtrant, routant et livrant des messages cliniques et administratifs.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Scope'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-516352689e",
    "title": "Eclipse Open Integration Engine (projectvoorstel)",
    "publisher": "Eclipse Foundation",
    "url": "https://projects.eclipse.org/proposals/eclipse-open-integration-engine",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-20acebff",
   "statement": "Het Nederlandse bedrijf Enovation biedt Cloverleaf samen met partner Infor aan en omschrijft het als communicatieserver die gegevens uit verschillende informatiesystemen verzamelt; dit toont geen Belgisch gebruik.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "inleiding 'Collect medical data'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-dd2b781f48",
    "title": "Cloverleaf - Enovation",
    "publisher": "Enovation",
    "url": "https://enovationgroup.com/en/cloverleaf/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-11f35873",
   "statement": "Selon la proposition OIE, la base de code contient des connecteurs pour HTTP/S, TCP/MLLP, FTP/SFTP, SMTP, le système de fichiers, JMS et la connectivité directe à des bases de données via JDBC.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Scope'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-516352689e",
    "title": "Eclipse Open Integration Engine (projectvoorstel)",
    "publisher": "Eclipse Foundation",
    "url": "https://projects.eclipse.org/proposals/eclipse-open-integration-engine",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-3e9fe0f5",
   "statement": "Dans OIE (et dans la base de code Mirth), un canal est une seule intégration entre systèmes: il détermine d'où viennent les messages, ce qui leur arrive en chemin (filtrage, transformation, enrichissement, routage) et où ils vont.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Description'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-516352689e",
    "title": "Eclipse Open Integration Engine (projectvoorstel)",
    "publisher": "Eclipse Foundation",
    "url": "https://projects.eclipse.org/proposals/eclipse-open-integration-engine",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-eae96652",
   "statement": "InterSystems-producten kunnen HL7-berichten zonder schema doorgeven, maar met een gekoppeld schema kunnen ze velden parsen voor transformaties en routeringsregels en berichten valideren tegen het schema.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Overview of HL7 Schemas and Messages'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-f7ca717425",
    "title": "Introduction to HL7 Version 2 (Routing HL7 Version 2 Messages in Productions)",
    "publisher": "InterSystems",
    "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=EHL72_intro",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-2fa36873",
   "statement": "Pour HL7 v2, Mirth Connect utilise la bibliothèque HAPI; la release 3.12.0 l'a actualisée pour HL7 v2.7 et versions supérieures.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "3.12.0 What's New, HAPI-update",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-25769bece9",
    "title": "Mirth Connect wiki - 3.12.0 What's New",
    "publisher": "NextGen Healthcare",
    "url": "https://github.com/nextgenhealthcare/connect/wiki/3.12.0---What's-New",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-c2efda59",
   "statement": "Mirth Connect transforme le format de message entrant en un autre format (p. ex. HL7 vers XML), peut lire des données dans des bases de données et y écrire, et route les messages vers leurs destinations.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "README, 'About Mirth Connect', Transformation/Extraction/Routing",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-8da1ea8396",
    "title": "Mirth® Connect by NextGen Healthcare (GitHub-repository, README)",
    "publisher": "NextGen Healthcare (GitHub)",
    "url": "https://github.com/nextgenhealthcare/connect",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-dc9fc31d",
   "statement": "Health Connect bevat FHIR-client- en -servercomponenten, een FHIR-objectmodel en ingebouwde transformaties tussen FHIR en andere standaarden zoals HL7 v2 en C-CDA.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'FHIR Support'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-b870d6655c",
    "title": "InterSystems Health Connect Overview",
    "publisher": "InterSystems",
    "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=AHXHCOVW",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-44b9fbcf",
   "statement": "Health Connect gebruikt een eigen klinisch dataformaat, SDA, als tussenformaat bij conversies tussen zorgformaten (bv. CDA naar SDA naar FHIR).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Data Transformations'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-b870d6655c",
    "title": "InterSystems Health Connect Overview",
    "publisher": "InterSystems",
    "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=AHXHCOVW",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-d31dfbfd",
   "statement": "Voor sommige HD4DP-datacollecties is een HL7 FHIR-API beschikbaar; NextGen Connect transformeert de aangeleverde gegevens dan naar de Data Collections API van de form.io-server.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'NextGen Connect', 'HL7 FHIR API'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-cd9b7aab6e",
    "title": "General description of the HD4DP v2 application",
    "publisher": "healthdata.be (HDA)",
    "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/general-description-hd4dp-v2-application",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-33972230",
   "statement": "Ook CSV-bestanden met meerdere records per datacollectie worden in HD4DP v2 door NextGen Connect getransformeerd en naar de form.io-server doorgestuurd.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'NextGen Connect', 'CSV API'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-cd9b7aab6e",
    "title": "General description of the HD4DP v2 application",
    "publisher": "healthdata.be (HDA)",
    "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/general-description-hd4dp-v2-application",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-7efd81d7",
   "statement": "Avec Mirth Connect, Amaron permet de dater électroniquement notamment des prescriptions de médicaments et des demandes de laboratoire via le service de timestamping de la plate-forme eHealth, le plus souvent sur la base d'un message XML KMEHR provenant des systèmes sources.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie Elektronische datering (timestamping), 'Rol Amaron'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-268611b7ba",
    "title": "Interactie met externe platformen (e-health)",
    "publisher": "Amaron",
    "url": "https://amaron.be/ehealth/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-1358fd23",
   "statement": "Mirth Connect filtre les messages: il lit les paramètres du message et laisse passer un message vers la phase de transformation ou le retient.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "README, 'About Mirth Connect', Filtering",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-8da1ea8396",
    "title": "Mirth® Connect by NextGen Healthcare (GitHub-repository, README)",
    "publisher": "NextGen Healthcare (GitHub)",
    "url": "https://github.com/nextgenhealthcare/connect",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-78eaf1dd",
   "statement": "InterSystems-producten kunnen HL7 v2-berichten van de ene toepassing naar de andere routeren, waarbij het product als routing engine optreedt.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Introduction to HL7 Version 2, inleiding",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-f7ca717425",
    "title": "Introduction to HL7 Version 2 (Routing HL7 Version 2 Messages in Productions)",
    "publisher": "InterSystems",
    "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=EHL72_intro",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-8f7e1ce5",
   "statement": "Camel ondersteunt het Dead Letter Channel-patroon: een bericht dat niet verwerkt of verzonden kan worden, wordt naar een dead letter queue verplaatst (bv. bestand, database of log).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Dead Letter Channel, inleiding",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-d3df6e5982",
    "title": "Apache Camel - Dead Letter Channel",
    "publisher": "The Apache Software Foundation",
    "url": "https://camel.apache.org/components/4.22.x/eips/dead-letter-channel.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-d2b0f504",
   "statement": "IHE ondersteunt beide bevestigingsmodi (acknowledgement modes) van HL7 v2.5: Original en Enhanced Acknowledgement Mode.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "C.2.3 Acknowledgement Modes",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-b116a29d8b",
    "title": "IHE ITI Technical Framework Volume 2 - Appendix C: HL7 Profiling Conventions",
    "publisher": "IHE International",
    "url": "https://profiles.ihe.net/ITI/TF/Volume2/ch-C.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-96d1e5f0",
   "statement": "Grâce à la source queue, un canal peut recevoir et accuser réception (ACK) des messages plus rapidement qu'il ne les traite, puis les envoyer plus loin à son propre rythme (« ACK now, process later »).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Source Queue - ACK now, process later'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-c89553889f",
    "title": "Mirth Connect wiki - 3.0.0 What's New",
    "publisher": "NextGen Healthcare",
    "url": "https://github.com/nextgenhealthcare/connect/wiki/3.0.0---What's-New",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-6cc97ad8",
   "statement": "De Camel MLLP-component (sinds Camel 2.17) biedt een eenvoudige URI-configuratie, automatische aanmaak van HL7-bevestigingen (ACK) en automatische controle van ontvangen bevestigingen.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "MLLP, inleiding",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-766f18cbf7",
    "title": "Apache Camel - MLLP component",
    "publisher": "The Apache Software Foundation",
    "url": "https://camel.apache.org/components/4.22.x/mllp-component.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-dca55b1c",
   "statement": "Le dashboard affiche des statistiques par canal et par connecteur; une version web légère affiche les canaux et les connecteurs déployés sans charger l'Administrator.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Web Dashboard'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-c89553889f",
    "title": "Mirth Connect wiki - 3.0.0 What's New",
    "publisher": "NextGen Healthcare",
    "url": "https://github.com/nextgenhealthcare/connect/wiki/3.0.0---What's-New",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-135d02c8",
   "statement": "Chaque canal Mirth a son propre stockage de messages (message store), avec un navigateur de messages, des niveaux de stockage configurables et un archiver.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Message Storage'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-c89553889f",
    "title": "Mirth Connect wiki - 3.0.0 What's New",
    "publisher": "NextGen Healthcare",
    "url": "https://github.com/nextgenhealthcare/connect/wiki/3.0.0---What's-New",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-f4b4a42b",
   "statement": "La proposition OIE mentionne une application de gestion pour la création et le déploiement de canaux, pour le monitoring opérationnel et pour l'audit des messages.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Scope'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-516352689e",
    "title": "Eclipse Open Integration Engine (projectvoorstel)",
    "publisher": "Eclipse Foundation",
    "url": "https://projects.eclipse.org/proposals/eclipse-open-integration-engine",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-2a0d3143",
   "statement": "InterSystems stelt dat Health Connect door eventdetectie, alerting en monitoring berichten nooit verliest en dat een onderbroken bedrijfsproces kan herstarten vanaf het punt van onderbreking.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'Monitoring and Management'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-b870d6655c",
    "title": "InterSystems Health Connect Overview",
    "publisher": "InterSystems",
    "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=AHXHCOVW",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-663912f1",
   "statement": "HAPI FHIR is een Java-API (bibliotheek) voor FHIR-clients en -servers, open source onder de Apache Software License 2.0; commerciële ondersteuning verloopt via Smile CDR (recentste release 8.12.1 op 15 september 2026, via GitHub API).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "README, 'Documentation and wiki'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-98bb53751c",
    "title": "HAPI FHIR - Java API for HL7 FHIR Clients and Servers (GitHub)",
    "publisher": "HAPI FHIR-project",
    "url": "https://github.com/hapifhir/hapi-fhir",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-b5098d65",
   "statement": "Apache Camel is een veelzijdig open-source integratieframework gebaseerd op de Enterprise Integration Patterns.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "What is Camel?, eerste alinea",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-9bc6ac0a7f",
    "title": "What is Camel?",
    "publisher": "The Apache Software Foundation",
    "url": "https://camel.apache.org/manual/faq/what-is-camel.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-617f2bee",
   "statement": "Le Mirth Connect Server contient le back-end de l'interface de gestion ainsi que le moteur d'intégration proprement dit, qui filtre, transforme et envoie les messages.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "FAQ 'What are the key components of the Mirth Connect architecture?'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-ca89476bda",
    "title": "Frequently Asked Questions · nextgenhealthcare/connect Wiki",
    "publisher": "NextGen Healthcare (GitHub)",
    "url": "https://github.com/nextgenhealthcare/connect/wiki/Frequently-Asked-Questions",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-c273ba2b",
   "statement": "De Camel HL7-component verwerkt het HL7 MLLP-protocol en HL7 v2-berichten met de HAPI-bibliotheek.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "HL7, inleiding",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-6cb214c582",
    "title": "Apache Camel - HL7 (component en dataformat)",
    "publisher": "The Apache Software Foundation",
    "url": "https://camel.apache.org/components/4.22.x/dataformats/hl7-dataformat.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-5f6f3c45",
   "statement": "Microsoft adviseert om voor een volledige workflow rond de conversie van gezondheidsgegevens naar FHIR een ETL-pijplijn (extract, transform, load) te maken.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'Use the $convert-data endpoint'",
   "as_of": "2026-10-08",
   "source": {
    "id": "SRC-b98c0fb8ce",
    "title": "Convert health data with $convert-data in FHIR",
    "publisher": "Microsoft",
    "url": "https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/convert-data-overview",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-52ee955e",
   "statement": "Microsoft raadt voor de ETL-pijplijn rond $convert-data het gebruik van een ETL-engine aan op basis van Azure Logic Apps of Azure Data Factory.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'Use the $convert-data endpoint'",
   "as_of": "2026-10-08",
   "source": {
    "id": "SRC-b98c0fb8ce",
    "title": "Convert health data with $convert-data in FHIR",
    "publisher": "Microsoft",
    "url": "https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/convert-data-overview",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-1c217489",
   "statement": "Bij een geslaagd verzoek geeft de FHIR-service van Azure een FHIR-bundel terug met de gegevens omgezet naar FHIR R4.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'Use the $convert-data endpoint'",
   "as_of": "2026-10-08",
   "source": {
    "id": "SRC-b98c0fb8ce",
    "title": "Convert health data with $convert-data in FHIR",
    "publisher": "Microsoft",
    "url": "https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/convert-data-overview",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-16aeb194",
   "statement": "Microsoft levert de standaard-conversietemplates van $convert-data onder de MIT-licentie maar ondersteunt ze niet en bedoelt ze niet voor productie.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Considerations', waarschuwing",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-b98c0fb8ce",
    "title": "Convert health data with $convert-data in FHIR",
    "publisher": "Microsoft",
    "url": "https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/convert-data-overview",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-8154aa5f",
   "statement": "NextGen décrit Mirth Connect comme un moteur d'intégration sous licence que l'organisation entretient et exploite elle-même.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "FAQ 'What's the difference between Mirth Connect and Mirth Fully Managed?'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-f2aa84429a",
    "title": "Healthcare Integration Engine | Mirth® Connect by NextGen Healthcare",
    "publisher": "NextGen Healthcare",
    "url": "https://www.nextgen.com/solutions/interoperability/mirth-integration-engine",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-0c95a7ee",
   "statement": "Le repository GitHub public mentionne que Mirth Connect est publié sous la Mozilla Public License 2.0 (cela vaut pour le code open source jusqu'à la 4.5.2 incluse).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "README, sectie '7. License'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-8da1ea8396",
    "title": "Mirth® Connect by NextGen Healthcare (GitHub-repository, README)",
    "publisher": "NextGen Healthcare (GitHub)",
    "url": "https://github.com/nextgenhealthcare/connect",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-52d16276",
   "statement": "Le 19 mars 2025, NextGen a annoncé qu'avec la version 4.6, Mirth Connect passe d'une double licence (open source et commerciale) à une licence unique, commerciale et proprietary.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "aankondiging, gedateerd 'Wednesday, March 19, 2025'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-2aa07dd2b9",
    "title": "A New Era for Mirth® Connect by NextGen Healthcare",
    "publisher": "NextGen Healthcare",
    "url": "https://www.nextgen.com/blog/industry-news/a-new-era-for-mirth-connect-by-nextgen-healthcare",
    "published": "2025-03-19"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-e54a354d",
   "statement": "La release 3.9.0 a étendu la FHIR Connector Extension notamment à FHIR R4 (à côté de DSTU2, STU3 et d'une preview R5); l'extension est diffusée séparément via le site web de NextGen.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'FHIR R4/R5 Support'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-41e47a2e35",
    "title": "Mirth Connect wiki - 3.9.0 What's New",
    "publisher": "NextGen Healthcare",
    "url": "https://github.com/nextgenhealthcare/connect/wiki/3.9.0---What's-New",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-ea0fa5c0",
   "statement": "Open Integration Engine (OIE) est une fork communautaire de Mirth Connect, née après le passage à un modèle proprietary; le repository GitHub a été créé le 28 mars 2025 (API GitHub).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "README, sectie 'History and Roadmap'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-035f231c9a",
    "title": "OpenIntegrationEngine/engine – An open source fork of the now closed-source Mirth Connect",
    "publisher": "Open Integration Engine-project (GitHub)",
    "url": "https://github.com/OpenIntegrationEngine/engine",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-da3a8bb6",
   "statement": "OIE est entré en incubation auprès de l'Eclipse Foundation et s'appelle désormais formellement « Eclipse Open Integration Engine » (article d'actualité du 7 septembre 2026).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Latest news, 7 september 2026",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-bcf20c768e",
    "title": "Open Integration Engine – Healthcare Integration, Free and Open Source",
    "publisher": "Open Integration Engine-project",
    "url": "https://openintegrationengine.org/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-00eeeca6",
   "statement": "Open Integration Engine est placé sous licence Mozilla Public License 2.0.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "README, sectie 'Licensing'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-035f231c9a",
    "title": "OpenIntegrationEngine/engine – An open source fork of the now closed-source Mirth Connect",
    "publisher": "Open Integration Engine-project (GitHub)",
    "url": "https://github.com/OpenIntegrationEngine/engine",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-dcb67e02",
   "statement": "Selon la proposition OIE, la base de code prend en charge HL7 v2.x, FHIR, DICOM et CDA, ainsi que JSON, XML et du texte avec des séparateurs.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Scope'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-516352689e",
    "title": "Eclipse Open Integration Engine (projectvoorstel)",
    "publisher": "Eclipse Foundation",
    "url": "https://projects.eclipse.org/proposals/eclipse-open-integration-engine",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-322e5f30",
   "statement": "BridgeLink est une deuxième fork de Mirth Connect, mise en place par Innovar Healthcare et d'autres membres de la communauté (première release GitHub v4.5.3 le 18 mars 2025, via l'API GitHub).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "inleiding artikel (14 augustus 2025)",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-1e4f421d7e",
    "title": "A Look at BridgeLink's Fork of the Open Source Mirth Connect",
    "publisher": "Healthcare IT Today",
    "url": "https://www.healthcareittoday.com/2025/08/14/a-look-at-bridgelinks-fork-of-the-open-source-mirth-connect/",
    "published": "2025-08-14"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-05fdc8d6",
   "statement": "BridgeLink est publié sous la Mozilla Public License 2.0.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "README, sectie '7. License'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-413a8a189a",
    "title": "Innovar-Healthcare/BridgeLink (GitHub-repository, README)",
    "publisher": "Innovar Healthcare (GitHub)",
    "url": "https://github.com/Innovar-Healthcare/BridgeLink",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-6a60adeb",
   "statement": "Apache Camel is een project van de Apache Software Foundation onder de Apache v2-licentie.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "voettekst",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-9bc6ac0a7f",
    "title": "What is Camel?",
    "publisher": "The Apache Software Foundation",
    "url": "https://camel.apache.org/manual/faq/what-is-camel.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-edba5f7e",
   "statement": "De Open eHealth Integration Platform (IPF) is een uitbreiding van Apache Camel voor berichtverwerking en het koppelen van informatiesystemen in de zorg, beschikbaar onder de Apache License 2.0.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "README, 'IPF Overview'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-54855d801f",
    "title": "Open eHealth Integration Platform (IPF) - GitHub",
    "publisher": "Open eHealth Foundation",
    "url": "https://github.com/oehf/ipf",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-d4e1052b",
   "statement": "De Camel FHIR-component (sinds Camel 2.23) integreert met de HAPI FHIR-bibliotheek.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "FHIR, inleiding",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-e9063759a6",
    "title": "Apache Camel - FHIR component",
    "publisher": "The Apache Software Foundation",
    "url": "https://camel.apache.org/components/4.22.x/fhir-component.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-d70d208d",
   "statement": "IPF biedt bouwstenen voor IHE-profielen zoals XDS, PIX, PDQ en XCPD, en DSL's voor HL7v2 en HL7v3 (CDA, CCD).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "README, 'IPF Overview'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-54855d801f",
    "title": "Open eHealth Integration Platform (IPF) - GitHub",
    "publisher": "Open eHealth Foundation",
    "url": "https://github.com/oehf/ipf",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-f7180413",
   "statement": "Het HAPI HL7v2-project werd gestart door University Health Network, een groot universitair ziekenhuis in Toronto (Canada), en is niet verbonden aan de HL7-organisatie.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Welcome'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-aa061878d4",
    "title": "HAPI - The Open Source HL7 API for Java",
    "publisher": "HAPI-project (University Health Network)",
    "url": "https://hapifhir.github.io/hapi-hl7v2/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-16175437",
   "statement": "HAPI HL7v2 heeft een dubbele licentie (Mozilla Public License of GNU GPL) en mag royaltyvrij in open- én closed-sourcetoepassingen gebruikt worden.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Project License'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-c6240a0598",
    "title": "HAPI - Project License",
    "publisher": "HAPI-project",
    "url": "https://hapifhir.github.io/hapi-hl7v2/license.html",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-d3f47764",
   "statement": "InterSystems omschrijft Health Connect als een integratie-engine met ondersteuning voor grote transactievolumes, procesbeheer en continue monitoring.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "InterSystems Health Connect Overview, eerste alinea (documentatie 2026.2)",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-b870d6655c",
    "title": "InterSystems Health Connect Overview",
    "publisher": "InterSystems",
    "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=AHXHCOVW",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-4866354d",
   "statement": "Elke InterSystems IRIS-instantie heeft een licentiesleutel nodig (behalve evaluatie-installaties); het gaat om commerciële, gelicentieerde software.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Introduction to License Management'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-c89022e014",
    "title": "Managing InterSystems IRIS Licensing",
    "publisher": "InterSystems",
    "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=GSA_license",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-4cadafc8",
   "statement": "Een ziekenhuis beschrijft in een TED-gunningsbericht (november 2025) een opdracht voor IRIS for Health-programmering aan de serverzijde van zijn EPD-toepassing en voor de integratie van die toepassing met andere software via Ensemble.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie Beschrijving",
   "as_of": "2026-09-26",
   "source": {
    "id": "SRC-a1e3d9ea7c",
    "title": "België – Informaticadiensten – Raamovereenkomst voor EPD consultancy, specifiek voor IRIS for Health platform ontwikkeling (UZ Gent) – 792714-2025",
    "publisher": "Publicatieblad van de EU (TED)",
    "url": "https://ted.europa.eu/nl/notice/792714-2025/html",
    "published": "2025-11-28"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-c4b57282",
   "statement": "Lyniate herdoopte zich op 3 april 2023 opnieuw tot Rhapsody (oorspronkelijk opgericht als Rhapsody in 2018); de merknaam Corepoint blijft bestaan voor de Corepoint Integration Engine.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "artikel van 3 april 2023, eerste alinea's",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-15645f681e",
    "title": "Interoperability Platform Lyniate Rebrands as Rhapsody",
    "publisher": "HIT Consultant",
    "url": "https://hitconsultant.net/2023/04/03/lyniate-rebrands-as-rhapsody/",
    "published": "2023-04-03"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-d3e120af",
   "statement": "Rhapsody wordt aangeboden als SaaS, op eigen infrastructuur of als Integration Platform as a Service (iPaaS); het is een commercieel product.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'Options to meet you where you are'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-9559264fe8",
    "title": "Rhapsody Integration Engine for Healthcare Interoperability",
    "publisher": "Rhapsody",
    "url": "https://rhapsody.health/solutions/rhapsody/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-4f288ded",
   "statement": "Rhapsody zegt een 'FHIR- en API-first'-aanpak te volgen en tegelijk HL7-protocollen te blijven ondersteunen.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'Pioneering interoperability, enabling digital health'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-0c54db06e2",
    "title": "About us - Rhapsody",
    "publisher": "Rhapsody",
    "url": "https://rhapsody.health/about-us/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-65ff6420",
   "statement": "Rhapsody claimt dat zijn toolkit in 31 landen in gebruik is; een uitsplitsing per land (bv. België) geeft de pagina niet.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'Deploy globally'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-9559264fe8",
    "title": "Rhapsody Integration Engine for Healthcare Interoperability",
    "publisher": "Rhapsody",
    "url": "https://rhapsody.health/solutions/rhapsody/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-13605c49",
   "statement": "Infor Cloverleaf is de integratie-engine voor de zorg van Infor; volgens Infor standaardiseert en transformeert het dataformaten als HL7v2, FHIR, CDA en X12.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'Overcome diverse and legacy data challenges'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-f4f81515f7",
    "title": "Infor Cloverleaf healthcare integration engine",
    "publisher": "Infor",
    "url": "https://www.infor.com/products/cloverleaf",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-f68daa0c",
   "statement": "Rhapsody stelt dat zijn integratie-engine integraties bouwt van elke bron naar elke bestemming over FHIR, API's, HL7 en MCP heen.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'Coding options for today + tomorrow'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-9559264fe8",
    "title": "Rhapsody Integration Engine for Healthcare Interoperability",
    "publisher": "Rhapsody",
    "url": "https://rhapsody.health/solutions/rhapsody/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-bb2d829f",
   "statement": "Leveranciersclaim: de integratie-engine Rhapsody heeft ingebouwde FHIR-ondersteuning (conversie tussen FHIR XML en JSON, mapping tussen FHIR en andere standaarden); Belgisch gebruik is niet aangetoond.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "p. 4 (pdf-pagina 3), 'FHIR capabilities'",
   "as_of": "2026-10-01",
   "source": {
    "id": "SRC-1dd1e122c7",
    "title": "Product brochure – Rhapsody Integration Engine (2026)",
    "publisher": "Rhapsody Health",
    "url": "https://rhapsody.health/wp-content/uploads/2023/03/rg_Product_brochure_Rhapsody-Integration-Engine_2026.pdf",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-cf49678a",
   "statement": "Leveranciersclaim: FHIR Station bevraagt bestaande bronnen (FHIR Box of andere FHIR-repositories) online en dupliceert of bewaart de data zelf niet (façade/gateway-patroon, geen eigen opslag).",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "p. 7, '2. FHIR Station'",
   "as_of": "2026-10-01",
   "source": {
    "id": "SRC-b85fced929",
    "title": "White paper – Beginnen met FHIR: waarom en hoe pak je het aan? (© 2024-07, bestand 2024-11-28)",
    "publisher": "Amaron BV",
    "url": "https://amaron.be/wp-content/uploads/2024/12/AMARON_WhitePaper_Beginnen-met-FHIR_NL_20241128_DIGITAL.pdf",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-ae15ffec",
   "statement": "Leveranciersclaim: InterSystems Health Connect bevat FHIR-client- en -servercomponenten, een FHIR-objectmodel en ingebouwde transformaties tussen FHIR en HL7 v2/C-CDA, en kan FHIR-resources via de FHIR REST-API ontvangen en versturen (alternatief voor een FHIR-façade op een integratieplatform).",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'FHIR Support'",
   "as_of": "2026-10-01",
   "source": {
    "id": "SRC-b870d6655c",
    "title": "InterSystems Health Connect Overview",
    "publisher": "InterSystems",
    "url": "https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=AHXHCOVW",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-e7d74439",
   "statement": "Infor Cloverleaf kan in de cloud, on-premises of hybride worden geïmplementeerd, met Docker-containers.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'Cloud, on-prem, or hybrid'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-f4f81515f7",
    "title": "Infor Cloverleaf healthcare integration engine",
    "publisher": "Infor",
    "url": "https://www.infor.com/products/cloverleaf",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-95776dab",
   "statement": "Infor verwijst naar een Black Book-rapport (2026) dat Infor als topleverancier van klinische data-integratieplatformen rangschikt; dit is een leveranciersclaim.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "banner 'Analyst Report'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-f4f81515f7",
    "title": "Infor Cloverleaf healthcare integration engine",
    "publisher": "Infor",
    "url": "https://www.infor.com/products/cloverleaf",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-166c1f66",
   "statement": "Dans HD4DP v2 (healthdata.be), le composant NextGen Connect assure toutes les intégrations, tant au sein de HD4DP qu'avec le monde extérieur.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'NextGen Connect' (pagina laatst bijgewerkt 2026-06-24)",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-cd9b7aab6e",
    "title": "General description of the HD4DP v2 application",
    "publisher": "healthdata.be (HDA)",
    "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/general-description-hd4dp-v2-application",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-ebfb4c34",
   "statement": "Les systèmes maîtres des data providers n'adressent pas directement l'API de formulaires de HD4DP v2, mais passent par l'API que propose le composant NextGen Connect (un proxy avec notamment la sécurisation, le monitoring et le throttling).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Data collections API'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-cd9b7aab6e",
    "title": "General description of the HD4DP v2 application",
    "publisher": "healthdata.be (HDA)",
    "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/general-description-hd4dp-v2-application",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-341a8ece",
   "statement": "Pour la connexion avec le service eHealth Registre central de traçabilité (CTR, implants), Amaron utilise un service web dans Mirth Connect, avec authentification et chiffrement au moyen de certificats eHealth.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie Centraal Traceerbaarheidsregister (CTR), 'Rol Amaron'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-268611b7ba",
    "title": "Interactie met externe platformen (e-health)",
    "publisher": "Amaron",
    "url": "https://amaron.be/ehealth/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-70361611",
   "statement": "Amaron héberge au sein de Mirth Connect deux webservices REST qui communiquent avec HD4DP et qui envoient les données reçues via l'application eHealthBox d'Amaron.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie Healthdata.be (Sciensano), 'Rol Amaron'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-268611b7ba",
    "title": "Interactie met externe platformen (e-health)",
    "publisher": "Amaron",
    "url": "https://amaron.be/ehealth/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-77f38a9a",
   "statement": "ZORGI meldt op 26 februari 2026 in België Implementation Partner van InterSystems te worden voor HealthShare-implementatieprojecten, als reseller en onafhankelijke dienstverlener.",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "Inleiding, tweede alinea",
   "as_of": "2026-09-26",
   "source": {
    "id": "SRC-9750479a42",
    "title": "InterSystems et ZORGI renforcent leur partenariat autour des solutions HealthShare en Belgique",
    "publisher": "ZORGI",
    "url": "https://www.zorgi.be/actualites/corporate/intersystems-zorgi-renforcent-partenariat-solutions-healthshare-belgique/",
    "published": "2026-02-26"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-b887c30d",
   "statement": "De eHealth-connector (V4) is beschikbaar als Java-bibliotheek (JAR) en als Microsoft.NET-versie (DLL) met identieke API; de gids richt zich op ontwikkelaars die een extern framework of component in hun eigen toepassing integreren (versie 1.10, 27 november 2025).",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "p. 9, sectie 5 'Use of the connector'",
   "as_of": "2026-10-08",
   "source": {
    "id": "SRC-6fed0ba536",
    "title": "eHealth-platform Services Connectors V4 - Guide v.1.10",
    "publisher": "eHealth-platform",
    "url": "https://www.ehealth.fgov.be/ehealthplatform/file/cc73d96153bbd5448a56f19d925d05b1379c7f21/8f40846c5d1c18ead66a323e5c51200ee84df14d/eh_connectors-v4-introduction_guide-1.10.pdf",
    "published": "2025-11-27"
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-0f9a2ba2",
   "statement": "Pour les releases open source, NextGen n'évalue, ne backporte ni ne corrige les vulnérabilités, et ne publie pas d'avis de sécurité à leur sujet.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Supported Versions and End-of-Life (EOL) Notice'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-2f0d02aa2a",
    "title": "Security Policy (SECURITY.md) – nextgenhealthcare/connect",
    "publisher": "NextGen Healthcare (GitHub)",
    "url": "https://github.com/nextgenhealthcare/connect/blob/development/SECURITY.md",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-68a758b3",
   "statement": "Pour pouvoir passer à la 4.6 ou à une version ultérieure, il faut acheter une licence auprès de NextGen Healthcare.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "'New licensing model – Mirth Connect Enterprise License'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-d17c49e8bc",
    "title": "Mirth Connect Distribution – New licensing model (mirth-downloads)",
    "publisher": "NextGen Healthcare",
    "url": "https://www.nextgen.com/solutions/interoperability/mirth-integration-engine/mirth-connect-downloads",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-1f63c184",
   "statement": "Dans Mirth, les filtres et les transformers sont écrits en JavaScript, exécuté par le moteur Mozilla Rhino; depuis la 3.7, la version JavaScript/ECMAScript (notamment ES6) peut être configurée.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'JavaScript ES6'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-de53c34c4c",
    "title": "Mirth Connect wiki - 3.7.0 What's New",
    "publisher": "NextGen Healthcare",
    "url": "https://github.com/nextgenhealthcare/connect/wiki/3.7.0---What's-New",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-9605ff05",
   "statement": "Camel brengt bijna maandelijks een release uit; LTS-versies krijgen tot één jaar bug- en beveiligingsfixes.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "Downloads, inleiding",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-1e7e6d2774",
    "title": "Apache Camel - Downloads",
    "publisher": "The Apache Software Foundation",
    "url": "https://camel.apache.org/download/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-3ace548d",
   "statement": "Les instructions d'infrastructure de HD4DP v2 citent Nextgen Connect comme partie de la pile applicative modulaire qui est installée chez l'organisation qui fournit les données; la page ne mentionne aucune version ni licence de ce composant.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Overview' (pagina laatst bijgewerkt 2026-06-24)",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-4df4701ab2",
    "title": "HD4DP v2 Infrastructure instructions",
    "publisher": "healthdata.be",
    "url": "https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/hd4dp-v2-infrastructure-instructions",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": true,
   "on_page": true
  },
  {
   "id": "CLM-362c4039",
   "statement": "De recentste HAPI HL7v2-release is 2.6.0 (GitHub-release 5 februari 2025, via GitHub API), met o.a. een instelbare connect-timeout voor clientsockets.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "releasenota v2.6.0 (datum via GitHub API)",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-7e70f83902",
    "title": "HAPI HL7v2 release v2.6.0",
    "publisher": "HAPI-project",
    "url": "https://github.com/hapifhir/hapi-hl7v2/releases/tag/v2.6.0",
    "published": "2025-02-05"
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": false
  },
  {
   "id": "CLM-537648d3",
   "statement": "Volgens Enovation ondersteunt Cloverleaf internationale berichtstandaarden zoals HL7 V2 en V3 (en daarnaast HL7 FHIR, DICOM en Edifact).",
   "kind": "vendor-claim",
   "kind_label": "affirmation du fournisseur",
   "locator": "sectie 'The benefits of Cloverleaf', 'International standards'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-dd2b781f48",
    "title": "Cloverleaf - Enovation",
    "publisher": "Enovation",
    "url": "https://enovationgroup.com/en/cloverleaf/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": false
  },
  {
   "id": "CLM-7391a746",
   "statement": "Apache Kafka is een event-streamingplatform om stromen van events te publiceren, erop in te schrijven en ze duurzaam op te slaan; het kent zelf geen HL7-specifieke functies.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Apache Kafka is an event streaming platform. What does that mean?'",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-4b6feb6916",
    "title": "Apache Kafka - Introduction",
    "publisher": "The Apache Software Foundation",
    "url": "https://kafka.apache.org/intro/",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": false
  },
  {
   "id": "CLM-8ad97e8e",
   "statement": "Interpretatie: een integratie-engine (interface engine) combineert in één beheerde server connectoren (MLLP/TCP, HTTP/SOAP/REST, bestanden, databases, DICOM), parsing en validatie, transformatie en mapping, routering en filtering, persistente wachtrijen met herlevering, ACK-afhandeling en monitoring. Een algemene message broker (ActiveMQ, Kafka) levert enkel betrouwbaar berichtentransport zonder zorgspecifieke parsing of mapping; een integratiebibliotheek of -framework (HAPI, Apache Camel, IPF) levert bouwstenen die een ontwikkelaar in eigen code inbouwt. Het centrale model vervangt daarnaast veel punt-tot-puntkoppelingen door één aansluiting per systeem op de engine.",
   "kind": "interpretation",
   "kind_label": "interprétation",
   "locator": "synthese uit claims integratie-engine-01..17, apache-camel-01..08, mirth-connect-aanvullingen",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-8da1ea8396",
    "title": "Mirth® Connect by NextGen Healthcare (GitHub-repository, README)",
    "publisher": "NextGen Healthcare (GitHub)",
    "url": "https://github.com/nextgenhealthcare/connect",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": false
  },
  {
   "id": "CLM-db56c999",
   "statement": "Servers van BridgeLink 26.9.0 met de ingebouwde Derby-database vereisen Java 21.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "releasenota 26.9.0, Upgrade and Compatibility Notes, punt 1",
   "as_of": "2026-10-08",
   "source": {
    "id": "SRC-082567f062",
    "title": "BridgeLink v26.9.0 (releasenota)",
    "publisher": "Innovar Healthcare",
    "url": "https://github.com/Innovar-Healthcare/BridgeLink/releases/tag/v26.9.0",
    "published": "2026-10-01"
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": false
  },
  {
   "id": "CLM-eb9aa9c7",
   "statement": "BridgeLink 26.9.0 (GitHub-release 1 oktober 2026) verwijdert het meegeleverde jTDS-stuurprogramma.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "releasenota 26.9.0, Upgrade and Compatibility Notes, punt 2",
   "as_of": "2026-10-08",
   "source": {
    "id": "SRC-082567f062",
    "title": "BridgeLink v26.9.0 (releasenota)",
    "publisher": "Innovar Healthcare",
    "url": "https://github.com/Innovar-Healthcare/BridgeLink/releases/tag/v26.9.0",
    "published": "2026-10-01"
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": false
  },
  {
   "id": "CLM-edefdfe5",
   "statement": "Microsoft positioneert de $convert-data-operatie van de Azure FHIR-service als component in een ETL-pijplijn om o.a. HL7v2- en C-CDA-gegevens naar FHIR R4 om te zetten; de orkestratie gebeurt met Azure Logic Apps of Azure Data Factory.",
   "kind": "fact",
   "kind_label": "fait",
   "locator": "sectie 'Use the $convert-data endpoint' (pagina bijgewerkt 2026-08-24)",
   "as_of": "2026-09-28",
   "source": {
    "id": "SRC-b98c0fb8ce",
    "title": "Convert health data with $convert-data in FHIR",
    "publisher": "Microsoft",
    "url": "https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/convert-data-overview",
    "published": null
   },
   "citaat": null,
   "figuur": null,
   "in_text": false,
   "on_page": false
  }
 ],
 "diagrams": [],
 "facets": {
  "type": [
   "Topic"
  ],
  "jurisdiction": [
   "internationaal",
   "belgie"
  ],
  "theme": [
   "architectuur-en-infrastructuur",
   "softwaremarkt",
   "standaardisatie-en-governance"
  ],
  "lifecycle": [
   "onbekend"
  ],
  "section": [
   "landschap",
   "europa"
  ]
 },
 "search_terms": [
  "Moteur d'intégration (interface engine)",
  "interface engine",
  "integration engine",
  "communicatieserver",
  "HL7-integratie-engine",
  "interfacemotor",
  "moteur d'intégration",
  "Integratie-engine",
  "Kommunikationsserver"
 ],
 "release_id": "2026.11.12-3",
 "license": "CC BY 4.0"
}
