Echo One /

Integrations and migration

The connections
your practice relies on.

Claiming, payments, practice tools and clinical data exchange, with the scope of each connection made clear. Echo One is coming soon. Connections and channels are confirmed per deployment.

Claiming and payments · Practice tools · National services · Data and migration

01

Claiming and payments.

Claims route from the invoice to the appropriate channel. Anything outside the supported channels is lodged with the funder directly. Channels are confirmed per deployment.

Stripe

Payment processing involves financial information. Stripe is a United States provider; payment setup and the applicable third-party terms are confirmed for the deployment.

Platform data handling

Stripe payments
02

Practice and productivity tools.

Bring the tools your team uses to the evaluation. Confirm the specific workflow, account permissions and third-party licence before relying on a connection.

Xero

For accounting, agree the invoice export, account mapping and payment reconciliation your practice needs. Confirm the available scope during your evaluation.

Xero accounting

Microsoft 365 and Google Workspace

Calendar and meeting requirements vary by practice. Confirm which capabilities you need and which account permissions each connection will require.

Microsoft 365

Google Workspace

Microsoft Teams and Zoom

Confirm whether your telehealth workflow uses a meeting link in the practice's own service or Echo One's configured video service, and who manages access and the licence.

Echo One telehealth

Zoom meetings
03

Prescribing and national digital health.

These connections have their own conformance, credentials and onboarding requirements. Confirm readiness for your practice before planning a change.

Electronic prescribing

Coming soon. Paper scripts today; eScripts coming soon. Electronic prescribing conformance and the production connection must be in place.

Australian Immunisation Register

Coming soon. Immunisations are recorded in Echo One today. AIR reporting through a partner is coming soon.

My Health Record

Not connected yet. A product preview is not a live My Health Record connection. Conformance and the live connection must be confirmed.

Provider messaging networks

Coming soon. Secure link and email today; the provider messaging networks are coming soon.

Direct Medicare lodgement

Coming soon. Medicare claims route through THELMA or Tyro Health's claim window. Direct lodgement with Services Australia is coming soon.

04

Clinical data exchange and migration.

Structured clinical-record export

FHIR R4 Bulk Data export includes a report naming what it leaves out. Note text, documents, correspondence, form responses and appointments are not in it.

Read the export coverage

Moving from your current system

Data comes across from the practice management systems most Australian general practices run today, with a reconciliation the practice can check. Specialist and allied health systems are coming soon.

Plan your practice migration

Start with your current system and export, agree what will move, inspect the reconciliation, and confirm training and the go-live plan before relying on the new record.

05

Platform providers and data location.

Practice data is stored at rest in the AWS and Supabase Sydney region. AI processing uses AWS Bedrock in Sydney and Melbourne and Deepgram's Australian endpoint. SMS through Twilio, transactional email through Postmark and payments through Stripe involve United States providers. Storage location and processing location are different parts of the data flow.

Supabase

Platform database services, with practice data stored at rest in the Sydney region.

Supabase platform

Transactional email

Postmark is a United States provider. The platform and website privacy notices describe the relevant processing.

Postmark email service

Provider logos identify the services described here. They do not indicate endorsement or a certification of Echo One.

Security and data · Platform privacy · Countries and availability

Questions

Common questions.

Which claiming services does Echo One connect to?

Medicare claims route through THELMA or Tyro Health's claim window, in-hospital claims through ECLIPSE, and allied and extras private health claims through Tyro HealthPoint. Channels are confirmed per deployment. Echo One is coming soon; direct Medicare lodgement and DVA claiming through eHealthwise are coming soon.

Are all connections available at launch?

Each practice's connection scope, third-party accounts, permissions and conformance requirements are confirmed before deployment. eScripts, AIR reporting, My Health Record and provider messaging networks are not presented as live connections.

Can we export our clinical record?

The structured clinical record exports in FHIR R4 Bulk Data format, with a report naming what it leaves out. Note text, documents, correspondence, form responses and appointments are not in that export.

Plan your connections

Bring your practice's
integration requirements.

Registering interest is not a commitment to purchase. The overview above is available without submitting a form.

Discuss your practice