MEGAN ALISE LYNCH MD
NPI 1699494443
Anesthesiology in Rochester, MN
About Megan Alise Lynch Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MEGAN ALISE LYNCH MD (NPI 1699494443) is an individual anesthesiology provider in Rochester, Minnesota, licensed in Minnesota (80259) and active in the NPI registry since August 2022. She is enrolled in Medicare PECOS, maintains a secondary practice location in Sacramento, and is a graduate of University Of California, Davis School Of Medicine (2024).
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)
Megan Alise Lynch Md is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
ROCHESTER, MN 55905
ROCHESTER, MN 55905
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 Megan Lynch's NPI number?
The NPI number for Megan Lynch is 1699494443. It was assigned to this individual provider in the NPPES registry on August 24, 2022.
Where is Megan Lynch located?
Megan Lynch practices at 200 1st St SW, Rochester, MN 55905. The listed phone number is (507) 284-2511.
What is Megan Lynch's specialty?
The primary specialty registered for this NPI is Anesthesiology with taxonomy code 207L00000X.
Is Megan Lynch enrolled in Medicare?
Yes. Megan Lynch is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Megan Lynch was last updated on July 31, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 12 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.