CDR0007 Consultation on Clarification of Self Testing Requirements
Status
Outcome
This DIP CR will be classified as a Tier Two change. We will consult to ensure potential DIP users are aware of the functionality available through PIT guidance. The DIP Manager will make the final determination on this change request afterward.
On 8 August 2025, DIP Change Request (CR) 0003 ‘DIP On-boarding and requirements clarification’ was implemented. DCR0003 clarified some of the non-functional requirements in DSD002, Annex 1 DIP On-Boarding and Non-Functional Checks, a Potential DIP User would have to demonstrate before on-boarding to the DIP. To do this, a Potential DIP User could demonstrate the requirement either via:
- Self-testing, which would be demonstrate to the DIP Manager in a manner it prescribed; or
- DIP Manager testing, which would involve the DIP Manager undertaking testing on a Potential DIP User’s system to determine whether it meets specific requirements.
One of the on-boarding non-functional requirements the DIP Manager (DSD002, Annex 1, 1.3), as part of DIP Manager testing, assesses is:
| DSD002 Annex 2 Reference | Category | Sub-Category | Title | Requirement Description |
| 9.1.1 | Compatibility | Interoperability | Messaging Interfaces | All services shall send and receive messages for all DIP Interfaces and publications via the API definitions in the DIP Open API Definitions (known as DIP Swagger) |
The self-testing requirements should be amended to reflect where the Potential DIP User would undertake specific testing. It is an issue that requirements are not aligned between different documents that are used and relied on by the Potential DIP User to understand what they should do to be able to onboard onto the DIP.
Original consultation
Who will this impact?
Amending DSD002, Annex 1, impacts Potential DIP Users and the DIP Manager. The requirement for Potential DIP Users to send and receive all messages for DIP interfaces is part of their testing requirements and system development. Changing this requirement during PIT could pose a risk if systems lack this functionality. However, the MHHS PIT Guidance Document confirms this as a system requirement, and the DIP Manager will test this under ‘MHHS Non-SIT Supplier & Agent Qualification Testing’.
The DIP Manager will shift focus from testing message functionality to assessing compliance with DIP Rules through PIT and evidence assurance. This may reduce assurance levels for the DIP Manager regarding Potential DIP Users’ capabilities. Nevertheless, the risk that users will not adhere to PIT Guidance remains low, and the DIP Manager can still request demonstrations of compliance. Therefore, amending DSD002, Annex 1, is unlikely to weaken the assurance provided by testing
What is proposed?
To resolve this issue, the requirement set out in DSD002, Annex 2, 9.1.1 should be included within Self Testing in DSD002, Annex 1, and removed from DIP Manager testing. It will, therefore, ensure Potential DIP Users are aware of the requirement they must fulfil when on boarding to the DIP.