Quick answers
- Can SignalEDI help me connect to Medibank?
- SignalEDI helps prepare mappings, sample validation, and the workflow required for your Medibank 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 Medibank 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 Medibank?
- 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.
Plan the integration workflow
SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.
1. Your business system
Identify the source records, system edition, data owner, and allowed access.
2. SignalEDI preparation
Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.
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 checklistPublic sources reviewed 2026-11-09
What the public record confirms
- Medibank's public provider guidance separates hospital, medical, ancillary and non-resident claims. Its hospital claiming information identifies ECLIPSE, while its ancillary guidance identifies HICAPS or HealthPoint terminals for direct provider claiming. There is no basis here for treating all Australian Medibank workflows as US X12 837/835/270/271 transactions.
- The medical guidance distinguishes GapCover, Medical Purchaser Provider Agreement (MPPA) and Fund Gap routes. MPPA concerns specified pathology and diagnostic services, while the public GapCover description concerns medical gaps for hospital stays. Select the applicable provider agreement and claim category before importing examples from another route.
- Services Australia's insurer function table, marked updated 22 July 2026, lists Medibank Private Limited and distinguishes patient verification, several eligibility variants, medical claims, hospital claims, overseas claims and remittance functions. Participation in ECLIPSE does not imply support for every possible operation. Confirm the exact function with current product and payer instructions.
- Services Australia's ECLIPSE registration guidance requires compatible software, a developer-issued minor ID, individual and organisation PRODA registration, the provider agreement and service linking. Those Australian channel prerequisites are distinct from Medibank's commercial arrangements and a provider's right to claim for a particular service.
- HICAPS explains that provider approval involves individual health funds, and that the registered provider number should match the practitioner delivering the service. Its public digital-card guidance names Medibank as a participating fund. A terminal or membership card alone does not settle provider recognition, benefits or approval of a separate integration.
- Medibank's non-resident guidance separates outpatient OSHC medical claims through its direct-billing portal from other hospital and GP routes. Keep resident, overseas-student and other non-resident scope explicit. This review establishes public channel distinctions, not a current technical payload version, contract-specific fee schedule or SignalEDI capability.
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.
- Program and agreement record: identify the member-cover category, provider role, service setting and applicable hospital, GapCover, MPPA, Fund Gap, ancillary or non-resident workflow.
- Claiming specification: obtain the current authorised software and payer instructions for the selected route. Record function names, required identifiers and supported corrections without copying a generic US companion guide.
- Eligibility and verification results: identify the exact Australian function used and what the returned result establishes. Keep patient matching, benefit assessment and authority to bill as separate business decisions.
- Processing and payment reports: Services Australia distinguishes ECLIPSE status, processing and remittance reports. Define their relationship to the original claim and ledger; the term remittance does not prove an X12 835 payload.
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.
- Medibank's public provider guidance separates hospital, medical, ancillary and non-resident claims. Its hospital claiming information identifies ECLIPSE, while its ancillary guidance identifies HICAPS or HealthPoint terminals for direct provider claiming. There is no basis here for treating all Australian Medibank workflows as US X12 837/835/270/271 transactions.
- The medical guidance distinguishes GapCover, Medical Purchaser Provider Agreement (MPPA) and Fund Gap routes. MPPA concerns specified pathology and diagnostic services, while the public GapCover description concerns medical gaps for hospital stays. Select the applicable provider agreement and claim category before importing examples from another route.
- Services Australia's insurer function table, marked updated 22 July 2026, lists Medibank Private Limited and distinguishes patient verification, several eligibility variants, medical claims, hospital claims, overseas claims and remittance functions. Participation in ECLIPSE does not imply support for every possible operation. Confirm the exact function with current product and payer instructions.
- Services Australia's ECLIPSE registration guidance requires compatible software, a developer-issued minor ID, individual and organisation PRODA registration, the provider agreement and service linking. Those Australian channel prerequisites are distinct from Medibank's commercial arrangements and a provider's right to claim for a particular service.
- HICAPS explains that provider approval involves individual health funds, and that the registered provider number should match the practitioner delivering the service. Its public digital-card guidance names Medibank as a participating fund. A terminal or membership card alone does not settle provider recognition, benefits or approval of a separate integration.
- Medibank's non-resident guidance separates outpatient OSHC medical claims through its direct-billing portal from other hospital and GP routes. Keep resident, overseas-student and other non-resident scope explicit. This review establishes public channel distinctions, not a current technical payload version, contract-specific fee schedule or SignalEDI capability.
Questions to resolve from the current buyer packet
- Start with the service and cover category, then confirm the provider's agreement. Do not reuse an ancillary terminal workflow for an in-patient medical claim just because both involve the same fund.
- Verify payer, provider and service-location references against current authorised records. Keep Medibank and other branded arrangements explicit rather than substituting an identifier from an older example.
- Check software support for the precise ECLIPSE function or terminal workflow. Resolve differences between broad eligibility descriptions and detailed function tables before proposing production behaviour.
- Document registration, linking and payer enablement as separate evidence. An authorised owner should handle account and banking prerequisites without exposing credentials or sensitive documents in the planning pack.
- Assign owners for rejected claims, unavailable reports, adjustments and unmatched payments. Preserve original service and submission references so an operator can investigate without creating an accidental duplicate.
- Use synthetic data for all advisory exercises. Confirm contract-specific rules, current technical revisions and permitted data handling before live activity; no compliance or production-readiness conclusion follows from this guide.
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 plansPractice 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.
Sort services into the correct claiming route
Advisory exercise: prepare fictional examples of a hospital stay, a diagnostic service, an ancillary visit and an overseas student's outpatient appointment. For each, record the intended program, service setting, cover category and agreement owner. Leave the route unconfirmed where evidence is missing rather than choosing whichever electronic channel is already familiar.
What a useful result looks like
The proposed pass condition is a clear boundary around every workflow. The same fund name cannot collapse different provider and member arrangements into one mapping. No fictional example is treated as a medical coverage decision or evidence that a claim can be submitted.
Match function support to requirements
Advisory exercise: create a local requirements sheet for patient verification, eligibility, claim submission and reporting. Attach the current public function reference and identify the authorised technical material needed for each detail. Add one deliberately unresolved operation so the reviewer must distinguish a broad channel description from evidence for the specific requested capability.
What a useful result looks like
Every proposed operation has a supported, unsupported or unconfirmed decision. Participation in the network cannot automatically satisfy all rows. An unresolved difference stays with a named owner and prevents the planning record from being reported as completed production validation.
Verify provider identity before a mock submission
Advisory exercise: model a practice with two fictional practitioners and one newly added location. Trace the responsible provider, location and payer arrangement through a proposed claim. Introduce a mismatched identifier and decide where it should stop for review. Keep all account, card and bank details synthetic and make no changes to real enrolments.
What a useful result looks like
The mock result identifies the mismatch without silently substituting another practitioner's identity. Operational ownership is clear and any missing approval remains visible. A working terminal or existing software account cannot stand in for the correct provider relationship.
Reconcile an uncertain claim outcome
Advisory exercise: walk through a synthetic submission, an interrupted response, a later assessment and an unmatched payment. Record which authorised status or report would resolve each question and who should review it. Preserve the original claim reference and adjustment history while defining the next check, without sending another live request or guessing a payment outcome.
What a useful result looks like
The proposed result is an auditable exception trail with deliberate reconciliation. Transport success, claim assessment and financial settlement stay distinguishable. The exercise provides preparation evidence only and makes no assertion that SignalEDI can exchange or reconcile Medibank production data.
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.
- Medibank hospital claiming — Medibank
Supports: Publicly indexed official guidance identifies ECLIPSE hospital submission; no authenticated technical packet was reviewed.
- Medibank ancillary claiming — Medibank
Supports: Publicly indexed official guidance names HICAPS or HealthPoint terminals for direct ancillary provider claims.
- Medibank MPPA billing channel — Medibank
Supports: Publicly indexed description of the pathology and diagnostic-services billing channel.
- Medibank GapCover scheme — Medibank
Supports: Publicly indexed description of the medical gap scheme and hospital-stay context.
- Medibank non-resident claiming — Medibank
Supports: Publicly indexed distinctions between non-resident hospital, GP and outpatient OSHC routes.
- Services Australia ECLIPSE insurer functions — Services Australia
Supports: Directly reviewed Medibank participation and function-specific matrix, updated 22 July 2026.
- Services Australia ECLIPSE registration — Services Australia
Supports: Software, minor ID, PRODA, provider agreement and service-linking prerequisites.
- Services Australia processing and payment reports — Services Australia
Supports: Separate ECLIPSE status, processing and remittance reporting and software-dependent presentation.
- HICAPS claim rejection guidance — HICAPS
Supports: Individual-fund provider acceptance and matching the registered provider to the treating practitioner.
- HICAPS digital membership cards — HICAPS
Supports: Directly reviewed public confirmation of Medibank digital-card participation at HICAPS terminals.
Medibank questions
- Does Medibank use the same electronic channel for every claim?
- No. Public provider guidance distinguishes hospital and medical ECLIPSE workflows, ancillary terminal claiming and non-resident arrangements. Choose the service category, cover and provider agreement first. The selected route's current instructions determine the required fields and supported operations; a universal US healthcare transaction list does not establish them.
- What should I verify before planning Medibank eligibility and payment handling?
- Confirm the exact supported verification or eligibility function, software release and provider arrangement. Review how claim assessment and applicable reports work for that route, then identify the ledger references needed for reconciliation. Fund participation, a matched patient and a final payment each require their own evidence.
- Does this Medibank guide prove SignalEDI can send Australian claims?
- No. It is public preparation guidance with advisory local scenarios. It does not establish a SignalEDI-approved software product, Medibank commercial agreement, production access or permission to process patient data. Confirm the specific product and provider approvals independently before considering any live exchange.
Related EDI resources
- Customer requires EDI guide turns the buyer packet into a scoped implementation checklist.
- QuickBooks EDI integration explains supported accounting workflows. Confirm system edition and document scope; it does not establish a connector for this program.
- Managed EDI onboarding is an optional paid path when your team wants help coordinating the scoped partner workflow.
- Walmart EDI requirements covers publicly documented supplier interfaces and buyer-packet boundaries for Walmart programs.
- EDI requirements checker drafts a local readiness checklist without saving buyer data.
Prepare your side for partner testing
SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.
Connect nowTopics: Medibank EDI requirements · Medibank supplier EDI · Medibank EDI AU