Check whether the tenant successfully ingested an NPI on a roster
POST/roster-records/provider-lookup
Answers whether the tenant in the tenant-id header imported the NPI on a roster uploaded at or after timestamp (default: now minus 3 months).
What counts: only rows that were imported - row status COMPLETED or CRED_STARTED. Rows still awaiting approval, failed rows and terminations (CRED_STOPPED) do not.
States: with no statesToCredential, the response only says whether the NPI was found and gives the latest row. With states, every state must appear in the statesToCredential of some imported row; each state carries the latest row that contains it, and statesNotFound lists the rest. "Latest" is the most recently uploaded roster, then the last row in file order.
Entity type: PRACTITIONER (default); FACILITY is rejected as not supported yet.
Read-only. No row content is returned. tenantId in the body is optional and, when sent, must equal the header.
Request
Responses
- 200
- 400
- 401
- 403
- 500
- 503
Lookup result. npiFound=false is a normal answer, not an error.
Invalid NPI, unknown state, unsupported entity type, a bad or future timestamp, or a body tenantId that differs from the header.
Returned when the request carries no valid authentication.
Returned when the caller lacks the READ_ROSTER permission for this tenant.
A roster read failed.
The provider lookup is switched off.