We recently migrated with another organization. We have multiple Interface Engines. What should we do?
That is a great question, but not an easy one to answer. The first question is are they the same software vendor. If they are the same vendor, I would recommend that you develop an architecture that will help you support it more easily. For example, divide engine based upon location or by functionality. Location could be by hospital or clinic while functionality could be ADT/SCH versus ORU. This also gives you an opportunity to build redundancy in case one system goes down.
If they are not the same software vendor, I strongly encourage to pick one vendor and convert. There is tangible and intangible savings with going with one vendor. The tangible savings will be the annual support fees, cross over training for personnel. The intangible savings are on going support of two systems. Conversion will have a one time expense
Your comment will be posted after it is approved.
Leave a Reply.
Kevin L Frederick
Founder & CEO
Welcome to our blog! Our purpose at D288 IT Solutions is to support the advancement of healthcare IT. Our hope is to create an environment through sharing of topics aimed to help the healthcare IT professional in their careers. We hope you find the information useful and practical, so enjoy and check back often!