#### Child Screening
Domain Message Specification

### ITK Implementation

Application Roles | Responsible for sending | Responsible for receiving
--- | --- | ---
Child Screening Report Originating System (POCD_AR010001GB01) | Primary Recipient Child Screening Report Copy Recipient Child Screening Report Nullify Child Screening Report |
Child Screening Report Primary Receiving System (POCD_AR010002GB01) |  | Primary Recipient Child Screening Report Nullify Child Screening Report
Child Screening Report Copy Recipient (POCD_AR010003GB01) |  | Copy Recipient Child Screening Report Nullify Child Screening Report

#### Trigger Events

Child Screening Report Send (POCD_TE010001GB01) The Child Screening Report Send trigger event indicates that a Child Screening Report document is ready to send from the originating system.
Child Screening Report Nullify By Replacement (POCD_TE010002GB01) For the Child Screening Report to be nullified the trigger event is the realisation that the Child Screening Report was sent in error, in that it contained an error and should never have been sent and that no correct Child Screening Report is available to send.

#### Interactions

#### Child Screening Report interactions

Note : A Business Acknowledgement is only returned on receipt of a message where the received Distribution Envelope has a handlingSpecification with a key of “urn:nhs-itk:ns:201005:ackrequested” and a value of “true”.

Primary Recipient Child Screening Report (urn:nhs-itk:interaction:primaryRecipientChildScreeningReport-v1-0) Communicates a Child Screening 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: Child Screening Report Originating System (POCD_AR010001GB01) Receiver: Child Screening Report Primary Receiving System (POCD_AR010002GB01) Message: Wire Format: NHS CDA RMIM (POCD_MT000002UK01) Conformance Format: Child Screening (POCD_MT010000GB01) Trigger Event: Child Screening Report Send (POCD_TE010001GB01) Transmission Wrapper: ITK Distribution Envelope (Version 2.0) (distributionEnvelope-v2-0) Web Service Wrapper: SendCDADocument-v2-0 CoreServices-v1-0.wsdl
Copy Recipient Child Screening Report (urn:nhs-itk:interaction:copyRecipientChildScreeningReport-v1-0) Communicates a Child Screening 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: Child Screening Report Originating System (POCD_AR010001GB01) Receiver: Child Screening Report Copy Recipient (POCD_AR010003GB01) Message: Wire Format: NHS CDA RMIM (POCD_MT000002UK01) Conformance Format: Child Screening (POCD_MT010000GB01) Trigger Event: Child Screening Report Send (POCD_TE010001GB01) Transmission Wrapper: ITK Distribution Envelope (Version 2.0) (distributionEnvelope-v2-0) Web Service Wrapper: SendCDADocument-v2-0 CoreServices-v1-0.wsdl
Nullify Child Screening Report (urn:nhs-itk:interaction:nullifyChildScreeningReport-v1-0) Communicates the nullification (by replacement) of any Child Screening 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: Child Screening Report Originating System (POCD_AR010001GB01) Receiver: Child Screening Report Primary Receiving System (POCD_AR010002GB01) Receiver: Child Screening Report Copy Recipient (POCD_AR010003GB01) Message: Wire Format: NHS CDA RMIM (POCD_MT000002UK01) Conformance Format: Nullification Document (POCD_MT130001UK05) Trigger Event: Child Screening Report Nullify By Replacement (POCD_TE010002GB01) Transmission Wrapper: ITK Distribution Envelope (Version 2.0) (distributionEnvelope-v2-0) Web Service Wrapper: SendCDADocument-v2-0 CoreServices-v1-0.wsdl