Hi Pablo, I agree with your and Diego's suggested change. That was the intended meaning of the original statement but yours expresses this more clearly.
I was just interested in Diego's actual experience with the CKM web-services as the basis for a generic API. 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 openEHR Clinical Knowledge Editor www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL BCS Primary Health Care ?www.phcsg.org On 6 September 2011 00:11, pablo pazos <pazospablo at hotmail.com> wrote: > Hi, > > I think Diego's point is to change this "... directly interacting with the > Clinical Knowledge Manager and equivalent repository and review tools"to > something like "... to interact with any Clinical Knowledge Manager through > a standard API (to be defined)". > > > -- > Kind regards, > Ing. Pablo Pazos Guti?rrez > LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez > Blog: http://informatica-medica.blogspot.com/ > Twitter: http://twitter.com/ppazos > > ________________________________ > Date: Mon, 5 Sep 2011 21:49:01 +0100 > Subject: Re: openEHR Transition: two procedural and one licensing question > From: Ian.McNicoll at oceaninformatics.com > To: openehr-technical at openehr.org > > Hi Diego, > > I understand from Sebastian that you have been exploring the current CKM web > services. ?Do you think these might form the basis for an open repository > API or do you have any other comments or alternative suggestions? > > Ian > > On Monday, 5 September 2011, Sam Heard <sam.heard at oceaninformatics.com> > wrote: >> Thanks Diego >> >> [Sam Heard] ?This would be a step forward and would allow for slim and fat >> systems to offer the same basic calls. >> >>> > My suggestion is for the this point >>> "Begin an open source software project for tools, web-based if >>> possible, to author archetypes, templates and terminology reference >>> sets directly interacting with the Clinical Knowledge Manager and >>> equivalent repository and review tools" >>> >>> I agree with the first part (create web-based open source tools), but >>> I think that the second part should be clarified. We should define a >>> basic API to access repositories, to avoid doing ad-hoc >>> implementations for each one of the possible repositories >> >> >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical at openehr.org >> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >> > > -- > 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 > openEHR Clinical Knowledge Editor www.openehr.org/knowledge > Honorary Senior Research Associate, CHIME, UCL > BCS Primary Health Care ?www.phcsg.org > > > _______________________________________________ openEHR-technical mailing > list openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > >
