CHRISTOPHER MCBRIDE
NPI 1225860406
Nurse Practitioner - Acute Care in Long Beach, CA
About Christopher Mcbride NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
CHRISTOPHER MCBRIDE (NPI 1225860406) is an individual acute care provider in Long Beach, California, licensed in California (95030609) and active in the NPI registry since August 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)
Christopher Mcbride is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 90815 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Christopher Mcbride's NPI number?
The NPI number for Christopher Mcbride is 1225860406. It was assigned to this individual provider in the NPPES registry on August 16, 2024.
Where is Christopher Mcbride located?
Christopher Mcbride practices at 2201 N Lakewood Blvd Ste D624, Long Beach, CA 90815. The listed phone number is (205) 394-1966.
What is Christopher Mcbride's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Acute Care, with taxonomy code 363LA2100X.
Is Christopher Mcbride enrolled in Medicare?
Yes. Christopher Mcbride is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Christopher Mcbride was last updated on August 16, 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.