Software products using digital health

The Agency supports a number of digital health solutions and functions for a range of healthcare software providers in general practice, pharmacy, and aged care.

Register of Conformity

The Register of Conformity is used to record information about the conformity to digital health specifications of medical software and health IT services (e.g. from vendors and health jurisdictions). It is managed by the Agency and provides information on health software systems and organisations that meet national digital health standards and specifications. 

This is a comprehensive list of clinical software products that meet conformance for a number of My Health Record system clinical functions.

Register Summary

The Register of Conformity lists software products and the versions that have been assessed for conformance with national digital health requirements. This includes the ability to view a My Health Record, upload a Shared Health Summary, upload prescriptions, provide Assisted Registration, and more.

Software developers must declare the conformance of their products to be included in the Register.

Download: Register of Conformity - Register Summary (PDF, 445.07 kB)

Last updated on Thursday 1 September 2016.

Register Detail

The Register Detail shows the scope of assessment for each digital health and My Health Record system clinical function, plus other related information for each software product or service in the Register Summary.

Download: Register of Conformity - Register Detail (PDF, 411.67 kB)

Last updated on Thursday 1 September 2016.

My Health Record Developer

Integrate digital health into your platform with My Health Record Developer. We provide easily customised guides and resources for developers who want to integrate digital health products into their platforms.

Visit My Health Record Developer

The CCD Register is used by vendors, suppliers, healthcare service providers and other organisation or members of public. Users can be categorised as Primary Users and Secondary Users. The Primary users own at least one entry in the CCD Register while the Secondary users browse information in the register.

Primary Users

Software Developers and Vendors - To declare conformance of their products to digital health specifications, and to be listed as eligible suppliers.

Healthcare Service Providers and IT Service Providers - To declare compliance of their systems to published digital health compliance requirements.

Secondary Users

Healthcare organisation or members of public - To look up list of healthcare system software developers and products that supports digital health conformance or compliance.

Products, services and organisations are eligible for inclusion on the Registers if they have been assessed for conformance or compliance with national digital health requirements. Listing is voluntary and reflects information supplied by the conforming organisation or product owner. Software products are eligible for inclusion on this Register if the software vendor declares conformance with the requirements for each product by completing and submitting a Declaration of Conformity.

Requirements on how to submit a Register Request as a Healthcare Organisation or Software Vendor can be found in the content outlined below.

The webpage for the CCD Register is made up of a series of sub-Registers that are customised for the digital health requirements.

My Health Record system

To prepare for gaining access to the My Health Record system, you may need to make changes to the software in your practice. The upgrades required will depend on whether you are using the provider portal or conformant clinical software. Refer to www.myhealthrecord.gov.au for more information.

If your organisation uses conformant clinical software, authorised and registered users in your practice will be able to view shared health information and create and upload health information such as shared health summaries and event summaries.

Conformance is based on strict compliance controls to ensure the integrity and security of the My Health Record system is maintained. The Register Summary is used to identify clinical software systems that are conformant with the My Health Record system.

Healthcare Identifiers

Software systems listed here meet the conformance requirements for using Australia's national Healthcare Identifiers (HI).

Products and systems listed here have been independently assessed to conform to the software requirements for the safe implementation and use of healthcare identifiers for patients, providers and healthcare organisations. The assessment was performed by test laboratories accredited to perform HI conformance testing.

The Healthcare Identifiers (HI) Service is a national system used for uniquely identifying healthcare professionals, organisations and individual consumers of healthcare services. The service is operated by the Department of Human Services (DHS). Healthcare identifiers will help ensure individuals and healthcare professionals have confidence that the right information is associated with the right individual at the point of care.

The HI Service allocates and manages the following types of healthcare identifiers:

  • Healthcare Provider Identifier – Individual (HPI-I) – for healthcare professionals involved in providing patient care;
  • Healthcare Provider Identifier – Organisation (HPI-O) – for organisations that deliver healthcare (such as general practices and hospitals); and
  • Individual Healthcare Identifier (IHI) – for individuals using healthcare services.

You may find it beneficial to talk about setting up HPI-O(s) for your practice with the organisation(s) that provides you with IT and/or digital health support, as it can be complex depending on your organisational structure and level of knowledge and experience. Please also refer to the Clinician's Desktop User Guide available at www.digitalhealth.gov.au and specifically the sections HPI-O Structure Options and Deciding on your HPI-O Structure.

For useful information, guides and forms for the HI Service and to apply for a HPI-O, refer to the DHS website www.humanservices.gov.au >For Health Professionals >Healthcare Identifiers Service

When you have established the necessary Roles, your practice's HPI-O, and the links to it in the HI Service for your clinicians and nominated staff, you can plan and then implement updates to your clinical software system that includes healthcare identifier functionality. You can use this Register to identify clinical software systems that meet the national conformance requirements for the use of Healthcare Identifiers in clinical software systems.

