Hi, Heather

I'm much interested in this project, because we are just launching a few
projects.
as Eric mentioned, I think incubator would be good.

Shinji
2014/07/11 14:46 "Heather Leslie" <heather.leslie at oceaninformatics.com>:

>  Hi everyone,
>
>
>
> *I cautiously send this email as I?m aware that it can be perceived to
> border on the line between commercial and community, so request if anyone
> is interested in following through with my idea to email me privately and
> not use the list any further.*
>
>
>
> I?ve been approached by someone requesting an academic CKM instance that
> could be used for university teaching purposes.
>
>
>
> So I am curious to see if there was broader interest in establishing a
> shared academic CKM for use by universities - for academic, non-commercial
> purposes only.
>
>
>
> I?m proposing a solution that would operate a little along the lines of
> the UK CKM, where there are a number of academic entities sharing the same
> CKM domain instance, but each with their own autonomous subdomains. This
> could be useful to kickstart some collaborative academic activity between
> universities in clinical knowledge management.
>
>
>
> There are pros and cons for this arrangement, which I?ve tried to outline
> below:
>
>
>
> Pros:
>
> ?         All functionality of the standard CKM will be fully available
> (ie what you currently see on the openEHR CKM) ? the library, collaborative
> portal and governance/distribution capability will be fully enabled,
> including projects/incubators and running archetype/template reviews.
>
> ?         You would have autonomy within your subdomain (ie effectively a
> folder or subset of the whole CKM instance) and all of the assets within it.
>
> ?         The price per university would be minimised as the costs in
> running, maintaining and hosting the CKM instance would be shared by all.
>
> ?         As more universities came on board, potentially the cost of the
> subdomain based on the shared running costs would be minimised, and the
> license price would mostly be based on the number of assets in the
> subdomain ie starting with a minimum of 50, and above that it is based on
> honest usage.
>
> Cons:
>
> ?         If we had multiple universities participating in a single CKM
> instance who are not coordinating their activity, then I would anticipate
> that the CKM could become quite a mixed and confused set of models ?
> acceptable perhaps for academic purposes, but not a good basis for
> implementations, except at subdomain level.
>
> ?         No choice about others who would share your CKM instance.
>
> ?         No control over what activity occurred in other subdomains eg
> others may upload other archetypes that were similar or potentially
> conflicting. This is being managed to some degree in the UK instance by the
> presence of Ian McNicoll, but may not be possible if a widely varied group
> of academic institutions participate. Coordination between the other
> subdomain users would be up to all parties voluntarily deciding to work
> together.
>
>
>
> I would propose an initial CKM to be in English, although if there was
> enough interest from a single language group, we could potentially arrange
> for a number of translated CKMs as well.
>
>
>
> Please contact me on heather.leslie at oceaninformatics.com if you have any
> questions or wish to express interest.
>
>
>
> I am also planning to attend MIE 2014 in Istanbul next month if anyone
> wants to discuss this further.
>
>
>
> Regards
>
>
>
> Heather
>
>
>
> *Dr Heather Leslie*
> MBBS FRACGP FACHI
> Director/Consulting  Lead
> *Ocean Informatics <http://www.oceaninformatics.com/>*
> Phone -  +61 418 966 670
> Skype - heatherleslie
> Twitter - @omowizard
>
>
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20140711/acc8fa95/attachment.html>

Reply via email to