Skip to main content

Medicare Australia EDI: requirements and onboarding

Plan Australian Medicare claiming around Services Australia's Medicare Online and ECLIPSE channels, compatible practice software, and the applicable registration process. This is a public planning guide, not a US Medicare companion guide or evidence that SignalEDI has an approved connection. The scenarios below are advisory exercises, not official integration tests.

Quick answers

Can SignalEDI help me connect to Medicare Australia?
SignalEDI helps prepare mappings, sample validation, and the workflow required for your Medicare Australia program. Scope is confirmed during setup. Production connection requires the applicable partner approval; this guide is not evidence of a live connection or certification.
What determines the Medicare Australia onboarding timeline?
The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule. Agree the schedule after requirements and testing scope are confirmed. This is not a guaranteed go-live date.
Which practice or billing systems can I use for Medicare Australia?
Start with the country, provider program, practice or billing software and the authorised channel for the specific workflow. Confirm vendor eligibility, permitted interfaces, registration and patient-data controls before planning any connection. Scope is confirmed during setup. This planning page does not establish SignalEDI approval, a live integration or authority to handle patient information.
Review integration scope

Plan the integration workflow

SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.

  1. 1. Your business system

    Identify the source records, system edition, data owner, and allowed access.

  2. 2. SignalEDI preparation

    Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.

  3. 3. Partner testing and approval

    Complete the partner-controlled tests and retain permission before enabling live exchange.

Conceptual workflow only. A diagram or catalog listing does not establish certification or an active production connection.

Build your onboarding checklist

Download the onboarding worksheet (text)

Public sources reviewed 2026-11-09

What the public record confirms

  • Services Australia says health care locations using Medicare Online or ECLIPSE need web-services-compatible software and an organisation registered for Provider Digital Access (PRODA). An Australian claiming workflow should not inherit a US HIPAA X12 837/835 specification merely because both systems use the name Medicare.
  • The Medicare Online developer overview covers patient claiming, bulk bill claiming, DVA medical and pathology, AIR notifications, patient verification, ECLIPSE, in-hospital claiming and eligibility. These are separate functions to scope with the software provider, not a promise that every software product includes every function.
  • ECLIPSE registration includes compatible software, a developer-issued minor ID, individual and organisation PRODA accounts, the online claiming provider agreement, and linking the organisation to Medicare Online/ECLIPSE/DVA/AIR. The current linking instructions also address B2B device registration when the software product is available.
  • Software development has a separate approval path. Services Australia's public process requires developer-portal registration, acceptance of an Interface Agreement, and integration testing before a Notice of integration is issued. Licensed technical material is not replaced by this public guide. Provider registration and software approval are different evidence.
  • ECLIPSE distinguishes patient-detail verification from eligibility checking. The relevant private health insurer and software must support the required function. Processing status and payment reports are separate from submission: the reporting guide advises checking status before retrieving a report, because a report that is not ready can be empty.
  • The public software directory was marked updated 19 October 2026 when reviewed. Services Australia says it is not exhaustive and does not endorse a particular developer. Its published function columns can help shortlist software, but neither directory presence nor this page establishes SignalEDI capability, certification, privacy compliance or production approval.

Document and workflow scope

Use the cited source boundaries below, then confirm your current assigned program: Exact specifications come from your partner packet. Treat this as a planning checklist, not a substitute for the current implementation guide.

  • Claim submission: identify the actual Medicare Online or ECLIPSE service, claim category, software release and current authorised specification. Do not substitute a generic 837 claim map.
  • Patient verification and eligibility: specify which function is needed and which organisation returns the result. A patient match, an eligibility response and a paid claim are different events.
  • Processing and payment reports: define the status, processing and applicable ECLIPSE Remittance Advice workflow. The term remittance advice does not establish an X12 835 payload.
  • Implementation and access records: retain the applicable approved-product scope, provider registration, minor ID association and guide revision in authorised internal records. Do not place credentials or patient examples in public project material.

Connectivity and testing requirements

Connectivity

Confirm the current authorised interface, enrollment and software requirements for the specific provider, payer or supplier program.

Onboarding window

Not verified on this page.

Certification focus

The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule.

  • Services Australia says health care locations using Medicare Online or ECLIPSE need web-services-compatible software and an organisation registered for Provider Digital Access (PRODA). An Australian claiming workflow should not inherit a US HIPAA X12 837/835 specification merely because both systems use the name Medicare.
  • The Medicare Online developer overview covers patient claiming, bulk bill claiming, DVA medical and pathology, AIR notifications, patient verification, ECLIPSE, in-hospital claiming and eligibility. These are separate functions to scope with the software provider, not a promise that every software product includes every function.
  • ECLIPSE registration includes compatible software, a developer-issued minor ID, individual and organisation PRODA accounts, the online claiming provider agreement, and linking the organisation to Medicare Online/ECLIPSE/DVA/AIR. The current linking instructions also address B2B device registration when the software product is available.
  • Software development has a separate approval path. Services Australia's public process requires developer-portal registration, acceptance of an Interface Agreement, and integration testing before a Notice of integration is issued. Licensed technical material is not replaced by this public guide. Provider registration and software approval are different evidence.
  • ECLIPSE distinguishes patient-detail verification from eligibility checking. The relevant private health insurer and software must support the required function. Processing status and payment reports are separate from submission: the reporting guide advises checking status before retrieving a report, because a report that is not ready can be empty.
  • The public software directory was marked updated 19 October 2026 when reviewed. Services Australia says it is not exhaustive and does not endorse a particular developer. Its published function columns can help shortlist software, but neither directory presence nor this page establishes SignalEDI capability, certification, privacy compliance or production approval.

