If we use a screen based approach, our integration will break when a vendor ships an upgrade. Why would we use Boston Software Systems for integration into EHR/HIS's or revenue cycle systems?

The notion that the integration will break is largely untrue, and the reality is more nuanced and much less scary. Of course screens can, and over time, will change. But since we provide non-positional based features, a change may not cause any problem at all. And of course an upgrade may not influence the workflow of your integration.

Vendors add features to their products for a variety of reasons; new features mean differences in workflow, which also usually means differences in data requirements.  This means any integration mechanism, be it HL7, web services, custom import routines, etc. will need to be changed when the vendor changes the screens. The concern shouldn’t be change; change is inevitable. The concern should be how quickly can you detect and respond to change!

One of the greatest strengths of the Boston Software Systems approach is the ability to rapidly react to change. Change detection is instantaneous; and you control the timeline and the methodology for reacting to change. It is not possible to instantly divert R&D resources in your organization to modifying a broken standards based integration for a single early adopter customer, especially within large organizations. Boston Software Systems’ integrations are not implemented by your R&D, they are created by client facing technical staff, or even directly by Boston Software Systems. This allows your organization to respond to and fix the integration the way your customer wants you to – yesterday! We routinely see response times measured in hours and days, not weeks or years.

Back to Overview