DHA Sheryan Registration Guide 2026: Step-by-Step Application for General Practitioners

• Sheryan is the DHA portal where general practitioners submit the license application after you have confirmed eligibility and your DataFlow is prepared

• To avoid delays, get your documents ready, choose the correct service, and double-check every upload before you submit

• By the end of this guide, you will know how to submit, track common status updates, fix typical issues, and move forward to exam booking

Also, picture this: you have your passport, degree, and experience letters ready, but the next steps in the Sheryan portal feel time-sensitive and unclear. At this stage, the risk is not effort, it is small mismatches like a name format, a different date, or selecting the wrong service and then waiting for a return.

Most delays in licensing workflows come from three avoidable issues: missing documents, mismatched details across systems, or choosing the wrong service path in the portal. By the end of this section, you will have a clean end-to-end workflow for what to do next, what to check first, and what to leave alone until DataFlow updates.

Next, treat this phase like a checklist, not a race. Your goal is to keep every identity and credential detail consistent across your documents, DataFlow, and Sheryan so the portal can match records without manual back-and-forth.

If you do one thing, do this: make one “master identity line” and copy it everywhere (English spelling, order of names, date of birth, passport number). Common mistake: uploading a document with a different spelling than the one used in the DataFlow profile; fix it by aligning the spelling in the source profile first, then re-uploading the corrected file.

That said, not everything should be edited while DataFlow is moving. Some updates are safe and prevent return cycles, while others can create duplicate records or reset parts of the verification.

Check now:

• Your selected service matches your role and license goal (for example, General Practitioner vs another category)

• Document validity dates are readable and current (passport, professional card if applicable)

• File basics: clear scan, correct orientation, and consistent naming so you can track uploads

• Contact details you actually monitor for updates

Wait before changing:

• Core identity fields in multiple places at once (change in one source, then let it sync)

• Re-starting a verification because the status feels slow (this often creates more delay)

If you're short on time, focus on identity consistency and service selection first, then file clarity second. Works best when your documents are already issued in a consistent name format; it tends to fail when you mix shortened names, initials, or different surname order across files.

Next, place Sheryan in the correct spot so you do not repeat steps or wait too long.

Think of Sheryan as the DHA’s online application portal where you submit your license application, upload documents, pay fees, and track status updates. It is not the same as DataFlow (the primary source verification of your credentials) and it is not the same as the Prometric exam (your computer-based assessment).

Also, it helps to separate the three steps by what each one is responsible for:

• Sheryan: your DHA application record, document uploads, fees, and application tracking

• DataFlow: checks your degree, registration/license, work experience, and other credentials directly with issuing sources

• Prometric: tests your knowledge so DHA can confirm you meet the exam requirement for your category

A common mistake is assuming that a DataFlow submission is the “DHA application.” The fix is simple: treat DataFlow as one requirement you later connect or reference inside Sheryan, not a replacement for it.

That said, not everyone uses Sheryan the same way at the same time. If you are applying for a DHA license as a General Practitioner, you should expect to use Sheryan for the main application steps once you are ready to submit a complete file.

If you do one thing, do this: start Sheryan when you can upload a consistent set of documents within 1 to 2 sittings (often 60 to 120 minutes), rather than opening an application and leaving it half-finished for weeks. Sheryan works best when your documents, names, and dates match across files; it fails when files are missing, unclear, or inconsistent, which often leads to returns and extra back-and-forth.

In practice, “when to start” depends on your bottleneck:

• If your passport, internship certificate, and current license are ready now, you can set up Sheryan and prepare the application fields while DataFlow continues

• If you are still waiting on a key document (for example, a recent Good Standing Certificate or an employer experience letter), hold off on final submission so you do not trigger avoidable returns

• If you are short on time, skip polishing non-essential uploads and focus on the items most likely to block review: identity document, qualification, registration/license, and experience proof

The goal is a clean sequence: DataFlow verifies, Prometric confirms exam readiness, and Sheryan is where you assemble and submit the full DHA application for review and licensing steps.

Also, most Sheryan delays happen before you ever click Submit: a mismatched name, the wrong file type, or a missing stamp can trigger a return and cost you days.

A simple pre-flight check (15 to 30 minutes) usually prevents the most common back-and-forth: re-upload requests, clarification emails, and DataFlow mismatches.

