DANIEL T. ACOSTA – NPI #1144304544
Technician/Technologist

DANIEL ACOSTA is a technician located in SAN DIEGO, CA. NPPES has assigned the NPI number 1144304544 to DANIEL ACOSTA on October 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 156FX1700X from the Health Care Provider Taxonomy code set, which is classified as Technician/Technologist, specializing in Ocularist

The NPI profile was previously updated about 19 years ago on Dec 06, 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 DANIEL ACOSTA below.

NPI Profile for
DANIEL T. ACOSTA

NPI Number
1144304544
Enumeration Date

(more than 19 years ago)
Entity Type
Type-1  Individual (Male)
Legal Name
DANIEL T. ACOSTA
Primary location
635 C ST
APT. 502
SAN DIEGO, CA 92101-5381
Phone: (619) 235-8950 Fax: (619) 235-8959
Mailing address
Same as primary location
Sole Proprietor
Yes
Updated
Identifiers

Identifiers for DANIEL ACOSTA

Identifiers are used to associate other provider identifiers such as Medicaid or other insurers (ie:, Blue Cross, Blue Shield, Aetna, Kaiser-Permanente, etc.), with their NPI number. These identifiers can be used in matching an NPI number to an insurer's records. However, not all providers have such numbers and not all providers choose to include them in their NPI information.

DescriptionIssuerStateIdentifier
OTHERBLUE SHIELDCAZZZ02268Z
MEDICAIDCADXX00002F
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
156FX1700X
- Technician/Technologist / Ocularist (Primary)

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.