JEFFREY SCOTT ALDERMAN MD
NPI 1356311757
Internal Medicine - Hospice and Palliative Medicine in Tulsa, OK
About Jeffrey Scott Alderman Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
JEFFREY SCOTT ALDERMAN MD (NPI 1356311757) is an individual hospice and palliative medicine provider in Tulsa, Oklahoma, licensed in Oklahoma (21706) and active in the NPI registry since January 2006. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 2
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Jeffrey Scott Alderman Md is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 13
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
TULSA, OK 74135
TULSA, OK 74135
TULSA, OK 74135
Frequently Asked Questions NPPES & CMS
Common questions about this NPI record, answered from the official NPPES registry and CMS datasets shown on this page.
What is Jeffrey Alderman's NPI number?
The NPI number for Jeffrey Alderman is 1356311757. It was assigned to this individual provider in the NPPES registry on January 26, 2006.
Where is Jeffrey Alderman located?
Jeffrey Alderman practices at 4444 E. 41st St 3rd Floor, Ste A, Tulsa, OK 74135. The listed phone number is (918) 619-4101.
What is Jeffrey Alderman's specialty?
The primary specialty registered for this NPI is Internal Medicine, specializing in Hospice and Palliative Medicine, with taxonomy code 207RH0002X.
Is Jeffrey Alderman enrolled in Medicare?
Yes. Jeffrey Alderman is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Jeffrey Alderman was last updated on August 20, 2007. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 18 years ago. If this record has changed at CMS more recently, you can request an on-demand re-check against the live CMS registry, directly from this page.