ROSIN EYECARE, P.A.
NPI 1790330942
Optometrist in Lauderhill, FL
About Rosin Eyecare, P.a. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ROSIN EYECARE, P.A. (NPI 1790330942), doing business as Isee Eyecare, is a healthcare organization registered as an optometrist in Lauderhill, Florida and active in the NPI registry since August 2019. The organization lists Nicholas A Chiaramonti, Director, as its authorized official.
NPPES Registry Identity
Specialties & Licenses
Other Names 1
Group Practice 1
Accepted Insurance
Other Providers at the Same Location NPPES 3
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
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 Rosin Eyecare, P.A.'s NPI number?
The NPI number for Rosin Eyecare, P.A. is 1790330942. It was assigned to this organization in the NPPES registry on August 5, 2019. The provider is doing business as iSee Eyecare.
Where is Rosin Eyecare, P.A. located?
Rosin Eyecare, P.A. is located at 7187 W Oakland Park Blvd, Lauderhill, FL 33313. The listed phone number is (954) 578-9599.
What is Rosin Eyecare, P.A.'s specialty?
The primary specialty registered for this NPI is Optometrist with taxonomy code 152W00000X.
What insurance does Rosin Eyecare, P.A. accept?
Health plans from Florida Blue (BlueCross BlueShield FL), Florida Blue HMO (a BlueCross BlueShield FL company), Molina Healthcare and Oscar Health Maintenance Organization of Florida list Rosin Eyecare, P.A. as in-network in at least one marketplace plan. Coverage varies by plan and year; verify with the insurer or the provider before a visit.
When was this NPI record last updated?
The NPPES record for Rosin Eyecare, P.A. was last updated on August 5, 2019. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 7 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.