Community Consultation: Task Planning Specification Licensing Change

The openEHR @SEC has asked the openEHR Foundation Board, which has responsibility for matters of copyright, licensing and trademarks, to consider changing the current license for the Task Planning (TP) specifications from CC-ND to CC-0.

For further information on CC licensing, see: Deed - CC0 1.0 Universal - Creative Commons

Why has this request been made?

The SEC has decided that, although the TP specifications had been published, they are not currently being actively maintained or developed and have therefore been given a ‘paused’ status.

There is, however, interest from entities and individuals outside openEHR in further developing the TP specifications. The current standard specification license is, as applied to TP is CC-ND (No Derivative), which prevents any adaptation/development by entities/ individuals outside openEHR. Changing the license to CC-0 would allow the TP specifications to be ‘forked’ by another entity and further developed. It would also allow the openEHR community to ‘fork back’ any future CC-0 licensed developments.

Note that this consultation only applies to licensing for TP specifications, it has no implications for broader licensing changes to other specifications, or clinical modelling artefacts. We are aware that it may be necessary to release some other specifications, on which TP is dependent, but which are not pertinent to ‘core openEHR’ but we feel that should follow a decision on the key TP components.

Why is CC-ND the default license for openEHR Specifications?

The principle reason for CC-ND being used for specifications, it that is prevents external parties from forking the specifications and claiming to be ‘openEHR’ i.e the intent is to maintain a single, authoritative source for the openEHR standard.

What is the process for a Licensing change request?

A protocol has been agreed between openEHR Foundation and openEHR International (Licensing Changes Policy), which includes a 30-day community consultation via Discourse and email notification.

After that period, any comments raised will be taken into consideration before a final decision is made.

Please raise any issues or comments in this post - or alternatively email to comms@openehr.org where your comments can be posted anonymously.

This communication represents the start of the 30-day period which will close on 25th November 2026.

Here we go again with licenses… :joy:

Why is CC-0 chosen over CC BY to at least keep the original attribution?

From memory, I think the feeling within SEC / Foundation was that CC-0 was cleaner, and in particular that CC-BY might imply ongoing interest/responsibility from openEHR. That might not apply in general, just to the specifics of Task planning and associated specs.

For what it’s worth, if this consultation confirms the SEC proposal (or something that makes friendly forking possible), I would make a fork of the spec as it is today, and republish it openly with all attributions intact (this goes without saying from my point of view). Further changes will be a bit more in the R&D mode rather than formal change management, and may well involve Karolinska University Hospital at some point. So hopefully we will produce something improved and most importantly, implemented, at least to the level of a working simulator.

Agree, I think CC-0 was what the SEC recommended to make a clean separation.

Also FHIR has dared to use CC-0 (and rather rely on tradmark for not mixing FHIR with derivative work), so why not :slight_smile:

P.S. And, yes, there is an interest in advanced process support at Karolinska, including for research projects related to e.g. nursing process support, laboratory workflow support and modeling of cross-system and cross-provioder processes. I hope something can be tested and contributed back in more battle proven form, including an open reference imnplementation that makes it easier for different system providers and projects to implement similar support.