REEM BECHARA
NPI 1780377515
Counselor - Professional in Baltimore, MD

Active since May 29, 2023
827 MCHENRY ST, BALTIMORE, MD 21230(410) 300-7068 Get Directions Write a Review

NPPES record last updated: May 29, 2023. Verified against the NPPES registry weekly; last sync: October 25, 2026.

About Reem Bechara NPPES

Official registry information on file with the National Plan and Provider Enumeration System.

REEM BECHARA (NPI 1780377515) is an individual professional provider in Baltimore, Maryland, licensed in Maryland (LGP13722) and active in the NPI registry since May 2023.

NPPES Registry Identity

NPI1780377515
Entity TypeIndividualFemale
Primary Taxonomy101YP2500X
Provider Legal NameREEM BECHARA
Location Address827 MCHENRY STBaltimore, MD 21230-2133
Mailing Address827 Mchenry StBaltimore, MD 21230-2133 · (410) 300-7068
Sole ProprietorYes
Enumeration DateMay 29, 2023
NPPES CertifiedMay 29, 2023
✔ NPI 1780377515 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

★ Primary SpecialtyCounselor · ProfessionalBehavioral Health & Social Service Providers
Taxonomy Code101YP2500X
License✔ Licensed in MD · LGP13722
827 MCHENRY ST, Baltimore, MD 21230

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 Reem Bechara's NPI number?

The NPI number for Reem Bechara is 1780377515. It was assigned to this individual provider in the NPPES registry on May 29, 2023.

Where is Reem Bechara located?

Reem Bechara practices at 827 Mchenry St, Baltimore, MD 21230. The listed phone number is (410) 300-7068.

What is Reem Bechara's specialty?

The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.

When was this NPI record last updated?

The NPPES record for Reem Bechara was last updated on May 29, 2023. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.