Stream: implementers
Topic: Find active Encounters for particular patient
Dimitar Dimitrov (Oct 19 2019 at 15:45):
Hi all.
I am trying to use a search query to find all active Encounters for particular patient. I tried to search with the following query /Encounter?status:below=finished, but the FHIR server does not returns anything. My question is what is the right query that will returns all the Encounters with statuses in the range from 'planned' to 'onleave'?Find all active Encounters for particular patient
Lloyd McKenzie (Oct 19 2019 at 16:25):
You may find it works better to enumerate the statuses. Not a lot of servers support the terminology subsumption operations
Lloyd McKenzie (Oct 19 2019 at 16:26):
E.g. status=finished,planned,onleave,...
Michael Lawley (Oct 19 2019 at 22:54):
Not a lot of servers support the terminology subsumption operations
Which is a real shame - it shouldn't be that hard
natus (Oct 20 2019 at 14:03):
Which is a real shame - it shouldn't be that hard
to my knowledge, if the terminology store has been well designed, hierearchycal query results for RDBS as a recursive query or a graph traversal in other tehcnologies. that's not trivial question indeed.
natus (Oct 20 2019 at 14:06):
i'd rather prefer to :
- ask to terminology server for code below or above, mapped and so on
- pass the list to the resource to filter
Or maybe the server should do that step itself under the hood
Michael Lawley (Oct 20 2019 at 21:19):
For simple code:below, just ask an external terminology server (& cache the result) as you say (ignoring issues wrt infinite code systems).
For code:in it can get more complex, but you can still offload to a terminology server (who wants to implement all that SNOMED, LOINC, etc) logic.
But to your first point, if the Tx store is well-designed you should (almost) never be doing recursive / graph traversal queries.
Last updated: Apr 12 2022 at 19:14 UTC
