Skip to Content
Home

Developer Centre

  • Log in
  • Register
  • Products
  • What's happening
  • Feedback
  • Register
  • Home
  • Developer Resources

Developer Resources

Go to top of page
  • Featured
  • Developer guides
  • Products
  • Specifications
  • News

Featured content

My Health Record CIS to NPP - Complete Implementation - Developer Guide

Developer Guides

Reading & Development: 2 hours

My Health Record CIS to NPP - Introduction

Developer Guides

Reading:       15 minutes
Register:       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

Introduction to the Healthcare Identifier Service

Developer Guides, Products

In this guide, you will; Understand high level concepts regarding the HI Service, Register as a developer for the HI Service, Request Test Certificates and Test Environment Data, Install the Test Certificates locally and Import Certificates in CIS Software

Introduction - My Health Record - B2B Developer Guides

Developer Guides

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.

Information Quality Rules v1.6

Products, Specifications, Toolkits | EP-2895:2019

The Information Quality Rules (IQ Rules) is a tool that helps developers, testers and analysts determine the quality of clinical documents including the conformance of clinical documents to the My Health Record system conformance requirements.

Login to download

HIPS - Health Identifier and PCEHR System

Products, Sample Code, Specifications, Toolkits

The Health Identifier and PCEHR System (HIPS) is an interface service designed originally for health systems, particularly within hospitals. Different healthcare systems can be connected to share data using HIPS to pass information back and forth.

Healthcare Identifiers Integration Toolkit

Products, Sample Code, Specifications, Toolkits

The eHealth integration toolkits are a collection of integration tools and sample code resources available in both .NET and Java. The sample code and integration tools are used within the eHealth Reference Platform, forming part of the code library for tools and simulators.

My Health Record Integration Toolkit

Products, Sample Code, Specifications, Toolkits

The My Health Record integration toolkit contains libraries for business-to-business (B2B) connectivity to the My Health Record system. The toolkit provides sample code for all operations, schemas used and sample SOAP request and response messages.

Secure Messaging Integration Toolkit

Products, Sample Code, Specifications, Toolkits

The eHealth integration toolkits are a collection of integration tools and sample code resources available in both .NET and Java. The sample code and integration tools are used within the eHealth reference platform, forming part of the code library for tools and simulators.

Clinical Documents Integration Toolkit

Products, Sample Code, Specifications, Toolkits

The eHealth integration toolkits are a collection of integration tools and sample code resources available in both .NET and Java. The sample code and integration tools are used within the eHealth Reference Platform, forming part of the code library for tools and simulators.

Clinical Package Validator

Products, Sample Code, Specifications, Toolkits

The Clinical Package Validator is a tool to automate some of the tests needed to assess conformance of clinical documents and clinical packages with the eHealth Specifications.

Developer Guides

My Health Record CIS to NPP - Complete Implementation - Developer Guide

Developer Guides

Reading & Development: 2 hours

My Health Record CIS to NPP - Introduction

Developer Guides

Reading:       15 minutes
Register:       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

Introduction to the Healthcare Identifier Service

Developer Guides, Products

In this guide, you will; Understand high level concepts regarding the HI Service, Register as a developer for the HI Service, Request Test Certificates and Test Environment Data, Install the Test Certificates locally and Import Certificates in CIS Software

Introduction - My Health Record - B2B Developer Guides

Developer Guides

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.

Additional requirements for Electronic Prescribing - HI Service Developer Guide 4

Developer Guides

If you are connecting to the HI Service for the purpose of implementing Electronic Prescriptions, some of the existing HI Service test cases will now be mandatory instead of recommended.

Gain access to a My Health Record - My Health Record B2B Developer Guide 2

Developer Guides

This guide walks through the steps to access a patient’s My Health Record using the GainPCEHRAccess web service. When gaining access to a patient’s My Health Record, it is important to understand Access Codes and Emergency Access.

Find whether a My Health Record exists - My Health Record B2B Developer Guide 1

Developer Guides

This developer guide helps you to verify whether a My Health Record exists for a patient using their Individual Healthcare Identifier (IHI). If you have not already done so, you should follow our HI Service Developer Guides.

Remove Document - My Health Record B2B Developer Guide 7

Developer Guides

This guide will describe the steps to remove a Clinical Document. If your software product uploads Clinical Documents then you must have the option for your users to remove Clinical Documents that they have uploaded.

Supersede document - My Health Record B2B Developer Guide 6

Developer Guides

This guide describes the steps to supersede a Clinical Document in the My Health Record system. The ability to supersede a document is a requirement of uploading (unless your software only uploads Shared Health Summaries).

Upload Document - My Health Record B2B Developer Guide 5

Developer Guides

This guide will walk through the steps to create and upload clinical documents. The following steps are involved in this process.

Get Views - My Health Record B2B Developer Guide 4

Developer Guides

This guide will use the My Health Record getView web service to download collated information from a My Health Record in a ‘View’. A view is simply a representation of data from a My Health Record which has been collated from multiple clinical documents.

Get Patient Document List and View Document - My Health Record B2B Developer Guide 3

Developer Guides

This guide will walk through the process to get patient clinical documents from the My Health Record system and display them to your users using a generic style sheet. To retrieve documents you must already have conducted a GainPCEHRAccess call as conducted in the previous guide.

IHI Lookup - Test Cases - HI Service Developer Guide 2

Developer Guides

After successfully executing the IHI Lookup, it is important to modify your implementation to meet the Test Cases for the Use Cases we have built to. Continued from: IHI Lookup - HI Service Developer Guide 1

Search for HPI-I - HI Service Developer Guide 3

Developer Guides

It is highly recommended that your software conduct HPI-I searches for users of your system. The primary reason for this is that most healthcare provider individuals do not know their HPI-I number however their AHPRA number is often known.

