DataFlow Status Check Online: How to Track Your Verification (2026)

If you have searched for a DataFlow status check online and come away frustrated, the problem is not you. DataFlow Group's public website describes its process in three sentences - submit, we verify, access your report - and publishes no standard timeline, no fee schedule and no glossary of the status values it shows you. Its applicant pages promise “real-time tracking” without ever explaining what the tracking screen is telling you.

DataFlow is a contractor to the regulators, not a service you can hold to a published SLA. It verifies your degree, registration and experience letters by writing directly to the institutions that issued them - a network the company describes as over 160,000 issuers in more than 200 countries - and it cannot control how fast a nursing council in Kerala, a registrar in Manila or a merged hospital's HR office in Cairo writes back.

What follows is everything DataFlow and the GCC regulators do state publicly, plus the failure patterns we see repeatedly. If you are still at the start, read our complete guide to DataFlow verification first; this article assumes your case is submitted and paid for.

There is exactly one official tracking screen, and it is not on dataflowgroup.com. It sits on a separate domain: www.dataflowstatus.com/applicationstatus. Bookmark it. Most other “DataFlow status check” pages in search results are consultancy landing pages, and some are outright scams harvesting passport numbers.

The form offers two ways in, and choosing the wrong one is the most common reason people conclude “my case doesn't exist”:

• DataFlow Case Number + Passport Number. Use this if you applied directly through DataFlow's own portal. The case number arrives in your payment confirmation email.
• Client Reference Number + Passport Number. Use this if the application was raised through the regulator's own system - an SCFHS Mumaris Plus request, or a hospital HR department submitting on your behalf. Here the identifier is the number the regulator gave you, not a DataFlow one.

You also select your organisation from a dropdown listing 60-plus clients. Pick the exact entity your licence is with: “Dubai Health Authority” and “Dubai Healthcare City Authority” are different clients with different cases, and applicants routinely search under the wrong one and panic.

The passport number must match the one you uploaded, character for character, including any letter prefix. If you renewed your passport mid-application, the portal still expects the old number until DataFlow updates the record.

DataFlow states that every candidate receives a registration or DataFlow Case Reference Number on successful submission of a PSV application, and that the case ID is available in the payment confirmation email. In practice it reaches you in one of four places:

1. The payment confirmation email - check spam and promotions folders, and search for the word “case” rather than “DataFlow”.
2. The acknowledgement email sent immediately after you submitted the form.
3. Inside the regulator's own portal, where the PSV reference is usually shown against your licence application record.
4. From the agency or hospital HR team, if they paid for you - which also means the confirmation email went to them, not you.

If none of these produce a number, do not create a second application. A duplicate means a second fee, two parallel verifications and, frequently, a discrepancy flag when two records for the same person disagree. Raise a ticket at support.dataflowgroup.com instead, quoting your name exactly as printed in your passport, passport number, date of birth, registered email address and the regulator you applied to.

DataFlow does not publish a status glossary. Based on what the company documents across its own applicant guidance, these are the states you will see and what each genuinely signals.

Under process / In progress. The least informative and most common status. It means only that your case is open and no final outcome has been recorded. It does not tell you whether letters have gone out, whether any reply has come back, or whether a single component is complete - a case can show it on day 3 and on day 90 and mean two entirely different things. The useful signal is the component breakdown underneath it: each degree, registration and employment record is tracked separately, and that is where movement shows.

Cases in insufficiency. DataFlow's own guidance confirms this exact wording, displayed with a “Click here to provide missing information” prompt. It means DataFlow has stopped work and is waiting on you. This is the most important status to catch early, and it is covered in detail below.

Verified. The issuing institution confirmed the credential as genuine. Individual components can be verified while others are still open, so a partially green report mid-process is normal.

Discrepancy. DataFlow defines this as the issuing authority stating that the document was not issued by them or was tampered with. It is serious and almost always blocks the licence.

