Skip to content
← Back to all articles

MoPH MediTrack submission errors — the most common ones and how to fix them

The error patterns Lebanese pharmacies hit when submitting to MoPH MediTrack — UHID format, GTIN not registered, batch already consumed, expiry mismatch — and what to do about each.

Selim Moukarzel portrait

Selim Moukarzel

Co-founder · Pharmacy Operations

Definition

MediTrack submission errors are responses from the MoPH MediTrack API rejecting a dispense record. Common causes are mis-formatted Unique Health IDs, GTINs not yet registered with MoPH, batches already consumed elsewhere in the supply chain, and expiry-date mismatches between the scanned barcode and MoPH's master record.

Why MediTrack rejects a submission

The MediTrack API does not just accept everything it is sent. Every submission is validated against MoPH's master records — the drug must be registered, the GTIN must match a known product, the batch must exist and have available units, and the patient UHID must be in the correct format and belong to a registered patient. Any mismatch returns a rejection with a reason code.

The five errors we see most often

Across the pharmacies running on PharmEasy, five error patterns account for most rejections. None of them are software bugs — they are data-quality issues that show up when MoPH's records and the pharmacy's reality drift. The fix is almost always procedural rather than technical.

  • Invalid UHID format — patient ID not yet issued, or typed wrong at the till
  • GTIN not registered — drug not yet entered in MoPH's master catalog
  • Batch already consumed — same serial already dispensed elsewhere (rare; usually a barcode scan error)
  • Expiry mismatch — scanned expiry doesn't match MoPH's record for the batch
  • Credential expired — pharmacy's MoPH MediTrack credential needs renewal

Fix #1 — Invalid UHID format

The most common rejection. Either the patient does not yet have a UHID, or the UHID was mis-typed at the till. The fix is to verify the UHID against the patient's MoPH card or the centre that issued it, then re-record the UHID against the patient in the pharmacy system once. Done correctly, every future dispense to that patient submits cleanly without re-typing.

Fix #2 — GTIN not registered

Happens when a new SKU arrives at the pharmacy faster than MoPH's master catalog updates. The pharmacy receives stock, scans the GS1 barcode, and the GTIN comes back unknown to MediTrack. The fix is to contact the importer or distributor — they are responsible for registering the GTIN with MoPH before the drug can be dispensed under MediTrack. Until they confirm registration, the dispense queues but cannot submit.

Fix #3 — Batch already consumed

Rare but it happens — typically a barcode scanning artefact (the cashier scanned the same pack twice, or the same serial appears on two physical packs which suggests a counterfeit). The fix is to verify the physical stock against the barcode, re-scan with care, and if the same serial truly appears twice, escalate to MoPH and the distributor — that is what MediTrack is designed to catch.

Fix #4 — Expiry mismatch

The scanned barcode encodes an expiry date that does not match MoPH's record for the batch. Usually a barcode-printing error at the importer; sometimes a barcode reader misreading the date segment. The fix is to verify the printed expiry on the physical pack matches the scanned value, then either correct the scan (if a misread) or escalate to the distributor (if a print error). Do not dispense until the discrepancy is resolved — a known mismatch is exactly what MediTrack flags for inspection.

Fix #5 — Credential expired

The pharmacy's MoPH MediTrack credential has a validity window and needs periodic renewal. When the credential expires, every submission rejects with an authentication error. The fix is to renew the credential through MoPH's pharmacy portal and re-configure it in the pharmacy software. PharmEasy surfaces credential-expiry warnings 30 days ahead so renewal happens before submissions start failing.

How PharmEasy surfaces these errors

Every failed submission appears in the compliance dashboard with the MoPH error code, the exact reason text MoPH returned, the patient, the drug, and the timestamp. Errors are grouped by reason so the same root cause across multiple dispenses appears as a single actionable item — fix the UHID once, all the queued submissions for that patient retry automatically. There is no daily catch-up batch to type out.

Frequently asked

How many submission failures should I expect?
Well below 1% of dispenses once the catalog and patient UHIDs are clean. Most pharmacies see a higher rate in the first month after go-live (mostly UHID format issues from legacy data) and converge to under half a percent by month three. Patterns above 5% almost always point to a misconfigured credential or a master-data sync issue worth escalating to MoPH.
How does retry work for transient failures?
PharmEasy retries on exponential backoff — first retry within seconds, then a minute, then ten, capped at hourly intervals after the first hour. Idempotency keys mean the same submission can be sent multiple times without MoPH recording duplicates. Once MoPH returns an explicit non-retryable error (UHID invalid, GTIN unknown), retries stop and the submission surfaces for human action.
Will failed submissions show up in an inspection?
Yes — and that is the point. MoPH inspectors expect to see a clean dashboard of acknowledged submissions plus a transparent record of failures with their reasons and resolution dates. Failures hidden in a spreadsheet are a red flag; failures surfaced in the system with documented follow-up are exactly what good compliance looks like.
Selim Moukarzel portrait

About the author

Selim Moukarzel

Co-founder · Pharmacy Operations

LinkedIn

Run your pharmacy with PharmEasy.

Founders-run demos, 30 minutes, tailored to your pharmacy. We typically schedule within 24 hours.