Hi @joshdcollins,
Does the other system need to be responsible for reaching back, or could it be that the FHIR data gets pushed into it as it gets available?
If the latter then I’d just design a Camel route for openmrs-eip that filters for the changed entities that need to get propagated, fetch their FHIR representation, and then push them to the third party system.
This is exactly what we’re working on right now with lab test orders (amongst other things), see for example ‘Posting laboratory service requests to OpenELIS Global’.