How should we query openEHR data?
· One min read
Pablo and Sidharth recently kicked off a great debate: Should we write queries using AQL/SQL, or is a visual query builder the way to go?
I think there’s a third option that is changing the game: Natural Language via AI.
Instead of wrestling with syntax, you type:
Get EHR data where systolic blood pressure > 140 mm[Hg] and pulse > 80/min
In ArcEHR, I use SQL as the main querying language, allowing developers to either write queries by hand or let the integrated AI assistant do the heavy lifting.
Modern LLMs excel at translating intent to precise database queries. If they can navigate complex codebases, a few lines of SQL is a breeze.
What’s your preferred approach for openEHR?
- By hand (SQL/AQL) – Complete control and precision.
- Visual Builder – Drag-and-drop, low-code, accessible.
- AI/Natural Language – Fast, intuitive, zero syntax overhead.
ArcEHR Studio is a great example of the first and third approach in action:
