• Primary General Practitioner Recipient NHS 111 CDA Document
• Primary Emergency Department Recipient NHS 111 CDA Document:
• Primary Out of Hour Recipient NHS 111 CDA Document
• Primary Repeat Caller Repository Recipient NHS 111 CDA Document
• Copy Recipient NHS 111 CDA Document
• Nullify NHS 111 CDA Document
• Primary NHS 111 Request for Ambulance
• Primary NHS 111 Repeat Caller Document Set

• Primary General Practitioner Recipient NHS 111 CDA Document
• Nullify NHS 111 CDA Document

• Primary Emergency Department Recipient NHS 111 CDA Document:
• Nullify NHS 111 CDA Document

• Primary Out of Hour Recipient NHS 111 CDA Document
• Nullify NHS 111 CDA Document
• Primary NHS 111 Repeat Caller Document Set

• NHS 111 Repeat Caller Sync Query

• NHS 111 Repeat Caller Sync Query Response

• NHS 111 Repeat Caller Sync Query Response

• NHS 111 Repeat Caller Sync Query

• Copy Recipient NHS 111 CDA Document
• Nullify NHS 111 CDA Document

• Primary NHS 111 Request for Ambulance

• Primary Repeat Caller Repository Recipient NHS 111 CDA Document
• Nullify NHS 111 CDA Document

The NHS 111 Send trigger event indicates that a NHS 111 CDA document is ready to send from the originating system.

For the NHS 111 CDA Document to be nullified the trigger event is the realisation that the NHS 111 CDA Document was sent in error, in that it contained an error and should never have been sent and that no correct NHS 111 CDA Document is available to send.

The NHS 111 Ambulance Request trigger event indicates that an ambulance request or an update to an existing ambulance reuest is sent.

The NHS 111 Repeat Caller Query trigger event indicates that a query of the repeat caller system is triggered.

The NHS 111 Repeat Caller Response trigger event indicates that a response from the repeat caller system is triggered.

The NHS 111 Repeat Caller Identified trigger event indicates that a caller has been identified as a repeat caller.

Communicates NHS 111 Report to a General Practitioner recipient where the recipient is recommended to act upon information carried in the document.

Note: This interaction has a message format that is constrained using HSCIC templates. This format is validated using a two level process. There are two sets of schema one for each level. The sender of this interaction must build all instances to the "on the wire" format using the generic CDA definition indicated in the wire format below. These instances must also conform to the rules stated in the conformance definition indicated in the conformance format below. The second level of validation requires transformation before schema validation can take place. For full details of this validation process please see the "Technical Guidance for Templated CDA Domains" section under the associated specifications tab.

• Wire Format: NHS CDA RMIM (POCD_MT000002UK01)
• Conformance Format: NHS111 Report (POCD_MT200001GB02)

Communicates an NHS 111 Report to a Emergency Department recipient where the recipient is recommended to act upon information carried in the document.

Note: This interaction has a message format that is constrained using HSCIC templates. This format is validated using a two level process. There are two sets of schema one for each level. The sender of this interaction must build all instances to the "on the wire" format using the generic CDA definition indicated in the wire format below. These instances must also conform to the rules stated in the conformance definition indicated in the conformance format below. The second level of validation requires transformation before schema validation can take place. For full details of this validation process please see the "Technical Guidance for Templated CDA Domains" section under the associated specifications tab.

• Wire Format: NHS CDA RMIM (POCD_MT000002UK01)
• Conformance Format: NHS111 Report (POCD_MT200001GB02)

Communicates NHS 111 Report to a Out of Hour recipient where the recipient is recommended to act upon information carried in the document.

Note: This interaction has a message format that is constrained using HSCIC templates. This format is validated using a two level process. There are two sets of schema one for each level. The sender of this interaction must build all instances to the "on the wire" format using the generic CDA definition indicated in the wire format below. These instances must also conform to the rules stated in the conformance definition indicated in the conformance format below. The second level of validation requires transformation before schema validation can take place. For full details of this validation process please see the "Technical Guidance for Templated CDA Domains" section under the associated specifications tab.

• Wire Format: NHS CDA RMIM (POCD_MT000002UK01)
• Conformance Format: NHS111 Report (POCD_MT200001GB02)