Here’s what to have ready in a single folder before you start the portal steps:

• Identity: passport bio page and a recent photo that matches the portal requirements

• Education: primary medical qualification and internship certificate (if applicable), plus required attestations

• Experience: employment letters with clear dates, role title, facility name, and signatures or stamps

• Good standing: valid certificate from your current or most recent regulator, within the accepted validity window

• Naming conventions: a consistent file naming pattern such as LASTNAME_Firstname_DocumentType_Date

• Translations: certified English or Arabic translations for any non-accepted language documents

• File formats: save scans as PDF or image files only, with readable resolution and complete pages

If you do one thing, standardize your file naming and scan quality first. It is the quickest fix for avoidable rework.

Next, align your personal details across every document before you enter them in Sheryan, because inconsistencies often show up later as DHA eligibility application issues.

Check these fields side by side: passport, degree certificate, license or registration, and the exact details used in DataFlow:

• Full name order and spelling (including middle names)

• Date of birth format (day-month-year vs month-day-year)

• Nationality and passport number

• Gender (as shown on passport)

Here’s the catch: the portal form may accept your entry even if it differs slightly, but the review step can still flag it. If you are short on time, focus on name spelling and date of birth first, then fix the remaining fields before uploading.

Next, treat your DHA Sheryan account setup like a clinical handover: small details prevent delays later. Many returned applications come from simple mismatches like a name order difference or an email you can no longer access, not from missing credentials.

Before you start, choose one email and one mobile number you can keep for at least the next 3 to 6 months, because these are commonly used for verification and updates.

Use this sequence to get through account creation and profile setup with fewer edits later:

1. Create your account with an email you check daily and set a strong password you can recover

2. Set up login recovery (security questions, recovery email or phone if available) and save your username details in a secure place

3. Complete your profile exactly as it appears in your passport

4. Add contact details using a consistent country code format

5. Enter your professional details (degree, graduation year, licensing country) using the same wording style you used for DataFlow submissions

If you do one thing, do step 3 slowly. A common mistake is adding initials, changing spelling, or using a shortened surname, then having to correct multiple screens later to match your passport and DataFlow report.

Also, when you reach the service selection part, choose the professional service that matches your target license so your form fields align with a General Practitioner pathway. Double-check the category before you proceed, because choosing a nearby option can send you into the wrong document list and add weeks of back-and-forth.

Enter information the way an evaluator reads it:

• Personal information: passport name, date of birth, nationality, passport number

• Professional identity: current job title, employer (if applicable), work history blocks with month and year ranges

• Registration and licensing: current license number and issuing authority, issue and expiry dates where relevant

Tradeoff: going fast works when you already have your passport, degree, and license details open in front of you. It fails when you are copying from memory, because even small date swaps (for example, month and day formats) can trigger corrections later.

That said, if you are short on time, skip perfect formatting tweaks and focus on three items that most often cause returns:

• Name spelling and order matches the passport

• Dates are consistent across profile, uploaded documents, and DataFlow entries

• The selected professional service is correct for DHA GP registration

Once your profile is saved, take 2 minutes to review every field as if you were verifying a colleague’s credentials. Fixing a typo now is usually a same-day edit, while fixing it after submission can mean a status change and an extra review cycle.

Next, treat uploads like a clinical handover: if the reviewer cannot read a stamp, date, or registration number in under 10 seconds, your file is at risk of being returned.

Before you upload, do a quick quality check on every scan or PDF:

• Text is sharp at 100% zoom, not photographed at an angle

• All pages are included and in the correct order

• Names and passport numbers match across documents

• Dates are fully visible, including issue and expiry where relevant

• Stamps and signatures are clear, not cut off by margins

Here's the catch: most upload failures are not about the document itself, but about the file you submitted. Common failure points and fixes:

• File naming is inconsistent (Fix: use one naming pattern like DocumentType_FullName_ID_Year)

• File is too large or the portal times out (Fix: export to PDF and reduce size; split into 2 files if needed)

• Multi-page documents are uploaded as separate images (Fix: combine into one PDF per document type)

• Low-contrast scans hide embossed seals (Fix: rescan in better lighting; avoid heavy filters)

If you do one thing, do this: create one folder per document type and keep one final PDF in each folder so you never upload an outdated version by mistake.

