...
The messaging system exists to support context-based routing of messages. The FHIR use case is to support the FHIR subscription resource. When a subscription is submitted to the API server (created, updated, deleted), the subscription is registered with the messaging system as a Drools rule based on the subscription criteria. When non-subscription resource (Observation, Patient, etc.) is submitted to the API server (created, updated, deleted), the resource is submitted to the messaging system for routing. If the resource matches (using Drools rules) the resource is routed according to the channel definitions of the subscription.
Alternatively, a back-end service could use a polling strategy to determine when any changes have occurred to the FHIR resources (for example, from an external data feed). This back-end service would then submit the resource to the messaging system for routing.
Bilirubin Monitor Application
...