One of the main considerations when building a system to integrate your case management system to Nexus is where unique identifiers will be stored. Nexus makes this as easy as possible by allowing you to use your own system generated unique identifiers to identify every resource in Nexus.
Nexus generated events broadcast through Nexus Transmit are structured in a way that allows a lot of flexibility for how they are translated and stored in you case management system. If your case management system already has the concept of a Drug Test, then a completed Nexus Drug test can be mapped to the properties of the drug test within the case management system. Important information that cannot be mapped can be appended to a Note. Nexus events that do not have a structured concept in the case management system can be saved as a generic note or chron.
Both Nexus Sync and Nexus Transmit are designed to be used in real-time. If your case management system allows for notifications as soon as a client is added or updated, this could be the best place to initiate the synchronization back to Nexus. This allows for the most flexibility in workflow as users won’t have to wait for one system to update another. Knowing that not every case management system allows for real-time notifications, both Nexus Sync and Nexus Transmit allows for batch processing as well.
If events from Nexus Transmit cannot be process immediately as they happen, it may make sense to setup a middle-tier system that can receive Nexus events as they happen and perform some basic filtering or preprocessing of the data. This will setup the data to be in a more consumable format when its time for the batch system to run.