DataFlow Verification for Indian Healthcare Professionals: How It Actually Works (and Where It Stalls)

The short answer first

DataFlow Group is the GCC's healthcare credential verifier. When an Indian healthcare professional applies for SCFHS (Saudi), DHA (Dubai), DOH (Abu Dhabi), QCHP (Qatar), NHRA (Bahrain), or OMSB (Oman) licensing, the regulator routes the credential check through DataFlow. DataFlow does not "review" the candidate's documents; it contacts the issuing Indian university, professional council (NMC, INC, PCI, AIIMS), and past employers directly to confirm the documents are real. Typical timeline: 4 to 8 weeks when universities and employers respond promptly; 8 to 16 weeks for slow universities or closed past employers. DataFlow runs in parallel with the apostille step on the India side; do not wait for one to finish the other. The single biggest reason Indian DataFlow cases stall is unresponsive past employers, not university issues. Kuwait MOH only rarely asks for DataFlow.

What DataFlow actually checks

DataFlow does Primary Source Verification, which means the verifier contacts the issuing source directly, not through any intermediary. For an Indian nurse applying to SCFHS, DataFlow will:

• Write to the issuing university (e.g., Rajiv Gandhi University of Health Sciences, RGUHS) to confirm the BSc Nursing degree was issued.
• Write to the State Nursing Council to confirm registration.
• Write to the Indian Nursing Council (INC) to confirm national registration and the Good Standing Certificate.
• Write to each past employer (hospital HR, signed copies on letterhead) to confirm experience dates and role.
• For doctors, the National Medical Commission (NMC, which replaced MCI in 2020) confirms registration; State Medical Councils confirm state registration; medical colleges confirm degree; hospitals confirm experience.

DataFlow does not check apostille status; the apostille is a separate Indian-side authentication. DataFlow does not check translation; that is also separate. DataFlow does not check whether the candidate has passed the exam (Prometric for SCFHS, Pearson VUE for DHA, etc.); the exam is a separate licensing step.

Which GCC regulator asks for which DataFlow package

DataFlow has multiple packages because regulators ask for different document combinations:

• SCFHS (Saudi) — DataFlow PSV for degree, transcripts, council registration, internship certificate, experience letters. Required for Mumaris+ licence. Doctors, nurses, pharmacists, lab technicians, radiographers all go through SCFHS.
• DHA (Dubai) — DataFlow PSV for degree, transcripts, council registration, Good Standing Certificate, internship, experience. Required for DHA licence application before the DHA exam.
• DOH (Abu Dhabi) — Similar to DHA. DOH licence application before Pearson VUE exam.
• MOH (other UAE emirates) — Similar to DHA and DOH.
• QCHP (Qatar) — DataFlow PSV before QCHP licensing exam.
• NHRA (Bahrain) — DataFlow PSV for NHRA licence.
• OMSB (Oman) — DataFlow PSV for OMSB licence and exam.
• MOH (Kuwait) — Kuwait MOH rarely asks for DataFlow; most Kuwait healthcare cases proceed without it. The exception is some institutional categories where DataFlow is specifically asked.

Documents DataFlow asks for, by profession

Nurses (GNM / BSc Nursing / MSc Nursing)

• GNM Diploma or BSc/MSc Nursing Degree Certificate
• Consolidated Marksheet or Year-wise Marksheets
• INC (Indian Nursing Council) Registration Certificate
• State Nursing Council Registration
• Good Standing Certificate (from INC or State Nursing Council)
• Internship / Service Completion Certificate
• Experience letters on hospital letterhead with HR signature, dates, role, and stamp

Doctors (MBBS / MD / DM / MCh / DNB / MS)

• MBBS Degree Certificate
• Post-graduation Degree (MD, MS, DNB, DM, MCh) if applicable
• Academic Transcripts or Marksheets
• NMC (National Medical Commission) Registration — replaced MCI in 2020
• State Medical Council Registration
• Good Standing Certificate from NMC or State Council
• Internship Completion Certificate
• Experience letters from each hospital with HR signature, dates, role, and stamp

Pharmacists (B.Pharm / M.Pharm / Pharm.D)

• Degree Certificate
• Academic Transcripts
• PCI (Pharmacy Council of India) Registration
• State Pharmacy Council Registration
• Good Standing Certificate
• Experience letters

Lab Technicians, Radiographers, Physiotherapists, Other Allied Health

