NPI profile
SHERIF AHMED
NPI record status, taxonomy, official source timestamp, and OIG LEIE screening context.
Identity
- NPI
- 1053544577
- Entity type
- NPI-1
- Primary taxonomy
- 101YM0800X
- NPI source updated
- Feb 28, 2011
- Enumeration date
- Sep 01, 2009
- Cache fetched
- May 05, 2026
NPI does not validate licensure, credentialing, Medicare enrollment, or current practice authority.
OIG LEIE screening
Exact OIG exclusion match by NPI.
NPI addresses
| Purpose | Address | Phone |
|---|---|---|
| MAILING | 2675168948 | |
| LOCATION | 2157444343 |
NPI lookup by number
How this NPI registry lookup is interpreted
Last verified: 2026-05-31. date_retrieved: 2026-05-31. SourceCheckHealth starts with the exact 10-digit NPI Registry record, then keeps source dates, taxonomy, address context, and OIG LEIE screening status together for review.
| Signal | What this page shows | Review limit |
|---|---|---|
| NPI Registry | NPI-1 record with enumeration and last-updated dates. | NPI issuance does not validate licensure, credentialing, Medicare enrollment, or current practice authority. |
| Taxonomy | 101YM0800X | Taxonomy helps classify the record but does not prove active scope of practice. |
| Addresses | 2 public address rows available on this lookup. | Addresses can be mailing or practice locations and should be checked against current official context. |
| OIG LEIE | Exact OIG exclusion match by NPI. | Possible or fuzzy matches require manual review against OIG before action. |
CMS field provenance
NPI registry field provenance
Last verified: 2026-05-31. date_retrieved: 2026-05-31. The NPPES API field map ties the lookup response to CMS source fields, so a reviewer can distinguish registry identity facts from SourceCheckHealth screening context.
| Lookup question | CMS API field | This record | Review note |
|---|---|---|---|
| Is this an individual or organization NPI? | enumeration_type | NPI-1 | Type 1 is an individual provider; Type 2 is an organizational provider. |
| When was the NPI assigned or updated? | basic.enumeration_date / basic.last_updated | Sep 01, 2009 / Feb 28, 2011 | Dates describe the public registry record, not current licensure or enrollment status. |
| Which taxonomy data came from CMS? | taxonomies[].code / taxonomies[].desc / taxonomies[].primary | 1 taxonomy on the record | Taxonomy helps classify the record but does not prove active scope of practice. |
| Which address purposes are present? | addresses[].address_purpose | MAILING, LOCATION | Address rows can be mailing, primary, or secondary practice locations and may need current confirmation. |
FAQ
Practical notes
What does an NPI lookup by number show?
It shows the public NPI Registry identity fields available for that 10-digit NPI, including entity type, taxonomy, source dates, public addresses, and related OIG LEIE screening context.
Does an NPI record validate licensure?
No. NPI data does not validate licensure, credentialing, Medicare enrollment, or current practice authority.
How should I use an NPI registry lookup with OIG screening?
Use the NPI record to anchor identity and taxonomy, then review OIG LEIE exact or possible matches with the official source links before taking any compliance action.
Which CMS fields matter most in an NPI lookup by number?
Start with the exact 10-digit NPI, entity type, enumeration date, last-updated date, primary taxonomy, and public address purpose. SourceCheckHealth keeps those fields beside OIG context so reviewers can see what came from the CMS NPI Registry before checking other sources.