My Health Record Notice of Connection (NoC) and Conformance Compliance and Declaration (CCD) testing

DG-3110

Type

Guide

Version

1.0

Status

Active

Created date

02/06/2023

Updated date

05/06/2023

This is the current version.

Overview

To integrate software products with the My Health Record system, two types of testing are required.

My Health Record Notice of Connection (NOC)

What is it?
Tests the web services interactions between your software and the My Health Record Notice system.
Who does it?
Our partner Deloitte via the Australian Digital Health Agency.
How do I start?
Refer to the My Health Record Developer Registration section on this Developer Portal and download the My Health Record Welcome Pack. The Welcome Pack contains the Vendor Product Details (VPD) form which is the entry point into My Health Record NOC testing. Fill it out and send it to [email protected]
Once you submit the VPD
Deloitte will issue you a My Health Record Test Data Pack which will include test cases and data tailored to the scope of your implementation.
Testing
Is done in two stages i) via a self-paced self-assessment and ii) a Deloitte-observed assessment stage. Deloitte will issue the Agency with a My Health Record Declaration of Notice of Connection for the specific version of the product that has been tested.

My Health Record Conformance

What is it?
Tests your software’s conformance to My Health Record Conformance Profiles for connecting systems, clinical documents, rendering, authoring, packaging etc.
Who does it?
The software vendor who is developing the integration.
How do I start?
You can use the Agency’s Conformance Test Specifications published on this Developer Portal or create your own tests based off the requirements in the Conformance Profiles. If you are developing the ability to upload clinical documents, we recommend you also use our Clinical Package Validator tool.
Testing
Once the software vendor has undertaken their own testing, an My Health Record Conformance Vendor Declaration must be completed which declares that the software conforms to the mandatory requirements. This is a legal which also outlines the software organisation’s compliance obligations once the software is connected to the My Health Record System.

Resources: Test Specifications and Test Data

Conformance Test Specifications have been developed to support self-assessment. These will vary according to your specific development scope. We have listed some key ones below:

Clinical Package Validator (inc. Template Package Libraries and IQ Rules)

The Clinical Package Validator (CPV) is a tool which automates some of the conformance requirements of clinical documents and clinical packages. It is important to note that the CPV does not test conformance against all specifications and the Product Data Sheet that comes with the tool lists the tests that are supported, partially supported, and a general description of the types of tests not supported.

The Information Quality Rules (IQ Rules) are an extra layer of conformance tests which should be used in tandem with the CPV to further help developers, testers and analysts determine the conformance of clinical documents. For more information on CPV visit here.

Re-testing

If your software product changes in a way that affects My Health Record system functionality or interaction, such as:

The development of new functionality pertaining to My Health Record (e.g. a new web service, authoring of a new clinical document type)
Upgrading conformance to a newer version of our specifications; or,
Development in response to an identified software error.

It may be necessary to repeat some of the NOC and Conformance testing with and an incremented version number for the software.

In these cases, the software version in the SOAP header must be updated, and the software product version declared in a new Conformance Vendor Declaration. More information is contained in Managing Your B2B Software in Production.