#### Nullification
Domain Message Specification

### ITK Implementation

Application Roles | Responsible for sending | Responsible for receiving
--- | --- | ---
The relevant Sender Application Roles used for Nullification are contained within each message specification. (Sender Application Roles) | The relevant Interactions used for Nullification are contained within each message specification. |
The relevant Receiver Application Roles used for Nullification are contained within each message specification. (Receiver Application Roles) |  | The relevant Interactions used for Nullification are contained within each message specification.

#### Trigger Events

The relevant Trigger Events used for Nullification are contained within each message specification. (Trigger Events)

#### Interactions

Note : Message acknowledgements and responses are requested by the document sender via handlingSpecifications within the ITK Distribution Envelope. For more detail on handlingSpecifications and the acknowledgement framework see the ITK Core pack (available from TRUD).

handlingSpecification key | handlingSpecification allowable values
--- | ---
urn:nhs-itk:ns:201005:infackrequested | “true” or “false”
urn:nhs-itk:ns:201005:ackrequested | “true” or “false”
urn:nhs-itk:ns:201005:busresponserequested | “false”

The relevant Interactions used for Nullification are contained within each message specification. (Interactions) Sender: The relevant Sender Application Roles used for Nullification are contained within each message specification. (Sender Application Roles) Receiver: The relevant Receiver Application Roles used for Nullification are contained within each message specification. (Receiver Application Roles) Message: Wire Format: NHS CDA RMIM (POCD_MT000002UK01) Conformance Format: Nullification Document (POCD_MT130001UK05) Trigger Event: The relevant Trigger Events used for Nullification are contained within each message specification. (Trigger Events)