DR. GREGORY JOHN ARGYROS MD
NPI 1437129137
Internal Medicine - Pulmonary Disease in Olney, MD
About Dr. Gregory John Argyros Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. GREGORY JOHN ARGYROS MD (NPI 1437129137) is an individual pulmonary disease provider in Olney, Maryland, licensed in Pennsylvania (MD043212E) and active in the NPI registry since January 2006. He is enrolled in Medicare PECOS.
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)
Dr. Gregory John Argyros Md 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 20832 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 Gregory Argyros's NPI number?
The NPI number for Gregory Argyros is 1437129137. It was assigned to this individual provider in the NPPES registry on January 25, 2006.
Where is Gregory Argyros located?
Gregory Argyros practices at 16809 Ethelwood Ter, Olney, MD 20832. The listed phone number is (202) 782-6206.
What is Gregory Argyros's specialty?
The primary specialty registered for this NPI is Internal Medicine, specializing in Pulmonary Disease, with taxonomy code 207RP1001X.
Is Gregory Argyros enrolled in Medicare?
Yes. Gregory Argyros is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Gregory Argyros was last updated on July 13, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 30 days 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.