Ambulance
Domain Message Specification

TMS Implementation

Application RolesResponsible for sendingResponsible for receiving
Ambulance Service Patient Report Originating System (POCD_AR030001UK01)
Ambulance Service Patient Report Primary Receiving System (POCD_AR030002UK01)
Ambulance Service Patient Report Receiving System (PSIS) (POCD_AR030003UK01)
Ambulance Service Patient Report Copy Recipient (POCD_AR030004UK01)

Trigger Events

Ambulance Service Patient Report (POCD_TE030001UK01)

The Ambulance Service Patient Report trigger event indicates that an Ambulance Service Patient Report is ready to send from the originating system.

Ambulance Service Patient Report Nullify By Replacement (POCD_TE030002UK01)

For the Ambulance Service Patient Report document to be nullified the trigger event is the realisation that the Ambulance Service Patient Report document was sent in error, in that it contained an error and should never have been sent and that no correct Ambulance Service Patient Report document is available to send.

Send Application Acknowledgement (MCCI_TE010000UK01)

The sending of an application acknowledgement occurs in response to the receipt of an HL7 composite message payload.

Interactions

Ambulance Report interactions

Note - Application Acknowledgements are sent to originating systems for notification of successful or failure handling by the receiving application.



Primary Recipient Ambulance Service Patient Report (POCD_IN030001UK01)   View Interaction Schema

Communicates an Ambulance Service Patient Report to a primary 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.


Sender: Ambulance Service Patient Report Originating System (POCD_AR030001UK01)
Receiver: Ambulance Service Patient Report Primary Receiving System (POCD_AR030002UK01)
Message: Trigger Event: Ambulance Service Patient Report (POCD_TE030001UK01)
Transmission Wrapper: Send Message Payload (Version 12.0) (MCCI_MT010101UK12)
Control Act Wrapper: Trigger Event Control Act (Version 3.0) (MCAI_MT040101UK03)
PSIS Ambulance Service Patient Report (POCD_IN030002UK01)   View Interaction Schema

Communicates an Ambulance Service Patient Report to PSIS for processing and storage.

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.


Sender: Ambulance Service Patient Report Originating System (POCD_AR030001UK01)
Receiver: Ambulance Service Patient Report Receiving System (PSIS) (POCD_AR030003UK01)
Message: Trigger Event: Ambulance Service Patient Report (POCD_TE030001UK01)
Transmission Wrapper: Send Message Payload (Version 12.0) (MCCI_MT010101UK12)
Control Act Wrapper: Trigger Event Control Act (Version 3.0) (MCAI_MT040101UK03)
Copy Ambulance Service Patient Report (POCD_IN030003UK01)   View Interaction Schema

Communicates an Ambulance Service Patient 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.


Sender: Ambulance Service Patient Report Originating System (POCD_AR030001UK01)
Receiver: Ambulance Service Patient Report Copy Recipient (POCD_AR030004UK01)
Message: Trigger Event: Ambulance Service Patient Report (POCD_TE030001UK01)
Transmission Wrapper: Send Message Payload (Version 12.0) (MCCI_MT010101UK12)
Control Act Wrapper: Trigger Event Control Act (Version 3.0) (MCAI_MT040101UK03)
Nullify Ambulance Service Patient Report (POCD_IN030004UK01)   View Interaction Schema

Communicates the nullification (by replacement) of any Ambulance Service Patient 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.


Sender: Ambulance Service Patient Report Originating System (POCD_AR030001UK01)
Receiver: Ambulance Service Patient Report Primary Receiving System (POCD_AR030002UK01)
Receiver: Ambulance Service Patient Report Receiving System (PSIS) (POCD_AR030003UK01)
Receiver: Ambulance Service Patient Report Copy Recipient (POCD_AR030004UK01)
Message: Trigger Event: Ambulance Service Patient Report Nullify By Replacement (POCD_TE030002UK01)
Transmission Wrapper: Send Message Payload (Version 12.0) (MCCI_MT010101UK12)
Control Act Wrapper: Trigger Event Control Act (Version 3.0) (MCAI_MT040101UK03)
Application Acknowledgement (MCCI_IN010000UK13)  

The application acknowledgement wrapper enables a response indicating either successful receipt of the message or that the message has been received containing issues or errors.


Sender: Ambulance Service Patient Report Primary Receiving System (POCD_AR030002UK01)
Sender: Ambulance Service Patient Report Receiving System (PSIS) (POCD_AR030003UK01)
Sender: Ambulance Service Patient Report Copy Recipient (POCD_AR030004UK01)
Receiver: Ambulance Service Patient Report Originating System (POCD_AR030001UK01)
Message: Trigger Event: Send Application Acknowledgement (MCCI_TE010000UK01)
Transmission Wrapper: Send Message Payload (Version 12.0) (MCCI_MT010101UK12)
Control Act Wrapper: Trigger Event Control Act (Version 3.0) (MCAI_MT040101UK03)