Searching InterSystems FHIR Server for specific Encounter (based on peroid)

Question

Question

Hi guys,

I am looking for a way to search for FHIR Encounter resources from an InterSystems FHIR server where there period.start is before or after a certain time. I can´t get my head around which would be a correct way to do this since docs and FHIR spec is not clear to me which fields can be used for searching with wich prefixes.

In my local InterSystems FHIR server I have a set of Encounter ressources, each set with a period.start and (possibly) a period.end. I´d like to retrieve all Encounters with a start date time prior to a given datetime. I did a little testing with URL parameters.

// retrieve encounters with a start prior to 2024-10-25T15:30:00Z
http://localhost:54107/csp/healthshare/ukerhirservernew/fhir/r4/Encounte...
http://localhost:54107/csp/healthshare/ukerhirservernew/fhir/r4/Encounte...

But none of the calls returned the correct set of encounters I expected. I´am not sure If I get the whole idea of searching for periods wrong or if it has something to do with the way period (datatype) information are stored and indexed within the InterSystems FHIR server.

Any idea or hint would be hihgly apreciated.

Best regards,
sebastian

Product version: IRIS 2022.1

$ZV: IRIS for Windows (x86-64) 2022.1.4 (Build 812U) Mon Oct 16 2023 10:09:39 EDT

Discussion (7)2

Log in or sign up to continue

score 0 · Answer 1 · 2025-02-27T04:59:04-05:00

Hello @Sebastian Thiele
As per the documentation, date is fully supported search parameter. so, This should work prefix lt dates

I've 2 encounter resource in my FHIR server and I've tested with different dates ex: &date=lt2024-10-27T15:29:00Z period and it works to me

score 0 · Answer 2 · 2025-02-27T07:01:23-05:00

Hi Ashok,

thank you for the response. This url is the exact same syntax that I used above (possibly my links contracted by the UI and therefore not fully visible). Anyway in my case there is no filtering applied at all and simply all encounters are returned regardless of the date. Could you post your encounter resources he used for testing so I can test if it is a FHIR server version specific issue?

best regards,
Sebastian

score 0 · Answer 3 · 2025-02-27T07:29:59-05:00

Hi @Sebastian Thiele

Here is the Encounter resource. I'm using IRIS for Windows (x86-64) 2024.1.1

url : http://localhost:52773/csp/healthshare/learning/fhir/r4/Encounter?&date=lt2024-10-27T15:29:00Z

Spoiler

score 0 · Answer 4 · 2025-02-27T07:37:55-05:00

Sebastian Thiele Feb 27 to Ashok Kumar

Hi Ashok,

seems there is no Encounter resource in your post. Did you missed that?

best regards,
Sebastian

0 0

score 0 · Answer 5 · 2025-02-27T07:58:24-05:00

Ashok Kumar Feb 27 to Sebastian Thiele

Can you click the Spoiler to view the message.

0 0

score 0 · Answer 6 · 2025-03-04T04:39:37-05:00

Hi Ashok,

sorry for the late response. That get me a little further. The approach of ordering by date seem to work only as long as all of the resources have a period.start and period.end provided. In my scenario the most acutal encounter doesn´t have an period.end set since it has not yet ended. The field period.start of one encounter is the the period.end of it´s predecessor. Can you confirm that behaviour of the FHIR server if no period.end is set? If so what would be your approach?

best regards,
sebastian

score 0 · Answer 7 · 2025-03-13T04:38:24-04:00

I think what you are looking for is... (I have not tried this on the InterSystems FHIR server as I use the Microsoft Azure FHIR server)

Search where start date is after a time... /Encounter?date=sa2022-08-15T09:00:00

Search where a start date is before a time /Encounter?date=lt2022-08-15T09:00:00

For me the times I search by are UTC so that might be catching you out?