Servicing Provider Eligibility | RebateRight

This endpoint checks whether a servicing (rendering) provider may perform and claim an MBS item. It runs before the claim is lodged, so RebateRight catches a wrong-provider rejection before Medicare assesses the claim.

The check runs entirely within RebateRight. It needs only a ProviderNumber and an ItemNumber, with no patient details and no request to Medicare. That makes it fast enough to check every line of a batch.

Provider Atlas: every specialty and credential

Every eligibility answer rests on the recognitions Medicare holds for the provider. The Provider Atlas maps every recognition, and shows how the same recognitions decide who may render, claim and refer each item.

The sources behind every check

RebateRight resolves the answer from the authoritative sources that govern who may render an item:

Provider recognitions

The specialties, fields and credentials Medicare recognises for the provider. RebateRight expands them through its recognition hierarchy, so a rule that allows a broad class, such as a specialist medical practitioner, also covers every sub-specialty beneath it.

MBS item structure

The item’s MBS category, group and sub-group, each mapped to the specialties eligible to render its items. The item’s own descriptor can override the group rule where that item is tighter or broader.

Legislative determinations

The Diagnostic Imaging, Pathology and General Medical Services Tables on the Federal Register. This legislation sets, item by item, which providers may render and bill a service, beyond what the descriptor alone states.

MBS explanatory notes

Conditions a specialty alone cannot express, such as Approved Pathology Practitioner status, MRI licensing or supervision rules. RebateRight names these in Reason for you to verify separately, with the MBS reference.

To stay accurate, RebateRight continually reconciles its determinations against Medicare. The result is advisory. Medicare makes the binding decision when it assesses the claim.

Reading the result

A 200 always returns a boolean IsEligible and a plain-language Reason. Three shapes come back:

IsEligible: true with a specialty named. One of the provider’s specialties may render the item. Reason names the matching specialty and the MBS group or item rule it satisfied.
IsEligible: true, no rule held. RebateRight holds no servicing rule for this item or its MBS group, so the provider is not checked. Reason says no restriction is recorded. Treat this answer as unchecked, not as a finding that any provider may render the item.
IsEligible: false. None of the provider’s specialties may render the item. Reason lists the provider’s specialties beside the specialties eligible to render the item.

Where an item carries a further condition the API cannot confirm from a provider number, such as a credential, supervision or accreditation rule, Reason ends with a “verify separately” note and the MBS reference.

Status codes

200: the check ran. Read IsEligible and Reason.
400: a required field is missing, a field name is not recognised or the request body could not be parsed. The body is plain text.
404: the ProviderNumber or ItemNumber was not found. The body is plain text, shown in the 404 example.

Authentication

x-api-keystring

API Key authentication via header

Request

This endpoint expects an object.

ProviderNumberstringRequired

The servicing provider’s Medicare provider number, exactly as issued (case-sensitive, including the location and check-digit characters).

ItemNumberstringRequired

The MBS item number being checked.

Response

The check ran. Read IsEligible and Reason.

IsEligibleboolean

Whether the provider is eligible to perform and claim the item. It is also true when RebateRight holds no servicing rule for the item, and in that case the provider is not checked.

Reasonstring

Plain-language explanation of the eligibility decision, naming the matching or eligible specialties, the MBS group or item rule applied, and any “verify separately” note.

Errors

400

Bad Request Error

404

Not Found Error