Blog
Monitoring Matchbox with OpenTelemetry
How busy is your Matchbox server? Which validations are slow, and is it about to run out of memory? Through OpenTelemetry, the open standard that most monitoring tools support, Matchbox can now send its metrics, traces and logs to a monitoring platform such as Traceway, which collects them and gives you the answers. In this hands-on tutorial, Quentin shows how to set it up in a few minutes, build a dashboard and add alerts, so you always have a clear view of how your validation service is doing.
Matchbox: from 12 GB to 4 GB – 24 hours with an AI agent and a test setup
Matchbox 4.1.18 needs a fraction of the memory: a typical validation server now runs in a 4 GB container instead of a fixed 12 GB heap. How an AI agent and a reproducible load test got us there in 24 hours.
Beginner's Guide to Apache Camel™ and IPF for the Swiss EPR
Deep integration of the Swiss Electronic Patient Record (EPR) into primary systems is crucial for acceptance by healthcare professionals. Quentin Ligier, who has extensive experience in supporting primary systems for integration with the EPR, provides comprehensive guidance on how to effectively send requests to the Swiss EPR using Apache Camel and the Open eHealth Integration Platform (IPF).
The blog post describes the necessary settings, request types and security aspects. Follow the link for the full article on Quentin's site.
How we implemented the Gazelle EVS Client's new validation API in Matchbox
Matchbox is used within the Gazelle ecosystem for validating FHIR-based content and we have recently integrated it with the new validation API from EVS Client. In this post, we look at the structure, requirements and advantages of the new API, and the reasons for our integration, before detailing the steps we took to implement it.
But first, some background.