On Thu, 28 Aug 2003, David Forslund wrote: > What you say is very important. OIO is basically a very good Content > Management System will suited to the healthcare needs.
Dave, Thanks! I am most interested in your view on OIO's limitations, especially from OpenEMed's perspective. Mapping out the boundaries is the only way to make progress. > We are using Plone/Zope ourselves. I in no way would want you to change > what you are doing. On the other hand, I am always looking for opportunities to change what we are doing. :-) > And graphs are far from everything, but are nice to have for certain > applications. I think just like Fred's FreeB module, the graphing function is another opportunity for us to compare notes. Your reference to JFreeChart is very helpful. ... > People use JSP/Struts today without knowing any Java, but I can't say > what is a better environment to use. This Struts example looks pretty complicated: http://jakarta.apache.org/struts/faqs/actionForm.html > I do believe that we shouldn't have physicians building web pages. Why shouldn't everyone, including physicians, be able to build web-pages? Just like everyone "should" learn how to read and write. > Also, any system needs to plug into the wider world to get data, etc. I agree. Like an web-browser that can be used to query Google.com. > We need interoperable tools spanning these diverse systems to make this > happen. I agree. I think we start small - with Microsoft Office product, then Mozilla, and various URL-accessible applications (e.g. Google). For example, if OIO can query OpenEMed via URL to retrieve a patient record, then OIO and OpenEMed will be one big step closer to being able to interoperate! (or, if you want to do it the other way around, it would be good too.) Best regards, Andrew --- Andrew P. Ho, M.D. OIO: Open Infrastructure for Outcomes www.TxOutcome.Org
