Claims
Approval back before the patient leaves.
EzRx is the insurance side of the counter — eligibility, prior approval, submission, remittance download and denial correction — live on Shafafiya, DHPO and NPHIES, and connected to eRx. It runs inside EzPOS, so a pharmacist never leaves the till to work a claim.
1M+
claims processed
3
payer gateways live
1 day
to onboard*
* Hardware and network ready on the day. Connecting your payer mailbox is scoped separately.
Approved and connected
The gateways this product is live on.
LOGO
Shafafiya
LOGO
DHPO
LOGO
NPHIES
LOGO
eRx
LOGO
OpenJet
LOGO
Daman
What it does
Every step between the prescription and the payment.
Most pharmacies lose money in the gap between dispensing and being paid — a denial nobody chased, a remittance nobody matched. EzRx closes that gap inside the dispensing workflow, not in a separate system somebody logs into on Thursdays.
Prescriptions in
eRx prescriptions download straight into the till, external portals such as OpenJet come in the same way, and offline or cash prescriptions are handled in the same queue.
Eligibility and prior approval
Online approval requests to the insurer, with the answer back before the medicine is handed over.
Submission
Claims for online and offline prescriptions submitted to the payer through the Shafafiya, DHPO or NPHIES mailbox.
Remittance and reconciliation
Prior requests, authorisations, submissions and remittances downloaded from the mailbox and matched, so you can see what was paid against what was claimed.
Denial correction
Denied claims are shown with their reason, corrected and resubmitted rather than written off at month-end.
Clinical safety on the way through
Drug-to-drug interaction warnings, recorded patient allergies, prescription history and Daman tier calculation as the medicine is selected.
A day on the floor
How the claim actually goes.
STEP 01
The prescription arrives
It downloads from eRx or an external portal into the POS queue, with the patient's insurer, plan and TPA already attached.
STEP 02
The insurer answers
The approval request goes out and comes back while the patient is still at the counter. Interactions and allergies flag as the pharmacist selects.
STEP 03
The claim goes out
Dispensing generates the claim, which is submitted to the payer mailbox with the tier calculation applied.
STEP 04
The money is matched
Remittances download and reconcile against submissions. Denials come back with a reason, get corrected, and go out again.
Inside the product
Modules, in the order you'd meet them.
Three screens between the prescription and the bank. Each one closes a way for a pharmacy to work for free.
Prescription queue
Where dispensing starts: eRx and portal downloads, offline and cash prescriptions, prescriber and patient records, allergies and history. The pharmacist works one list instead of three screens.
eRx download Patient history
Approvals and submission
Where the claim is made: eligibility, prior authorisation, submission of online and offline claims, and the insurer, plan and TPA records behind them.
Prior approval Shafafiya & DHPO
Reconciliation and denials
Where the money is recovered: remittance download, claim status, denial reasons, correction and resubmission. Rejections become work items rather than losses.
Remittances Resubmission
Proof
One customer, one number, one quote.
[Customer quote to come — two sentences from a named operator at a named site.]
[Name Surname]
[Role · Organisation]
[00%]
Outcome measured
[00m]
Outcome measured
Deployment
One day on an existing EzPOS site — we register your insurers, plans and TPAs, load the authority prescriber list, and run the first submissions with your team watching. Connecting your Shafafiya, DHPO or NPHIES mailbox depends on the authority's own onboarding, which we take care of but do not control the clock on.
Works with
Pairs with the rest of the suite.
Each of these does its own job. Most customers add the next one once the first has paid for itself.
EzPOS
EzRx is the payer side of the same counter — the prescription, the approval and the claim never leave the till.
CCMS
When a chain wants one central team working every branch's claims rather than a pharmacist per site.
EzDx
Clinic prescriptions and claims run on the same payer connections.
AMS
Insurer payments arrive as identified receipts against receivables instead of unexplained bank lines.
Questions
The four things buyers ask first.
What it is, who it reaches, what happens to a rejection, and what a patient record shows.
Is EzRx separate software, or part of EzPOS?
It runs inside EzPOS — the prescription, the approval and the claim are steps in the same workflow, against the same database on your own server. It is licensed as its own product because plenty of pharmacies buy the claims side first, and because it is the piece that pays for itself fastest.
Which insurers and gateways are you live on?
Approvals, claims and remittances go through Shafafiya in Abu Dhabi, DHPO in Dubai and the Northern Emirates, and NPHIES in Saudi Arabia — so every payer on those three gateways. Prescriptions download from eRx and external portals, and Daman tier calculation is built in.
What happens to a claim the insurer rejects?
It appears in the reconciliation queue with its denial reason. You correct it and resubmit from the same screen — which is the whole point of having claims in the dispensing system rather than in a spreadsheet.
Can we see what an individual patient was dispensed and claimed for?
Yes, in the patient profile: prescription history, recorded allergies, and the claims raised against each visit.
See it on your own workflow.
Tell us which authority licenses you and what you run today. We'll configure the walkthrough for your market — thirty minutes, no slide deck.
A specialist replies within one working day
Onboarded in one day once you are ready
We review your data migration before you commit