Unable to Verify (UTV). DataFlow defines this as results that could not be obtained due to non-disclosure policies or non-cooperative authorities. Crucially, UTV is not a finding that your document is fake - it is a finding that nobody would confirm it. Some regulators still reject on a UTV, which is why the appeal route matters. Our guide on what to do after a negative DataFlow report covers both outcomes.

The figures below are the ones DataFlow itself publishes. Every one is a stated norm, not a guarantee, and all are subject to change - confirm current timeframes and fees on DataFlow's portal before you plan around them.

Two things there deserve emphasis. First, the clock runs from date of payment, not date of submission - if you completed the form on the 1st and paid on the 14th, you lost two weeks. Second, DataFlow states explicitly that working days exclude days spent waiting for further information from you due to incomplete or insufficient data. A case parked in insufficiency for three weeks is not “late” by DataFlow's own definition, however it looks to you.

Country of origin drives the variance more than anything else. Institutions with central registries and online verification desks close near the fast end. Cases depending on a single university registrar, a hospital that has closed or merged, or a council that only answers postal requests can run far past it. If you trained in India, expect state nursing council responses to be the pacing item - see our note on Indian state council registration and DataFlow.

The tracking screen is the same for everyone, but what happens either side of it differs by regulator. DataFlow's own client list for GCC healthcare licensing names the following bodies.

Saudi (SCFHS). Your PSV is initiated from inside Mumaris Plus rather than as a standalone DataFlow purchase - which is why so many Saudi applicants find nothing searching by “DataFlow Case Number” and need the Client Reference Number route. Check both systems in parallel; they do not update in lockstep.

Dubai (DHA). Sheryan is DHA's stated digital gateway for registering and licensing professionals in Dubai. Your Sheryan record shows the licensing workflow; dataflowstatus.com shows the verification underneath it. Dubai Healthcare City is a separate authority with a separate case.

Bahrain (NHRA). DataFlow states its NHRA package includes verification of your Good Standing Certificate at no extra cost - useful, because a GSC has a short validity window and re-issuing one mid-process is a common source of delay. See our Good Standing Certificate guide.

Qatar and Oman. DataFlow screens credentials for the Qatar DHP and for OMSB; in both, the completed report feeds the regulator's own registration queue, which has its own timeline you cannot see on the DataFlow screen.

Kuwait. Kuwait's Ministry of Health does not appear among DataFlow's GCC healthcare licensing clients. If you are applying to Kuwait, confirm the current verification and attestation route directly with the Ministry rather than assuming a DataFlow PSV is required.

If your case has not moved in weeks, check for this status before anything else. DataFlow describes it precisely: the portal displays “Cases in insufficiency” with a “Click here to provide missing information” link, and a matching email goes to your registered address.

The trap is the email. It goes to the address on the application - often an old address, an agency's address, or a mailbox where DataFlow mail is auto-filed as promotional. We regularly see cases idle for two or three months for want of one scanned page, and by DataFlow's own definition the clock was not even running.

What to do:

• Open the insufficiency prompt on dataflowstatus.com and upload exactly what is asked for - no more, no less. Extra unrequested documents create new verification components and new delay.
• Alternatively, reply directly to the DataFlow email with the requested document attached, which DataFlow lists as an accepted route.
• Expect a confirmation email within 48 hours of submitting the required information. If nothing arrives, treat that as a failed submission and raise a support ticket.
• Scan at full page size, in colour, with all four corners visible and stamps and signatures legible. Angled phone photographs are a leading cause of a second insufficiency on the same document.

Set a reminder to run your DataFlow status check online once a week for the life of the case. That two-minute weekly habit is the highest-value thing you can do in this entire process.

Assume nothing is wrong until you are meaningfully past the stated window. DataFlow's standard is usually 15-25 working days from payment - roughly five calendar weeks at the top end. Escalating on day 10 achieves nothing but a templated reply.

Once you are genuinely past it, escalate in this order:

