Published: 16 September 2026
A recent Daman payer update has changed the status of IFHAS service code 52-62, creating an immediate coding, authorization and claims-management issue for UAE healthcare providers.
According to a UAE insurance update tracking payer circulars, Daman issued circular PND/SA/AC/26/UAE-46 on 15 September 2026, stating that service code 52-62 was discontinued from the Mandatory Tariff List, with the change effective 1 September 2026. The update also states that the change relates to the ACMG report for male and female patients aged 18–75 and updates the earlier circular PND/SA/AC/26/UAE-41.
The two-week gap between the effective date and the notification date is particularly important for medical coders, billers, authorization teams and accounts-receivable teams.
What Changed in UAE Medical Coding?
The affected SRVC code 52-62 has been removed from the Daman Mandatory Tariff List.
| Coding element | Previous position | Current position |
|---|---|---|
| Payer | Daman | Daman |
| Service code | IFHAS 52-62 | Discontinued |
| Service | ACMG report | No longer listed under the affected tariff |
| Patient age | Male & female, 18–75 | Affected by the discontinuation |
| Tariff status | Included | Removed |
| Effective date | — | 1 September 2026 |
| Circular | PND/SA/AC/26/UAE-41 | Updated by PND/SA/AC/26/UAE-46 |
| Notification date | — | 15 September 2026 |
The payer update should be interpreted against the applicable Daman circular and current payer configuration rather than relying on an old charge-master entry or historical claim pattern. Daman’s adjudication guidelines also state that their guidance is intended for claim-adjudication reference and is not comprehensive.
DHA’s eClaimLink coding framework includes ICD-10-CM, CPT, HCPCS, CDT, Dubai Drug Code, Dubai Service List, LOINC and other coding/list systems, alongside payer, denial, facility and benefit-package lists.
Why This Creates a Problem for Medical Coders
The main issue is not simply that a code has changed.
The operational problem occurs when the effective date, coding system, authorization record, charge master and claim submission workflow are not synchronized.
1. Old code remains in the charge master
If 52-62 remains active in the hospital or clinic’s charge master, a medical coder may continue selecting the historical service code.
That can result in a claim being generated with a code that is no longer payable under the applicable tariff.
2. Previously authorized services require review
The update is particularly important because the effective date is 1 September, while the circular was issued on 15 September. The payer-update source specifically identifies claims and authorizations falling between those dates as requiring attention.
Medical coding teams should therefore identify:
- Authorizations created using 52-62
- Services performed after 1 September
- Claims already submitted
- Claims still in billing queues
- Claims pending adjudication
- Claims returned for correction
3. Coding and authorization can become inconsistent
A common workflow problem is:
Authorization → Procedure → Coding → Claim submission
If authorization contains the previous service code but the current payer configuration no longer recognizes it, the claim can enter an exception or denial workflow.
4. Retrospective correction becomes more difficult
When a payer update is published after the effective date, medical billing teams may discover affected claims only after submission or adjudication.
This can create additional work involving:
Claim review → Coding validation → Resubmission → Denial follow-up → AR reconciliation
What Can Happen After the Coding Change?
The consequences depend on the claim status and payer adjudication.
Claim rejection
A claim containing a discontinued or non-payable service code may be returned during payer validation.
Authorization mismatch
An authorization may contain a historical code while the submitted claim uses a changed or unavailable tariff item.
Claim correction workload
Medical coders may need to review individual encounters rather than simply correcting a single claim.
AR ageing
If affected claims remain unresolved, the issue can move from the coding queue into accounts receivable, increasing follow-up requirements.
Charge-master contamination
If the old code is not appropriately retired or flagged, future encounters can continue generating the same coding problem.
Data-quality impact
Incorrect historical coding can affect:
- Claim analytics
- Denial reports
- Coding productivity
- Payer reconciliation
- Revenue-cycle reporting
What UAE Medical Coders Should Do Now
1. Identify every use of code 52-62
Run a report covering at least:
1 September 2026 → current date
Search the billing system, charge master, authorization system and claims queue for 52-62.
Do not limit the search to rejected claims.
2. Separate claims by status
Create separate work queues:
| Claim status | Required review |
|---|---|
| Not submitted | Validate coding before submission |
| Submitted | Check payer adjudication |
| Pending | Monitor payer response |
| Rejected | Review rejection reason |
| Denied | Determine correction/resubmission route |
| Paid | Verify payment and remittance |
| Authorized but not billed | Validate authorization and current payer requirements |
This prevents the coding team from treating every affected encounter as the same problem.
3. Review the charge master
The charge master should be checked for:
- Active status of 52-62
- Effective dates
- Payer mapping
- Tariff mapping
- Service description
- Authorization mapping
- Alternative/current service configuration
The objective is to prevent the discontinued code from automatically appearing in new claims.
4. Reconcile authorizations
For encounters between 1 September and 15 September, compare:
Authorization code → Performed service → Coded service → Submitted claim
Any mismatch should be investigated before the claim progresses further.
5. Check payer-specific instructions
Do not automatically replace 52-62 with another code simply because it appears similar.
The replacement must be supported by:
- Current Daman payer configuration
- Applicable tariff
- Clinical documentation
- Service performed
- Authorization requirements
- Current coding rules
A discontinued code does not automatically mean another code should be substituted.
6. Review clinical documentation
The coder should confirm that the medical record supports the service actually performed.
Relevant documentation may include:
- Physician order
- Clinical indication
- Patient demographics
- Laboratory/genetic report
- Test/service details
- Authorization documentation
- Payer correspondence
A Practical Workflow for UAE Medical Coding Teams
Payer update received
↓
Identify affected code
↓
Check effective date
↓
Extract affected encounters
↓
Review authorization
↓
Validate clinical documentation
↓
Check current payer tariff/configuration
↓
Update charge master where appropriate
↓
Correct affected claims
↓
Submit/resubmit according to payer requirements
↓
Monitor adjudication and AR
This workflow is more reliable than waiting for the first denial to identify a coding change.
Old Coding Workflow vs Updated Workflow
| Area | Historical workflow | After payer coding update |
|---|---|---|
| Code selection | Historical code library | Current payer configuration |
| Charge master | Existing mapping | Effective-date validation |
| Authorization | Existing authorization | Authorization-to-claim reconciliation |
| Claim review | Pre-submission checks | Code + tariff + authorization review |
| Denial management | Reactive | Early identification of affected claims |
| AR | Follow-up after rejection | Preventive reconciliation |
| Audit trail | Claim-level | Circular + effective date + encounter-level |
| Coder responsibility | Code assignment | Code validation + payer update tracking |
Why Effective Dates Matter More Than the Announcement Date
This is one of the most important points for UAE medical coders.
The reported Daman update was issued on 15 September 2026, but the change was stated to be effective from 1 September 2026.
That means coding teams should not review only claims created after 15 September.
They should investigate the effective period beginning 1 September and establish which encounters, authorizations and claims used the affected code.
This is particularly important for revenue-cycle teams because coding changes can affect claims that have already moved from coding → billing → payer adjudication → AR.
Daman’s current medical library shows new or updated guidance throughout 2026, including CGM and external insulin pumps (15 September), tonsillectomy/adenoidectomy (28 July), benign prostate hyperplasia and ultrasound scrotum (8 July), and several other clinical services
Where Medical Billing Teams Fit In
For healthcare providers handling high claim volumes, payer-update management often extends beyond the medical coder.
A coordinated medical billing and revenue-cycle management (RCM) process can connect:
Medical coding + authorization + charge master + claim submission + denial management + AR follow-up
For a UAE provider using an outsourced billing team such as Escrow Medical Billing Service LLC, this type of payer update can be incorporated into the claim-review and denial-management workflow rather than handled only after a rejection occurs.
The important requirement is not simply outsourcing the claim. The billing team needs a documented process for payer circular tracking, effective-date identification, code validation and affected-claim reconciliation.
Key Takeaway for UAE Medical Coders
The Daman IFHAS 52-62 update demonstrates why UAE medical coding teams need to track payer changes by code, circular, effective date and claim status.
For this particular update:
Issued: 15 September 2026
Effective: 1 September 2026
Payer: Daman
Affected code: IFHAS 52-62
Status: Discontinued from the Mandatory Tariff List
Primary operational areas: Coding, charge master, authorization and AR
The immediate priority is to identify affected encounters from 1 September onward, reconcile authorization and claim data, validate the medical record, and use the current payer requirements before correcting or resubmitting claims.
Frequently Asked Questions
1. What happened to Daman code 52-62?
Daman’s reported payer circular PND/SA/AC/26/UAE-46 states that IFHAS service code 52-62 was discontinued from the Mandatory Tariff List. The circular was issued on 15 September 2026, with the change stated as effective from 1 September 2026.
2. Which service does code 52-62 represent?
The reported update identifies 52-62 as the SRVC code for the ACMG report for male and female patients aged 18–75. Medical coders should verify the exact service description against the applicable Daman circular and current payer configuration before making coding changes.
3. Why is the effective date important?
The effective date determines which encounters can be affected. Because the reported effective date is 1 September while the notification date is 15 September, claims and authorizations during the intervening period require specific review rather than being excluded because they preceded the announcement.
4. Should medical coders replace 52-62 with another code?
Not automatically. A discontinued code should not simply be replaced with a similar-looking service code. The coder should verify the current Daman tariff, clinical documentation, authorization requirements and applicable payer instructions before selecting any alternative code.
5. Which claims should UAE coders review?
Start with encounters from 1 September 2026 onward where 52-62 appears in the charge master, authorization, coding record or claim. Separate unsubmitted, submitted, pending, rejected, denied and paid claims because each status requires a different reconciliation or follow-up action.
6. Can an old authorization still be used?
That depends on the payer’s applicable authorization and adjudication requirements. An authorization containing a historical code should be reconciled against the service date, current tariff configuration and submitted claim. Medical coders should avoid assuming that an existing authorization guarantees claim payment.
7. What should happen to the charge master?
The charge master should be reviewed for the discontinued code, including its active status, payer mapping, tariff mapping and effective dates. Any configuration change should follow the healthcare provider’s controlled change-management process and the applicable Daman payer requirements.
8. Can this coding change affect AR?
Yes. If affected claims are submitted with outdated or non-payable coding, they may enter rejection, denial or correction workflows. Unresolved claims can subsequently require AR follow-up. Early identification allows coding, billing and AR teams to isolate affected encounters before the issue becomes a larger outstanding-balance problem.
9. What should coders check before resubmission?
Coders should verify the clinical documentation, service performed, patient information, authorization, payer tariff configuration and claim data. The corrected claim should represent the documented service and comply with the applicable payer requirements rather than using an alternative code solely to prevent rejection.
10. Why should UAE medical coders track payer circulars?
Daman, DoH Abu Dhabi, DHA and other UAE healthcare stakeholders can publish requirements affecting coding, documentation, tariffs, authorizations and claims. A payer-circular tracking process helps coding teams connect each change to its effective date and identify affected encounters before claim errors accumulate.
Source note: The specific 52-62 discontinuation details above are based on the current UAE insurance-update record identifying Daman circular PND/SA/AC/26/UAE-46; the record itself advises users to work from the original payer/regulatory document for operational decisions. Daman’s published adjudication guidance similarly describes its material as reference/guidance rather than comprehensive instructions.
