Same Day Delete | RebateRight

Same Day Delete lets a practice withdraw an interactive patient claim that was sent earlier the same calendar day. Medicare only allows the delete when the original claim was accepted and assessed (final status MEDICARE_ASSESSED).

Matching the original submission: use the same transaction correlation, location context, and patient details as the claim you are withdrawing, sent through this API.

Headers and registration: use the same Medicare claiming header pattern as your other interactive patient claims (including dhs-correlationId and dhs-auditId, which Medicare uses in its business rules). Your organisation must have suitable PRODA access and a Notice of Intent (NOI) that covers interactive claiming and same-day delete.

Messages from Medicare: when you surface errors to end users, show serviceMessage[].reason exactly as returned — do not shorten, paraphrase, or “improve” the wording.

Field rules, lengths, formats, and examples are on the request body, 200, and 400 schemas below.

Same Day Delete lets a practice **withdraw an interactive patient claim** that was sent **earlier the same calendar day**. Medicare only allows the delete when the original claim was **accepted and assessed** (final status **`MEDICARE_ASSESSED`**). **Matching the original submission:** use the **same transaction correlation**, **location context**, and **patient details** as the claim you are withdrawing, sent through this API. **Headers and registration:** use the same Medicare claiming header pattern as your other interactive patient claims (including `dhs-correlationId` and `dhs-auditId`, which Medicare uses in its business rules). Your organisation must have suitable **PRODA** access and a **Notice of Intent (NOI)** that covers interactive claiming **and** same-day delete. **Messages from Medicare:** when you surface errors to end users, show **`serviceMessage[].reason`** **exactly as returned** — do not shorten, paraphrase, or “improve” the wording. Field rules, lengths, formats, and examples are on the **request body**, **`200`**, and **`400`** schemas below.

Authentication

x-api-keystring

API Key authentication via header

x-minor-idstring

API Key authentication via header

Request

Body for a same-day delete. It identifies the original claim’s transaction and supplies the patient and reasonCode Medicare uses to validate the delete.

Medicare ties the delete to the original claim using dhs-correlationId (transaction correlation) and dhs-auditId (location / audit context), together with the values in this JSON.

Body for a same-day delete. It identifies the **original claim’s transaction** and supplies the **patient** and **reasonCode** Medicare uses to validate the delete. Medicare ties the delete to the original claim using **`dhs-correlationId`** (transaction correlation) and **`dhs-auditId`** (location / audit context), together with the values in this JSON.

correlationIdstringRequired

Correlation / transaction id for the original interactive claim to delete. It must refer to a claim Medicare can match for the same calendar day and same location as this delete request. If nothing matches, Medicare often returns 9775 (see the 400 response — serviceMessage[].code).

Correlation / transaction id for the **original** interactive claim to delete. It must refer to a claim Medicare can match **for the same calendar day** and **same location** as this delete request. If nothing matches, Medicare often returns **`9775`** (see the **`400`** response — `serviceMessage[].code`).

sameDayDeleteobjectRequired

Patient identity and Medicare card details must match the original claim. reasonCode is required.

Response

OK — delete accepted. When Medicare removes the claim, status is SUCCESS.

statusenum

Outcome when Medicare accepts the same-day delete.

Value	Meaning
`SUCCESS`	Same-day delete processed; the claim is removed at Medicare.

Allowed values:

correlationIdstring

Optional echo of the request correlation id for support tracing — not always returned.

Errors

400

Bad Request Error

Matching the original submission: use the same transaction correlation, location context, and patient details as the claim you are withdrawing, sent through this API.

Messages from Medicare: when you surface errors to end users, show serviceMessage[].reason exactly as returned — do not shorten, paraphrase, or “improve” the wording.

Field rules, lengths, formats, and examples are on the request body, 200, and 400 schemas below.

1	curl -X POST https://api.rebateright.com.au/Medicare/samedaydelete/v1 \
2	-H "x-api-key: <apiKey>" \
3	-H "Content-Type: application/json" \
4	-d '{
5	"correlationId": "urn:uuid:MDE00000ba81c42faf654e8b",
6	"sameDayDelete": {
7	"patient": {
8	"identity": {
9	"givenName": "Clint",
10	"familyName": "FLETCHER"
11	},
12	"medicare": {
13	"memberNumber": "4951525561",
14	"memberRefNumber": "3"
15	}
16	},
17	"reasonCode": "001"
18	}
19	}'

1	{
2	"status": "SUCCESS",
3	"correlationId": "urn:uuid:MDE000001d00753cdd504109"
4	}