My Health Record Production System - Notifications

Article

Context

No current notifications

Contact [email protected] for further advice if you are experiencing any issues.
For technical support please contact [email protected]

Notices regarding SVT are available at: https://developer.digitalhealth.gov.au/resources/news/my-health-record-svt-system-notifications


Resolved 

REMINDER | My Health Record B2B and Mobile Gateway Production SSL Certificate Renewal

The My Health Record System Operator advises there will be a My Health Record B2B Gateway SSL Certificate update to the Production My Health Record system.

The Production My Health Record System Secured Socket Layer (SSL) certificates below are scheduled for renewal at the following times:

  • apinams.ehealth.ehealth.gov.au between 4:00PM and 6:00PM on Thursday, 19 March 2020 (AEDT)
  • services.ehealth.gov.au between 4:00PM and 6:00PM on Tuesday, 24 March 2020 (AEDT)

Details of the replacements:

apinams.ehealth.ehealth.gov.au;

services.ehealth.gov.au

Root Certificate Authority:

DigiCert Global Root CA

Intermediate Certificate:

DigiCert SHA2 Secure Server CA

Technical Notice of My Health Record Gateway Certificate Renewal

The My Health Record systems will be renewing the Secured Socket Layer (SSL) certificate.

If any software vendor has chosen to implement explicit trust against an instance of the My Health Record B2B or Mobility Gateway SSL certificate, there is a risk that the SSL certificate validation flow may fail under the following situations:

  • The software explicitly trusts a particular instance of the My Health Record SSL certificate; or
  • My Health Record B2B or Mobility Gateway SSL certificate has been renewed but the vendor trust store has not been updated.

Action may be required by vendors of software that connect to My Health Record System to ensure communication with the My Health Record System B2B and Mobility gateway will not be affected by the change.

To assess if your software product could be impacted by the renewal of the My Health Record B2B or Mobile Gateway SSL certificate, you should clarify the following:

1.       Is your product explicitly configured to trust the My Health Record B2B or Mobile Gateway SSL certificates issued above?

If you answered “YES”, you will be required to trust the renewed certificate. Please contact us for the renewed certificate.

Please note that the Software Vendor Test (SVT) My Health Record system Secured Socket Layer (SSL) certificates below were successfully renewed yesterday, 17 March 2020 between 5:30PM and 7:30PM (AEDT).

Details of the replacements:

b2b.ehealthvendortest.health.gov.au;

apinams.ehealthvendortest.health.gov.au;

api.ehealthvendortest.health.gov.au

Root Certificate Authority:

DigiCert Global Root CA

Intermediate Certificate:

DigiCert SHA2 Secure Server CA

If you are experiencing any issues connecting to Software Vendor Test (SVT) environment, please contact the System Operator as soon as possible.

The System Operator apologises for any inconvenience this will cause.  

Contact [email protected] or [email protected] for further advice about this message if necessary or to request the certificates.

For technical support please contact [email protected].


My Health Record – Renewal of Production Secured Socket Layer (SSL) certificates B2B and Mobile Gateway

The My Health Record System Operator advises that the My Health Record systems will be renewing the following Production Secured Socket Layer (SSL) certificates:

  • apinams.ehealth.ehealth.gov.au between 4:00 PM 19 March 2020 and 6:00 PM 19 March 2020 (AEDT)
  • services.ehealth.gov.au between 4:00 PM 24 March 2020 and 6:00 PM 24 March 2020 (AEDT)

ACTION MAY BE REQUIRED by vendors of software that connect to My Health Record System to ensure communication between your customers and the My Health Record System. B2B and Mobility gateway will not be affected by the change.

Technical Notice of My Health Record Gateway Certificate Renewal

The Production My Health Record systems will be renewing their Secured Socket Layer (SSL) certificate.

If any software vendor has chosen to implement explicit trust against an instance of the My Health Record B2B Gateway SSL certificate, there is a risk that the SSL certificate validation flow may fail under the following situations:

  • The software explicitly trusts a particular instance of the My Health Record SSL certificate; or
  • My Health Record B2B Gateway SSL certificate has been renewed but the vendor trust store has not been updated.

Background

The My Health Record system makes use of Public Key Infrastructure to secure its communication with consumers and participants.

Systems connecting to the My Health Record rely on the My Health Record B2B Gateway SSL certificate to authenticate the connection. This occurs at the transport layer using the Transport Layer Security (TLS) protocol and at the B2B service layer using an XML signature. It is also used by the My Health Record to add an XML signature to documents that it generates in response to certain view requests, e.g. the Prescription and Dispense View. In all cases the same SSL Certificate is used by the My Health Record B2B gateway.

Which certificate is being renewed?

Details of the replacement: services.ehealth.gov.au

Root Certificate Authority: DigiCert Global Root CA

Intermediate Certificate: DigiCert SHA2 Secure Server CA

Mobile applications connecting to the My Health Record system could rely on the below Mobility Gateway SSL certificate.

Which certificate is being renewed?

Details of the replacement: 
apinams.ehealth.ehealth.gov.au

Root Certificate Authority: DigiCert Global Root CA

Intermediate Certificate: DigiCert SHA2

Please email [email protected] or [email protected] if you require further information.


My Health Record Release 11 Production System Upgrade

