BRYAN JENKIN
NPI 1275393696
Student in an Organized Health Care Education/Training Program in Baltimore, MD
About Bryan Jenkin NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BRYAN JENKIN (NPI 1275393696) is an individual student in an organized health care education/training program in Baltimore, Maryland and active in the NPI registry since March 2024. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Bryan Jenkin is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
BALTIMORE, MD 21287
BALTIMORE, MD 21287
BALTIMORE, MD 21287
BALTIMORE, MD 21287
BALTIMORE, MD 21287
BALTIMORE, MD 21287
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 Bryan Jenkin's NPI number?
The NPI number for Bryan Jenkin is 1275393696. It was assigned to this individual provider in the NPPES registry on March 21, 2024.
Where is Bryan Jenkin located?
Bryan Jenkin practices at 1800 Orleans St # 110, Baltimore, MD 21287. The listed phone number is (410) 955-5020.
What is Bryan Jenkin's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Bryan Jenkin enrolled in Medicare?
Yes. Bryan Jenkin is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Bryan Jenkin was last updated on May 21, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.