KATELYNN AMBER PICABO SALYAN
NPI 1487500526
Nurse Practitioner - Family in Chardon, OH
About Katelynn Amber Picabo Salyan NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
KATELYNN AMBER PICABO SALYAN (NPI 1487500526) is an individual family provider in Chardon, Ohio, licensed in Ohio (APRN.CNP.0041705) and active in the NPI registry since March 2026. She is enrolled in Medicare PECOS and is a graduate of Other (2025).
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)
Katelynn Amber Picabo Salyan 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 44024 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 Katelynn Salyan's NPI number?
The NPI number for Katelynn Salyan is 1487500526. It was assigned to this individual provider in the NPPES registry on March 10, 2026.
Where is Katelynn Salyan located?
Katelynn Salyan practices at 531 5th Ave, Chardon, OH 44024. The listed phone number is (440) 285-2300.
What is Katelynn Salyan's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Family, with taxonomy code 363LF0000X.
Is Katelynn Salyan enrolled in Medicare?
Yes. Katelynn Salyan is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Katelynn Salyan was last updated on March 10, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 5 months 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.