My Health Record (MHR)

This page is designed to guide your team through the process of connecting to My Health Record (MHR) via your FYDO account. It outlines the key steps to ensure a seamless integration, helping your hospital streamline the process of uploading of Discharge Summaries.

By preparing ahead of time, you’ll have everything needed for a smooth transition, allowing both staff and patients to benefit from a more connected healthcare experience.

Explore the page to ensure your team is ready for this important integration, and feel free to contact us with any questions at (02) 9632 0026 or support@alturahealth.com.au

On the 28th of November 2023 we partnered with the Australian Digital Health Agency to present a webinar to our customers. This webinar provided essential information on the steps required for your hospital’s integration with MHR.

Click the link below to access the slideshow from this presentation. It offers step-by-step instructions on tasks like how to register a seed organisation, registering for PRODA, linking your Healthcare Identifiers to HPOS, registering your organisation for HPI-O, and more.

Implementing My Health Record in a Private Hospital or Day Surgery Webinar

Additional information on how to register your organisation for My Health Record can be accessed here.

My Health Record Timeline

The Advisory AS18/11: Implementing systems that can provide clinical information into the My Health Record system outlines the timeframes for implementation of a system to upload Discharge Summaries to MHR.

As of September 2024, this advisory stated:

To comply with Actions 1.17 and 1.18, health service organisation must:

  • By June 2024, have developed a detailed plan that complies with:
    – all requirements of Part 5 of the Rule;
    – user of national patient and provider identifiers (IHIs, HPI-Os, HPI-Is); and,
    – user of standard national terminologies.

  • By December 2024, have ongoing monitoring and evaluation of compliance with the requirements of Action 1.17 and 1.18.

Accrediting agencies are required to:

  • Review evidence that:
    – From July 2024, the organisation has completed a gap analysis, has a detailed plan and the plan is being implemented
    – From January 2025, the organisation has as system to monitor and evaluate compliance with Action 1.17 and 1.18.
  • Rate Action 1.17 as met, only if the organisation demonstrates achievement of the specific requirements of the Action in the relevant year.
  • Rate Action 1.18 as met only if the organisation demonstrates embedded processes in accordance with the specific requirements of the Action in the relevant year.
  • Rate Actions 1.17 and 1.18 as met with recommendations if there is evidence of a gap analysis and finalised plan endorsed by executive and the plan is being implemented and monitored (NB. where these requirements are met, these actions may be rated ’met with recommendation’ for no more than one accreditation cycle).

The information above outlines that, from January 2025, the health service organisation are expected to works towards implementing systems capable of providing clinical information to MHR. Additionally, organisations must have processes that

  • describe access to the system and
  • maintain the accuracy and completeness of information the organisation uploads

What can you do to prepare for the MHR integration?

Facilities can ensure they are ready for the integration as soon as it becomes available by:

  • Ensuring they have registered their organisation and obtained their HPI-O
  • Collecting the individual HPI-I’s of their doctors
  • Review Advisory AS18/11 to conduct the required gap analysis and ensure a detailed plan is in place and being implemented.
  • Await an email, from us at FYDO, that advises of our CSP number so that you can link your HPI-O

We appreciate your patience and support as we continue to undergo conformance testing, with the Australian Digital Health Agency, to implement this integration with MHR.




Obtaining Country of Birth Statistical Data (Hospital)

From time to time, it will be necessary to report on County of Birth statistics.
FYDO makes this extremely easy using the Episode Stats report.
  1. Select Reports from the main menu
  2. Select Episode Stats

  3. In the Group By (Primary) field select Country of Birth
  4. Select the date range required in the From & To fields
  5. Click Update

The report will give you the total number & percentage total of episodes that fall under each category.




Tracking User Activity in FYDO

Did you know you can view user activity history in FYDO? Whether it’s to track changes made to an invoice, to see when a patient record was deleted or which user undertook what action, and when, the FYDO’s Audit Logs feature can help! Read on to learn more.

The audit logs show information about the action performed, who performed it, when they performed it, and their IP address. It can be used for troubleshooting purposes or monitoring user activities.

To view the audit logs, first navigate to Settings, then Logs.

How is user activity recorded?

Every user login is unique. So when a user logs in and begins taking actions on FYDO, their activity is logged. Here are some examples of logged user activity in FYDO:

  • User login
  • Changes to patient record
  • Changes to appointment details
  • Billing and invoicing changes
  • Claims sent and batches receipted
  • Payments taken, split, or reallocated
  • Documents deleted
  • Batches removed

You can view user action history within a date range, sort by user, action, or date, as well as search. 

Why use FYDO’s Audit Logs?

Let’s take a closer look at the benefits of this feature.

  1. Greater accountability: logged user action history fosters a culture of responsibility by users being aware that their actions are being logged, promoting responsible behaviour within the organisation.
  2. Enhanced troubleshooting: logged user action history can aid in pinpointing the source and cause of an issue, helping users to troubleshoot problems faster.
  3. Improved security: logged user action history offers a log of most system activities, enabling the identification of unauthorised access attempts, powering administrators to take the necessary steps to secure the system.

Who can view the Audit Logs?

Any user can be given access to view the audit logs by the Subscriber for their facility. The access is granted or removed in Settings > User and User Groups.