# Dispatcher Queue

Whenever SanteDB 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. 

{% hint style="info" %}
Dispatcher queues differ from synchronization queues used on the dCDR in that they do not support reconciliation of conflicts or subscription management. Dispatcher queuest are intended from remote targets that aren't SanteDB such as FHIR endpoints, HL7v2 endpoints or GS1 endpoints.
{% endhint %}

![](/files/IuYJZMCb6AXmqOYvCI5S)

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. Additionally administrators may `Purge` a queue, which instructs the dCDR or iCDR to purge all data in the waiting dispatch list.

SanteDB may be used with a queueing technology like MSMQ or a simple queue like the default file based queue. Common queues used in the SanteDB server 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.

## Related Topics

{% content-ref url="/pages/7bdN98ot7NzYsEKlMd38" %}
[Pub/Sub Manager](/operations/cdr-administration/santedb-administration-panel/system-administration/pub-sub-manager.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MfoQqYW3Sp8aIRYVrA5" %}
[FHIR Subscriptions](/developers/service-apis/hl7-fhir/santedb-fhir-implementation/publish-subscribe.md)
{% endcontent-ref %}

{% content-ref url="/pages/38mDCcpmCkpGIcYpsDDa" %}
[Audit Dispatch Service](/developers/server-plugins/implementing-.net-features/service-definitions/audit-dispatch-service.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.santesuite.org/operations/cdr-administration/santedb-administration-panel/system-administration/dispatcher-queue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.