Thanks Pablo, I was dealing with some monster requirements documents which were perhaps atypical.
Ian Dr Ian McNicoll office / fax? +44(0)1536 414994 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical analyst,?Ocean Informatics openEHR Clinical Knowledge Editor www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL BCS Primary Health Care SG Group www.phcsg.org On 1 December 2010 15:06, pablo pazos <pazospablo at hotmail.com> wrote: > Hi Ian, it works without copying and pasting chunks. I just uploaded a doc, > look for the "Tools > Translate Document" on the menu, and here is the > translated "template sintax and config": > > https://docs.google.com/document/pub?id=17-vZ8OElOuWRLTsOXpzOJksW25lw0asQaSq1ZWDr7AU > > Warning: the automatic translation may break some of the sintax, I have to > check it more carefuly. Here is the docs in spanish for gudance: > http://code.google.com/p/open-ehr-gen-framework/downloads/list > > -- > Kind regards, > A/C Pablo Pazos Guti?rrez > LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez > Blog: http://informatica-medica.blogspot.com/ > Twitter: http://twitter.com/ppazos > > > >> From: Ian.McNicoll at oceaninformatics.com >> Date: Wed, 1 Dec 2010 12:54:55 +0000 >> Subject: Re: new openEHR-based framework >> To: openehr-technical at openehr.org >> >> Hi Thilo, >> >> Having done a load of Slovenian->English translations using Google >> Docs, I would suggest the following approach. >> >> 1. Split the original doc into reasonable size chunks - Google chokes >> above a certain limit and save as ? MS Word docs or equivalent >> 2. Upload to Google Docs and open the file >> 3. Ignore any offer from Google to 'translate this page' , if you have >> aotmatic trnslation turned on. >> 4. In Google Docs, Choose Tools->Translate from the top menu. >> 5. Create the translated doc as a copy and then download to your system. >> >> The translation quality is not too bad, although fairly amusing on >> occasion!! Most of the formatting is retained although Word numberings >> tend to get lost. >> >> Ian >> Dr Ian McNicoll >> office / fax? +44(0)1536 414994 >> mobile +44 (0)775 209 7859 >> skype ianmcnicoll >> ian.mcnicoll at oceaninformatics.com >> >> >> Clinical analyst,?Ocean Informatics >> openEHR Clinical Knowledge Editor www.openehr.org/knowledge >> Honorary Senior Research Associate, CHIME, UCL >> BCS Primary Health Care SG Group www.phcsg.org >> >> >> >> >> On 1 December 2010 12:42, Thilo Schuler <thilo.schuler at gmail.com> wrote: >> > Hi Pablo >> > >> > thanks for your answers. Good tip with Google translation, hadn't >> > thought of >> > it... >> > >> > I have your app running on my machine now. I can see the login screen. >> > The >> > hardest bit was to convince my macbook to use jdk 1.6 :)... Otherwise a >> > breeze. I like grails! >> > >> > Could you please tell me a login and password I can use to get into your >> > great application. >> > >> > Thanks a lot >> > -thilo >> > >> > On Tue, Nov 30, 2010 at 12:47 PM, pablo pazos <pazospablo at hotmail.com> >> > wrote: >> >> >> >> Hi Thilo, >> >> >> >> The current performance would make it cumbersome to use it in a >> >> productive >> >> environment,? but it will be great as a prototyping and demonstrating >> >> tool. >> >> Clinicians can judge the value/completeness of archetypes and templates >> >> much >> >> better, if they see them as a working GUI. Your framework seems to be >> >> very >> >> suited for that. >> >> >> >> In fact I used the framework to show the archetype concept, something >> >> like >> >> "archetypes in action". >> >> >> >> I will try to get a small template running locally on my computer >> >> sometime >> >> this week. I will report my experience back to the list. Maybe this >> >> helps to >> >> decide how the community can leverage your work. >> >> >> >> Great! let me know if you need some help. >> >> >> >> A couple of questions to start (Cave: Will possibly bug you with more >> >> questions in the process): >> >> - Does it matter what version of grails I use? >> >> >> >> Now it works only on Grails 1.1.1, you can read the installation page >> >> on >> >> the wiki: >> >> >> >> >> >> http://translate.google.com/translate?js=n&prev=_t&hl=es&ie=UTF-8&layout=2&eotf=1&sl=es&tl=en&u=http%3A%2F%2Fcode.google.com%2Fp%2Fopen-ehr-gen-framework%2Fwiki%2FInstalacion >> >> >> >> You can use google traductor to translate the spanish pages and docs. >> >> >> >> - Can I use the in-memory DB HSQLDB for testing? Or should I set it up >> >> with MySQL. >> >> >> >> Yes, you can use HSQLDB, you can configure it in >> >> grails-app/conf/DataSource.groovy: >> >> >> >> http://code.google.com/p/open-ehr-gen-framework/source/browse/trunk/open-ehr-gen/grails-app/conf/DataSource.groovy, >> >> just uncomment this 2 lines: >> >> >> >> // dbCreate = "create-drop" // one of 'create', 'create-drop', 'update' >> >> // url = "jdbc:hsqldb:mem:devDB" >> >> >> >> and comment the MySQL config. >> >> >> >> >> >> - By looking at your proprietary templates it seems you determine a >> >> root >> >> archetype (usually of type SECTION) and the included archetypes (each >> >> is >> >> either fully included --> 'includeAll="true"' or only a subset --> >> >> specified >> >> by one or several paths). Is this generally correct? >> >> >> >> Yes, it's correct. All the template roots are SECTION or ENTRY, and >> >> each >> >> EHR domain have only one COMPOSITION that record all the data for all >> >> it's >> >> templates. You can see in Config.groovy we have a trauma domain, an >> >> emergency domain, etc. We want to improve that to define multiple >> >> COMPOSITION templates to one domain. >> >> >> >> Cheers, >> >> Pablo. >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> 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 >> > >> > >> >> _______________________________________________ >> 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 > >
