Because iNTERFACEWARE's products are 'middleware', compatibility with evolving integration standards and health information technology is critical. For these reasons we have a well defined upgrade and update policy.
"Thanks for the excellent support! ... Really a great job on your part. We all expect software to have bugs - what we need is:
a. confirmation that the problem isn't due to something we've done;
b. direction as to a workaround; and
c. an idea of when a fix will be available.
As you know, steps a-c tend to be an issue for a lot of companies! Thanks to you and your team for showing how this should be done."
- Andy Schriever,
CEO
Park Street Solutions
Of course, we understand that there needs to be a balance between providing state-of-the-art software with continued support of prior software releases for a reasonable period of time.
As a valued customer, we want to work with you as you upgrade, ensuring that the time, effort and funds you have invested in integration is prudently protected.
The overwhelming feedback we get from customers who upgrade is that they wish they had done so much earlier, noting that the improvements in usability and power make the upgrade well worth the small amount of effort required.
To ensure your upgrade is as smooth and simple as possible, we have implemented a rigorous quality assurance process that tests for backward compatibility and bugs. Our documentation on how to upgrade Iguana™ and how to upgrade Chameleon™ is self-explanatory and makes implementation easy.
"Everything is running smoothly, so 'if it ain't broke, don't fix it'."
"New versions may also have bugs, so why introduce a potential problem?"
It is true that new software releases raise the possibility of new bugs - so not having the latest version might seem advantageous. However, waiting too long to upgrade is a mistake. Not only do you miss out on real improvements in the software, but the applications, databases and platforms you are integrating are themselves being constantly updated. The further you fall behind, the more likely some incompatibility will occur. You do not want to resolve a problem under pressure when it could have all been tested and taken care of in an orderly, well-tested environment. In addition, when you do decide to upgrade you may find that you have fallen so far behind that the newer versions cannot flawlessly read the older configuration data files.
If you still have any questions or concerns, please do not hesitate to contact us directly.
"What was estimated to take four months of implementation time, took six weeks. Because of iNTERFACEWARE™, a major obstacle became a minor speed bump."
Mike Gogola, Hermitage Medical Clinic
Contact Support