HI Service and My Health Record test endpoint access information:
HI Service: https://www5.medicareaustralia.gov.au/cert/soap/services/
Please note that the last character (forward slash “/”) of the endpoint is significant. If this character is missing, you may get an exception if you are using our .NET library.
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>[ISS.0088.9109] SOAP is only supported using HTTP POST protocol</faultstring>
<faultactor>http://: 10.254.51.155:15511/soap/services/</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Configuration changes required for My Health Record Software Vendor Test environment
(Last updated 30 June 2022, 10.00 AM AEST)
On 25 May, the Australian Digital Health Agency changed the endpoints to the My Health Record Software Vendor Test (SVT) environment and the My Health Record public SSL certificate.
These changes were required because the Agency moved the endpoints for SVT from the previous Global Switch data centre to an Agency-managed secure hosting service, which is Certified Strategic under the Australian Government’s Hosting Certification Framework.
Software endpoints must now be updated so that you can continue to use the SVT environment. The current endpoints are no longer accessible.
My Health Record - Data Centre Rehosting - SVT Certificates V1.1 removes the Apache Server instructions and text files related to language translation.
Changes for B2B Gateway users
Endpoint updates in SVT environment
The old and new FQDN details for SVT in the B2B Gateway domain are as follows.
| Old FQDN (no longer accessible) | New FQDN |
| b2b.ehealthvendortest.health.gov.au | services.svt.gw.myhealthrecord.gov.au |
| registrations.ehealthvendortest.health.gov.au | registrations.svt.gw.myhealthrecord.gov.au |
There are no changes required to endpoints in the My Health Record production environment.
Add new My Health Record public SSL certificate in trust store
Software systems connected to the SVT environment must trust the new My Health Record public SSL certificate.
Changes for FHIR Mobility Gateway domain users
Endpoint updates in SVT environment
The old and new FQDN details for SVT in the FHIR Mobility Gateway domain are as follows.
| Old FQDN (no longer accessible) | New FQDN |
| For apps using interaction model 4 | |
| api.ehealthvendortest.health.gov.au | api.svt.gw.myhealthrecord.gov.au |
| For apps using interaction model 1 | |
| apinams.ehealthvendortest.health.gov.au | apinams.svt.gw.myhealthrecord.gov.au |
| Used by provider apps | |
| apiprov.ehealthvendortest.health.gov.au | apiprov.svt.gw.myhealthrecord.gov.au |
There are no changes required to endpoints in the My Health Record production environment.
Changes for National Provider Portal (NPP) and National Consumer Portal (NCP)
Endpoint updates in SVT environment
The old and new FQDN details for the test National Provider Portal (NPP) and test National Consumer Portal (NCP) domains are as follows.
| Old FQDN (no longer accessible) | New FQDN |
| National Provider Portal (NPP) | |
| https://ehealthvendortest.health.gov.au/ | https://provider.svt.mhr.myhealthrecord.gov.au |
| National Consumer Portal (NCP) | |
| https://myrecord.ehealthvendortest.health.gov.au/locallogin/login.html | https://myrecord.svt.mhr.myhealthrecord.gov.au/locallogin/login.html |
There are no changes required to endpoints in the My Health Record production environment
Add new My Health Record public SSL certificate in trust stores
Any application using interaction model 4 and provider apps to connect to the SVT environment must trust the new My Health Record public SSL certificate in the app’s intermediary server trust store.
Contacts for questions about these changes
| Topic | Contact details |
| Changing endpoints for the SVT environment | Email [email protected] |
| Logging into Developer Centre | Email [email protected] |
| Updating the SSL certificate | Digicert livechat or phone support https://www.digicert.com/support |