How a verification is assembled
- Interpret the query without discarding the original spelling or number.
- Resolve registration identifiers within the medical-system and authority namespaces.
- Search the maintained database first.
- When no local record matches, perform a user-triggered lookup against a policy-approved official source and cache only minimized professional fields.
- Store a new, timestamped observation instead of overwriting history.
- Attach provenance and limitations to each normalized claim.
- Detect conflicts and route high-risk ambiguity to a reviewer.
Status language
| Status | Meaning |
|---|---|
| An approved authoritative source explicitly confirms the claim. | |
| ✓Registry listed | The record is listed; the source may not expose current standing. |
| ✓Publicly listed | A public professional source reports a workplace or affiliation that the facility has not necessarily confirmed. |
| !Possible match | Some identity fields agree, but evidence is insufficient to conclude. |
| ✓Unable to check | The source was unavailable, blocked by policy, or does not support the query. |
Identity resolution and deduplication
The canonical registration key combines country, medical system, authority, and normalized registration number. Exact canonical keys can join observations for one registration. Names are normalized and token-matched to generate candidates, but fuzzy name similarity, relatives’ names, qualifications, years, institutions, and locations never authorize a silent merge by themselves. Conflicts keep candidates separate for review.
National index versus current status
The historical NMC IMR is used as a broad discovery index. Its own page describes data through 2021 and notes council-specific gaps. An IMR match is therefore labeled “registry listed,” not “currently active.” Current status must come from the relevant state council or newer NMR evidence.
Workplace enrichment
Hospitals and clinics are separate entities with normalized names, public business addresses, identifiers and time-stamped evidence. Doctor-to-facility relationships retain their own confidence and source type. A directory listing, corporate role and facility-confirmed appointment are never treated as equivalent. Conflicting addresses are displayed rather than silently resolved.
Normalization and minimization
Qualification wording is preserved beside a normalized title such as MBBS. The maintained projection excludes home addresses, birth dates, relatives’ names, personal phone numbers, personal email addresses, and photographs—even when a source response contains them. Public hospital and clinic addresses are allowed only as professional workplace context. Source extracts are hashed so later changes can be detected without storing unnecessary personal data.
Maintenance
Each ingestion run records its source, time, outcome, and non-sensitive counts. New observations supersede rather than erase history. Source policies separately control public search, automation, caching, republication, retention, and a connector kill switch. Coverage reports both the source-reported population and how many records are locally indexed and enriched.
Adverse-record safeguards
Adverse records are searched separately. An authority-namespaced registration identifier is the primary matching basis. Ambiguous name-only matches stay private and require human approval. Restoration, expiry, appeal, and superseding context must remain attached to any published record.
What this service does not say
Registration is not a rating of clinical competence, treatment quality, ethics, patient satisfaction, malpractice history, or suitability for a specific condition. Coverage is a description of sources checked, not a score of the practitioner.