FerroEHR's public sandbox now opens on the admin console

Implementation Tools
1

The FerroEHR sandbox at https://sandbox.ferroehr.eu used to land you on a Swagger page. After some feedback I got today :wink: (Thank you @borut.jures) I changed that. The sandbox now opens on the admin console, connected to the live CDR. Login is ferroehr / ferroehr.

The console is a plain web client of the openEHR REST API (ITS-REST 1.1.0). It has no private channel into the server, so whatever you see in it, your own client can read from the same endpoints.

Some things to try:

  • upload an operational template and open its web-template path catalog
  • browse an EHR, its compositions and the version history behind them
  • run AQL in the query workbench, or click a query together in the builder and chart the result set
  • commit a CONTRIBUTION against an EHR and find it back in the history
  • open the audit browser and look at the trail your own actions left

Swagger is still there for the API itself: https://sandbox.ferroehr.eu/ferroehr/rest/swagger-ui, same login, also linked from the sign-in screen.

A few honest expectations. The data is synthetic and the repository gets wiped every night. The whole thing runs on free compute, so when several people hammer it at once it will get slow.

Code is MIT: https://github.com/rubentalstra/FerroEHR. Docs: https://ferroehr.eu/docs/latest/. A local instance is one docker compose up away, see the getting-started page.

If the sandbox refuses something you think is valid openEHR, or swallows something it should refuse, please file an issue with the request and response.

Thank you already in advanced :slight_smile:

PS. The UI is still subject to changes for better user experiences.

2

The speed at which you are doing things is impressive. Also, nice little change to make the admin interface the default.

I can see this, ehrbase sandbox admin, ehr-ctrl and my openEHR explorer have a lot of similarities. Which is great, it reaffirms that a good UI helps a lot to discover / explore the contents and the structure of an openEHR CDR.

3

I will be transitioning to use the FerroEHR Rust crates inside anarchie - it makes sense not to duplicate the effort of writing and maintaining ‘openEHR Rust SDK’ if we are all using the same stuff. If I find any bugs or missing features during the port I’ll raise an Issue or send a PR.

I’ll continue developing anarchie - even though to some extent FerroEHR is a far better option for orthodox use-cases. I do think that databases tend to cause organisation-centric thinking in EHR design, hence why GitEHR and anarchie are file-based, offline-first, Git-tracked repositories of clinical data. Interoperable and portable by design.