Release Date: October 2023
See the detailed list of changes.
Release Date: August 2023
Deployments: August - September 2023
See the detailed list of changes.
Release Date: August 2022
Deployments: August - October 2022
See the detailed list of changes.
Date: October 2021
See the detailed list of changes.
Date: February/March 2021
Minor bug fix release.
See the detailed list of changes.
Date: February 2021
See the detailed list of changes.
Date: September/October 2020
In addition to extensive finetuning and some bug fixes, this release contains among many others:
the ability to connect to an external Terminology Server to show value sets inline in the various archetype and template displays;
the ability to add configurable secondary (additional) transforms for templates;
a new drop zone for file uploads;
an additional in process state for Archetype Proposals and Change Requests;
various finetuning to the template displays;
an indicator showing the percentage of completion for each translation language of an archetype in the status report;
updated Archie ADL2 conversion routines.
See the detailed list of changes.
Date:
See the detailed list of changes.
Date:
See the detailed list of changes.
Date:
See the detailed list of changes.
Date:
See the detailed list of changes.
Date:
This release introduces new mindmaps which longer depend on Flash technology.
Also, it further adds to the recently introduced CKM REST API, which can be regarded as a replacement for the old SOAP-based CKM webservices.
In addition, it contains a myriad of finetuned fuinctionality and speed and scalability improvements.
See the detailed list of changes.
Date:
See the detailed list of changes.
Date:
See the detailed list of changes.
This release is a major new release. It adds a new Dashboard for new or not-logged in users. It also completely revamps the current Dashboards for logged-in users, editors and clinical knowledge administrators. See some screenshots here.
In addition - among many others - new Audit Log functionality has been introduced, the CKM theming has been improved, there has been some finetuning around the review process, statistics, various grid tooltips, and the UCUM unit validation.
See the detailed list of changes.
This release includes improvements to the user registration, password retrieval as well as the reviewing process. Also fixes some minor bugs.
See the detailed list of changes.
This release of CKM offers a complete rework of the various statistics pages for archetypes, templates, termsets and users, including for the status report page for individual published resources.
This release also adds a lot of flexibility to the search ontology (Professions, Health Domains, ...) to be able to hide the individual classes, sort the elements and disallow classifying into some 'abstract' classes.
The GitHub directory structure for exporting of remote subdomains has been adapted to include the namespace of the remote subdomain in the directory structure. It is now possible to bulk export all archetypes as XML.The search functionality has been finetuned to provide a better search order of found resources, in particular if searching for multiple words or word fragments at once. Also, projects that may be relevant to the search will now be listed above the resource search results. Some initial changes and additions for a new training CKM instance have been included in this release as well as some bug fixes.
See the detailed list of changes.
See the detailed list of changes.
The release of CKM 1.4.0 features some major new additions to the functionality of CKM. It also improves on many details in CKM and fixes a number of bugs.
Most likely the biggest change in this release is CKM's support for v0 archetypes for in_development archetypes and the introduction of additional meta-data for each archetype, carried in its other_details field and managed by CKM where applicable. This includes a revision number, namespaces, unique ids, etc. As a consequence, it is now also possible to for example fork an archetype that was developed elsewhere as well as to internalise remote archetypes (i.e. that were cached previously).
Other major new pieces of functionality include:
See the detailed list of changes.
The most prominent new feature of this release is the new Change Request Functionality: For each archetype (and other resources as well), any user can now create a change request. User can configure a panel in their Dashboard to see all the change requests submitted by them or can see all change requests via the Report menu. The submitter of the change request will be notified of any updates to the change request.
This release also improves the rendering speed of the Archetype revision history for large revision histories like e.g. for the Blood Pressure archetype.
Your CKM username/password combination will now be picked up by most Password Managers (as desired).
As usual, a few bugs were found and fixed, mostly in the areas of remote subdomains, bulk uploads and comparisons of archetypes - see the detailed list of changes.
This release adds an automatic export of all resources (archetypes, templates and termsets) that are uploaded to CKM to a Git repository.
It offers many usability improvements such as for example an easier way to merge various translations of an archetype into a new trunk archetype, easier sharing of archetypes and other resources via direct links, usability improvements to the search in the left hand tree, some big green buttons, and a simpler registration process.
Editors now have the ability to add special comments to reviewers of an archetype when creating a new review round for an archetype which will be displayed inline to the reviewers.
For templates, a new Printable view was added and templates with its sub-templates and contained archetypes can now be viewed as an Organisational Chart. Also, many details of the form view of a template have been enhanced.
This release also adds some checks around ensuring that archetypes use correct UCUM-units as specified by the specs and fixes a number of bugs.
Also see the detailed list of changes.
This release adds the possibility to connect to remote CKM instances and import/update archetypes from there. For example, the UK or the Nehta CKM can import archetypes directly from the openEHR CKM, this enabling federation of archetypes in a controlled way.
For template-based projects, a new hierarchical view of the project's template is introduced. Go to a project and select "Project Hierarchy" to see this.
This release also contains a number of bug-fixes and finetunes some other aspects of CKM, e.g. the template import mechanism or the display of archetypes, especially in the printable view of an archetype.
Also see the detailed list of changes.
This release adds reviewing for templates based on the operational template (OPT).
It improves some aspects of the archetype and template views, finetunes projects and incubators and adds administration control on subdomain level.
Also see the detailed list of changes.
This CKM release is a major new release which achieves two main objectives:
1. Modifications to the user interface to simplify the interface and allow users to focus on specific projects and components.
2. Modifications and additions to CKM and associated tooling to create a model and terminology based end-to-end tool chain.
The first objective has been achieved by adding finer grained governance components, known as 'sub-domains', each with underlying 'project' sub-components. This means that clinical models can be 'owned' and developed more easily by various groups and jurisdictions in the eHealth community. Users now have a more customisable view of the application and can narrow their view to specific artefacts. The help system has been improved through enhancements to the navigation functions and understanding of functionality for new users.
The second objective has been achieved by adding functionality to enable an end-to-end tool chain with the following characteristics:
Importantly, the new tool chain allows end-to-end visibility and governance of the artefacts that are produced and published in this environment. The transformation engine allows us to continue to evolve its published artefacts and to add new ones without the vendor needing to modify the CKM environment.
The CKM application now has a project type called an incubator, for users to work on models and artefacts in a sand-box environment, before they are made visible to the general community.
Also see the detailed list of changes.
The 1.1.5 release of CKM is a release that contains some major new functionality and some minor usability changes and bugfixes.
Most prominently, it features the newly developed review functionality for terminology subsets (termsets) within CKM following a similar process to the currently available archetype content reviews.
Some new functionality has been integrated into this release in an effort to streamline some of the tasks for CKM editors: For example, there is a new admin report on active branches of all resources that helps in keeping track of current (and outdated) activity. Also there is a new overview of users with a certain CKM-wide role (e.g. all administrators) and editors are now able to upload to branches that have not originally been checked out by them (used e.g. for merging). This release does not contain any major changes to the user experience other than minor fine-tuning.
Also see the detailed list of changes.
This release includes new functionality, but also a lot of fine-tuning at many places:
See the detailed list of changes. for further changes.
Once an archetype is published, it will normally have to be translated into various languages without changing the definition of the archetype itself or the terms in existing language. In general it is better to use the online translation facility built into CKM but it will sometimes be the case that a translation is added locally to an archetype via the Archetype Editor or other tool. This CKM release adds a facility to allow a local translation to be safely uploaded and integrated into the CKM archetype, but without uploading the whole archetype, which may a different, usually older, version to that on CKM.
The CKM release also adds the ability to conduct reviews of archetype translations. The process is similar to conducting content and terminology binding reviews but uses a different layout, more appropriate for reviewing translations
A total of over 110 additions, improvements and bug fixes are incorporated in this release, including improvements to the way reviews are handled, archetypes are displayed and compared, emails are being sent out, etc. Please see the detailed list of changes below for more information.
See the detailed list of changes for further changes.
See the detailed list of changes for further changes.
This release features a new type of review: Terminology reviews. Terminology editors can now use CKM to review the terminology bindings of an archetype.
Snomed CT and LOINC codes in the archetype are being reviewed. For this, the fully specified term is being displayed for Snomed CT as well as LOINC.
There is a new status page (the star) for an archetype, where detailed information about the status of an archetype is being displayed, such as when the content was published after how many review rounds, etc. Published archetypes can also be rated on this page. In addition, the status of each translation and terminology for this archetype is being displayed. For example, the content of an archetype can be agreed on and published, but a translation or the bindings to Snomed CT may not be complete.
You can subscribe to http://twitter.com/openEHR_CKM to get all the latest updates to archetypes and templates, etc.
Apart from this, this release contains a lot of finetuning as well as bug fixes - see the detailed list of changes for more information.
This Release adds initial support for templates within CKM. Templates in OET format can be uploaded to CKM. They are linked to the archetypes in CKM, so that an Operational template can be generated and displayed as form at any time for a template. Template version management principles are similiar to those used for archetypes.
It is possible to comment on templates, export all templates, get a mindmap overview of all or a selected template, add resources to a template, etc.
In addition to the initial template support, many improvements and bug fixes have been included in this release.
For example, an XML view of archetypes is now supported, webservices have been added or improved, the tabbed view of archetypes has been finetuned with many minor changes.
See the detailed list of changes for more information.
With the new release, editors can explicitly close a review roundand no more reviews or modifications to existing reviews are allowed for this review round. All expired invitations will be removed.
Review Rounds now have a sequential number to easier identify where in the review process an archetype is. It has been made more obvious to reviewers how to modify a completed review(orange arrow in the completed reviews portlet on the Dashboard for open review rounds). Editors can now see how engaged a user is in order to help to determine if a user should be invited for a review round. Editors can synchronise the other contributorsfrom the archetype with those who submitted a review for the archetype, thus ensuring completeness of contributors and consistency of the user details displayed. Editors can create tasks directly from the feedback overview for a review round, ensuring that nothing gets lost.
With regards to the validation of archetypes, validation of specialised archetypes is now supported by CKM. A couple of other validation errors are now reported by CKM as well.
In addition to this, to ensure consistency of style, a "content style validation" feature has been introduced to be able to check for some inconsistency, such as that the text of an element doesn't start with an uppercase letter (or digit) or there is no full stop at the end of a description, or a description is missing completely, etc.
Before committing an archetype or setting up a new review round, editors are warnedif there are technical validation errors, content validation errors, active tasks, or discussion items for this archetype and can fix this before committing/setting up a new review round.
A couple of additions to the presentation of archetypes have been made, e.g. additional information is displayed for DV_Count, DV_Date (etc), DV_Interval datatypes.
Editors now have ability to change the archetype id of an archetype while preserving all reviews, documentation etc. for this archetype.
An issue where not all archetypes containing a search term where found in "complete search" mode has been fixed. Also an issue where a direct link to an archetype may have not worked correctly if the user is already logged in to CKM has been fixed.
See the detailed list of changes for more information.
Please note: Due to the first change below, you will need to install the lastest Archetype Editor to be able to open/edit some of the archetypes!
See the detailed list of changes for more information.
See the detailed list of changes for more information.
See the detailed list of changes for more information.
See the detailed list of changes for more information.
See the detailed list of changes for more information.