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



On 24 February 2014 23:27, pablo pazos <pazospablo at hotmail.com> wrote:
> Awesome idea, we can also use github to report and follow issues, to make
> corrections and send pull requests, etc. Nice!
>
> --
> Kind regards,
> Eng. Pablo Pazos Guti?rrez
> http://cabolabs.com
>
>> From: ian.mcnicoll at oceaninformatics.com
>> Date: Mon, 24 Feb 2014 09:54:41 +0000
>> Subject: Clinical Knowledge Manager update + Github Mirror
>> To: openehr-clinical at lists.openehr.org;
>> openehr-technical at lists.openehr.org
>
>>
>> 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
>>
>>
>> --
>> Dr Ian McNicoll
>> office +44 (0)1536 414 994
>> fax +44 (0)1536 516317
>> mobile +44 (0)775 209 7859
>> skype ianmcnicoll
>> ian.mcnicoll at oceaninformatics.com
>>
>> Clinical Modelling Consultant, Ocean Informatics, UK
>> Director openEHR Foundation www.openehr.org/knowledge
>> Honorary Senior Research Associate, CHIME, UCL
>> SCIMP Working Group, NHS Scotland
>> BCS Primary Health Care www.phcsg.org
>>
>> _______________________________________________
>> openEHR-clinical mailing list
>> openEHR-clinical at lists.openehr.org
>>
>> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org



-- 
Dr Ian McNicoll
office +44 (0)1536 414 994
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com

Clinical Modelling Consultant, Ocean Informatics, UK
Director openEHR Foundation  www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
SCIMP Working Group, NHS Scotland
BCS Primary Health Care  www.phcsg.org

Reply via email to