RICHARD H. SHULMAN DDS – NPI #1588686109
Oral & Maxillofacial Surgery

Oral and maxillofacial surgeons are trained to recognize and treat a wide spectrum of diseases, injuries and defects in the head, neck, face, jaws and the hard and soft tissues of the oral and maxillofacial region. They are also trained to administer anesthesia, and provide care in an office setting. They are trained to treat problems such as the extraction of wisdom teeth, misaligned jaws, tumors and cysts of the jaw and mouth, and to perform dental implant surgery.

RICHARD SHULMAN is an oral & maxillofacial surgeon located in LANSDALE, PA. NPPES has assigned the NPI number 1588686109 to RICHARD SHULMAN on July 24, 2006. It is a Type-1 NPI, indicating this NPI number is associated with an individual. The primary taxonomy selected by this provider is 204E00000X from the Health Care Provider Taxonomy code set, which is classified as Oral & Maxillofacial Surgery.

The NPI profile was previously updated about 19 years ago on Jul 08, 2007. Use the NPI data found here to bill health insurance companies, identify providers enrolled in Medicare and Medicaid services or other HIPAA compliant transactions. See the complete NPI profile for RICHARD SHULMAN below.

NPI Profile for
RICHARD H. SHULMAN

NPI Number
1588686109
Enumeration Date

(about 20 years ago)
Entity Type
Type-1  Individual (Male)
Legal Name
RICHARD H. SHULMAN
Credentials
DDS
Primary location
2100 N BROAD ST
STE 106
LANSDALE, PA 19446
Phone: (215) 368-8104 Fax: (215) 368-3711
Mailing address
Same as primary location
Sole Proprietor
No
Updated
Taxonomy Code(s)

A taxonomy code is a code that describes the health care service provider's type, classification, and the area of specialization. The primary specialty for this provider is indicated as (Primary) below.

Taxonomy Classification / Specialization State License
204E00000X
- Oral & Maxillofacial Surgery (Primary)
PA DS16838

The taxonomy codes are selected by the provider at the time of NPI registration. Selection of a taxonomy code does not replace any credentialing or validation process that the provider requesting the code should complete.