YVETTE SIDONIE TEMKENG
NPI 1417619966
Nurse Practitioner - Primary Care in Las Vegas, NV
About Yvette Sidonie Temkeng NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
YVETTE SIDONIE TEMKENG (NPI 1417619966) is an individual primary care provider in Las Vegas, Nevada, licensed in Nevada (842658) and active in the NPI registry since October 2021. She is enrolled in Medicare PECOS and is a graduate of Other (2021).
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)
Yvette Sidonie Temkeng 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 89113 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 Yvette Temkeng's NPI number?
The NPI number for Yvette Temkeng is 1417619966. It was assigned to this individual provider in the NPPES registry on October 12, 2021.
Where is Yvette Temkeng located?
Yvette Temkeng practices at 5135 S Durango Dr Ste 102, Las Vegas, NV 89113. The listed phone number is (702) 407-9994.
What is Yvette Temkeng's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Primary Care, with taxonomy code 363LP2300X.
Is Yvette Temkeng enrolled in Medicare?
Yes. Yvette Temkeng is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Yvette Temkeng was last updated on October 12, 2021. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 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.