Hi Erik, This is a very important point. I agree entirely. The aim of the Wave project is wholly around working up some early drafts of possible archetypes. As such, this is really a new sort of activity which, in the past would tended to have been done by individuals or projects in isolation. It is not the sort of work that would ever have appeared on the lists in any case. Having said that, I would hope to feed back progress to the non-Wave community, especially if more general issues arise that would be of interest to the community. I will investigate the blog-feed addons you suggested.
The number of Wave participants does now seem to be rising very rapidly and I would hope that if anyone wants to participate in the Wave 'experiment', that we should be able to get an invitation to them before too long. Certainly I still have a couple of invitations to hand-out if anyone would like to take part. I hope to get things started later this week. Fair point, though. For the moment we must ensure that we are not inadvertantly creating 'private' discussions, which is entirely contra to the purpose of using Wave in the first place!! The philosophy is to encourage collaboration at a very early stage so that overlapping and contradictory models/requirements can be rationalised before different groups have invested too much time and energy. Share early, share often. Dr Ian McNicoll office / fax +44(0)141 560 4657 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com ian at mcmi.co.uk Clinical Analyst Ocean Informatics openEHR Archetype Editorial Group Member BCS Primary Health Care SG Group www.phcsg.org / BCS Health Scotland 2009/11/17 Erik Sundvall <erik.sundvall at liu.se> > Hi! > > Google Wave is very interesting, but not yet very widespread. I think > Wave can be a good tool for openEHR. > > Could you please make sure that the OpenEHR-related wave-discussions > of public interest get copied to a more common and search-engine > freindly format too as soon as possible. (There are Google Wave > robots/bots that can be added to a wave in order to automatically copy > the wave content to e.g. blog format.) > > Otherwise you are again moving conversations from public searceable > space to restricted private space, just like with discussions moved > from open searchable wikis/mailinglists to the CKM. That is a very bad > thing for an open project. Many people start problem solving by a > using a search engine, so the discussions need to be publicly > available for reading without login. Currently you get good openEHR > search engine results from the specifications, mailing list archives, > wiki and openEHR web, but most likely not from CKM or wave. > > Best regards, > Erik Sundvall > erik.sundvall at liu.se > http://www.imt.liu.se/~erisu/<http://www.imt.liu.se/%7Eerisu/> Tel: > +46-13-286733 > (Mail & tel. recently changed, so please update your contact lists.) > > > > On Tue, Nov 17, 2009 at 04:46, Heather Leslie > <heather.leslie at oceaninformatics.com> wrote: > > For anyone who is interested and has a Google Wave account, I have > started > > an openEHR community Wave with the intent of it being a coordinating > point - > > which we can use as a jumping off point to various conversations or waves > on > > specific topics or projects. This may work, or it may result in total > chaos > > - I don't know ;-) > > > > >From this first wave I have set up two linked waves to kick it off - one > > for clinical modelling, particularly with trying to start to communicate > and > > coordinate early archetype efforts, so that resources and efforts might > be > > shared and enhanced rather than duplicated. It will no doubt evolve > where > > the community wants to take it. > > > > I have set up an additional wave that can kickstart technical waves - I > > won't presume to suggest topics there. And anyone can add others as they > > see a need - the wave is totally open & public, so all can contribute and > > shape it. > > > > I certainly don't see this as conflicting to the current openEHR wiki nor > to > > the lists. It is a different kind of medium - where IM, email and wiki > > overlap to achieve specific collaborative tasks, or to explore particular > > issues before recording/reporting them back to wiki or email list etc. > We > > can make it what we want. > > > > It has been interesting to explore uses for Wave. I have been using it > to > > collaborate on some of the CKM direction with Ian McNicoll and Sebastian > > Garde - there are situations where it has helped us communicate when > these > > other mediums haven't been able to. > > > > And I'm also collaborating with clinicians in other countries re some > > content definitions and teasing out issues. In fact started one > > conversation on Twitter with a couple of pharmacists - one from UK and > the > > other from US - re allergies. The US pharmacist put it into a blog to > try > > to pull it together cohesively (http://bit.ly/4EV0uw) and then we ended > up > > thrashing out many points in detail and in context via a private Google > Wave > > - an interesting and useful experience. > > > > For those who are interested and would like to participate, the openEHR > > community wave is http://bit.ly/2unchr - invite all your friends. > > > > The Complete Guide to Google Wave is a useful resource - > > http://completewaveguide.com/ > > > > Regards > > > > Heather > > -- > > > > Dr Heather Leslie > > MBBS FRACGP FACHI > > Director of Clinical Modelling > > Ocean Informatics > > Phone (Aust) +61 (0)418 966 670 > > Skype - heatherleslie > > Twitter - @omowizard > > > > _______________________________________________ > > openEHR-clinical mailing list > > openEHR-clinical at openehr.org > > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20091117/39adca42/attachment.html>