So, once your documents are in place, link or use your DataFlow results inside Sheryan as soon as the portal provides the option. If your result is available, you should be able to select it from the relevant verification area instead of uploading a screenshot.

If results do not appear, try this sequence before you raise a ticket:

• Confirm your identifiers match exactly (name spelling, passport number, date of birth)

• Wait and recheck later if your status recently changed, since syncing can take time

• Sign out and sign back in, then check the verification section again

• If the portal offers a manual reference entry, paste the DataFlow reference carefully and save

If you're short on time, skip reformatting everything at once and re-upload only the files that fail the readability check first, then return to cleanup and naming.

Next, treat the final submit step like a handover checklist in a clinic: one missed field can send the whole case back for rework. A careful 10 to 15 minute review before you click submit often saves days of waiting and repeated uploads.

If you do one thing, confirm that every document you uploaded matches what you typed in the application fields. The most common returns happen when names, dates, or document types do not match exactly across passport, degree, internship, experience letters, and DataFlow-linked details.

So use this quick list before submitting:

• Check your name spelling and order matches your passport and DataFlow record

• Confirm your profession and scope are correct for General Practitioner, not a nearby category

• Match each upload to the right slot (degree in degree slot, internship in internship slot, license in license slot)

• Verify issue and expiry dates for licenses and IDs are entered correctly

• Make sure experience letters include role title, start and end dates, and facility details

• Confirm all files open clearly and are readable at 100% zoom

• Recheck contact email and phone number you will monitor daily for the next 2 to 4 weeks

Common mistake and fix:

• Mistake: Uploading the right document into the wrong category

• Fix: Rename files before upload, for example “Passport Bio Page”, “MBBS Degree”, “Internship Certificate”, “Current License”, then upload slowly one slot at a time

That said, once you submit, your job shifts from editing to monitoring. The portal status is your signal for what to do next, and the right response depends on whether the case is still in review or has been sent back to you.

Here are common status patterns and the next action to take:

• Submitted or Received: Your application is in the queue

  • Next action: Do not upload extra files unless requested, check messages every 1 to 2 business days

• Under Review or In Process: The authority is checking your details and documents

  • Next action: Keep your phone and email available, prepare missing items in case they ask

• Additional Information Requested: A reviewer needs a specific clarification or document

  • Next action: Reply only to what was asked, in the format requested, within the stated time window if shown

• Returned: Something needs correction before they continue reviewing

  • Next action: Compare the return notes to your fields and uploads, fix the exact item, then resubmit

• Rejected: The case was not accepted as submitted

  • Next action: Read the rejection reason carefully, correct what is correctable, and consider formal support if the reason is unclear

• Approved: Your registration step is accepted and you can move to the next licensing steps shown in your portal

  • Next action: Save confirmation screenshots or PDFs, then follow the next required steps without delay

Here’s the catch: adding new documents “just in case” can slow review because it changes what the reviewer must re-check. If you are short on time, skip reformatting every file and focus on the high-risk items first: name matching, correct document slots, and complete experience letters.

So treat your Sheryan application like a clinical handover: clear, complete, and easy for the next person to verify. “Smooth is fast” means fewer returns, fewer back-and-forth messages, and less waiting while your file sits in review.

Next, pick the one step most likely to delay you and fix it before you submit today. For many GP applicants, the usual delay points are simple but costly:

• A document upload that does not match the required format or file naming

• A mismatch between passport name, degree name, and DataFlow entries

• An expired ID, license, or certificate that gets overlooked until submission

• Missing translations or unclear scans that force a resubmission

If you do one thing, do a final 15-minute cross-check: names, dates, and document clarity across every upload and every profile field. If you’re short on time, skip rearranging optional details and focus only on what triggers returns: identity, qualifications, licensure, and linked verification results.

In practice, alt text should describe what the image shows in plain words, not keywords. Aim for 6 to 12 words and mention GP only when it is relevant to the screenshot or checklist.

Suggested alt text options:

• DHA Sheryan portal application steps for GP

• DHA license application document checklist

• Sheryan application status meanings overview

Tradeoff: longer alt text can add clarity for screen readers, but it can get vague. Works best when it describes the exact screen, fails when it turns into a list of terms.