Migration to Helix

Helix uses a FHIR-based tool to migrate your MedicalDirector Clinical data using an iterative approach.

The initial data extraction from the source system is reviewed before proceeding with the full migration. Successfully extracted data is migrated into Helix; for data that failed, the process is repeated until the data is successfully extracted and can be imported into Helix. This iterative approach reduces the downtime for customers.

When migrating from MedicalDirector Clinical to Helix you will go through the following steps after you sign off UAT and plan to Go Live. For example:
Example migration process from MDC to Helix
  1. You run a backup of your MedicalDirector Clinical data overnight.
    Note: You can continue using MedicalDirector Clinical after you have supplied your MedicalDirector Clinical data to Telstra Health. However, do not resolve billing, any third party connections, billing and so on.
  2. You supply the MedicalDirector Clinical backup to Telstra Health the next day who then migrate your data into Helix.
  3. After the data migration is complete, Telstra Health Implementation consultants configure clinic and HCP data in Helix.
  4. Your practice goes live in Helix.
  5. Duplicate any data added to MedicalDirector Clinical after you took the backup in step 1 manually in Helix, including appointments, patient and clinical information. Resolve any billing or third party connections.

After your data has been migrated from MedicalDirector Clinical to Helix, review the data.

Tip: Use the following topics to help find your data in Helix and to identify functional areas where your data has either been only partially migrated or has not been migrated.