DR. SCOTT FELTON HEINE DMIN, MDIV, MA
NPI 1053909515
Counselor - Professional in Jeffersonton, VA
About Dr. Scott Felton Heine Dmin, Mdiv, Ma NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. SCOTT FELTON HEINE DMIN, MDIV, MA (NPI 1053909515) is an individual professional provider in Jeffersonton, Virginia, licensed in Virginia (0701012917) and active in the NPI registry since January 2021. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Accepted Insurance
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. Scott Felton Heine Dmin, Mdiv, Ma is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
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 Scott Heine's NPI number?
The NPI number for Scott Heine is 1053909515. It was assigned to this individual provider in the NPPES registry on January 9, 2021.
Where is Scott Heine located?
Scott Heine practices at 17279 Banbury Ct, Jeffersonton, VA 22724. The listed phone number is (540) 878-0078.
What is Scott Heine's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Scott Heine enrolled in Medicare?
Yes. Scott Heine is registered in the Medicare PECOS enrollment system.
What insurance does Scott Heine accept?
Health plans from Providence Health Plan list Scott Heine as in-network in at least one marketplace plan. Coverage varies by plan and year; verify with the insurer or the provider before a visit.
When was this NPI record last updated?
The NPPES record for Scott Heine was last updated on December 11, 2023. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.