Stream: patient administration WG
Topic: Person/Patient Search
Yuval Romm (Mar 17 2022 at 15:12):
How does one perform a search using demographic data ONLY across both Person AND Patient resources simultaneously when one does not necessarily know if a person is or is not a patient?
Is it implicit that if some Persons are NOT patients then ALL Patients must also have associated Person resources so that the search function will run against the Persons rather than Patients?
Scenario: Mother is NOT receiving care in our system but her child is receiving care.
Initially, the mother is represented by a Person resource and the child is a Patient resource.
Mother then presents herself at our urgent care clinic. What search do we perform to make sure we locate the mother's record not knowing if she's an existing Patient or a known Person?
René Spronk (Mar 17 2022 at 15:31):
You can't assume that Patients will have an associated person resource, nor the other way around. Your search would require complex server side logic, using _query (a stored/named query) or some other non-search-url based search mechanism.
Gino Canessa (Mar 17 2022 at 15:40):
If the server supports base searching, the _type parameter, and all the demographics you want to search on are supported, it should be possible via something like http://example.org/fhir?_type=Patient,Person&name=someName....
Your milage will vary on whether a server supports all of those things - make sure to check the returned self link to verify that all of your conditions were met.
Brian Postlethwaite (Mar 17 2022 at 20:58):
With that mother case, you also be interested in the RelatedPerson resource too.
As things have been, not many do Person at all. Doing Patient and RelatedPerson would be more reliable.
And doing a batch search including the 2 (or 3) queries at once can make it a single call (from a rest perspective)
Last updated: Apr 12 2022 at 19:14 UTC
