Integrations Made Simple – An Intelligent Conversation Between Systems
It’s Friday afternoon and a notification goes out that there is cake in the break room. You sit there wrestling between the angel and the devil on your shoulders whether you should partake. You love cake, but you are also trying so hard to cut back. You decide more information is needed and ask questions. Is it chocolate? Vanilla? Is there also ice cream? Homemade or store bought? Is it someone’s birthday? It would be rude not to celebrate a birthday…
Whatever decision you end up making (cake!), an event was raised, you accepted the information, determined if further action was needed and proceeded from there.
What if clinical systems integrations could be that simple? The passing back and forth of data through a conversation, with the intelligence to make decisions based on that data, is now possible with modern technology.
Imagine this. An event happens in your Randomization and Trial Supply Management (RTSM) system (ex: a shipment is created). The RTSM then reaches out to the integration saying it has a message, a small amount of data passes back (where is the shipment coming from and where is it going), and the integration acknowledges the message and determines if an action is needed (does the depot use an integration for generated shipments?). If the answer is no, nothing else happens. If the answer is yes, the integration reaches back out to the RTSM for more information so it can process the data and send out the file.
And everyone has cake. Or not.
The challenge is most integrations are not simple conversations, but rather involve complicated custom coding, time and resources to develop. Modern technology enables the transfer of information because the integrations are in their own system outside of the RTSM. New integrations or modifications to existing integrations can be made without having to worry about impact on the RTSM itself.
Since all the business logic is within the integration, the RTSM does not make the decision, it simply relays the message. This allows integrations to be a conversation, distilled down to three main areas.
1) What data is being sent?
2) In what format?
3) How is it being transferred?
If you know the answers to those three questions, let’s have a conversation. Those answers aren’t quite as simple, however, and if you would to discuss data strategy or requirements building, our experts are here to help.