KRISSIA BRINGAS APRN
NPI 1376326686
Nurse Practitioner in Miami, FL
About Krissia Bringas Aprn NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
KRISSIA BRINGAS APRN (NPI 1376326686) is an individual nurse practitioner in Miami, Florida, licensed in Florida (APRN11024032) and active in the NPI registry since August 2023. She is enrolled in Medicare PECOS, maintains a secondary practice location in Miami, and is a graduate of Other (2022).
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Krissia Bringas Aprn 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 33183 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 Krissia Bringas's NPI number?
The NPI number for Krissia Bringas is 1376326686. It was assigned to this individual provider in the NPPES registry on August 18, 2023.
Where is Krissia Bringas located?
Krissia Bringas practices at 8200 SW 117th Ave Ste 404, Miami, FL 33183. The listed phone number is (470) 945-0588.
What is Krissia Bringas's specialty?
The primary specialty registered for this NPI is Nurse Practitioner with taxonomy code 363L00000X.
Is Krissia Bringas enrolled in Medicare?
Yes. Krissia Bringas is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Krissia Bringas was last updated on August 18, 2023. 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.