Why health insurance claims are rejected in Saudi Arabia

A technical rejection means the claim is wrong as data. A field is missing, a code was not valid on the date of service, the policy was inactive, or prior authorization was never obtained. The care itself may have been entirely appropriate.

A medical rejection means the reviewer did not find enough clinical reason, in what was submitted, for what was billed. The reviewer sees only what was written, so a reason the physician had but never recorded does not count.

A third group is coverage: the policy does not pay for the service, the medicine or the provider, or a benefit limit has been reached. NPHIES sorts its rejection reasons into five groups: administrative, billing, coverage, medical necessity and supporting evidence. Reasons such as an inadequate chief complaint or examination, or a service that is not clinically justified, fall under the last two.

The two kinds start in different places, are caught by different checks and are fixed by different people. Treating every rejection as a billing problem leaves the medical kind to repeat.

The team that receives a rejection is often not the one that caused it. Billing sees every rejection, but causes only some of them.

• Reception: an inactive policy, member details that do not match the policy, or a service that needed prior authorization nobody requested.
• Physician: the chief complaint, findings, diagnoses and orders written during the consultation. This is where medical rejections begin.
• Coder: codes that are invalid, incomplete, or more or less specific than the note supports.
• Billing: format errors, duplicate lines, late submissions, and claims that do not match the authorization.

Coverage rules, authorization requirements and submission periods vary by insurer and by policy, so the same service can be paid for one patient and rejected for another.

A medical rejection comes down to a missing link between the note and a line on the claim. These are the patterns to look for.

• The diagnosis does not explain the service: a chest X-ray, for example, with nothing in the note to say why it was needed.
• The diagnosis is less specific than the note allows, so it no longer explains what was ordered, such as an antibiotic.
• The diagnosis is more specific than the note supports: a confirmed diagnosis billed without the findings or results that confirm it.
• The medicine is not indicated for any diagnosis on the claim, or its dose, duration or quantity goes beyond what the record explains.
• The note is too thin: a one-word chief complaint such as "pain", an examination copied from a normal template, no duration and no severity.

Each service is judged on its own, so a claim is often paid in part. The lines the note supports are paid and the others are rejected.

The revision works only because the cough, the fever and the crackles were real. Documentation describes what was found; it is never adjusted to fit what is billed.

A technical rejection is usually a data error that whoever finds it, often in billing, can correct and resubmit.

A medical rejection is about evidence written during the consultation. After the visit, fixing it means pulling the record and finding the physician. If the reason existed but was not written, a dated addendum marked as added later may be possible under the clinic's records policy. If it never existed, there is nothing honest to add.

Medical rejections also repeat. The habit behind one, such as a brief chief complaint or the same set of orders for every cough, produces the same rejection at the next visit. Correcting claims one at a time does not change the habit.

Rule-based claim scrubbers help little here. They check fields and fixed rules, not the note.

A checklist before a claim goes out:

• The policy was active, and the service covered, on the date of service.
• Services that need prior authorization have it, and the claim matches what was authorized in service, quantity and dates.
• Codes are valid on the date of service, and no line duplicates an earlier claim.
• Each billed service has a diagnosis on the claim that calls for it.
• Each diagnosis is coded to the level of detail the note supports, and no further.
• Each medicine is indicated for a diagnosis on the claim, with a dose, duration and quantity the record explains.
• The chief complaint says what the symptom is, where, for how long and how severe, and the note gives a reason for each order.

The first three belong to reception and billing; where they depend on the insurer's rules, check the contract and the policy. The last four need the physician, and are cheapest to check while the note is open.

• Technical rejections are about claim data. Medical rejections are about whether the note supports what was billed.
• Technical problems start at reception, coding and billing, and are usually fixed by correcting the data.
• Medical problems start in the consultation, and only the physician can say what was found and why each service was ordered.
• Medical rejections cost more after the visit, and repeat until the habit behind them changes.
• The best time to check whether the documentation supports the claim is while the note is being written.