The more real-world Use Cases we can define, the better. I like the idea of interfacing the two products -- but would need some real use cases to understand the 'why' we'd do that...
JohnLeo Zimmer wrote:
- Such an interface might also allow us to populate fields in a form (DOT physical, insurance physical, etc.) with fields generated within a VISTA reminder dialog.
This is an interesting Use Case. Are there standard forms used in a private practice?
JohnLeo Zimmer wrote:
- And it could be used to glamorize printed output, with letterhead, other images, improved fonts and other formating that don't really fit very well on the server-side.
- Going the other way, might it be used to provide OO's spell-check to CIS/CPRS?
1) My preferred path to improved reporting (letterhead, images, fonts) is to integrate a report server. Our direction would be to use to provide read-only access to Jasper's report server. Sites could then use the WYSIWYG report writing tool, iReports, to author reports and load them into the Jasper server. Jasper would provide enterprise class reporting and simple BI capabilities. We did a live demo of using iReports to query an OpenVista server at VCM20, so this is not a "future" thing -- all the nuts and bolts exist.
2) CIS has built-in, inline spell checking (screenshot -- although w/out a medical dictionary loaded). The CPRS model has always seemed ridiculously hack-y to me (having made a similar mistake on a previous project trying to integrate w/ Excel). I would much prefer to use a native open source spelling library as we have in CIS.