The My Health Record System Operator advises there will be a planned upgrade of the My Health Record system production environment from 8:30pm Friday 13 March to 5:00am Saturday 14 March (AEDT) with a Restricted-Write period from 9:00pm Friday 13 March to 2:30am Saturday 14 March 2020 (AEDT).

During the restricted-write period, the My Health Record system, including connecting mobile applications, will be available to access My Health Record functionalities including some write transactions.

The following subset of write transactions to the My Health Record System will be disabled:

  • Linking a My Health Record to a myGov account
  • Linking a PRODA account to National Provider Portal
  • Resetting password and ULC linking via Admin Portal
  • New Care Agency employee registration
  • Notify Account Change (NAC) flow

Before the conclusion of the ‘Restricted Write’ window, there will be a 30-minute outage to the Mobility channel as the tokens are migrated. This outage will commence on Saturday 14 March 2020 at approximately 2:00am (AEDT) and is expected to conclude at 2:30am (AEDT).

The My Health Record System Operator apologises for any inconvenience this may cause.

Contact [email protected] for further advice about this message if necessary.

For technical support please contact [email protected].


The My Health Record System will undergo scheduled maintenance from 9:00PM (AEDT) Monday, 10 February 2020 to 12:00 AM (AEDT) Tuesday, 11 February 2020, which may affect some services to the My Health Record system.

During this time, the My Health Record system, including connecting mobile applications, will be available to access My Health Record functionalities including some write transactions.

The following subset of write transactions to the My Health Record System however will be disabled:

  • Linking a myGov account to My Health Record
  • Linking a PRODA account to National Provider Portal
  • Resetting password and ULC linking via Admin Portal
  • New Care Agency employee registration
  • Notify Account Change (NAC) flow

Before the conclusion of the upgrade, there will be a 30-minute restricted function period for mobile applications. This period will commence at approximately 11:30 PM (AEDT) Monday, 10 February, 2020 to approximately 12:00 AM (AEDT) on Tuesday, 11 February, 2020. During this time, consumers using mobile apps connected to the My Health Record system won’t be able to:

  • Link a My Health Record to a patient’s myGov account
  • Access, create or register for a patient for new My Health Record
  • Access or create a My Health Record for a child

Please note, there will be no change to vendor products.

The My Health Record System Operator apologises for any inconvenience this may cause.

Contact [email protected] for further advice about this message if necessary.

For technical support please contact [email protected].

Services Australia: System degradation to Healthcare Identifiers (HI) Service PRODUCTION environment 

Services Australia would like to advise that the Healthcare Identifiers (HI) Service PRODUCTION environment experienced a degradation of service between 15:55pm AEDT and 18:05 pm AEDT on Wednesday 5 February 2020.

This issue has been resolved.  

We apologise for any inconvenience this may have caused.

Should you have any queries regarding this advice please contact the department's Online Technical Support team at [email protected].


My Health Record System will undergo scheduled maintenance from 9:00PM (AEDT) Tuesday, 28th January 2020

The My Health Record System will undergo scheduled maintenance from 9:00PM (AEDT) Tuesday, 28th January 2020 – 12:30AM (AEDT) Wednesday, 29th January 2020, which may affect some services to the My Health Record system.

During this time, the My Health Record system, including connecting mobile applications, will be available to access My Health Record functionalities including some write transactions.

The following subset of write transactions to the My Health Record System however will be disabled:

  • Linking a myGov account to My Health Record
  • Linking a PRODA account to National Provider Portal
  • Resetting password and ULC linking via Admin Portal
  • New Care Agency employee registration
  • Notify Account Change (NAC) flow

Please note, there will be no change to vendor products.

The My Health Record System Operator apologises for any inconvenience this may cause.

Contact [email protected] for further advice about this message if necessary.

For technical support please contact [email protected].


My Health Record Scheduled Maintenance - 17 December 2019 

The My Health Record System Operator advises that the My Health Record system will undergo scheduled maintenance from 8:00PM to 11:00PM (AEDT) Tuesday 17 December 2019, which may affect some services to the My Health Record system.

During this time, the My Health Record system, including connecting mobile applications, will be available to access My Health Record functionalities including some write transactions.

The following subset of write transactions to the My Health Record System however will be disabled:

  • Linking a myGov account to My Health Record
  • Linking a PRODA account to National Provider Portal
  • Resetting password and ULC linking via Admin Portal
  • New Care Agency employee registration
  • Notify Account Change (NAC) flow

Please note, there will be no change to vendor products.


The My Health Record System will undergo scheduled maintenance from 9:00PM (AEDT) Tuesday, 28th January 2020 – 12:30AM (AEDT) Wednesday, 29th January 2020, which may affect some services to the My Health Record system.

During this time, the My Health Record system, including connecting mobile applications, will be available to access My Health Record functionalities including some write transactions.

The following subset of write transactions to the My Health Record System however will be disabled:

  • Linking a myGov account to My Health Record
  • Linking a PRODA account to National Provider Portal
  • Resetting password and ULC linking via Admin Portal
  • New Care Agency employee registration
  • Notify Account Change (NAC) flow

Please note, there will be no change to vendor products.

The My Health Record System Operator apologises for any inconvenience this may cause.

Contact [email protected] for further advice about this message if necessary.

For technical support please contact [email protected]

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).

Back to Top