Reading: 15 minutes
Registration: 30 minutes
Learning objectives: In this guide, you'll learn, Introduction to CIS to NPP service, CIS to NPP Limitations, Register for CIS-to-NPP implementation, Testing, Vendor conformance process and Go Live requirements
In this tutorial, you will;
- Understand high level concepts regarding My Health Record, NPP and CIS to NPP
- The limitations of CIS to NPP
- Register for CIS to NPP
- Understand the testing and conformance process
In the next CIS to NPP tutorial we will provide step-by-step directions to build the CIS to NPP functionality.
High level concepts
My Health Record is a secure online summary of an individual’s health information and is available to all Australians. Healthcare providers authorised by their healthcare organisation can access My Health Record to view and add patient health information.
The My Health Record National Provider Portal (NPP) is a portal which can be accessed by healthcare providers using a browser to view their patients’ My Health Records. A healthcare provider might use the NPP if they do not use a Clinical Information System (CIS) that has integrated My Health Record functionality.
If your organisation develops software for healthcare providers and you wish to integrate My Health Record viewing capability with minimal initial and ongoing development, then the CIS to NPP mechanism may be right for you. The CIS to NPP functionality embeds the NPP within a Browser Control (or similar element) within your software. You will be able to use patient information from your software to search their My Health Record, simplifying access for users. The NPP is a web-based portal which will provide ongoing updates to My Health Record viewing functionality and experience over time. There are several current limitations to the NPP to consider before opting for NPP access over B2B integration with My Health Record.
You are able to connect your software via both B2B and CIS to NPP, allowing the advanced upload functionality and atomic data integration which B2B has to offer, while providing the viewing capability of the NPP via CIS to NPP.
CIS to NPP limitations
If your customers will be using the NPP via a browser or via your software’s CIS to NPP interface;
- They will only have read access to the My Health Record system
- They will need to have their HPI-I linked to an organisation’s HPI-O. This step is conducted by the organisation using Services Australia - Health Professional Online Services (HPOS).
If you are seeking the advanced features of the My Health Record system such as uploading clinical content and retrieving atomic clinical data, you must integrate with the My Health Record Business to Business (B2B) interface, which provides the full capabilities of the My Health Record system.
The Healthcare Identifiers Service (HI Service) is not required for clinical software connecting to My Health Record using the CIS to NPP Service. Find out more about the HI Service.
Register for CIS to NPP
Before you can begin development, you are required to register for access to the My Health Record system. This process will provide you with the artefacts you require to begin development such as digital test certificates and test data (patients and providers).
1. Download the Welcome pack and read the document Software Vendor Guide to the Connection Process.
2. Fill in and return the Vendor Product Details Form, found in the Welcome Pack and return to Developer Support at Services Australia ([email protected]).
This form contains questions about connectivity related to all services provided by the My Health System. Please choose the options which related specifically to CIS to NPP.
When emailing Developer Support you will also be able to conduct the following steps;
- Apply for a NASH PKI Test Kit (which contains certificates and test data) by requesting the form Application to request a National Authentication Service for Health Public Key Infrastructure Test Certificate kit.
- Ask to have your test data provider’s HPI-I linked to your test organisation’s HPI-O.
3. You will receive NASH digital certificates in the NASH PKI Test Kit. You will also be provided with test data and Notice of Connection (NOC) test cases.
Once you have completed your development (see our next guide) there are two types of testing which must be undertaken. These are:
Conformance, Compliance and Declaration (CCD)
The CCD process requires that your software conforms to all applicable conformance profiles, the specifications they reference, and the conformance requirements for My Health Record Connecting Systems (Specifications), prior to your software being granted connection to the My Health Record system. Please find the conformance test specifications inside the CIS to NPP v1.0 folder download from this website. We will walk through some sample test cases in the next developer guide.
Notice of Connection (NOC) testing
NOC testing confirms that your software product performs according to the specified standards and conformance points defined in the technical and logical service specification documents. Once you have submitted the Software Vendor Product Details Form to Developer Support, NIO will send you a test plan, which includes the services nominated for use during the NOC process. NIO will observe NOC testing and when completed successfully, they will issue you with a My Health Record Notice of Connection for the specific version of your product that has been tested.
When you are ready to begin testing, please follow the steps below;
1. Contact [email protected] and request to be booked in to perform your observed NOC testing.
2. Complete a Conformance Vendor Declaration Form (available in the Welcome Pack) and email it to [email protected]
You should now have an understanding of the My Health Record system, the NPP, and CIS to NPP. You will have registered to connect to the Software Vendor Test (SVT) Environment and have your certificates and test data. You will now also understand your testing obligations. Continue onto our next guide to begin development.
View All | My Health Record CIS to NPP - Complete Implementation - Developer Guide