Skip to content
ehr-ctrlehr-ctrl

Frequently asked questions

Common questions about ehr-ctrl, openEHR, and EHRbase.

Don't see yours? Contact us.

What is ehr-ctrl?
A desktop app that gives the openEHR REST API a proper, user-friendly interface, so querying and administering your CDR doesn't require hand-writing HTTP requests.
Is it free?
Yes. ehr-ctrl is provided free of charge — download it and use it, no license required.
Why is it free — can we partner on a commercial version?
The application is free because the hope is that more people will use it and come to understand the openEHR standard. There's plenty of opportunity to build commercial products using openEHR — this isn't one of them.
Why create a desktop app?
Having a desktop app means that it can be used within an organisations own network. The app makes no network calls, other that to the CDR itself.
Which CDRs does it work with?
ehr-ctrl targets the openEHR REST API itself, so the goal is to work against any compliant CDR. So far it has been built and tested against EHRbase specifically, since it's free and open source. Once it has been validated against others, we'd be happy to mention them as well.
Why is it Windows only?
ehr-ctrl is developed as a cross platform application, so technically could be deployed to any platform. Currently, it is Windows only as the Apple developer licence, a requirement for the Mac, is not appealing.
Does my clinical data get sent to you?
No. ehr-ctrl is a desktop app that runs on your machine and connects directly to your own openEHR CDR — a local Docker or hosted EHRbase instance. Nothing about your clinical data is sent to us.
Do I need to know AQL?
Not necessarily. You can browse EHRs, compositions, and templates through guided forms, or run named stored queries. The AQL workbench is there if you want to write or inspect queries directly.
How do I report a bug or request a feature?
Send us a message from the Contact page — we read every submission and will get back to you.