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
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
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 ahsharif at gmail.com 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
new openEHR-based framework
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)
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
