BRIAN JAMES MCMAHON LMFT
NPI 1205395928
Counselor - Mental Health in Kansas City, MO
About Brian James Mcmahon Lmft NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BRIAN JAMES MCMAHON LMFT (NPI 1205395928) is an individual mental health provider in Kansas City, Missouri, licensed in California (112178) and active in the NPI registry since March 2019. He has opted out of Medicare through August 26, 2027.
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
Opted out of Medicare
Brian James Mcmahon Lmft has filed a Medicare opt-out affidavit. Services are provided under private contract between the provider and the patient, and are not billed to or reimbursed by Medicare. The opt-out is on file from August 26, 2025 through August 26, 2027.
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 Brian Mcmahon's NPI number?
The NPI number for Brian Mcmahon is 1205395928. It was assigned to this individual provider in the NPPES registry on March 13, 2019.
Where is Brian Mcmahon located?
Brian Mcmahon practices at 2942 Wabash Ave, Kansas City, MO 64109. The listed phone number is (503) 816-9435.
What is Brian Mcmahon's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Mental Health, with taxonomy code 101YM0800X.
Is Brian Mcmahon enrolled in Medicare?
No. Brian Mcmahon has opted out of Medicare through August 26, 2027. Care is provided under private contracts, and Medicare does not pay for services furnished by providers who have opted out.
When was this NPI record last updated?
The NPPES record for Brian Mcmahon was last updated on March 13, 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.