The Plugathon offers a unique educational and testing opportunity by leveraging IHE experiences from the well-established IHE-Europe Connectathon. This event provides an opportunity to learn & share experiences and a platform for a specific community to innovate, including on-the-fly connections, with the APIs of health IT product solutions in a standardized way. It's the way to propel your projects forward!
The 2026 IHE-Europe Connectathon Week edition will offer following events:
Plugathon EHDS Primary usage
Plugathon for Devices
Plugathon for OpenEHR
Upcoming Webinars
Our upcoming webinars bring together experts, projects, and community voices to explore key topics, share practical insights, and prepare for the Brussel edition.
Thursday, 26 February
OpenEHR: More information will be available soon
Speaker details and full agendas are available on the registration pages.
|
Plugathon for EHDS Primary Usage
Monday 23 - Wednesday 25
Description:
A hands-on session focused on testing European Implementation Guides for the EHDS primary use of data (IPS, Imaging, Laboratory, HDR). Participants will validate EU project test cases, work directly with experts to resolve technical issues, and strengthen their understanding of interoperability tools.
The session is ideal for technical teams and vendors preparing for EHDS-aligned integration and results in concrete feedback reports and verified implementations.
Register NOW
Webinar - IHE Plugathon – EHDS Primary Use
Learn more about how European Projects are preparing for the IHE Plugathon – EHDS Primary Use. An overview of how European initiatives are preparing for EHDS Primary Use activities within the IHE Plugathon framework, with contributions from ongoing projects and implementation experiences.
|
Plugathon openEHR – Exploring openEHR Integration within IHE Profiles and further collaboration opportunities
Wednesday, 25 March 2026, educational session in the afternoon and Thursday, 26 March 2026 all day, with a dedicated testing session followed by the wrap-up.
Reasons to come:
SUTs “IHE”: Come if you have the business need to get data from OpenEHR.
No need to change your system (standard QEDm or MHD consumer actor)
SUTs “openEHR”: Come if you have the business need to act as a data repository to the FHIR world.
No need to change your system, but need to support AQL and IPS archetype
Experimental “bridge” systems: Come if your business is to “bridge” the FHIR world to openEHR
If you come from openEHR side, you need to add IHE APIs (QEDm, MHD)
If you come from IHE side, you need to add OpenEHR APIs and AQL capabilities
Both need to include the https://open-fhir.com project – or – come with an own Archetype-FHIR translation
Come in any stage of maturity of your system (Planning, Prototype, Product)
|
