Recently, like many others, I was experimenting with Claude Code to see how it works and just how quickly something could be built using it. I took inspiration from the FHIR tool at https://vanyalabs.com/, which is targeted at people using FHIR.
I wasn’t aware of anything similar for openEHR, so I built a tool surprisingly quickly. I have attached a video, which is hopefully self-explanatory, but I thought I would ask the community two questions.
To be clear, the tool is intended as a development tool, not a tool for clinical end-users.
Is this a solved problem? Are there already existing tools that allow people to explore the content of a CDR?
Would the tool be useful to others (if developed further) ?
Atomik can also show queries, transform to AQL and execute the queries from the GUI to test them and check results before fully integrating clients for those queries form the REST API.
Funny timing looking back. I hit the same starting point independently around the same time (beginning of April). I also saw Vanya Labs (the Postman-style FHIR client) and asked myself the exact same: “does something like this exist for openEHR?”.
I then built openEHR Explorer: a cross-platform (Tauri + Rust + Vue) desktop CDR browser, Apache 2.0. Positioned it as “Postman for openEHR,” with the main differentiator being template-aware rendering — resolving at0006-style node IDs against the Web Template so compositions actually read like clinical data instead of opaque JSON.