new openEHR-based framework

2010-11-28 Thread pablo pazos
 the development en 3 months, using our
  openEHR-based framework.
 
  So, if we have 10 projects this are the numbers:
 
  * Without openEHR tools: total of 160 months (13.3 years)
  * With openEHR tools: total of 56 months (16 months for the first
  development, 4 months for the rest 9 projects, that's 4,7 years!!!)
 
 
  If we can improve the tools, these times could be improved, and the final
  solutions have the advantage of separating the knowledge from the software,
  and we can share and reuse archetypes between diferent projects, that's just
  great! :D
 
  Hope this experience can help you.
  -
 
 
  --
  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
 
 
  ___
  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/20101128/3fab6b1a/attachment.html


new openEHR-based framework

2010-11-28 Thread pablo pazos
-framework-para-crear-historias-clnicas-electrnicas,
 page 21

Java technologyGrails framework to build our Opeh EHR-Gen Framework with 
MVC+Services, and a great ORM for persistenceit uses the Groovy PL (is a 
dynamic, java-based, PL)


We want to add some features, like plugin support in order to add functionality 
to the apps created with the framework, like PIX-PDQ integration, DICOM 
query-retrieve integration (we have developed some hardcoded integration with 
both), etc.



I hope this can serve to better understanding of our project.

-- 
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




 Date: Wed, 24 Nov 2010 16:28:04 +0100
 Subject: Re: new openEHR-based framework
 From: rong.acode at gmail.com
 To: openehr-technical at openehr.org

 
 Hi Pablo,
 
 I was about to ask you to make a proper announcement on the list. Ian
 beat me on this ;-)
 
 Thanks for the excellent work and commitment to the open source

 community!! I will send you some specific questions later on.
 
 Cheers,
 Rong
 
 On 24 November 2010 16:20, pablo pazos pazospablo at hotmail.com wrote:

  Hi,
 
 
  I have send this same email to the last 21090 discussion, and Ian ask me if
  I can send it again in another thread, here it is.
  Just yto give some context, this was written in response to Koray who asks

  for real-world implementations, and who is studying the complexity/time of
  building openEHR-based systems.
 
  I should clarify that the framework is the core of the system, but not the

  whole system. The whole trauma application has also DICOM integration,
  external MPI integration via IHE PDQ, the generate CDA feature (we leave
  this on the framework too, but is not a part of the core), and the

  calculation of quality of care indicators.
 
  Ian ask me if I can publish the archetypes we use, archetypes, (our own)
  templates, the code, etc, are all here:
  http://code.google.com/p/open-ehr-gen-framework/source/browse/#svn/trunk/open-ehr-gen

 
 
  Cheers,
  Pablo.
 
  
  Hi Koray,
 
  As an example of a real-world implementation, we have build an EHR for

  trauma care. Our project was developed in one year and four months.
  The core of the development is an openEHR-based framework, wich takes
  archetypes and our own templates (with GUI directives), and generate GUI,

  data binding with RM structures, validation of data against archetypes
  contraints, and persistence of the RM structures. BTW, this framework has
  been open sourced: http://code.google.com/p/open-ehr-gen-framework/ (sorry

  docs in spanish only).
 
  I've estimated that this particular project without the openEHR overhead
  could be finished in 6 months.
  But if I have other project like this today (same size, same complexity,

  etc), I think we can finish the development en 3 months, using our
  openEHR-based framework.
 
  So, if we have 10 projects this are the numbers:
 
  * Without openEHR tools: total of 160 months (13.3 years)

  * With openEHR tools: total of 56 months (16 months for the first
  development, 4 months for the rest 9 projects, that's 4,7 years!!!)
 
 
  If we can improve the tools, these times could be improved, and the final

  solutions have the advantage of separating the knowledge from the software,
  and we can share and reuse archetypes between diferent projects, that's just
  great! :D
 
  Hope this experience can help you.

  -
 
 
  --
  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

 
 
  ___
  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




-- 
Thilo Schuler
+61 406 113 740



___
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/20101128/62012aee/attachment.html