Hello Sam. We are trying to reach Beatriz and other people in Brazil involved with openEHR and we want to attend at the Workshop on Open Source Health Informatics Projects at Rio in 2008. I spent the last days reading openEHR documents and at monday we will have a meeting when I want to share with the team what Ive learned about openEHR
I know its expensive and hard to develop software, thats why I've always searched for some way to not reinvent the wheel with my project. GestorPsi only exists because in Brazil there is no good software made for psychologists. Not for EHR and not for services management. And all the health software's company that I could find works with proprietary software. Since the beginning the hole idea is to use free software at all levels. Now that I understood a bit about archetypes I know that this will enable to have one system for psychology and also for other health practices. But your question remains: Build or use? The better would be both. We will build because its the nature of the project and of the founds. But would be better if we could do this with partners. And we are open and seeking partnerships and collaborations. Lets wait for Beatriz and other contacts in Brazil I will do everything possible to develop using openEHR model and to use free code or software/system available under opensource licences. If at the end we fail to have some usable stuff, at least we may still have a lot of archetypes about psychology and social sciences stuff. Regards Oliver Sam Heard wrote: > Dear Oliver > > Everyone wants to build things from scratch - it is human nature. I > would suggest these days that it is a bit like deciding to build a car > from scratch rather than getting one that is built by someone else. > The fact is that it is incredibly expensive these days to build > software from scratch. Administrative systems are difficult if they > include everything required, health records are very complicated. > > We would suggest that you look to a Service Oriented Architecture and > concentrate on the front end requirements. Beatriz is an expert on > health care standards and the company she works for have already > learned a lot about openEHR. It would undoubtedly be worth > collaborating on this. > > So to answer the key question - will it be easier or harder to use > openEHR? Harder to build software, easier to meet the needs of your > clients and patients for the years to come. The question is - do you > build health record software or use software that has been built? You > can go to the who is using openEHR space and look for suitable > partners. Building complex monolithic systems from scratch these days > is for big companies with massive resources. > > So have a chat with Beatriz and see what you come up with. > > Cheers, Sam > > Oliver Zancul Prado wrote: -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071116/5095850d/attachment.html>
