Medsphere.org: Message List - Just some food for thought on OVID and extending Open Office to OpenVista

Re: Just some food for thought on OVID and extending Open Office to OpenVista

noreply@medsphere.org — Wed, 17 Feb 2010 17:59:58 GMT

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 FM Projection 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.

Re: Just some food for thought on OVID and extending Open Office to OpenVista

noreply@medsphere.org — Wed, 17 Feb 2010 15:00:51 GMT

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.

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?

Re: Just some food for thought on OVID and extending Open Office to OpenVista

noreply@medsphere.org — Tue, 16 Feb 2010 17:04:31 GMT

Sure that could be one use case, Another would be clinical flowsheets in a spreadsheet. All in all I think it makes good sense to have links from the 2 leading Office packages into VistA. An MS Office link could likey be reasonably made from the CIS lbraries.

Re: Just some food for thought on OVID and extending Open Office to OpenVista

noreply@medsphere.org — Tue, 16 Feb 2010 13:29:53 GMT

Richard,

It looks like a definite possibility -- worth trying, anyway. What is the use case though? Creating templated documents in Open Office that supply information from OpenVista via OVID?

Just some food for thought on OVID and extending Open Office to OpenVista

noreply@medsphere.org — Sun, 14 Feb 2010 15:23:02 GMT

Andy,

I was doing some thinking about connecting OpenOffice to open vista when one of my clients asked me about creating office based applications for VistA data. I did a little digging and found that OO has an API called Universal Network Objects (UNO) that allow access to such objects via Open Office Basic. WOuld this work with OVID? I would like to try an find out.

This might be a supurb way of creating Office Productivity Apps (both clinical and administrative) from OV using OVID as the transport layer.

http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide/UNO

Richard