1. Confirm there is no insufficiency notice on the portal or in your email. Most “stalled” cases are waiting on the applicant.
2. Raise a ticket at support.dataflowgroup.com, quoting your Case Number or Reference Number as DataFlow's guidance instructs. Ask a specific question: which named component is outstanding, when the last follow-up went to that issuer, and what the next follow-up date is. “Please update my case” gets you nothing.
3. Contact the issuing institution yourself. The step most applicants skip and the one that most often works. Ask your registrar or council whether a DataFlow verification request has been received, and ask them to respond. You cannot supply the answer yourself - the institution must reply directly - but you can chase them.
4. Ask your employer or the regulator to nudge. A hospital HR department with an active recruitment file often has a channel you do not.
5. Consider a paid escalation only if it addresses your actual blocker. Express is bought at the start, not retrofitted to a running case. DataFlow's applicant support tiers - listed at the time of writing as roughly USD 20 for a licensing consultation, USD 42 for Applicant Assist and USD 210 for VIP Assistance, plus UAE-only onsite and doorstep options - buy attention and follow-up, not authority over a silent registrar. Confirm current prices before paying.

Keep a written log: date of payment, each status change, ticket numbers, and every component still open. When a case genuinely goes wrong, that log is the difference between a resolvable dispute and your word against a portal screen.

A negative outcome is not automatically the end. DataFlow allows one free appeal within 180 calendar days of the date the report was issued, for reports showing Discrepancy or Unable to Verify. The window is shorter for some non-healthcare clients - UAE Ministry of Education applications are stated at 90 days - and charges apply to appeals submitted after the free window.

To file, log in at dataflowstatus.com with your case number and passport number, select “File an Appeal”, and upload supporting documents. What actually changes an outcome is usually one of these: a corrected contact person and verification email address at the institution, a fresh letter on institutional letterhead confirming the credential, evidence the institution has merged or changed name, or proof of a name change reconciling your passport to your certificate.

Do not sit on it. The 180-day clock runs from report issue, and regulators impose their own separate deadlines on the licence application the report is attached to - the appeal window can outlive the application window.

Completion of the PSV is a milestone, not the finish line. DataFlow notifies you by email and the report becomes downloadable at dataflowstatus.com using your case number and passport number. Download it and keep the PDF; you will be asked for it repeatedly.

The report then feeds the regulator's own registration queue, which DataFlow describes as typically taking 5-10 weeks once all documents are received - a separate wait, on a separate portal, with its own status screen. Exam eligibility, classification decisions and the licence issue itself all sit downstream of it. Our GCC licensing timeline guide maps how the sequence fits together.

One asset worth knowing about: if you later apply to a second GCC regulator, you may not need to start over. DataFlow's Report Transfer service moves a completed PSV report between regulators - stated as ready in 5-7 days where no new documents need verifying, across 18-plus regulators including DHA and SCFHS. A newly signed Letter of Authorization is mandatory, some regulators require extra components such as mode of study, and the fee differs by regulator. Transferring is almost always faster and cheaper than a fresh verification - our DataFlow cost calculator helps you compare.

Most DataFlow horror stories are administrative, not adversarial. They happen because a notice went unread for six weeks. Ten minutes of discipline prevents nearly all of them.

• Every week: run the status check, look past the headline status to the component-by-component breakdown, and note what changed.
• Every week: search your email - including spam and promotions - for messages from DataFlow, and make sure your registered address is one you actually monitor.
• At submission: record your case number, date of payment, regulator selected and the exact passport number used, somewhere you will still find them in six months.
• Never: open a second application because the first seems slow. Duplicates cost money and create discrepancies.
• Always: keep originals accessible. Insufficiency requests often ask for a clearer scan of something you already sent.

If your case is stuck and you want a second pair of eyes on it, our team works with these authorities daily - see our DataFlow verification support or get in touch. No consultancy can make a registrar answer faster or guarantee a verification outcome or a licence - but we can usually tell you within one conversation whether you are looking at a normal wait, a missed notice, or a real problem that needs an appeal.