RxWorks transforms for Kettle
Submitted by Guest on Tue, 28/08/2012 - 08:05
I am planning to do a migration from RxWorks. Google got me to http://lists.openvpms.org/pipermail/users/msg00066.html which is Nov 2007 email from Tony Keizer which says that "you can find the transforms in the latest OpenVPMS release under the import/transforms folder".
However the 1.5.1 release package does not include them.
Are there any RxWorks transforms available, or do I have to start over?
Thnaks, Tim
Re: RxWorks transforms for Kettle
It was probably the transforms for quite an old release. They wouldnt be current anyway.
Generally data transformation is what a paid implementation service will provide. They do it to ensure data integrity and consistency from the old system. Most implementers will have up to date transforms for many systems including Rxworks
Openvpms operates on donations/contributions as well as a small yearly subscription fee. The developer doesnt do data transformation, however he is extremely helpful for those that try and work out there own. I did all mine for a very small clinic...but I will use a paid service when I transfer my main clinic...there is too much data to risk stuffing it up.
My advice, depending on how much data your transforming.
1. Reread some of the forums they have a number of Kettle Transforms you can work off and build your own. Ask on this forum if you get stuck with something
2. Discuss using a paid service with one of the implementers that provide that sort of service. Data transformation doesnt cost alot compared to implementing another package like RxWorks or Vetsql etc.
Good luck with OpenVpms I moved to it for my small practice 8mths ago and it is making me money.
Ben
Re: RxWorks transforms for Kettle - Thanks
Ben - thanks for your reply and advice.
To clarify my situation: its my son & daughter-in-law's practice; I do their sysadmin & support work; I am v.familiar with the RxWorks database structure; I want to end up with developer level expertise and hence I want to do the implementation myself; our plan allows for 12 months for implemenation, testing & training - and the business runs 24/7 so I need things set up so I can update the OpenVPMS system from the current RxWorks database so as to enable an RxWorks to OpenVPMS cutover with no data loss and minimal (under 4hrs) downtime.
However, I do suspect that I will end up buying some consultancy time from one of the implementors.
Regards, Tim