Query re RxWorks porting tools upload
I am nearing the end of my work on porting RxWorks to OPV.
Would it be stepping on anyone's toes (specifically the people who do implementations for a living) if I uploaded most of the Kettle and other files that I have built. [There are some 16 kettle jobs and 106 transforms which do a full port of the RxWorks system.]
Regards, Tim
Re: Query re RxWorks porting tools upload
Does anyone know if there are intellectual property issues hosting RxWorks migration scripts?
Other than that, I don't have a problem with including it here.
-Tim
Re: Query re RxWorks porting tools upload
Hi Tim,
I have no issues with you providing your Kettle transforms and jobs to the community.
I think the only issue you should consider is the one Tim mentioned, Intellectual Property. I understand that RxWorks is very protective of their IP rights and consider the database schema as part of these rights . Given the transforms necessarily contain information pertaining to the schema they may consider their publishing a breach of their IP and OpenVPMS may get a nasty take down notice and they may consider action against you. I would consider this very carefully before publishing. :-)
Cheers Tony
Re: Query re RxWorks porting tools upload
Tony - thanks for your input. I must admit that to me a sensible person would reason: the data within the database certainly belongs to the practice; access to the schema is not secret and indeed knowledge of the schema is necessary if one is to write queries and reports to help run the business; hence there is no bar on me using knowledge of the schema to export my data from the system.
However there remain four things to ponder: does the above arguement allow me to tell others how to export the data; what does the RxWorks licence say; are my lawyers better than theirs, and if so can I afford them; and finally do I need the hassle.
The last point of course trumps the others. Hence, regretfully, I retreat.
Regards, Tim
Re: Query re RxWorks porting tools upload
Hi Tim,
I agree with your sentiments completely but as you probably realise sensible and fair is not a word commonly used when referring to this particular company. :-)
Cheers Tony
Re: Query re RxWorks porting tools upload
I actually rang rxworks...to see what they said...the support had no idea...but said they would happily convert data FROM rxworks for a fee...nice (sarcasm)
Anyway
TimG can you email me here
benjicharlton @ gmail dot com
I am not really interested in the rxworks data (we dont use it - custom designed PMS 15yrs old) more so the data validation/openvpms loader steps you finally settled on for various data entry. When I did my small clinic we didnt bother with a lot of stuff..but now I am doing my bigger one hopefully to go live later this year I want to see how far I can take it.....mind you our data is a mess. I am findind PDI 3.2's DATA VALIDATION step to be vital. God I wish it could do UNIQUE rows (but split out the non uniques currently only available in PDI4 as a single step)
One of the most frustrating things I am finding is the product price list the practice uses...linking it to a supplier...matching or not matching etc etc. naming conventions are all over the place....
I suspect that posting the kettle transforms MINUS the initial DATA INPUT step would NOT breach any IP btw..because your omitting the data access step..but god knows what people see as IP and not IP...aka apple v samsung.
Ben