Test data

Patient / Claimant details

To get you going quickly, we’ve created the following test patients / claimants:

Note that some stubs track claims against each patient and so duplicate claim attempts (same provider, same patient, same day, same item code) may be automatically declined by the system. Note for Comcare claims, a specific combination of DOB and claim number is required. See "Comcare details" below.

Note for Comcare claims, a specific combination of DOB and claim number is required. See "Comcare details" below.

Test details for each funding type are as follows:

• Payment cards
• Medicare details
  • Concession details
  • DVA details
• HICAPS details
• Comcare details
• icare details
• WSV deatils

Payment card details

Use a valid test card number:

Payment card can have any valid expiration, some have set responses:

• Note: At present, the Medipass STG environement is connected live to payment card schemes test networks. Payment schemes do not always honour simulated timeout/expired responses.

Payment card CSC/CVV can be one of:

Apple Pay and Google Pay

Note that these payment options require a special setup for testing and can be problematic.

Generally, Google Pay can only be tested in production. Contact the Medipass support team at hello@medipass.com.au for other testing options.

For Apple Pay, follow the Create a Sandbox Tester Account and Test Card Number instructions as posted by Apple: https://developer.apple.com/apple-pay/sandbox-testing/

Medicare details

Valid test details include:

Alternative / exception test details include:

Concession details:

Medicare Bulk Bill and DVA simulated responses

Medicare Bulk Bill and DVA submissions are usually processed overnight. To quickly simulate responses (and test configured webhooks), transactions can be stubbed. Stubs can be applied at multiple levels:

• Submission
• Processing
• Processing claim item
• Payment

Stub text(s) are applied on claim item's Service Text field and should be set on the first claim item of the claim, with the exception of STUB_PROCESSING_ITEM_FAIL, which can differ for each claim item. Stub outcome can also be applied on different levels ie. Submission, Processing claim item, Payment. To initiate a stub, Submission level is mandatory.

Examples:

• STUB_OK;STUB_PROCESSING_ITEM_FAIL_123: Submission submits successfully, but processing report returns an explaination code of 123 and results in no benefits paid for the item.
• STUB_DOWN;STUB_PAYMENT_FAIL_1234: Submission failed because medicare was down. After a couple of hours, re-submission succeeds with a successful approval of claim. Payment fails with an error code of 1234

DVA details

Provider details

To get going quickly, we’ve created test business, practice and providers. Each test business has:

• two practice locations
• three providers: one allied healthcare professional, one GP and one Medical Specialist
• Providers enabled for claims across all HICAPS funds, all Medicare functions, all CTP / icare functions
• A merchant account enabled for all card payments

Contact the Medipass support team at hello@medipass.com.au for access credentials and API keys.

Alternatively, you can use the details listed below:

Servicing providers

Payee providers

(Medicare only) Any valid servicing provider can be used as payee provider.

Referee providers

HICAPS details

For patients/members:

• Select any supported health fund
• You can input any data for a health fund card as long as it passes the input validation:
  • Any membership number, some may require an alpha character where noted
  • Any card issue number where prompted - start with ‘01’, else if card issue date enter any previous date
  • A unique patient identifier - start with ‘01’

simulated HICAPS claim responses

The health fund claiming engine is stubbed in non-production environments. By default, claims are successful with each item receiving a 60% benefit (rounded to the nearest dollar less than the benefit). You can use other dollar amounts to simulate different scenarios:

Payment and health fund physical cards

Test payment and health fund cards can be arranged for testing. Contact the Medipass support team at hello@medipass.com.au to arrange test cards.

Comcare details

Claims submitted to Comcare are validated by claim number and DOB. Of note, the format of the claim number must include a forward slash followed by two digits. For testing purposes, any patient name can be used with the following claim numbers and DOB:

Note:If the above details do not work please contact our integration team partnerships@medipass.io.

Stubbing

For Comcare injured worker insurance claims, any patient name can be used with the following claim number

To receive a simulated response :

• 7777/77

To receive a simulated rejection:

icare details

For workers insurance claims, any patient name can be used with the following claim numbers:

To receive a simulated response

• 7777777

To submit to icare's testing environment claiming engine

• 4000162
• 4001079

simulated icare claim responses

The icare test claiming engine will not generate a response unless manually triggered by icare staff. Please contact us if this is required. It is preferred where possible to test using simulated responses. Only specified claim numbers above will receive a simulated response. By default, all claims from these numbers will receive an approved response from the stub. To simulate other responses, see the following table:

WSV details

The WSV test claiming engine will not generate a response unless manually triggered by WSV staff. To test cases where invoices go “Under Review” Please contact us . It is preferred where possible to test using simulated responses. Only the specified claim numbers below will receive a simulated response.

Providers:

Claims: