Dispatch Queues

System Dispatch Queues are intended for sending information outside of the system.

Whenever the system needs to send data (using a standards based interfaces) to systems that aren't the current instance of the iCDR or the dCDR, the messages will be placed into a dispatcher queue.

Dispatch Queues

Dispatcher queues differ from synchronization queues used on the dCDR in that they do not support reconciliation of conflicts or subscription management.

Examples of remote targets that aren't part of the system can be:

• FHIR endpoints,

• HL7v2 endpoints, or

• GS1 endpoints

The use of the Dispatch Queues allows for the reliability in sending messages, meaning that messages are queued in order and any messages that cannot be sent are relayed to a failed queue.

What technologies can be integrated with Dispatch Queues?

Technologies

The system may be used with a queueing technology like MSMQ, Rabbitmq, or a simple queue like the default file based queue.

What are common Dispatch Queues?

Common Queues

Common queues used in the system are:

• sys.pubsub - Used for all outbound dispatches to standards based pub-sub broker requests.

  • These are things like patient registrations, notifications of data changing, etc.

• sys.audit - Used for dispatching audits to remote systems.

• sys.ami - Used by direct connect dCDR instances to queue administrative command messages to the central iCDR.

---

Dispatch Queue Operations

🔁Resubmitting

🔁Resubmitting Messages in a Queue

Users can opt to Resubmit a queue, which instructs the dCDR or iCDR to take all messages from a dead letter queue and place them back into the primary queue for re-submission.

🚧To Resubmit a queue, please follow the resubmitting a queue guide.

🧹Purging