Practitioner returned by /Practitioner/{id} is missing from /Practitioner search #1708
jayant-walvekar-falconeer
announced in
Q&A
Replies: 1 comment
|
Hi @jayant-walvekar-falconeer — yes, this is expected behavior driven by a default filter on What we found on your dev instance
Why
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We have an active practitioner that can be fetched by id but does not appear in any /Practitioner search response, regardless of search parameters. We are trying to understand whether this is expected behavior or an index issue.
Reproduction (same OAuth token, Content-Type: application/fhir+json):
GET /Practitioner/{id} returns 200 with active: true.
GET /Practitioner returns a Bundle that does not contain this practitioner.
GET /Practitioner?_count=100 returns the same Bundle with the same total; practitioner still missing (so it is not a pagination issue).
GET /Practitioner?_count=200&active=true returns the same total; practitioner still missing.
GET /Practitioner?email= returns total=0.
Other practitioners on the same primary practice location and with similar configuration are returned by /Practitioner search correctly. Toggling the practitioner active off and on in the UI did not change the search results.
If you have access to my dev sandbox then you can try this. The ID of the entity in question is 9832e....
Questions:
Is there a known condition (creation path, missing field, role configuration, location membership, internal flag) that causes a practitioner to be excluded from /Practitioner search while remaining fetchable by id?
Is there a way to force the practitioner to re-appear in /Practitioner search results without contacting support — for example, an admin action in the UI, or a specific field edit that triggers a re-index?
Has anyone else hit this and found a workaround?
Any pointers appreciated.
All reactions