-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deactivated NPIs #22
Comments
@jgarrigan thanks for the question. The function npi_is_valid() only determines whether the NPI meets the check digit requirement described below: While this can be useful for catching invalid NPIs due to data integrity problems, it does not tell you anything about the administrative status of the NPI. Looking at the NPPES field map, I would expect that deactivation information, if present at all for a record, would probably appear in the following fields:
Deactivation reason codes are given in data dissemination file code values: Previously deactivated NPIs that were reactivated might have the date of reactivation:
You might wish to filter for these fields and apply suitable logic to meet the goals of your project. If you have more detailed questions about the meaning of the data elements themselves, I suggest contacting the NPPES NPI Registry. Good luck! |
@jgarrigan I just stumbled across this same issue. Were you ever able to determine a resolution? |
@frankfarach Thank you very much for creating this package. I only discovered it after I miserably failed to create a function of my own.
I am passing about 3000 call to the API and some of these NPIs appear to be deactivated
Is there an approach that can be used to handle deactivated NPIs?
The deactivated NPIs appear to be valid when I pass them to npi_is_valid()
An example of a deactivated NPI is 1710983663
This is an example of what I am trying to run
The text was updated successfully, but these errors were encountered: