Ambulance
Domain Message Specification

ITK 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 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.

Interactions

Ambulance Report 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”



Primary Recipient Ambulance Service Patient Report (urn:nhs-itk:interaction:primaryRecipientAmbulanceServicePatientReport-v1-0)  

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: ITK Distribution Envelope (Version 2.0) (distributionEnvelope-v2-0)
Web Service Wrapper: SendCDADocument-v2-0 CoreServices-v1-0.wsdl
Copy Ambulance Service Patient Report: (urn:nhs-itk:interaction:copyRecipientAmbulanceServicePatientReport-v1-0)  

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: ITK Distribution Envelope (Version 2.0) (distributionEnvelope-v2-0)
Web Service Wrapper: SendCDADocument-v2-0 CoreServices-v1-0.wsdl
Nullify Ambulance Service Patient Report (urn:nhs-itk:interaction:nullifyAmbulanceServicePatientReport-v1-0)  

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 Copy Recipient (POCD_AR030004UK01)
Message: Trigger Event: Ambulance Service Patient Report Nullify By Replacement (POCD_TE030002UK01)
Transmission Wrapper: ITK Distribution Envelope (Version 2.0) (distributionEnvelope-v2-0)
Web Service Wrapper: SendCDADocument-v2-0 CoreServices-v1-0.wsdl