[General Discussion] The Pom's back

Hi Folks, Time for an end-of-year check-in! When I was last here in Feb, I downloaded OpenVPMS and had a play. Results were mixed and I felt that there were signs of great potential, but that the software was not ready to take any further yet. How things have changed - a look at the current demo shows great progress so well done to all concerned! We are still looking for a suitable replacement for our 3 apps and although I don't think OpenVPMS is there yet I will be keeping an eye on things and possibly contributing where I can. It's interesting to see that some clinics are migrating from RxWorks - not that we use the package, but because it's quite a leap of faith to jump ship from such a mainstream PMS package (whether you love it or hate it) and so if some clinics are bold enough to make this move then it speaks well of OpenVPMS. Overall, our requirements remain the same and I would really appreciate any feedback from practices with a similar setup: 30 sites. 1 central database, 1 replicated copy at HQ. Sites possibly having their own local data set for ADSL fault tolerance. All sites able to see records from other clinics + able to book appointments in other clinics Site-specific pricing models, managed centrally. Online ordering of stock - it would be great to discover that the stock handling of OpenVPMS is modular so we can bolt on a module that works with our supplier (NVS broadband ordering) Here's a few other thoughts and issues for you: Reporting: If anyone is developing their own reports and hasn't found it already, I strongly recommend the Open Source package called iReport - it's very easy to use and has a host of features. We use it to supplement the (pretty dire) reporting in our existing packages - which means we are querying data from MS-SQL, MS Access and also MySQL (into which we import .csv files from our oldest PMS app). iReport will even work with .csv files - worth a look: http://www.jasperforge.org/sf/projects/ireport In the UK, the Society of Practising Veterinary Surgeons (SPVS) has formed a consortium looking at XML standards for transferring data between practices, PMS apps, insurance companies and diagnostics labs. The standards are currently being developed and there is interest from USA and mainland Europe. I am involved as we own a diagnostics lab as well as the clinics. It might be worth keeping an eye on things: http://www.vetxml.org/ Cheers! Nigel Kendrick

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: The Pom's back

Thanks for your annual report Nigel! Firstly let me tell you that our practice is in no way the size of your organization! Nevertheless we are quite a busy single site practice with up to 4 veterinarians consulting at any given time as well as full time hospital and surgical vets during the daytime. We have been running OpenVPMS for a few months now and it is proving to be extremely stable and reliable. With gradual refinement the basic functions are now running really well but what excites us most is the fact that in the near future projects aimed at developing stock control, graphic scheduling and investigations modules will be getting underway. We are hoping that people like yourself and the growing band of practitioners who use OpenVPMS will put their hands up and get involved in this process. We should all sit down, create a wish list of features for these functions and throw them at the forum and share our ideas. Peter

Re: The Pom's back

Hi Nigel, Welcome back. Things are progressing quite well and it is good to have more live sites to test the application and generate new feature requests. The two things that have been most pleasing so far are the reliability and also how quickly we have been able to generate new features. As far as your requirements many of them relate to the database system chosen which is very flexible in OpenVPMS. Although I have not had any real experience with replicated databases in larger organisations I am fully aware that a range of database systems that we can utilise support the features you mention. We have mainly used MySQl as our SQL database engine. I understand some implementors have experimented with posgres. If you want to experiment with other database engines that support replication we would be happy to help where we can. Site specific pricing models is not part of the current feature set but has been discussed as a future enhancement. Your timing is good as we are in the process of designing and implementing stock management functions which includes a number of pricing management features (both sell and supplier). This will also include discussion on online supplier pricing and stock enquiry and ordering. I hope you can participate in the discussion that we will initiate soon on the mailing lists. Interesting you should mention iReport because OpenVPMS implements all it's printing functions using either jasperreport or open office templates. We use iReport to design the jasperreport templates and also to develop reports that can be incorporated into the Reporting section of OpenVPMS. All invocies , receipts , Statemets, drug labels are generated by jasperreports. In fact you can develop a report in iReport and deploy to OpenVPMS and it will prompt for any parameters defined in the report. We also support the graphing options in jasperreport. We think it is pretty nifty ... Down the track I hope to develop a data warehousing tool for OpenVPMS which will allow even more complex reporting including pivot table support using the jasperserver project. I am definitely looking for people to contribute to this sub project ... Cheers Tony
Syndicate content