NPI
Detects NPI patterns.
- Type
- regex
- Engine
- universal
- Confidence
- high
- Confidence justification
- High confidence: validated with Luhn with 80840 prefix and supported by corroborative keyword evidence.
- Detection quality
- Verified
- Jurisdictions
- us
- Regulations
- CCPA/CPRA, FTC Act s5, HIPAA, State Breach Laws (US)
- Frameworks
- ISO 27001, ISO 27701, SOC 2
- Data categories
- phi, healthcare
- Scope
- narrow
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible
Pattern
\b[12]\d{9}\bCorroborative evidence keywords
MRN, medical record number, patient ID, NPI, DEA, medicare, medicaid, insurance ID, member ID, beneficiary, ICD-10, ICD-9, CPT, NDC, SNOMED, HCPCS, diagnosis code, procedure code, drug code
Proximity: 300 characters
Should match
1234567890— NPI starting with 12345678901— NPI starting with 21111111111— Repeated-digit NPI
Should not match
3234567890— Starts with 3 (must start with 1 or 2)234567890— Starts with 0 (must start with 1 or 2)123456789— Only 9 digits instead of 10
Known false positives
- Medical terminology in health education materials, research publications, clinical guidelines, or public health documents without patient-specific data. Mitigation: Require corroborative evidence keywords confirming patient context. Look for co-occurrence with patient identifiers such as medical record numbers or dates of birth.
- General wellness and fitness content using medical vocabulary without constituting protected health information. Mitigation: Layer with patient identifier patterns or healthcare-specific document structure detection to distinguish clinical records from general health content.