Secure Message Delivery

Healthcare organisations that implement products and services compliant with the SMD specifications, either directly or indirectly via an intermediary, will be able to connect to and exchange a broad range of message types, securely and reliably with any other healthcare organisation that also uses software compliant with the specification. Parties will also be able to communicate even where the sender and receiver use different intermediaries to route messages provided that those intermediaries have established commercial interconnect agreements.

The webpage for the CCD Register is made up of a series of sub-Registers that are customised for the digital health requirements.

My Health Record system

Conformance assessment provides assurance that a clinical software system adheres to digital health specifications as defined in the My Health Record CIS conformance assessment scheme. It gives users of conforming implementations confidence that an implementation will behave as expected, perform functions in a known manner, has interfaces or formats that adhere to agreed specifications, and is likely to interoperate with other conforming implementations.

Conformance testing for software developers is performed according to the approved CCD self-assessment process. It is a process which enables a developer to assess their own software system, using the test documentation and tools provided by the Agency.

Refer to resources For Implementers for more information on the conformance requirements of software systems connecting to the My Health Record system.

When you have met the requirements for your software product to access the My Health Record system and you wish to record this in the Register of Conformity, you should submit the following to help@digitalhealth.gov.au:

  • Completed and signed My Health Record Declaration of Conformity Form (123 KB);
  • The My Health Record system Production Access Letter issued by the Department of Health; and
  • The healthcare identifiers test report issued by the test laboratory, if your software accesses the HI Service.

Healthcare Identifiers

The intent of this requirement is to make Healthcare Identifiers available for electronic messaging and for use in the My Health Record system.

Clinical software systems must demonstrate the capability of direct access to the Healthcare Identifiers (HI) Service by completing HI conformance testing, as documented in the HI Conformance Assessment Scheme. The CCD tests are performed by independent National Association of Testing Authorities (NATA) accredited testing laboratories to assure the safe use of Healthcare Identifiers by clinical software systems. Conformance assessment must be performed by a test laboratory accredited by NATA under its classification 22.40.02 in the NATA Information and Communications Technology Testing, Classes of Test.

The Software Conformance Requirements for HI provide detail of the clinical software system behaviour and refers to relevant Business Use Cases. Refer to the Healthcare Identifiers Service - Support Documents for the HI Conformance Assessment Scheme, HI Business Use Cases and the Software Conformance Requirements.

When you have successfully completed the Notice of Connection (NOC) and CCA testing requirements for your software product to access the HI Service and you wish to record this in the Register of Conformity, you should submit the following to help@digitalhealth.gov.au:

Efficient and secure transfer of electronic information is a key building block for digital health. Software vendors and organisations who choose to implement Secure Message Delivery (SMD) Australian Technical Specification published by Standards Australia which defines a set of interfaces and associated application behaviour suitable for clinical messaging over the Internet.

Health messaging software systems listed here has been independently assessed for conformance to the SMD specifications. The assessment was performed by testing laboratories accredited to perform SMD conformance testing.

Secure Message Delivery

SMD enables the health messaging software system to interoperate with other products which conform to the same specification.

While it is possible that a health messaging software system used by a healthcare provider may have a “native” capability to send and receive secure messages, in many cases the sending and receiving of secure messages is likely to be via a messaging service provider. SMD messaging capability must conform to the Standards Australia technical specifications for SMD ATS 5822-2010.

Listings on the Register of Conformity for secure message delivery may be sought by messaging service providers, and by those software developers of clinical information systems which have a built-in SMD messaging capability.

Clinical information systems used by healthcare providers do not appear on the Register of Conformity for secure message delivery unless they have a built-in SMD capability. It is intended that healthcare providers will establish its SMD compliance by checking that either its messaging service provider is listed on the Register, or that its SMD-capable clinical information system is listed on the Register.

Conformance is demonstrated by independent testing by a National Association of Testing Authorities (NATA)- accredited testing facility. Conformance assessment of SMD software products must be performed by a test laboratory accredited by NATA under its classification 22.40.01 in the NATA Information and Communications Technology Testing, Classes of Test. A test report as evidence of such testing should be submitted with an application for listing.

Refer to the Secure Message Delivery End Product for more information on software conformance for SMD.

Software developers who wish to claim software conformance to the requirements for SMD must complete the Implementation Conformance Statement (ICS) for SMD to indicate which requirements are satisfied by their SMD implementation before submitting their software to an accredited test laboratory for formal testing.

When you have successfully completed the testing requirements for your software product and you wish to record this in the Register of Conformity, you should submit the following to help@digitalhealth.gov.au:

