new openEHR-based framework
rs. 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 > > > > > > > > > > ___ > > 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 > > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110403/0f1621c4/attachment.html>
Overview
Dear Friends, I started OpenEHR and want to know the project. Any good references, over-views and ... can help me. I planned to know the concept, architecture and source subsequently. Any help will be appreciated before. Regards, -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110403/66b588cf/attachment.html>
new openEHR-based framework
an 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 > > > > > > ___ > 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/20110403/e70bf1ad/attachment.html>
GUI stuff in AOM/ADL? (Was: future ADL-versions)
international > (e.g. European) discharge summary, referral, e-prescription etc - but > whose GUI models are very unlikely to be shared. On that view of > things, you don't want to have to revise such a published resource due > to some particular GUI directives buried inside it. This doesn't mean > that the ADL (abstract or XML form) formalism can't be used, but I > still think a separation of the pieces will make dependency and > release management a lot easier. Erik may be right: if the GUI hints > can be expressed in a template, then by definition, it can be done in > a specialised template, and that can clearly be local. > > At the moment, we have to consider this area as 'industrial research', > and I for one would encourage all experimentation to be published and > flagged on this list, as a way of getting us all on the same page with > respect to lessons being learned. > > - thomas beale* > * -- Hong Yul Yang Research Programmer Department of Computer Science The University of Auckland Office (tamaki): 731-339 Phone: +649 373 7599 x88237 http://www.cs.auckland.ac.nz/~hongyul -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110403/0b602a14/attachment.html>
Overview
Hi and welcome to the list, openEHR is a big and wide topic - is your interest technical, clinical, research or implementation. We are a friendly bunch but it would help to know more about your background and reason for interest in openEHR so that you get some pointers in the right direction. Ian Dr Ian McNicoll office +44 (0)1536 414994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical analyst, 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 3 April 2011 12:17, A.H. Sharif wrote: > Dear Friends, > I started OpenEHR and want to know the project. > Any good references, over-views and ... can help me. > I planned to know the concept, architecture and source subsequently. > Any help will be appreciated before. > Regards, > > > ___ > 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/20110403/fc21871e/attachment.html>
Overview
Most of the references at http://www.openehr.org/shared-resources/getting_started/getting_started.html are likely to be useful, depending on what you have already read. For a 'serious' technical overview, see the Architectural Overview (PDF <http://www.openehr.org/svn/specification/TAGS/Release-1.0.1/publishing/architecture/overview.pdf>, HTML <http://www.openehr.org/svn/specification/TAGS/Release-1.0.1/publishing/html/architecture/overview/Output/front.html>) - a long-ish technical overview with many diagrams, covering the whole architecture of /open/EHR. * * - thomas beale -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110403/5b95c426/attachment.html>
