openEHR International is proud to announce the publication of abstracts from EHRCON25.
This collection highlights just some of the incredible work underway across the openEHR community and beyond, showcasing innovation, collaboration, and a shared commitment to advancing digital health.
Congratulations to all the authors for their contributions, and our sincere thanks to our diligent panel of peer reviewers for their time, expertise and dedication in making this possible.
Watch this space for more information about submitting your abstract for EHRCON26!
@Pete_Bouvier Great to see the continued momentum around openEHR and the visibility of work through EHRCON25.
From an engineering perspective, it would be valuable to see more of these abstracts evolve into:
production-grade reference implementations
open, reusable components
clear architectural patterns that teams can adopt directly
The research and innovation are clearly there — the next step is making them more accessible and actionable for engineering teams building real-world systems.
Also, it would be interesting if future conferences (EHRCON26 and beyond) put additional emphasis on:
interoperability in practice (not just theory)
deployment at scale (performance, reliability, multi-region setups)
developer experience and onboarding
Looking forward to exploring the published abstracts and seeing how these ideas translate into concrete tools and systems.
Welcome to the discussion! You raise valid points, and the good news is that quite a few of these abstracts already go in that direction. For example, A2, A5, A6 and A13 have published open-source implementations, A12 reports on a production deployment of nearly 800k ePROMs across Catalonia’s health system, and A9 benchmarks query performance at 1 billion compositions.
It’s definitely an evolving space, and I think EHRCON has been getting more engineering-focused with each iteration.
That said, I think there’s still room to grow, especially around developer experience and onboarding, which remains a barrier for teams new to openEHR. Would be great to hear which specific areas you’d most like to see evolve!
Hey Severin Kohler,
Really appreciate the detailed context, that’s actually very encouraging to hear. The examples you mentioned like A12 and A9 are exactly the kind of direction I was hoping to see more of.
If I had to point to a few areas where I think things could evolve further, from an engineering perspective, I’d highlight:
Clear, end-to-end reference architectures
Not just components, but full system blueprints showing how everything fits together in real deployments
Developer onboarding paths
Something like “from zero to production” guides with realistic scenarios, not just isolated tooling docs
Practical interoperability examples
Especially how openEHR systems integrate with existing hospital systems, APIs, and mixed standards in the real world
Operational concerns
Things like scaling strategies, monitoring, failure handling, and multi-region setups are still a bit underrepresented in public materials
I think the foundation is already very strong, it’s more about making that knowledge easier to consume and apply for teams trying to build production systems.
Would love to dig into those abstracts more and maybe even contribute back if there’s an opportunity.
Great to see the continued momentum around openEHR and the visibility of work through EHRCON25.