Three Countries, Three Coding Systems, One Very Common Mistake
A mid-sized RCM firm based in Dubai wins its first Saudi hospital client. It already codes UAE claims daily, so the operations team assumes the transition will be straightforward: assign the work to existing coders, adjust a few payer rules, and go live. Within sixty days, denial rates on the Saudi book are running at nearly 30 percent. The coders were skilled. The problem was that nobody had acknowledged they were being asked to operate in an entirely different coding system.
This is not an edge case. It is one of the most predictable failure modes for GCC billing companies and TPAs expanding across borders. The assumption that coding expertise transfers cleanly between Saudi Arabia, the UAE, and Qatar costs RCM firms client trust, rework hours, and sometimes the client relationship entirely. The truth is blunt: a coder trained and audited against one country's standards is not automatically competent in another's. Building a multi-country GCC coding team means building what are effectively three separate coding functions, and the org design decisions you make at the start will define your accuracy and your margin for years.
The Three Systems Are Not Dialects of the Same Language
It helps to be precise about just how different these three environments are, because the differences are not cosmetic.
Saudi Arabia: ICD-10-AM, ACHI, AR-DRG via NPHIES
Saudi Arabia's Council of Health Insurance mandates coding in ICD-10-AM (the Australian modification) alongside ACHI procedure codes and the Australian Coding Standards. Inpatient reimbursement runs through AR-DRG version 9.0 for case-mix grouping. Claims flow through NPHIES, the national platform that has its own structural and validation logic sitting on top of the clinical coding. A coder working Saudi accounts has to understand how principal diagnosis selection under Australian Coding Standards affects DRG assignment, and how NPHIES edits will fire based on that grouping. The ACS rules on sequencing, complication coding, and procedure classification are specific enough that even experienced coders from other systems need dedicated training before they are production-ready on Saudi work.
UAE: ICD-10-CM, CPT, IR-DRG via eClaimLink and Shafafiya
The UAE operates on ICD-10-CM for diagnosis coding and CPT for procedures, which is the American model. Inpatient claims are grouped through IR-DRG using 3M's grouper logic. Dubai Health Authority claims go through eClaimLink; Department of Health Abu Dhabi claims go through Shafafiya. These are separate platforms with different submission requirements, different pre-authorization workflows, and different payer-specific rules layered on top. A coder who knows ICD-10-AM and ACHI intimately may have never assigned a CPT code in their career. The procedure coding vocabulary is entirely different: ACHI is a hierarchical Australian classification; CPT is a five-digit American system with its own modifiers, bundling rules, and RVU logic.
Qatar: ICD-10-AM and QOCS via MOPH
Qatar uses ICD-10-AM for diagnoses, which superficially resembles Saudi Arabia's system. But Qatar's outpatient classification runs on the Qatar Outpatient Classification Scheme, and claims are governed by the Ministry of Public Health under mandatory insurance established by Law No. 22 of 2021. The patient minimum data set requirements, the outpatient grouping logic under QOCS, and the payer environment in Qatar are distinct from Saudi Arabia even where the underlying coding classification looks similar. Coders assuming that Saudi ICD-10-AM experience makes them Qatar-ready routinely miss documentation requirements and outpatient coding rules that are specific to the Qatari system.
The surface-level similarity between Saudi and Qatar coding is arguably more dangerous than the obvious gap between UAE and the other two. It breeds overconfidence.
Why Cross-Training Generalists Looks Efficient and Usually Is Not
When an RCM company starts expanding across GCC markets, the instinct is to train existing coders on the new country's rules rather than hire dedicated staff. This keeps headcount down and avoids the difficulty of recruiting in a tight labor market. The logic is understandable. The outcome, in most cases, is compromised accuracy in at least one of the markets being served.
A coder handling Saudi accounts in the morning and UAE accounts in the afternoon is switching between ICD-10-AM principal diagnosis sequencing under Australian Coding Standards and ICD-10-CM with CPT modifiers within the same shift. These are not minor adjustments. They are different coding philosophies, different documentation habits to look for, and different audit standards. The cognitive load of context-switching between systems is real, and it shows up in error rates.
The stronger model for a multi-country GCC coding team is country-dedicated coders: teams whose production, QA, and continuing education are organized around one system. This is more expensive to build internally. But it is the only configuration that can hold accuracy standards as volume grows. The generalist approach works at low volume, where a single senior coder can manage two books carefully. It breaks down at scale, exactly when client expectations and SLA commitments are highest.
You can read more about how this structure affects client delivery in our post on coding SLAs for GCC RCM companies.
QA and Audit Cannot Be a Single Pooled Function
One of the cleaner diagnostic questions for any RCM company's coding operation is: does your QA team audit Saudi work against Saudi standards and UAE work against UAE standards, with auditors who hold country-specific expertise? Or does a single audit team review everything against a generic accuracy checklist?
Pooled QA is common because it is cheaper to staff. It is also nearly useless for catching country-specific errors. An auditor who does not understand AR-DRG grouping logic will not catch the principal diagnosis sequencing error that is inflating your Saudi DRG assignments. An auditor unfamiliar with CPT bundling rules will not identify the unbundling pattern generating your UAE denials. The audit function has to mirror the country structure of the coding function, or it is providing a false sense of quality control.
Our coding quality audit function is organized exactly this way: country-specific auditors reviewing against the actual payer and platform standards relevant to each market, not against a generalized accuracy metric. That structure is what makes audit findings actionable rather than cosmetic.
Country-specific QA also matters for client reporting. When a Saudi hospital client asks about its coding accuracy, it wants to know its first-pass acceptance rate on NPHIES, its principal diagnosis accuracy against ACS rules, and its DRG validation rate. If your QA system cannot generate those metrics separately from your UAE and Qatar books, you cannot have a credible conversation with that client about quality.
The Build Versus Outsource Decision at Each Country Launch
For a GCC billing company or TPA evaluating its next country expansion, the build-versus-outsource question is not abstract. It has a real cost on both sides.
Building internally means recruiting coders with demonstrated country-specific competency, which is genuinely difficult in a market where Saudi-trained ICD-10-AM/ACHI coders and UAE-trained ICD-10-CM/CPT coders are both in short supply. It means standing up country-specific QA. It means investing in platform-specific training for NPHIES, eClaimLink, Shafafiya, or whatever system governs the new market. It means absorbing the ramp time before those coders are producing at an accuracy level that can hold your SLAs. During that ramp, someone is covering the gap, usually by stretching coders who already have full books in other countries.
Outsourcing the coding function to a partner that already has dedicated country-specific teams, existing platform knowledge, and an established audit structure removes most of that ramp risk. The critical question is whether the partner is actually organized by country or is offering you the same generalist pool with a different label. This is where due diligence matters.
Grab the free GCC Claim Rejection Prevention Checklist to see the specific questions worth asking before trusting a new coding partner with a market entry.
What to Ask a Potential Coding Partner Before Trusting Them With a New Country
Any coding partner worth considering for a multi-country GCC operation should be able to answer these questions specifically, not in generalities.
- How many of your coders hold current certification or demonstrated production experience in ICD-10-AM and ACHI specifically, as distinct from ICD-10-CM? Can you show us sample audit scores for Saudi accounts?
- Do you have separate QA tracks for Saudi, UAE, and Qatar work, with auditors who specialize in each system's platform and payer rules?
- What is your first-pass acceptance rate on NPHIES submissions for existing Saudi clients, and on eClaimLink for UAE clients?
- How do you handle QOCS outpatient classification for Qatar accounts, and who on your team is trained specifically on that scheme?
- Can you provide country-specific SLA reporting so our clients see metrics relevant to their market, not pooled across all geographies?
- What is your onboarding process when we bring you a new country, and how long before your coders are at full production accuracy in that system?
A partner that answers these questions with specifics rather than reassurances is demonstrating that it has done the organizational work your internal build would require. One that talks in generalities about "GCC experience" without distinguishing between systems is offering you the generalist risk in outsourced form.
See how this maps to actual service design on our page covering white-label coding for billing and RCM companies, which explains how MedCodex operates as a country-aware delivery engine behind your brand.
Expansion Without the Internal Build Cost
The GCC coding environment is complex enough that a detailed breakdown of all six markets is worth reading before you design your operation. Visit our GCC coding and RCM hub for a full picture of how each country's system differs and what that means for multi-country RCM delivery.
For RCM firms and TPAs considering whether to build internally or outsource for a next-country launch, the honest framing is this: building three country-specific coding functions in-house is possible, but it is slow, expensive, and exposes your client relationships to accuracy risk during the ramp. Outsourcing to a partner that is already organized by country means you can take on a Saudi client, a Qatari client, or an Abu Dhabi book without rebuilding your delivery infrastructure each time. The partner absorbs the country expertise. You retain the client relationship, the brand, and the margin.
You can also read more about the core economics of this decision in our post on why GCC billing companies outsource coding.
If you are evaluating your next country launch and want to understand exactly how MedCodex is structured to support it, contact us through the MedCodex website to start a conversation about your specific expansion timeline and client mix.