
EMR and EHR vendors are discovering that the responsiveness of their data providers can have a big impact on their ability to get certification or get to market. This is especially true in
drug interaction databases, where the quality of the data can affect crucial product goals like Meaningful Use certification or SureScripts eprescribing certification.
Even beyond certification, a data provider can affect how quickly you can develop new features, respond to customer requests, or even whether you can develop new and necessary functionality at all. In many ways, a drug information vendor is one of a health IT developer's most important partners.
What if the partnership doesn't work out?
Real problems can arise if this partner is unresponsive or doesn't provide the expected level of customer service and new feature development. An EHR or EMR can literally be left treading water in situations such as these. What to do? Here are three tips.
1. "Bolt on" additional functionality: For some functionality, it's possible to lease an already-certified third-party solution that will help you meet short-term needs if your own development is stalled. The classic case for this electronic prescribing -- many EMR developers use pre-existing third-party eprescribing modules to get them to market faster while developing their own. One provider of such modules is DoseSpot.
2. Use web services to easily integrate multiple sources: Sometimes a single source just doesn't have everything you need, but maintaining multiple in-house databases can be costly and time-consuming. For specific bits of information you want to add -- for instance, patient education documents in foreign languages -- it may be easiest to access a second vendor using web services. This puts the responsibility for maintaining the data on the vendor, and leaves you with a much smaller development and maintenance task. One drug data provider, Lexicomp, now supplies much core functionality through web services, including all major Meaningful Use Stage 1 items.
3. Cut the anchor as soon as you can: Sometimes all you can do is look for another provider. The two items above can help you in some circumstances, but for core functionality you may need to cut your losses. The earlier you can identify a bad relationship, the better. One customer of Lexicomp came to us after unsuccessfully trying to work with another vendor's dataset. After a short while with the other database, they knew it wasn't right, and so they were able to painlessly replace the data with Lexicomp's. In less than a month after that, their product was live.
The moral of the story is that your drug vendor relationships are crucial to your success. If they don't feel right, then stop and look for alternatives. A slight delay upfront is better than being trapped with a vendor who makes it more difficult for you to meet your customers' needs and innovate new features.