THOM R. BRITTANY – NPI #1306288139
Technician, Other

A collective term for persons with specialized training in various narrow fields of expertise whose occupations require training and skills in specific technical processes and procedures; and where further classification is deemed unnecessary by the user.

THOM BRITTANY is a technician located in SAN FRANCISCO, CA. NPPES has assigned the NPI number 1306288139 to THOM BRITTANY on July 22, 2013. It is a Type-1 NPI, indicating this NPI number is associated with an individual. With multiple taxonomy codes selected, the primary taxonomy selected by this provider is 247200000X from the Health Care Provider Taxonomy code set, which is classified as Technician, Other.

The NPI profile was last updated on Jun 16, 2025. 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 THOM BRITTANY below.

NPI Profile for
THOM R. BRITTANY

NPI Number
1306288139
Enumeration Date

(about 13 years ago)
Entity Type
Type-1  Individual (Male)
Legal Name
THOM R. BRITTANY
Primary location
1500 FRANKLIN ST
SAN FRANCISCO, CA 94109-4523
Phone: (415) 474-7310 Fax:
Mailing address
Same as primary location
Sole Proprietor
Yes
Updated
Certification Date
Jun 16, 2025

Note: NPPES allows providers to attest to the accuracy of their NPI data. When a provider request any change to the NPI record, they will be able to attest to their changed NPI data, resulting in an updated certification date.

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
247200000X
- Technician, Other (Primary)
251S00000X
- Community/Behavioral Health

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.