openEHR Tooling: A Comprehensive Guide - Introduction [!warning] DRAFT - Work In Progress This series is intended to help new openEHR community members navigate the complex world of openEHR tools. It is a work in progress and may contain inaccuracies or outdated information. Please advise the auth…

This is a bit of a ‘starter’ attempt to create a Wikified entrypoint which we can build on. Feedback welcome. I have rough draft content for each of the sections enumerated above, but will post them one by one so I can edit for style and triple-check the details for accuracy.

@SPB as mentioned in the meeting I have started work on this overview, which aims to clarify for new developers/clinicians what tooling is available, what each thing does, and which tools are considered the ‘industry standard’ vs which ones are legacy/deprecated. Am I on the right track here?

I was thinking to start out first with an inventory of everyting akin of an excel sheet, so it would be easier to filter and distribute the review work. But if we are comfortable to dive right in the more “human-readable” format, you can count on me to review the lists of applications/software/scri…

Excel sheets are a disaster area for text. I’m happy for other people to collate a spreadsheet from this data, but I will be continuing with a text-based series of articles.

Agreed! Lets all work on the official text-based documentation.

@marcusbaw I know Discourse will be up for what are you proposing with wikified page set - but I was wondering what is your opinion on having a static website, rendered with mkdocs on github pages, based on markdown sources? it is also a “wiki”, easy to maintain, version control, cheap and easy main…

Yes, a static documentation site based on Markdown source could be a better fit for what we want to do than Discourse is. The reason I didn’t suggest it initially was that I didn’t want to start by suggesting yet another now toolset/platform, when we already have Confluence and Discourse. However,…

No, Antora would be too complex for this. Markdown on github, with static build with Mkdoc is much easier to manage and sufficient for the job, in my opinion. But it is up for the group to take a direction.

I think everybody here knows markdown and static pages. I personally don’t know Material for Mkdocs or Zensical but I guess with markdown knowledge it’s easy to handle. Let the group decide. Also open for Github pages.

DRAFT: Introduction (openEHR Tooling Overview series)

Software Program - open

joostholslag (Joost Holslag) 22 May 2026 06:05 8

Can we reuse the open source practise of the list of amazing for x on GitHub?

Explaining all the formats and language seems more of a specs and educational effort seperate from a tooling list to me.

DRAFT: Archetype Authoring Tools (openEHR Tooling Overview series)

Topic		Replies	Views
DRAFT: Archetype Authoring Tools (openEHR Tooling Overview series) Software Program - open archetype , tools , wiki	11	224	11 June 2026
Downloading previous versions of archetypes from CKM Clinical (archive)	15	61	29 May 2019
General archetype of clinical score/scale for templating measurement instruments Ask IEB archetype	8	595	10 June 2022
software development & starting out Technical (archive)	8	36	25 October 2007
How to transfer as much clinical complexity as possible to clinical terminologies Clinically Relevant RM Discussions terminology	17	284	9 September 2024
Using the openEHR Template Designer to create Clinical Document Definitions Template Designer	18	3104	19 September 2023
Updated Architectural overview Technical (archive)	5	23	25 October 2006
About the New to openEHR? category New to openEHR?	0	3269	30 October 2019
openEHR and PROMS, PREMS and patient self reported questionnaires Ask IEB	27	1071	5 August 2025
OPT 1.4 Specification ADL template	26	2003	21 December 2024

DRAFT: Introduction (openEHR Tooling Overview series)

Related topics