JORDAN WIEBE DO
NPI 1215590831
Surgery - Plastic and Reconstructive Surgery in Phoenix, AZ
About Jordan Wiebe Do NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
JORDAN WIEBE DO (NPI 1215590831) is an individual plastic and reconstructive surgery provider in Phoenix, Arizona, licensed in Arizona (012361) and active in the NPI registry since April 2019. She is enrolled in Medicare PECOS and is a graduate of Oklahoma State University College Of Osteopathic Medicine (2019).
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)
Jordan Wiebe Do is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 9
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
PHOENIX, AZ 85016
PHOENIX, AZ 85016
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 Jordan Wiebe's NPI number?
The NPI number for Jordan Wiebe is 1215590831. It was assigned to this individual provider in the NPPES registry on April 18, 2019.
Where is Jordan Wiebe located?
Jordan Wiebe practices at 2801 E Camelback Rd Ste 100, Phoenix, AZ 85016. The listed phone number is (480) 680-9903.
What is Jordan Wiebe's specialty?
The primary specialty registered for this NPI is Surgery, specializing in Plastic and Reconstructive Surgery, with taxonomy code 2086S0122X.
Is Jordan Wiebe enrolled in Medicare?
Yes. Jordan Wiebe is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Jordan Wiebe was last updated on July 30, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 11 days 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.