Medical Aid Claim Switching in South Africa: RocketSwitch EDI Explained
How HeroMed's built-in RocketSwitch EDI takes a South African medical aid claim from the signed consult note to scheme response, rejection fix and remittance — in one platform.
If you bill medical aids in South Africa, every consultation ends with a claim — and how quickly you learn whether it was accepted decides how quickly you get paid. In HeroMed, that whole journey runs through RocketSwitch EDI, HeroMed's built-in claim switching, unlocked by the AI Invoicing Hero for South African practices.
This guide walks through how a claim moves in HeroMed, why claims get rejected, and how RocketSwitch EDI handles submission, rejections and remittances from one screen.
How a claim travels in HeroMed
Consult → AI Scribe note (signed) → ICD-10 + tariff codes → invoice
→ RocketSwitch EDI pre-flight checks → submission → scheme response
→ amend & resubmit if needed → payment run → ERA matched to claim lines
Everything happens in the same platform as the diary, the patient record and the clinical note, so nothing is retyped between steps.
Accurate billing starts in the consult room. HeroMed Core AI includes an AI Scribe that drafts the consultation note while you consult. For South African practices, adding the AI Invoicing Hero unlocks RocketSwitch EDI, so the claim is built from the signed note and submitted from the same platform. Start a 14-day free trial.
What RocketSwitch EDI does
- Pre-flight checks before submission. Medical aid details, member and dependant details, billed lines and tariff validity are checked before the claim leaves, and anything missing is flagged so it can be fixed first.
- Eligibility and family checks. Confirm membership and the right dependant before you bill.
- Consult to claim in one click. The claim is built from the signed AI Scribe note and invoice.
- Real-time responses where the scheme supports them. Outcomes come back line by line — accepted in full, part paid with patient liability, or rejected with the reason in plain language.
- Amend and resubmit immediately. Fix the flagged item and resubmit on the spot.
- Reversals where the scheme allows. Reverse a claim, correct it and resubmit from the same screen.
- RocketSwitch pipeline and bulk switching. Track every claim from invoiced to awaiting response, accepted, part paid or rejected, and switch a batch of claims in one go.
- ERAs built in. Electronic remittance advices are matched back against the original claim lines, and patient-liability balances are tracked so your front desk knows what to collect.
Why claims get rejected — and how RocketSwitch EDI helps
The recurring causes are consistent:
- Membership lapsed, suspended, or dependant code wrong
- Benefit exhausted, or the service falls outside the plan option
- ICD-10 code missing, invalid, or not supported by the procedure billed
- Tariff code not valid for your discipline or practice number
- Duplicate claim, or claim submitted outside the scheme's time limit
- PMB or authorisation requirements not met
Many of these are caught by RocketSwitch EDI pre-flight checks before the claim is sent. The rest come back as a clear reason on the claim, ready to fix.
| What the response says | What it usually means | What to do in HeroMed |
|---|---|---|
| Member not found / not active | Membership lapsed, suspended, or captured wrong | Re-check membership, correct and resubmit the same day |
| Invalid dependant code | Claim billed against the wrong family member | Confirm the dependant, resubmit |
| Benefit exhausted / not covered | Outside the plan option or day-to-day benefit used up | Move to patient liability and collect before the patient leaves |
| ICD-10 invalid or unsupported | Diagnosis code missing, retired or inconsistent with the procedure | Re-code from the clinical note, resubmit |
| Tariff not valid for practice number | Code not billable for your discipline or registration | Check the tariff and practice-number setup |
| Duplicate claim | The claim was already submitted | Check the original response in the pipeline first |
| Outside submission window | Scheme time limit passed | Follow up with the scheme; submit daily from now on |
| Authorisation / PMB requirement not met | Pre-authorisation was needed | Add the authorisation number and resubmit |
Accepted is not the same as paid
Acceptance means the scheme received a valid claim. Payment follows the scheme's cycle, and the remittance may reduce lines, apply co-payments or shift amounts to patient liability. RocketSwitch EDI matches each ERA back to the claim lines, so shortfalls show up straight away instead of weeks later — see our cash flow guide for the 30-day version.
Timing: what happens when
- At capture: pre-flight checks flag gaps before submission.
- Seconds after submission: the scheme response, where the scheme supports real-time responses.
- Same day: work rejections in the pipeline and resubmit.
- Scheme payment cycle: payment runs, typically weekly or fortnightly.
- After payment: the ERA is matched against the original claim lines, and any shortfall moves to patient liability.
A short claim-hygiene checklist
- Check membership and dependant at check-in.
- Code from the signed clinical note, not from memory.
- Submit daily — never batch a week of claims.
- Work the RocketSwitch pipeline every morning.
- Let ERAs reconcile against claim lines, then follow up shortfalls.
- Invoice patient-liability balances the same week they appear.
Related reading
Skip the back-and-forth. Start your free trial.
14 days free — no credit card, no lock-in. Log in, run a real week, and decide on your own terms.