Communicates NHS 111 Report to a Repeat Caller Repository recipient where the recipient is recommended to act upon information carried in the document.

Note: This interaction has a message format that is constrained using HSCIC templates. This format is validated using a two level process. There are two sets of schema one for each level. The sender of this interaction must build all instances to the "on the wire" format using the generic CDA definition indicated in the wire format below. These instances must also conform to the rules stated in the conformance definition indicated in the conformance format below. The second level of validation requires transformation before schema validation can take place. For full details of this validation process please see the "Technical Guidance for Templated CDA Domains" section under the associated specifications tab.

• Wire Format: NHS CDA RMIM (POCD_MT000002UK01)
• Conformance Format: NHS111 Report (POCD_MT200001GB02)

Communicates NHS 111 Report to a copy recipient where the document is for information only and NO system action is defined.

Note: This interaction has a message format that is constrained using HSCIC templates. This format is validated using a two level process. There are two sets of schema one for each level. The sender of this interaction must build all instances to the "on the wire" format using the generic CDA definition indicated in the wire format below. These instances must also conform to the rules stated in the conformance definition indicated in the conformance format below. The second level of validation requires transformation before schema validation can take place. For full details of this validation process please see the "Technical Guidance for Templated CDA Domains" section under the associated specifications tab.

• Wire Format: NHS CDA RMIM (POCD_MT000002UK01)
• Conformance Format: NHS111 Report (POCD_MT200001GB02)

Communicates the nullification (by replacement) of any NHS 111 Report sent to any recipient.Must be sent to all information recipients (including copy recipients).

Note: This interaction has a message format that is constrained using HSCIC templates. This format is validated using a two level process. There are two sets of schema one for each level. The sender of this interaction must build all instances to the "on the wire" format using the generic CDA definition indicated in the wire format below. These instances must also conform to the rules stated in the conformance definition indicated in the conformance format below. The second level of validation requires transformation before schema validation can take place. For full details of this validation process please see the "Technical Guidance for Templated CDA Domains" section under the associated specifications tab.

• Wire Format: NHS CDA RMIM (POCD_MT000002UK01)
• Conformance Format: Nullification Document (POCD_MT130001UK05)

Communicates a NHS 111 request message to an ambulance system recipient where the recipient is recommended to act upon the request carried in the message.

• Wire Format: NHS 111 Ambulance Request (REPC_MT200001GB02)
• Conformance Format: NHS 111 Ambulance Request (REPC_MT200001GB02)

Communicates a NHS 111 repeat caller query to an repeat caller system recipient where the recipient is recommended to act upon request carried in the message. Recipient of the query message responds with the response message synchronously back to NHS 111 system.

• Wire Format: NHS111 Repeat Caller Service Query (QUPA_MT000001GB01)
• Conformance Format: NHS111 Repeat Caller Service Query (QUPA_MT000001GB01)

The fulfiller sends a query response, which may or may not have attached documents.

• Wire Format: NHS111 Repeat Caller Service Response (PRPA_MT000001GB01)
• Conformance Format: NHS111 Repeat Caller Service Response (PRPA_MT000001GB01)

Communicates NHS 111 repeat caller document set which includes the NHS 111 Reports from repeat caller system along with the current NHS 111 Report to an Out of Hour recipient where the recipient is recommended to act upon information carried in the document set. Distribution envelope will carry multiple NHS 111 Reports as different payloads within the same envelope..

Note: Although the main message is not a CDA document, the imbedded CDA documents carried in this interaction have a message format that is constrained using HSCIC templates. This format is validated using a two level process. There are two sets of schema one for each level. The sender of this interaction must build all instances to the "on the wire" format using the generic CDA definition indicated in the wire format below. These instances must also conform to the rules stated in the conformance definition indicated in the conformance format below. The second level of validation requires transformation before schema validation can take place. For full details of this validation process please see the "Technical Guidance for Templated CDA Domains" section under the associated specifications tab.

• Wire Format: NHS111 Repeat Caller Service Response (PRPA_MT000001GB01)
• Conformance Format: NHS111 Repeat Caller Service Response (PRPA_MT000001GB01)