Clinical Knowledge Manager update + Github Mirror

Clinical and technical members may be interested to know that a new
version of CKM has been released.

www.openehr.org/ckm

In particular this release adds an automatic export of all resources
(archetypes, templates and termsets) that are uploaded to CKM to a Git
repository. This will be automatically updated to mirror the contents
of the CKM Trunk.

The github repository can be found at https://github.com/openEHR/CKM-mirror

Note that the CKM Trunk is an 'editorial view' and includes both
published and unstable archetypes.

The CKM update 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.

The detailed change list is available at
http://www.openehr.org/wiki/display/healthmod/CKM+Release+1.2.4

Regards,

Ian

Awesome idea, we can also use github to report and follow issues, to make corrections and send pull requests, etc. Nice!

Hi Pablo,

Glad you like it.

It will be interesting to see how/if we can adopt a greater degree of
integration with Git/gitHub but for now can we ask everyone to keep
using CKM as the primary source of contact for discussion / change
requests, suggested corrections etc. Although GitHub is a great tool,
it will be pretty opaque to many clinicians and others without
technical expertise. I am sure we can add value to CKM by borrowing
some of the ideas inherent in Git/GitHub but we run the risk of
splitting important conversations if we try to work with both tools.

So for now, please regard the Git mirror as a read-only resource and
direct any CRs, comments etc to CKM.

Ian