Non-Coded CDA Document
Domain Message Specification

Version: 1.1; Status: Final

ITK Implementation

Application RolesResponsible for sendingResponsible for receiving
Non-Coded CDA Document Originating System (POCD_AR000001GB01)
Non-Coded CDA Document Primary Receiving System (POCD_AR000002GB01)
Non-Coded CDA Document Copy Recipient (POCD_AR000003GB01)

Trigger Events

Non-Coded CDA Document (POCD_TE000001GB01)

The Non-Coded CDA Document trigger event indicates that a Non-Coded CDA Document is ready to send from the originating system.

Non-Coded CDA Document Nullify By Replacement (POCD_TE000002GB01)

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

Interactions

Non Coded CDA Document 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 “true” or “false” (if “true”, this applies to Primary Recipients only)



Primary Recipient Non-Coded CDA Document (urn:nhs-itk:interaction:primaryRecipientNonCodedCDADocument-v1-0)  

Communicates a Non-Coded CDA Document 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: Non-Coded CDA Document Originating System (POCD_AR000001GB01)
Receiver: Non-Coded CDA Document Primary Receiving System (POCD_AR000002GB01)
Message: Trigger Event: Non-Coded CDA Document (POCD_TE000001GB01)
Transmission Wrapper: ITK Distribution Envelope (Version 2.0) (distributionEnvelope-v2-0)
Web Service Wrapper: SendCDADocument-v2-0 CoreServices-v1-0.wsdl
Copy Non-Coded CDA Document: (urn:nhs-itk:interaction:copyRecipientNonCodedCDADocument-v1-0)  

Communicates a Non-Coded CDA Document 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: Non-Coded CDA Document Originating System (POCD_AR000001GB01)
Receiver: Non-Coded CDA Document Copy Recipient (POCD_AR000003GB01)
Message: Trigger Event: Non-Coded CDA Document (POCD_TE000001GB01)
Transmission Wrapper: ITK Distribution Envelope (Version 2.0) (distributionEnvelope-v2-0)
Web Service Wrapper: SendCDADocument-v2-0 CoreServices-v1-0.wsdl
Nullify Non-Coded CDA Document (urn:nhs-itk:interaction:nullifyNonCodedCDADocument-v1-0)  

Communicates the nullification (by replacement) of any Non-Coded CDA Document 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: Non-Coded CDA Document Originating System (POCD_AR000001GB01)
Receiver: Non-Coded CDA Document Primary Receiving System (POCD_AR000002GB01)
Receiver: Non-Coded CDA Document Copy Recipient (POCD_AR000003GB01)
Message: Trigger Event: Non-Coded CDA Document Nullify By Replacement (POCD_TE000002GB01)
Transmission Wrapper: ITK Distribution Envelope (Version 2.0) (distributionEnvelope-v2-0)
Web Service Wrapper: SendCDADocument-v2-0 CoreServices-v1-0.wsdl