IHI Lookup - HI Service Developer Guide 1

Developer Guides

Your software will need to conduct lookups for Individual Healthcare Identifiers (IHIs) for patients. This is conducted when registering a new patient, updating a patient in your local system, and in some other specific circumstances. This can be done in batch, or individually. Our example will focus on looking up a patient IHI individually.

Products

My Health Record – B2B Gateway

Products, Sample Code, Specifications, Toolkits

The Business-to-Business (B2B) Gateway services allow a range of systems to access the My Health Record system, such as clinical systems, systems integrated via a gateway, and contracted service providers acting on behalf of healthcare organisations.

Audience 

HIPS - Health Identifier and PCEHR System

Products, Sample Code, Specifications, Toolkits

The Health Identifier and PCEHR System (HIPS) is an interface service designed originally for health systems, particularly within hospitals. Different healthcare systems can be connected to share data using HIPS to pass information back and forth.

Healthcare Identifiers Integration Toolkit

Products, Sample Code, Specifications, Toolkits

The eHealth integration toolkits are a collection of integration tools and sample code resources available in both .NET and Java. The sample code and integration tools are used within the eHealth Reference Platform, forming part of the code library for tools and simulators.

My Health Record Integration Toolkit

Products, Sample Code, Specifications, Toolkits

The My Health Record integration toolkit contains libraries for business-to-business (B2B) connectivity to the My Health Record system. The toolkit provides sample code for all operations, schemas used and sample SOAP request and response messages.

Secure Messaging Integration Toolkit

Products, Sample Code, Specifications, Toolkits

The eHealth integration toolkits are a collection of integration tools and sample code resources available in both .NET and Java. The sample code and integration tools are used within the eHealth reference platform, forming part of the code library for tools and simulators.

Clinical Documents Integration Toolkit

Products, Sample Code, Specifications, Toolkits

The eHealth integration toolkits are a collection of integration tools and sample code resources available in both .NET and Java. The sample code and integration tools are used within the eHealth Reference Platform, forming part of the code library for tools and simulators.

Clinical Package Validator

Products, Sample Code, Specifications, Toolkits

The Clinical Package Validator is a tool to automate some of the tests needed to assess conformance of clinical documents and clinical packages with the eHealth Specifications.

Specifications

Clinical Documents Integration Toolkit v1.8

Products, Sample Code, Specifications, Toolkits | EP-2912:2020
The Clinical Documents Integration Toolkit contains libraries for the creation, packaging and presentation of clinical documents through the use of style sheets.
Login to download

Information Quality Rules v1.6

Products, Specifications, Toolkits | EP-2895:2019

The Information Quality Rules (IQ Rules) is a tool that helps developers, testers and analysts determine the quality of clinical documents including the conformance of clinical documents to the My Health Record system conformance requirements.

Login to download

Clinical Package Validator v3.2

Specifications | EP-3408:2020
The Clinical Package Validator (Validator) provides software developers with enhanced capabilities to achieve a greater degree of automation and depth of their conformance tests of clinical documents.
Login to download

Digital Health Icon Library v1.0

Specifications | EP-2704:2018
The Icon Library is available as a resource for developers and implementers of digital health solutions and other interested parties.
Login to download

My Health Record Integration Toolkit v1.2.2

Specifications, Toolkits | EP-2603:2018
The My Health Record Integration Toolkit contains sample code for B2B connectivity to the My Health Record system.
Login to download

Secure Messaging Integration Toolkit v1.2.5

Specifications, Toolkits | EP-2730:2018
The Secure Messaging Integration Toolkit contains libraries for B2B connectivity to Secure Message Delivery (SMD) and Endpoint Location Services (ELS), providing sample code for all operations, as well as a Medical Document Management (MDM) library to create the payload for SMD.
Login to download

Healthcare Identifiers Integration Toolkit v1.2

Specifications, Toolkits | EP-2610:2018
The Healthcare Identifiers Integration Toolkit contains libraries for B2B connectivity to the Healthcare Identifiers service, used to search for IHI, HPI-Is and HPI-Os.
Login to download

News

Clinical Documents Integration Toolkit v1.8 and Health Record Overview v1.2 released

News

The Agency has released updates for the following products Clinical Documents Integration Toolkit v1.8 and Health Record Overview v1.2

Friday, 28 August 2020

By operation of the Public Governance, Performance and Accountability (Establishing the Australian Digital Health Agency) Rule 2016, on 1 July 2016, all the assets and liabilities of NEHTA will vest in the Australian Digital Health Agency. In this website, on and from 1 July 2016, all references to "National E-Health Transition Authority" or "NEHTA" will be deemed to be references to the Australian Digital Health Agency. PCEHR means the My Health Record, formerly the "Personally Controlled Electronic Health Record", within the meaning of the My Health Records Act 2012 (Cth), formerly called the Personally Controlled Electronic Health Records Act 2012 (Cth).

Stay Connected

with the Australian Digital Health Agency

Register to download resources and keep informed of the latest Developer News.

Register

Resources

  • My Health Record
  • Electronic Prescribing
  • Secure Messaging
  • Healthcare Identifiers
  • Clinical Terminology
  • View all

Help Centre

  • 1300 901 001
  • [email protected]
  • System Status
  • Terms of Use
  • Privacy

Connect

Help us improve

We are always looking for ways to improve Digital Health

Provide feedback

Australian Digital Health Agency logo of the Australian Digital Health Agency

Copyright © 2011-2021 Australian Digital Health Agency and third parties.

This website has been designed to be as accessible as possible. We are continually updating it to meet Web Content Accessibility Guidelines (WCAG) 2.0 Level AA.

If you have any problems using this site, or a document you need is not in a format you can access, email us or call us.

Back to Top