September 25, 2017 |
Five Tips for Big Healthcare Software Projects
January 13, 2014  | 
Fort Washington, PA - Software development isn't easy. The bigger the software gets, the harder it is to build right from the ground up. A string of high-profile failures have dealt a timely reminder of this. But it's not hopeless, even with the number of integration points common to healthcare applications. Aaron Mulder, Chief Technology Officer & Director of Chariot Solutions offers five things to consider which could bump the odds in your favor:

1. Separate integration logic from application logic

A user-facing application shouldn't be responsible for translating data formats, converting between synchronous and asynchronous requests, or retrying when a partner system is down. Not to mention there shouldn't be any need to redeploy an application if a partner endpoint changes. Application frameworks and application developers are better at building applications, while integration frameworks and tools are better at handling integration challenges. It's best to build an application to send and receive idealized formats, and use external integration tools to handle detailed transformations and other processing.

2. Use tools that make integration easy

When extensive integration is a given, it makes the most sense to select tools that make integration easy. This means easy to configure, easy to develop transformations and other logic, easy to test, easy to debug, and easy to deploy. It means supporting multiple options for building integration logic -- perhaps avoiding ugly generated code in favor of dynamic inspection, perhaps avoiding complex GUIs in favor of simple blocks of code. It means making it easy to reject or queue requests when an endpoint is down, easy to update individual integration flows, and easy to scale out to handle additional load. Why make a complex problem harder? Continue>

Page | 1 2 3
Suggested Articles