Go to top of page

My Health Record SVT System - Notifications

My Health Record Software Vendor Test (SVT) Environment – Planned Maintenance - The My Health Record System Operator advises there will be planned maintenance to the My Health Record system Software Vendor Test (SVT) environment on Friday 11 September 2020 from 6:00PM – 9:00PM (AEST). 

Wednesday, 9 September 2020

PCEHR Architecture v1.35

EP-1001:2011

The high level system architecture describes the fundamental organisation of the My Health Record system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.

Thursday, 10 Nov 2011

Mobile integration with My Health Record

The Australian Digital Health Agency aims to increase adoption of the My Health Record by connecting the My Health Record platform to mobile applications through industry standard APIs. 

Included below is key information about getting started and key forms required to connect to My Health Record Mobile Gateway. Learn more....

My Health Record – B2B Gateway

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 

Sample Code for connecting to the My Health Record system’s B2B Gateway

The Australian Digital Health Agency provides sample code to assist software development and integration with the Healthcare Identifiers Service and the My Health Record system. Most sample code is available in .NET and Java. To see the full list, please visit the eHealth Reference Platform section on the Australian Digital Health Agency website or GitHub. Read more....

FHIR Gateway (Mobile)

The Australian Digital Health Agency aims to increase adoption of the My Health Record by individuals as well as healthcare professionals by connecting the My Health Record platform to mobile healthcare applications (apps) via industry standard Application Programming Interfaces (APIs).

National Consumer Portal

The National Consumer Portal (NCP) is the front-end for participating individuals to access My Health Record via desktop or mobile devices.

Consumer functions

Access to:

Consumer Provided Information

Consumer provided information is a way for consumers to capture information about their health which they believe will assist when dealing with health care.

Context in digital health

HIPS - Health Identifier and PCEHR System

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.

National Authentication Service for Health (NASH)

The National Authentication Service for Health (NASH) makes it possible for healthcare providers and supporting organisations to securely access and exchange health information.

National Authentication Service for Health in the Australian context

My Health Record Integration Toolkit

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.

Clinical Documents Integration Toolkit

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 Portal Operator Registration Form (PORF) Instructions

This form is for mobile app developers to enable you to:

  • apply to the System Operator of the My Health Record system to have your organisation registered as a registered portal operator under the My Health Records Act 2012 (Cth); and
  • request access to the My Health Record Test Environment for your proposed application (app).

For further information about connecting with the My Health Record system, please refer to the App Vendor Guide to the Connection Process, which is distributed as part of the Welcome Pack for developers using the FHIR®[1] Gateway of the My Health Record system.

CIS to NPP v1.0

EP-2876:2019

This product assists software vendors with implementing the Clinical Information System to National Provider Portal (CIS to NPP) interface implementation.

Friday, 22 Nov 2019

Medicines View Optimisation

The Medicines View Optimisation aims to reduce duplication by enhancing the interoperability between PBS - and AMT- coded items as well as enhancing existing grouping and ‘Differs Advisory’ logic. 

Tuesday, 10 December 2019

Specialists Software Industry Offer - Webinar FAQs

Can we search for a HPI-I using a doctor's provider or prescriber number? 
No, To retrieve a providers HPI-I you will require the following,

1. Clinician demographics (name, sex, dob)

2a. Identifier (AHPRA number, HPI-I)

...

My Health Record Initial Registration

Please follow these steps to register your software product with the My Health Record system vendor (SVT) test environment. This is applicable for new products connections or conformant software enhancements.

My Health Record Usability Guidelines

It is recommended that the following usability guidelines, referenced in the My Health Record Usability Recommendations on the Agency website, be considered

My Health Record Views

There is a requirement that authorised users of the diagnostics services (pathology or DI) system have the capability to view patient information in the My Health Record system.

My Health Record Detailed Functionality

To enable the uploading of clinical documents and the viewing of a patient's My Health Record, the following functionality and supporting material is recommended.

Integrating Diagnostic Imaging Software with My Health Record

High Level Scope

The software will enable the upload of pathology or diagnostic imaging reports to the My Health Record system, and the viewing of the My Health Record system by authorised representatives of the diagnostic services organisations. This means that the software should:

  • Integrate to the HI Service for the purpose of sourcing and validating healthcare identifiers;
  • Support the use of NASH digital credentials for the purpose of authentication to the My Health Record system;

...

HI scope and use cases

Healthcare Identifiers licensed materials and software requirements for the use of healthcare identifiers

Updated Integration Toolkits Released

The Australian Digital Health Agency (“the Agency”) has released new and updated versions of the following Integration Toolkits. In addition, the Agency has announced it will use GitHub to enhance collaboration and sharing with developers. 

Monday, 25 June 2018

My Health Record Integration Toolkit v1.2.2

EP-2603:2018

The My Health Record Integration Toolkit contains libraries for B2B connectivity to the My Health Record system, providing sample code for all operations, as well as the schemas used and sample SOAP request and response messages.

Tuesday, 24 Apr 2018

PCEHR Template Service v1.3

EP-1514:2012

The Template Service is essential for ensuring semantic interoperability between interconnected clinical information systems in the Australian health sector.

Thursday, 06 Sep 2012

National Authentication Service for Health v1.0

EP-1011:2012

The National Authentication Service for Health (NASH) makes it possible for healthcare providers and supporting organisations to securely access and exchange health information.

NASH provides Public Key Infrastructure (PKI) Certificates that help you or your organisation to:

Friday, 30 Mar 2012