NPI Search Filters

Overview

NPI search criteria are specified through the use of a list of WhereClause objects, consisting of three properties: Field, Operator, and Value. An NPI much match all criteria to be included in search results. What follows is a comprehensive listing of valid field names and operators.

Fields

Field names are case-insensitive:

  • BusinessLine

    • Identifies the kinds of claims associated with the NPI in the latest two years' data

    • May be any of the following case-insensitive values:

      • HHA

      • SNF

      • Hospice

      • Physician

      • HHA-Physician

        • Matches if the physician was an HHA patient’s following physician at the HHA, the physician who saw them most recently, or saw them up to 3 months prior to their HHA care

      • Hospice-Physician

        • Matches if the physician was a hospice patient’s attending physician as the hospice, the physician who saw them most recently, or saw them up to 3 months prior to their hospice care

      • HHA-Facility

        • Matches if any patients received treatment at an HHA within 30 days of receiving treatment at the identified facility in the last two years

      • Hospice-Facility

        • Matches if any patients received treatment at a Hospice within 30 days of receiving treatment at the identified facility in the last two years

  • CCN

  • City

  • County

  • FirstName

  • LastName

  • Latitude

  • Longitude

  • Name

  • NPI

  • NPPES_Specialty

  • PhoneNumber

  • Prefix

  • Specialty

  • State

  • StreetAddress

  • Subspecialty

  • Suffix

  • TaxonomySpecialty

  • TaxonomySubspecialty

  • TrellaTypeCode

  • TrellaTypeDescription

  • TrellaTypeLongDescription

  • UnitAddress

  • ZipCode

Special Field: DxCategory

Used to filter NPIs with claims in a specified diagnostic category by volume. When filtering on this field, the WhereClause value must be in the format [category]@[claimType][comparison][target]. For example, Nervous System@Physician>200

  • The valid values that can currently replace [category] are available at GET https://dataapi.trellahealth.com/DiagnosticCategories

  • [claimType] can be replaced with one of:

    • HHA

    • Hospice

    • Inpatient

    • Outpatient

    • Physician

    • SNF

  • [comparison] supersedes the WhereClause operator and can be one of:

    • =

    • !=

    • >

    • >=

    • <

    • <=

To sort by diagnostic category, use [category]@[claimType]

Operators

All operators can be negated with a leading exclamation mark (for example, the negation of exactly is !exactly. These are the valid operators:

  • between

    • Matches NPIs for which the specified field has a value in an inclusive range. There WhereClause Value should be in the format [minimumValue],[maximumValue]. For example:

      { "Field": "Latitude", "Operator": "between", "Value": "35,45" }
  • contains

    • Matches NPIs for which the specified field is a string that contains the specified value as a substring

  • ends_with

    • Matches NPIs for which the specified field is a string ending with the specified value

  • exactly

    • Matches NPIs for which the specified field has exactly the specified value

  • greater_than

    • Matches NPIs for which the specified field has a value greater than the specified value

  • greater_than_or_equal

    • Matches NPIs for which the specified field has a value greater than or equal to the specified value

  • less_than

    • Matches NPIs for which the specified field has a value less than the specified value

  • less_than_or_equal

    • Matches NPIs for which the specified field has a value less than or equal to the specified value

  • one_of

    • Matches NPIs for which the specified field has a value that exactly matches any one value in a specified comma-separated list. For example:

      { "Field": "Specialty", "Operator": "one_of", "Value": "Radiology,Radiologic Technologist,Nuclear Medicine" }
  • starts_with

    • Matches NPIs for which the specified field is a string ending with the specified value