A fake or lapsed registration ends up as a malpractice claim, a rejected insurance case or a failed audit. DocTrace checks any Indian doctor against the state council and National Medical Register in under a second, and returns the answer with its source, so you can prove you checked.
Fake and borrowed registrations have reached operating theatres. These are reported cases, with sources. We do not quote a national count, because none exists.
A man working as a heart specialist at a private hospital was found to have no valid registration with the state council, and the registration he claimed elsewhere could not be traced. The National Human Rights Commission reported seven deaths and recommended compensation for the families and suspending the hospital’s licence.
The number is not on any register, so a lookup returns not found.
Police say an MBBS graduate worked for several months at a heart centre inside a civil hospital, run by a private contractor, using another cardiologist’s registration number. It came to light when a patient contacted the real doctor.
The number is genuine, so a lookup returns the real doctor’s name and qualifications. The mismatch shows when you compare that record with the person’s ID and certificates. That is why DocTrace returns a full, sourced record, not a bare yes or no.
The Delhi Medical Council found that a man who treated a patient who later died was not registered in Delhi and that the Goa registration certificate he relied on was fake. It recommended prosecution and asked for action against the hospital for employing an unqualified person.
Not registered in Delhi, and the claimed Goa registration does not match the Goa register.
Summarised from public reporting and official releases. Allegations in news reports are not proven in court. DocTrace checks a registration against the register. It does not by itself confirm who is standing in front of you, and it is not legal advice.
The question is always the same: is this person registered, and can we prove we checked?
Verify doctors at sign-up, then re-check the whole roster on a schedule.
See how it works for you →
One standard, timestamped record for every doctor you credential.
See how it works for you →
Test the treating doctor’s registration while the claim is still open.
See how it works for you →
Clean your doctor master and verify before every engagement.
See how it works for you →Pick your role. Each guide walks through the problem, how it is handled today, where that falls short, how DocTrace changes it, and the value on five measures.
You answer for every e-prescription on your platform. Telemedicine guidelines require the consulting doctor to be a registered practitioner, so you need to know before the first consultation, and be able to show it later.
Verification becomes a step in sign-up, and repeats across your whole roster on a schedule.
GET /api/v1/doctors/verifyJSON responsePOST /api/v1/doctors/bulk-verifyYour databaseBefore granting privileges, a hospital must verify a doctor's registration and qualifications at the source, and keep the evidence for accreditation reviews. Done properly, that means writing to councils and universities one by one.
A repeatable credentialing step with one standard record, at joining and at every renewal, across all your facilities.
GET /api/v1/doctors/verifyJSON responseYour credentialing systemPOST /api/v1/doctors/bulk-verifyCashless approvals move in minutes, and a claim is only as trustworthy as the practitioner behind it. Mistyped, forged or lapsed registration numbers are hard to catch at that speed.
A credential check on every claim that names a doctor, so invalid or sanctioned practitioners are flagged while the claim is still open. The same check works when you empanel doctors and hospitals.
GET /api/v1/doctors/verifyJSON responseYour claims rulesPOST /api/v1/doctors/bulk-verifyYour CRM holds a large doctor database, and you engage doctors for advisory boards and education under marketing codes. Duplicate or unverified records waste field effort and create compliance exposure.
One stable ID per doctor across the CRM, and a registration check inside the engagement workflow.
POST /api/v1/doctors/bulk-verifyYour data teamGET /api/v1/doctors/verifyScheduled jobYour system sends a number. DocTrace sends back the record, with its source. It works from an HMIS, CRM, claims engine or onboarding app.
A council and registration number, or the DocTrace ID, by REST API or bulk file.
Matched on council plus number, because registration numbers repeat across councils.
The answer comes back with its source and the time it was last confirmed.
Keep the response in your credentialing file, claims record or audit pack.
Your developers can try it without a key in the sandbox, or read the API docs.
DocTrace is built from the official registers of the National Medical Commission and the state medical councils, cleaned into one standard record. This is how complete the registry is, field by field.
Penal erasures and sanctions from state councils and the NMC ethics board are screened, and apex-hospital appointments are linked. Coverage is growing, and we share the current figures on request.
The National Medical Register and 26 state councils, normalised to one record shape: names, registration numbers, qualifications and universities cleaned and standardised.
Doing a security or procurement review? See the security and trust details.
Records come from registers that councils publish for public inspection. DocTrace holds no patient, clinical or prescription data.
Each result carries its source and the time it was confirmed, ready to file in a credentialing record or a claims pack.
Traffic is encrypted in transit. Every API key has its own usage limits, so access stays private, metered and logged.
Try it on your own records first, then pick the plan that matches how you buy.
100 lookups, free for qualified teams. Test it against doctors you already know, in one afternoon.
Request a pilotPer-verification pricing with a monthly base, higher rate limits and an uptime commitment for products that verify at sign-up.
Talk to usUnlimited credentialing checks for your facilities, with bulk verification and a dedicated account manager.
Talk to usHigh-volume claims verification with burst capacity and priority support, priced on expected monthly checks.
Talk to usIt catches a registration number that is not on a register, one that has been suspended or cancelled, and a name or qualification that does not match the register’s record. It cannot tell by itself that the person in front of you is the registered doctor, so compare the record with their ID and certificates. That check is still yours, now with a fast, sourced answer to compare against.
They can, one council at a time. Each has its own format, some are often offline, and none gives your HR or claims software a structured answer. DocTrace gives one request format, one response shape and a source on every result, fast enough to sit inside a sign-up flow or a claims approval.
Every result carries the time its record was last confirmed, so you can see its age rather than take it on trust. We share the refresh schedule for each council before you integrate, so you know how current a lookup can be.
Registration numbers repeat across councils, so the verify call takes the council as well as the number and returns the record for the council you asked about. In bulk checks, every result names its council so you can confirm the match.
The National Medical Register and 26 state medical councils, including Karnataka, Maharashtra, Tamil Nadu, Andhra Pradesh, West Bengal, Uttar Pradesh, Gujarat, Kerala (Travancore Cochin), Delhi and Bihar, representing ~95% of the central register. We send the council list and coverage per council before you integrate, so you know exactly what a lookup can answer.
No. DocTrace is an independent verification service built on registers that councils publish for public inspection. For a legal determination of a doctor’s standing, the issuing council remains the authority.
No. DocTrace confirms the registration and the qualification the register records. If a role needs a degree checked with the university, that step stays with you, but DocTrace removes the registration lookup and leaves you only the exceptions.
It is a standard REST API returning JSON over HTTPS, so it slots into an HMIS, CRM, claims engine or onboarding app with an ordinary HTTP call. Most teams run their first lookup within the hour.
Verify a doctor, check a whole roster, or search by name. Plain HTTPS and JSON, so any backend can call it.
https://api.doctrace.scangeni.usBearer key100 lookups · 60 req/mintypically under 1 sJSON over HTTPSThree steps to your first verified doctor.
verified, then registration_status, then disciplinary_standing.status.curl "https://api.doctrace.scangeni.us/api/v1/doctors/verify?council=Karnataka%20Medical%20Council®_no=000000" \ -H "Authorization: Bearer YOUR_API_KEY"
import requests
r = requests.get(
"https://api.doctrace.scangeni.us/api/v1/doctors/verify",
params={"council": "Karnataka Medical Council", "reg_no": "000000"},
headers={"Authorization": "Bearer YOUR_API_KEY"},
timeout=5,
)
data = r.json()
if data.get("verified"):
p = data["practitioner"]
print(p["name"], p["registration_status"], data["disciplinary_standing"]["status"])
else:
print(data.get("message")) const url = new URL("https://api.doctrace.scangeni.us/api/v1/doctors/verify");
url.search = new URLSearchParams({ council: "Karnataka Medical Council", reg_no: "000000" });
const res = await fetch(url, { headers: { Authorization: "Bearer YOUR_API_KEY" } });
const data = await res.json();
if (data.verified) {
console.log(data.practitioner.name, data.disciplinary_standing.status);
} else {
console.log(data.message);
} The name, number and key above are placeholders. Use your own key and a real registration number.
A sandbox that needs no key and no sign-up. It runs in your browser on made-up doctors, so nothing here is real data and no request leaves the page.
Press Send request.
The console above, plus the same sample responses as a file to mock against in your own tests.
Download sample responses (JSON) ↓Email us and we send a real key for the live API with 100 lookups, usually within one working day.
Email for an API key →Send your key on every request, in a header.
Authorization: Bearer YOUR_API_KEY # or X-API-Key: YOUR_API_KEY
X-Quota-Limit: 100 X-Quota-Used: 3 X-Quota-Remaining: 97
403 QUOTA_EXHAUSTED.Six endpoints. Open one to see parameters, a request and a response.
/api/v1/doctors/verify Verify by council and number The everyday call. Send the council and the registration number you were given and get the record back.
| Parameter | Notes | |
|---|---|---|
council | required | Council name, for example Karnataka Medical Council. |
reg_no | required | The registration number. |
uid | optional | A DocTrace ID, if you already hold one. |
curl "https://api.doctrace.scangeni.us/api/v1/doctors/verify?council=Karnataka%20Medical%20Council®_no=000000" \ -H "Authorization: Bearer YOUR_API_KEY"
{
"ok": true,
"verified": true,
"canonical_uid": "DT-KMC-000000",
"practitioner": {
"name": "A. Example",
"registration_number": "000000",
"state_medical_council": "Karnataka Medical Council",
"registration_date": "2015-06-01T00:00:00.000Z",
"registration_year": 2015,
"registration_status": "active",
"qualification": "MBBS, MD (General Medicine)",
"university": "Example University of Health Sciences",
"college": null
},
"disciplinary_standing": {
"has_disciplinary_record": false,
"status": "CLEAN_STANDING",
"orders": []
},
"hospital_affiliations": [],
"statutory_provenance": {
"source": "National Medical Commission & State Medical Council Statutory Rolls",
"verified_at": "2026-10-22T14:42:48.673Z"
}
}/api/v1/doctors/:canonical_uid Fetch by DocTrace ID Once you store a DocTrace ID against a doctor, this is the fastest way to re-check them.
| Parameter | Notes | |
|---|---|---|
canonical_uid | path | For example DT-KMC-000000: council code plus registration number. |
curl "https://api.doctrace.scangeni.us/api/v1/doctors/DT-KMC-000000" \ -H "Authorization: Bearer YOUR_API_KEY"
{
"ok": true,
"verified": true,
"canonical_uid": "DT-KMC-000000",
"practitioner": {
"name": "A. Example",
"registration_number": "000000",
"state_medical_council": "Karnataka Medical Council",
"registration_date": "2015-06-01T00:00:00.000Z",
"registration_year": 2015,
"registration_status": "active",
"qualification": "MBBS, MD (General Medicine)",
"university": "Example University of Health Sciences",
"college": null
},
"disciplinary_standing": {
"has_disciplinary_record": false,
"status": "CLEAN_STANDING",
"orders": []
},
"hospital_affiliations": [],
"statutory_provenance": {
"source": "National Medical Commission & State Medical Council Statutory Rolls",
"verified_at": "2026-10-22T14:42:48.673Z"
}
}/api/v1/doctors/bulk-verify Bulk verify, up to 50 a call For credentialing runs, CRM clean-ups and scheduled roster checks. Each item is a registration number or a name.
| Parameter | Notes | |
|---|---|---|
doctors | required | Array of up to 50 items, each { "registration_number": "…" } or { "name": "…" }. |
Heads up. Registration numbers repeat across councils. A bare number can match a doctor in a different council, so check the council returned on every result, or use the verify call when you need one exact match.
curl -X POST "https://api.doctrace.scangeni.us/api/v1/doctors/bulk-verify" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "doctors": [
{ "registration_number": "000000" },
{ "name": "B. EXAMPLE" }
] }'{
"ok": true,
"summary": {
"total_queried": 2,
"verified_in_registry": 2,
"timestamp": "2026-10-22T14:42:50.403Z"
},
"results": [
{
"input_query": "000000",
"status": "found",
"doctor_id": "00000000-0000-0000-0000-000000000000",
"name": "A. Example",
"registration_number": "000000",
"council": "Karnataka Medical Council",
"qualification": "MBBS, MD (General Medicine)"
},
{
"input_query": "B. EXAMPLE",
"status": "found",
"doctor_id": "00000000-0000-0000-0000-000000000001",
"name": "B. Example",
"registration_number": "000001",
"council": "Maharashtra Medical Council",
"qualification": "MBBS"
}
]
}/api/doctors/search Search by name Fuzzy, typeahead-style search across names, qualifications and councils. Use it to find a number, then verify.
| Parameter | Notes | |
|---|---|---|
q | required | Search text, 3 to 80 characters. |
curl "https://api.doctrace.scangeni.us/api/doctors/search?q=Example" \ -H "Authorization: Bearer YOUR_API_KEY"
{
"ok": true,
"doctors": [
{
"name": "A. Example",
"registration_number": "000000",
"state_medical_council": "Karnataka Medical Council",
"registration_year": 2015,
"qualification": "MBBS, MD (General Medicine)",
"university": "Example University of Health Sciences"
}
]
}/api/doctors/passport Doctor passport The fuller dossier for one doctor, with identity details and the trail of where each field came from.
| Parameter | Notes | |
|---|---|---|
q | required | A DocTrace ID or a registration number. |
curl "https://api.doctrace.scangeni.us/api/doctors/passport?q=DT-KMC-000000" \ -H "Authorization: Bearer YOUR_API_KEY"
{
"ok": true,
"passport": {
"doctor_id": "00000000-0000-0000-0000-000000000000",
"identity": {
"name": "A. Example",
"registration_number": "000000",
"state_medical_council": "Karnataka Medical Council",
"registration_year": 2015,
"qualification": "MBBS, MD (General Medicine)",
"address": "Example address, City 000000"
},
"field_provenance_trail": [],
"verification_status": "registry_only",
"generated_at": "2026-10-22T14:42:49.365Z"
}
}/healthz Health check Is the service up and talking to its database? Use it for your own monitoring. GET or HEAD.
curl "https://api.doctrace.scangeni.us/healthz"
{ "ok": true, "service": "doctrace-website" }Five outcomes cover almost every call. Try each one in the sandbox: it shows the response and what your code should do.
const res = await fetch(url, { headers });
if (res.status === 404) return "not_found";
if (res.status === 429 || res.status === 503) return retryLater();
const d = await res.json();
if (!d.verified) return "not_found";
if (d.practitioner.registration_status !== "active") return "inactive";
if (d.disciplinary_standing.status === "SANCTIONED") return "review";
return "ok"; Standard HTTP status codes. Failed calls return { "ok": false, "message": "…" }.
| Code | Meaning | What to do |
|---|---|---|
200 | OK | Request succeeded. Check verified in the body. |
400 | Bad request | A required parameter is missing, or the JSON body is invalid. |
401 | Unauthorised | No key, or an invalid key. Error code API_KEY_REQUIRED. |
403 | Quota used up | The key has no lookups left. Error code QUOTA_EXHAUSTED. |
404 | Not found | No such doctor in the registers. |
429 | Too many requests | Over the rate limit. Wait, then retry with backoff. |
500 | Server error | Unexpected failure. Retry once, then contact us. |
503 | Busy | Heavy burst load. Retry with backoff. |
One standard record, whichever council it came from. Fields can be null, so handle missing values.
practitionername | string | Full name, as on the register. |
registration_number | string | The council’s licence number. |
state_medical_council | string | The council that issued it. |
registration_date | date | null | ISO-8601, when known. |
registration_status | string | active, suspended or cancelled. |
qualification | string | For example MBBS, MD (General Medicine). |
university | string | Degree-granting university. |
college | string | null | Medical college, when known. |
disciplinary_standinghas_disciplinary_record | boolean | True if any order is on file. |
status | string | CLEAN_STANDING or SANCTIONED. |
orders[] | array | event_type, event_date, authority, order_reference, description, source_url. |
hospital_affiliations[]hospital_name | string | Canonical hospital name. |
hospital_city | string | City and state are also returned. |
nabh_accredited | boolean | Whether the hospital is NABH-accredited. |
department · designation | string | Where and in what role. |
is_current · last_verified_at | boolean · date | Whether it is a current post, and when it was last confirmed. |
statutory_provenancesource | string | The registers the record was built from. |
verified_at | timestamp | When it was last confirmed. Keep it with your record. |
Share of registry records carrying each field, from the platform’s own statistics.
Registration numbers repeat across councils. Use the verify call with both, and check the council on bulk results.
Store the response and its verified_at beside your own record. That is your dated evidence.
Run bulk-verify across your roster or CRM, 50 at a time, and review only what changed.
In our tests from India a round trip took about half a second, mostly network time. Set a timeout of 5 seconds, retry 429 and 503 with backoff, and do not retry 404.
Keep the key in a header on your backend. Never put it in a URL or in browser code.
You send a registration number or a name and get practitioner data back. No patient data is involved. Requests are metered and logged per key.
Email us for an API key. We usually reply within one working day.
Short answers for security, legal and procurement teams. Anything we cannot state as a fact today is listed under “In writing before go-live”, not guessed.
Records from public medical registers, one record per doctor. No patient, clinical or prescription data.
Each result names the register it came from and shows when it was last confirmed.
All API traffic uses HTTPS.
Access uses a bearer key. Every key has its own quota and rate limit, and usage is metered and logged per key.
A registration number or a name on each request. You never send patient data.
DocTrace is an independent service built on published registers. The issuing council stays the authority.
We answer these in a written pack before any production key is issued. Send us your own questionnaire and we will answer it too.
| Topic | What you get |
|---|---|
| Data-processing terms | A written agreement covering what we receive from you and how it is used. |
| Hosting | Where the service runs and who hosts it. |
| Logs | Which request logs we keep, and for how long. |
| Encryption and backups | How data is protected at rest and how it is backed up. |
| Incidents | A named contact, and how fast we tell you about a security incident. |
| Availability and support | Uptime reporting, support hours and escalation. |
| Change policy | How we announce API changes and retire old versions. |
| Access controls | Key rotation and IP allow-list options. |
DocTrace is a ScanGeni Ventures product.
doctrace@scangeni.us
We reply within one working day.
Privacy policy · Terms
These cover this website. API use will be covered by a separate written agreement.
Tell us what you verify and roughly how many checks a month. We'll set up a pilot and walk you through coverage, so you know what it will and won't answer.
Or write to doctrace@scangeni.us. We reply within one working day.
DocTrace is an independent verification service, not an official registry. It does not replace the issuing council's determination. Photographs on this page are AI-generated illustrations.