Questions to resolve from the current buyer packet

  • Write an Australian scope statement naming the practice, clinical billing workflow and Medicare Online or ECLIPSE functions. Keep US Medicare and other countries' payer requirements out of the mapping baseline.
  • Confirm the selected software product and release support each requested function. Review current Services Australia information and the developer's authorised material rather than inferring support from a product category.
  • Have the responsible organisation owner verify registration and linking prerequisites. Record whether access is ready without copying PRODA credentials, identity evidence or device secrets into implementation notes.
  • Record the revision and effective scope of the technical documents supplied through the authorised development process. Public page update dates are not API or payload version numbers.
  • Define operational states for submitted, awaiting assessment, rejected, corrected and reconciled work. Assign ownership of unresolved reports and uncertain outcomes before proposing a live cutover.
  • Use synthetic examples for planning. Establish the permitted data handling, approved software and production access separately before using real patient information; this page makes no jurisdictional compliance determination.

How SignalEDI handles it

  • Prepare a versioned mapping and testing checklist from the requirements you provide.
  • Validate synthetic or scrubbed samples before partner testing.
  • Review acknowledgement and exception handling before production cutover. Scope is confirmed during setup.

Review mapping and validation in the self-serve workspace before partner testing. Developer quickstart

Pricing

SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.

Compare current plans

Practice the workflow before partner testing

These are recommended preparation exercises, not additional partner requirements or a customer success story. Use synthetic or scrubbed samples and adapt each exercise to the current guide assigned to your program.

Choose the Australian claiming scope

Advisory exercise: create a synthetic service inventory containing a patient claim, bulk bill and in-patient workflow. For each, identify the intended Australian channel, software function, responsible owner and specification reference. Include an unresolved function deliberately. Do not send requests or infer that a generic healthcare adapter implements it.

What a useful result looks like

The planning record shows which functions are evidenced and which remain open. Unsupported functions stop at an explicit decision point. A US transaction label cannot silently become the specification for an Australian claim, and the inventory is not described as completed certification.

Separate access and product approval

Advisory exercise: build a readiness matrix using fictional identifiers and evidence labels. Distinguish practice registration, organisation linking, software release and product approval. Introduce a case where one prerequisite is ready but another is missing. Assign the person who can verify each missing item without collecting credentials in the worksheet.

What a useful result looks like

The proposed readiness result remains incomplete until each applicable prerequisite has its own evidence. A successful login does not prove software approval, and an approved product does not prove that a particular practice may start exchanging real claims.

Follow assessment before reconciliation

Advisory exercise: use a paper or local synthetic timeline showing submission, an interim status, an unavailable report and a later result. Decide how the operator distinguishes a pending assessment from a failure and how finance follows the final outcome. Use the actual product documentation to settle polling, retrieval and correction behaviour before implementation.

What a useful result looks like

The proposed pass condition is traceable state handling with an owner for unresolved work. An empty report is not automatically read as a zero payment, and successful transport is not treated as final assessment or bank reconciliation.

Rehearse a controlled specification change

Advisory exercise: compare two fictional revisions of a function inventory and mark one added capability, one changed report and one unchanged workflow. Record the authorised technical reference needed to decide each change. Prepare a review and rollback checklist using synthetic records only, without accessing restricted portal material or production systems.

What a useful result looks like

Every proposed change has a bounded scope, accountable reviewer and separate readiness decision. Documentation review dates cannot substitute for interface versions. The exercise produces useful planning evidence while making no claim about SignalEDI certification, live functionality or compliance.

Common integration questions

Can I keep my existing practice or billing software?
Start with the country, provider program, practice or billing software and the authorised channel for the specific workflow. Confirm vendor eligibility, permitted interfaces, registration and patient-data controls before planning any connection. Scope is confirmed during setup. This planning page does not establish SignalEDI approval, a live integration or authority to handle patient information.
Does validation mean my partner has approved production?
No. Passing document validation checks your sample against the configured rules. Partner certification, enrollment, transport approval, and permission to send live documents are separate steps controlled by the applicable partner program. Use synthetic or scrubbed samples while preparing and keep the approval evidence before switching to production.
Where can I see SignalEDI pricing?
SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.

Authoritative sources

Source review date: 2026-11-09. Links below establish only the facts described; your current buyer-issued materials remain authoritative for program-specific technical requirements.

Medicare Australia questions

Does Medicare Australia use the same claim setup as US Medicare?
Do not assume so. This page concerns Services Australia's Medicare Online and ECLIPSE workflows. Use the Australian channel's approved software, registration requirements and current authorised specification. A US payer's 837/835 companion guide does not establish the Australian payload or connection contract.
What should I confirm before planning a Medicare Australia connection?
Identify the claiming and verification functions, compatible software release, practice registration and PRODA linking requirements, and the approved product scope. Separate patient verification, assessment and payment reconciliation. Technical versions must come from authorised materials rather than a public marketing page or the date a website was updated.
Does this Medicare Australia guide prove SignalEDI is approved for live claims?
No. It documents public requirements and advisory preparation only. It does not establish a SignalEDI Notice of integration, live connectivity, provider enrolment or permission to process patient data. Confirm product-specific approval and the organisation's authorised production arrangements separately.

Related EDI resources

Prepare your side for partner testing

SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.

Connect now

Topics: Medicare Australia EDI requirements · Medicare Australia supplier EDI · Medicare Australia EDI AU

© 2026 SignalEDI Inc. All rights reserved.