This page shows the architecture for the HSPC Reference Implementation with messaging.
hsp-reference-messaging
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.
Related articles