The Agency publishes the Australian Register of Conformity as a service for third party vendors, health service providers, hospital or State and Territory health departments to declare the conformance of their systems to digital health specifications and standards. All organisations that wish to appear on the Australian Register of Conformity must certify that the information they provide is accurate, complete and up-to-date and are responsible for modifying or de-registering their entries if the software no longer meets relevant conformance requirements. The Agency takes no responsibility for the false or misleading representations of third parties entered on the Australian Register of Conformity.

Terms of Use for the Australian Register of Conformity

This webpage for the Australian Register of Conformity is owned and operated by the Australian Digital Health Agency (the Agency). By choosing to use the webpage or download materials from it, you agree to the following Terms of Use. If you do not accept these Terms of Use, you must not use the Webpage or download materials from it. Parts of the Webpage may have additional terms and conditions of use.

Copyright

Unless otherwise indicated, the Agency reserves all copyright in the content and design of the Webpage and all materials on it. The Agency owns this copyright or uses it under licence or applicable law. You may access and use content on the Webpage only for personal or non-commercial use or use within your organisation. You may not otherwise use, copy or reproduce this Webpage or any part of it (except as permitted by applicable copyright legislation) without the Agency's written consent. You may not reproduce any of the content of the Webpage on any other webpage (including by way of framing or embedding) without the Agency's written consent.

The Agency owns the trade mark "nehta" and reserves all rights in relation to it. Other product and company names referred to on this webpage may be trademarks owned by third parties. Nothing contained in this Webpage should be construed as being any licence or right of use of any trade mark displayed on the Webpage.

Links to third party webpages

This webpage may contain links to other websites controlled or produced by third parties. The Agency makes no representations about the accuracy of, and takes no responsibility for, the content contained on those websites. Unless expressly stated, any references to third parties or third party websites should not be taken as an endorsement or recommendation by the Agency and any opinions, statements, services or other information or content available on third party websites are those of the respective author(s) and not of the Agency. If you use a link from this Webpage to a third party website, you acknowledge that the Agency has no control over the content of that third party website and therefore has no responsibility for any transaction arising from your link to it.

Warranties

The Agency makes the information and other material (Information) on this Webpage available in good faith but without any representation or warranty as to its accuracy or completeness. All information is subject to change without notice. As the Information is of a general nature only and believed to be accurate at the time of publication, it is up to any person using or relying on the Information to ensure that it is up to date and suitable for the circumstances of its use. The Agency cannot ensure the accuracy of any information or advice contained after publication to the Webpage. Further, the Agency cannot accept any responsibility for the consequences of any use of the Information. To the maximum extent allowed by the governing law, the Agency will not be liable to you for any consequential loss or damage arising from any error or omission in the Information.

Updates

The Agency may revise these Terms of Use by updating this page at any time.

Governing law

The laws of New South Wales, Australia govern these Terms of Use.

The software developer acknowledges that:

  1. The Register of Conformity (Register) provides information to practices about conformant and compliant software products;
  2. The Agency operates the Register (Operator) on behalf of the Commonwealth Department of Health (Health); and
  3. Software developers are required to apply to have their products listed on the Register subject to the requirements described in the Vendor Guidelines (“listing”).

The software developer agrees as follows by submitting a product for listing on the Register:

  1. The software developer's name and submitted product details may be included on the Register and published;
  2. Product material or materials included with the application in support of a listing on the Register may be stored by the Operator and made available to users of the Register;
  3. While the Operator will use reasonable efforts to maintain the currency and accuracy of the Register, listings and the availability of the Register online, no assurance is given that the listings will be complete, accurate or up to date at any particular point in time and, without limitation, the Register may not be available through system or equipment failure, planned or unplanned maintenance/repair, or through communication carrier failure;
  4. The Operator is not obliged or required to check the accuracy or completeness of the information and materials relating to an application by a software developer for listing (or any application to change the details of a listing). However, the Operator, in its discretion, may not accept an application until it is satisfied that the information and materials is accurate or complete (as the case may be);
  5. Whether or not the Operator elects to check the accuracy or completeness of information and materials, the Operator will only publish information submitted by software developers and without giving any assurance as to the completeness or accuracy of that information and materials submitted. The Operator cannot ensure the accuracy of any information or materials contained after publication to the Webpage. Further, the Operator cannot accept any responsibility for the consequences of any use of the information and materials;
  6. The Operator may of its own accord or at the prompting of 'Health' or any third party, remove a listing where the Operator believes there is evidence of inaccurate or incomplete information or materials having been supplied in support of an application for listing. The Operator will provide the software developer with 10 days' notice of any such intention to remove a listing unless in the Operator's opinion the delay in the removal may directly or indirectly result in adverse clinical outcomes; and
  7. If the software developer disputes any action taken by the Operator, the software developer must contact 'Health' for resolution of the matter. Any decision by Department of Health regarding the disputed action is final and binding on the software developer and the Operator.