DVA testing
Provider details
To get going quickly, we have 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 Tyro Health Online support team at hello@medipass.com.au for access credentials and API keys. Alternatively, you can use the details listed below:
| Provider type | Provider number | Last name | First name |
|---|---|---|---|
| Physiotherapist | 2429581T |
Han |
Clifton |
| General Practitioner | 2409661B |
Miranda |
Raphael |
| Medical Specialist | 2429591L |
Browning |
Charlene |
Valid patient test details include:
| Veteran File No | Last name | First name | Date of birth |
|---|---|---|---|
| QX901543 | FIONA | ANNE-MARIE | 10/04/1954 |
| QX901544 | GRAHEME | DIMITRY | 27/05/1961 |
| QX901545 | JACKI | GERRY | 13/07/1969 |
| QX901546 | KEVIN | JADE | 28/09/1956 |
DVA simulated responses
Medicare Bulk Bill 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
| Sub Text | Level | Expected Response | Notes |
|---|---|---|---|
| STUB_OK | Submissions (required) | Submission succeeds | |
| STUB_DOWN | Submissions (required) | Submission fails with 3004 (medicare down) | Claim will be successful after the next batch run. Approx every 2 hour |
| STUB_FAIL | Submissions (required) | Submission returns a fail 3999 | Claim will not be resubmitted |
| STUB_FAIL_XXXX | Submissions (required) | Submission returns a fail XXXX | Replace XXXX |
| STUB_PROCESSING_ITEM_FAIL | Processing claim item | Processing report returns with Explanation code 160 | |
| STUB_PROCESSING_ITEM_FAIL_XXX | Processing claim item | Processing report returns with Explanation code XXX | Links to return codes: Medicare/, |
| STUB_PAYMENT_FAIL | Payment | Payment report returns with fail 8002 | |
| STUB_PAYMENT_FAIL_XXXX | Payment | Payment report returns with fail XXXX |
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 explanation 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.