• Profession-specific degree or diploma
• Council registration where applicable (Indian Association of Physiotherapists for PT, etc.)
• Experience letters
• Good Standing where the profession has a council

What slows DataFlow down

In our experience, the single biggest source of DataFlow delays is past employers, not universities. Specifically:

• Past employer hospital reorganised, merged, or closed. DataFlow cannot reach the original HR; the case stalls. Workaround: candidate gathers payroll records, IT returns, EPFO records, signed colleague letters as supporting evidence, and we submit a clarification to DataFlow.
• Past employer HR is slow. Some hospitals take 4 to 6 weeks to respond to DataFlow. Candidate should follow up actively; sometimes the HR cycle stalls because the verification request lands with a non-HR contact.
• Past employer asks the candidate to pay a verification fee. Many corporate hospitals (Apollo, Fortis, Manipal, Max) charge ₹500 to ₹2,000 for HR verification. Pay it; it speeds the case.
• Old experience letter is unsigned or undated. DataFlow rejects unsigned or undated experience letters. Get a fresh letter on letterhead with HR signature and stamp before submitting.
• University rename or reorganisation. Bangalore University split into Bangalore University, Bangalore North University, Bangalore Central University. RUHS, MUHS renames. DataFlow sometimes flags the rename and asks for clarification.
• Old council registration not digitised. State medical councils that have not digitised pre-2010 registrations sometimes cannot retrieve the record; physical archive search adds time.

What "Unable to Verify" means and how to fix it

"Unable to Verify" (UTV) is DataFlow's outcome when the issuing source did not respond or responded with an unclear answer within the verification window. UTV is not a rejection; it is a status that asks the candidate to provide supporting evidence and request re-verification. The fix:

1. Identify the document that returned UTV.
2. Gather alternative supporting evidence: payslips, IT returns, EPFO contributions, colleague letters, hospital ID photographs, signed handovers.
3. Submit a clarification to DataFlow with the supporting evidence.
4. Re-verification typically takes 2 to 4 weeks.

See our DataFlow Unable to Verify guide for the specific scripts and supporting-evidence checklists.

Realistic timeline

• Best case (responsive universities, currently-employed candidate with single past employer): 4 to 6 weeks.
• Typical case (multiple past employers, mid-sized hospitals): 6 to 10 weeks.
• Slow case (closed past employer, university rename, state council pre-2010 record): 12 to 20 weeks with re-verification.

Plan DataFlow in parallel with apostille, not after. Most Indian candidates can submit DataFlow uploads within one week of receiving the offer letter, because the candidate's own documents (degree, transcripts, council registration) are already in hand and apostille only needs to add the MEA stamp on the document, not the DataFlow upload itself.

What candidates get wrong

• Waiting for apostille before starting DataFlow. Start DataFlow uploads as soon as documents are MEA-stamped (or even before, depending on the regulator's specific instruction). DataFlow does not need the apostille.
• Skipping the Good Standing Certificate. SCFHS, DHA, DOH, QCHP, NHRA, OMSB all want Good Standing. Apply at the issuing council early because Good Standing takes 1 to 3 weeks.
• Assuming Kuwait needs DataFlow. Kuwait MOH rarely asks for DataFlow; most Kuwait healthcare cases skip it. Confirm with the specific Kuwait employer before starting an unnecessary DataFlow case.
• Experience letters not on letterhead. Plain paper letters are rejected. Original letterhead, HR signature, stamp, dates, role.
• Out-of-date council registration. Renew before submitting to DataFlow.
• Forgetting to upload the apostilled degree. Some regulators want the apostilled degree alongside DataFlow's report.
• Not tracking DataFlow status weekly. The candidate should check the DataFlow portal weekly and follow up if a verification is pending more than 4 weeks.

How we approach a DataFlow case

We start by identifying the destination regulator (SCFHS, DHA, DOH, QCHP, NHRA, OMSB) so we know which DataFlow package to choose. We help the candidate collect Good Standing from the council early because it is often the bottleneck. We coordinate the experience letters from past employers and provide template scripts for stalling HR. For Unable to Verify cases, we collect alternative supporting evidence (payroll, EPFO, IT returns) and submit clarification. We do not promise "4-week DataFlow" because cases with closed past employers honestly take longer; we tell the candidate the realistic 6 to 12 week range.

If you are looking at a DataFlow case, share the destination regulator, your profession, and your education and employment history. We will tell you the realistic timeline and the documents to start gathering. WhatsApp or contact.