The Australian Digital Health Agency has updated the following specifications. My Health Record B2B Gateway Services v2.0 & My Health Record Overviews, Guides and Conformance Material v1.5.
Overviews, guides and conformance material relating to the My Health Record system.
The My Health Record SVT environment allows software vendors to build and test the B2B Gateway web services for interactions with the My Health Record system.
The My Health Record Software Vendor Welcome Pack is a collection of forms and guides to help new software vendors connect to the My Health Record system for the first time. Some of these documents are also used by existing software vendors to connect their updated software to the My Health Record system.
The high level system architecture is a critical deliverable for the My Health Record system and 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.
Click on the link below to download the latest version of Managing Your B2B Software in Production.
The My Health Record Integration Toolkit contains sample code for B2B connectivity to the My Health Record system.
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.
The Clinical Documents Integration Toolkit contains libraries for the creation, packaging and presentation of clinical documents through the use of style sheets.
On this page you will find the latest version of the document, My Health Record Managing your B2B software in production.
The Goals of Care clinical document type is used to capture advance care information in alignment with Western Australia’s Goals of Patient Care Summary documents.
Advance care planning enables individuals to make choices about their future medical treatment in the event that they are cognitively impaired or otherwise unable to make their preferences known.
Advance care documents let individuals make choices about their future medical treatment in the event that they are cognitively impaired or otherwise unable to make their preferences known.
Services Australia advice: ANZAC Day Public Holiday - OTS and Developer Support availability - Services Australia advises that there will be a change in the availability of the Developer Support and Online Technical Support (OTS) teams on the upcoming ANZAC Day Public Holiday on Monday 26 April 2021.
The Australian Digital Health Agency is presenting a one hour introduction to integrating software with the My Health Record system.
The Australian Digital Health Agency has updated the following specifications. My Health Record B2B Gateway Services v2.0 & My Health Record Overviews, Guides and Conformance Material v1.5.
Overviews, guides and conformance material relating to the My Health Record system.
The My Health Record SVT environment allows software vendors to build and test the B2B Gateway web services for interactions with the My Health Record system.
Services Australia advice: ANZAC Day Public Holiday - OTS and Developer Support availability - Services Australia advises that there will be a change in the availability of the Developer Support and Online Technical Support (OTS) teams on the upcoming ANZAC Day Public Holiday on Monday 26 April 2021.
Reading & Development: 2 hours. In this guide, we will cover; How to implement CIS to NPP into your software, Solution overview and Conformance Test Requirements
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
Make sure your workplan includes: Transition from SHA-1 NASH PKI certificates to SHA-2 NASH PKI certificates and Using a NASH PKI Certificate to access the HI Service. Learn more....
The My Health Record Software Vendor Welcome Pack is a collection of forms and guides to help new software vendors connect to the My Health Record system for the first time. Some of these documents are also used by existing software vendors to connect their updated software to the My Health Record system.
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 high level system architecture is a critical deliverable for the My Health Record system and 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.
Click on the link below to download the latest version of Managing Your B2B Software in Production.
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....
Technical specifications to enable developers to connect applications to the My Health Record system via the FHIR® Gateway.
To better meet the expectations and requirements of developers, the Agency now provides sample code libraries directly from GitHub and NuGet.
The My Health Record Integration Toolkit contains sample code for B2B connectivity to the My Health Record system.
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).
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 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
Notice of changes: Changes are coming for National Authentication Service for Health (NASH) PKI Certificates and the Healthcare Identifiers (HI) Service. Make sure your work plan includes: Transition from SHA-1 to SHA-2 NASH PKI certificates and using a NASH PKI Certificate to access the HI Service. Learn more
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.
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.
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.
The Clinical Documents Integration Toolkit contains libraries for the creation, packaging and presentation of clinical documents through the use of style sheets.
On this page you will find the latest version of the document, My Health Record Managing your B2B software in production.
Services Australia advice: ANZAC Day Public Holiday - OTS and Developer Support availability - Services Australia advises that there will be a change in the availability of the Developer Support and Online Technical Support (OTS) teams on the upcoming ANZAC Day Public Holiday on Monday 26 April 2021.
Overviews, guides and conformance material relating to the My Health Record system.
These documents provide background and guidance for healthcare provider organisations, and conformance, compliance and accreditation requirements for vendors, regarding the Healthcare Identifiers Service.
From the 1st of November 2020, the Australian Digital Health Agency (the Agency) will be conducting Healthcare Identifier (HI) Conformance testing.
All products developed, or updated, to connect with the HI Service are required to undergo testing before production access is granted.
There are two mandatory testing processes that you will need to complete:
On this page you will find the latest version of the document, My Health Record Managing your B2B software in production.
Latest: Specialists Software Industry Offer - 2nd Tranche - Industry Briefing - 8 April 2021. Refer Slide Pack, Webinar Recording and Q&A Panel Session. Learn more.
Specialist letters are used in replying to a referral or reporting on a health event. They contain information related to the event or the requested diagnosis or treatment by a specialist.
The aim of an event summary is to add significant health care information to an individual’s electronic health record, at the discretion of the clinician and with the consent of the individual.
Dispense Records are used to transfer details of a dispense record, in a format suitable for sharing within My Health Record.
Dispense Records in the Australian context
The Australian Digital Health Agency has updated the Secure Messaging end product to reflect the following changes. The introduction of FHIR provider directories as a replacement for Endpoint Location Services; and
The discontinuation of the previous Conformance Assessment Scheme for Secure Message Delivery.
Make sure your workplan includes: Transition from SHA-1 NASH PKI certificates to SHA-2 NASH PKI certificates and Using a NASH PKI Certificate to access the HI Service. Learn more....
The Agency is providing developers of clinical information and secure messaging systems with a financial incentive to deliver enhanced functionality in an accelerated timeframe.
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.
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.
As part of the Australian National Digital Health Strategy, the Agency aims to end dependence on paper based correspondence and the fax machine or postal services by 2022.
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.
Services Australia advice: ANZAC Day Public Holiday - OTS and Developer Support availability - Services Australia advises that there will be a change in the availability of the Developer Support and Online Technical Support (OTS) teams on the upcoming ANZAC Day Public Holiday on Monday 26 April 2021.
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....
Technical specifications to enable developers to connect applications to the My Health Record system via the FHIR® Gateway.
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).
Specifications, guidance and associated collateral applicable to all types of clinical documents.
The Goals of Care clinical document type is used to capture advance care information in alignment with Western Australia’s Goals of Patient Care Summary documents.
eHealth prescription record documents can be used to share information about prescribed medications via the individual’s digital health record. Documents of this type do not represent actual prescriptions, but merely support the sharing of information about medication prescriptions via the individual’s digital health record.
The Common - Clinical Document end product provides developers of systems generating CDA documents with important updates of:
The Pharmacist Shared Medicines List (PSML) is a new clinical document type supported by the My Health Record system.
The PSML contains detailed information about medicines the consumer is known to be taking when the list was created.
Electronic Transfer of Prescription (ETP) involves the creation of an electronic message (alongside a legal paper prescription) which is transmitted to a prescription exchange service (PES).
Dispense Records are used to transfer details of a dispense record, in a format suitable for sharing within My Health Record.
Dispense Records in the Australian context
Background, Regulatory framework, Technical framework, Frequently Asked Questions and morne information on Webinars, Technical framework documents, Conformance Test Specifications, Developer welcome pack, Conformance Process and the Industry Offer.
Services Australia advice: ANZAC Day Public Holiday - OTS and Developer Support availability & Notice of changes: Changes are coming for National Authentication Service for Health (NASH) PKI Certificates and the Healthcare Identifiers (HI) Service. Make sure your work plan includes: Transition from SHA-1 to SHA-2 NASH PKI certificates and using a NASH PKI Certificate to access the HI Service. Learn more
This Developer Guide is for the use of developers whose products connect to the Healthcare Identifiers (HI) Service, My Health Record, Electronic Prescribing and Secure Messaging with a National Authentication Service for Health (NASH) PKI Certificate.
Australia’s Digital Health system is rapidly growing and evolving, therefore keeping Australian’s digital health information safe and secure is more important than ever! That’s why Australian Digital Health Agency (the Agency) needs your partnership to help your customers stay securely connected to Healthcare Identifiers Service, the My Health Record system, Electronic Prescriptions, and Secure Messaging.
An issue was identified with the Healthcare Identifiers (HI) Service IHI Inquiry web services, affecting the date of birth field. This issue resulted in a timezone to the consumer date of birth value in the IHI search response.
Make sure your workplan includes: Transition from SHA-1 NASH PKI certificates to SHA-2 NASH PKI certificates and Using a NASH PKI Certificate to access the HI Service. Learn more....
These documents provide background and guidance for healthcare provider organisations, and conformance, compliance and accreditation requirements for vendors, regarding the Healthcare Identifiers Service.
The following frequently asked questions relate to the use of Healthcare Identifiers in Health Software Systems.
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
From the 1st of November 2020, the Australian Digital Health Agency (the Agency) will be conducting Healthcare Identifier (HI) Conformance testing.
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.
All products developed, or updated, to connect with the HI Service are required to undergo testing before production access is granted.
There are two mandatory testing processes that you will need to complete:
The Healthcare Identifiers Service (HI) is a national system for uniquely identifying individuals and healthcare providers. HIs help to ensure individuals and providers can have confidence that the correct information is associated with the correct individual at the point of care.
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.
Make sure your workplan includes: Transition from SHA-1 NASH PKI certificates to SHA-2 NASH PKI certificates and Using a NASH PKI Certificate to access the HI Service. Learn more....
The following Electronic Prescribing Frequently Asked Questions (FAQs) are categorised into the following topics: General, Dispensing and Technical Questions along with a Glossary and links to more information.
eHealth prescription record documents can be used to share information about prescribed medications via the individual’s digital health record. Documents of this type do not represent actual prescriptions, but merely support the sharing of information about medication prescriptions via the individual’s digital health record.
Electronic Transfer of Prescription (ETP) involves the creation of an electronic message (alongside a legal paper prescription) which is transmitted to a prescription exchange service (PES).
eHealth Prescription and Dispense View documents represent an electronic summary of information about medication prescriptions and dispensations contained in an individual’s My Health Record.
Background, Regulatory framework, Technical framework, Frequently Asked Questions and morne information on Webinars, Technical framework documents, Conformance Test Specifications, Developer welcome pack, Conformance Process and the Industry Offer.
Australian pathology services are provided by public and private laboratories and provide the foundations on which much of the science of medicine is based.
Pathology in the Australian context
Diagnostic imaging services are provided by radiology providers in the public and private sectors.
Access to miscellaneous supporting documents
eHealth pathology reports can be used to share information about pathology tests via an individual's digital health record.
Reading & Development: 2 hours. In this guide, we will cover; How to implement CIS to NPP into your software, Solution overview and Conformance Test Requirements
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 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
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 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.
To better meet the expectations and requirements of developers, the Agency now provides sample code libraries directly from GitHub and NuGet.
The My Health Record Integration Toolkit contains sample code for B2B connectivity to the My Health Record system.
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.
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.
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.
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.
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.
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.
The Clinical Documents Integration Toolkit contains libraries for the creation, packaging and presentation of clinical documents through the use of style sheets.
Referrals in the Australian context
Referrals are communications with the intention of initiating a transfer of responsibility for some aspects of a consumer’s ongoing management from one provider to another across a range of healthcare and human services fields.
The aim of a shared health summary is to provide key pieces of information about an individual’s health status, facilitating care across their entire healthcare domain.
Shared health summary in the Australian context
A discharge summary is defined as "A collection of information about events during care by a provider or organisation." [AS4700.6(Int)2007]. It comprises a document produced during a patient's stay in hospital.
Discharge summaries in the Australian context
Reading & Development: 2 hours. In this guide, we will cover; How to implement CIS to NPP into your software, Solution overview and Conformance Test Requirements
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
On this page find information on SNOMED® CT-AU, National Clinical Terminology Service and Open Source Software.
Specifications, guidance and associated collateral applicable to all types of clinical documents.
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.
The participation data specification is a foundation document for the suite of data specifications that the Australian Digital Health Agency is developing for the Australian Health Informatics community across a range of health topics.
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.
This document defines the Australian Digital Health Agency’s required data types as a logical level profile that conforms directly to the draft ISO 21090 standard. The detail included in this specification is less than that specified in the ISO document and the technical detail becomes relevant within the scope of this profile, during construction/implementation of Agency information products.
The Detailed Clinical Model Library is a suite of logical models that underpins the national My Health Record system.
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.
The Medicare and Department of Veterans’ Affairs (DVA) benefits report records information about pharmaceutical items prescribed and dispensed to an individual that were partially or fully funded under the Pharmaceutical Benefit Schedule (PBS) or Repatriation Pharmaceutical Benefits Scheme (RPBS)
The Medicare and DVA benefits reports records information about Medicare and Department of Veterans’ Affairs (DVA) funded services provided to an individual.
Medicare DVA Benefits Report in the Australian context
The Australian Organ Donor Register (AODR) is the national register for people to record their decision about becoming an organ and tissue donor.
The Australian Childhood Immunisation Register (ACIR) was a national data register, established in 1996, that records details of vaccinations given to children under seven years of age who live in Australia and are enrolled in Medicare.
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).
with the Australian Digital Health Agency
Register to download resources and keep informed of the latest Developer News.
